Communicating through the RFP Process - what I want Consultants and Businesses to Know
This presentation is based on a business case study I am currently involved in, the RFP process for creating a SharePoint 2013 version of our compliance system and migrating the SharePoint 2010 data into it.
From beginning in 1964, gas stations & continued entrepreneurial growth
We do – process of guys going out into the field, etc.We use – many forms, regulatory agencies etc.
Giving examples specific to TECSWorkflow of Testing documents – discovered needed loop at end of the workflowCertifications – communication between forms and the server
Read the documentation provided to you. If you’re not going to set the time aside to, schedule time with someone to go over it with you – making yourself accountable to do it. It’s okay to charge time for this. It would have saved days of interviews & asking redundant questions. Learn first so you can dig deeper when you do arrive, and so you aren’t starting at the beginning. It’ll give you questions to arrive with.
Ask: Get expectations about the meeting from attendees prior to holding the meetings. Ex:Going over the RFP. Tim – over my head, Matt – don’t care only want to see the final results, Scott/Jim – just pick and tell me, I trust you. Figure that stuff out first, then you know who really should be attneding.
Define and explain who needs what. They don’t know and probably can’t tell you. Ex: Tim – high level overview (fluff), Matt – Forms to PDF final output and mirroring calendar, has to see it to believe it, Mel – technical details to have faith the consultant can do the work (dev & process)
Don’t make a promise you aren’t going to deliver on. Take notes on what you say you’ll do. Get that verbal discussion down in writing, because what you said to “sell” them, even if it’s not in the proposal may well be what the business remembers and that may be what sets their expectations.
Give them 2nd chances, opportunities, do-overs. Understand that clients are different and they may have to adjust. Withhold judgment as long as possible – be patient. Drive the project. Be the PM if you have to.
Create documentation as a deliverable, a product – presentation matters. Cater to your audience. I expect proper English writing such as consistency in bulleted lists (either all notes and no periods, or all full sentences).
Fully describe your expectations. So much is said verbally in sales conversations, you can’t expect them to remember it all. If it’s something you expect, you’d better write it down and send it to them, too. Working with a team of people, information may be lost / miscommunicated / misconstrued or not even given to the other team members. Sometimes the person you are expecting the action/deliverable/work from may not have heard what it is that you need – send info to the whole team because they may not. Document everything. Follow up email: Per our conversation today…Put all of your expectations in writing. Get expectations in writing from other decision makers. Filter data to them at the level they want. Ex: Tim – bullet points, low cost. Matt – visual solution, needs to be comfortable that we have control to create or alter or consultants can do it quickly = cheaply, Melanie – keep all the rest, the detailed info, the technical solution
Your goal is to make money and to get more work, because that makes more money. You need to keep the client happy. How do you do that? Fix their problems. Create solutions for them. Look for opportunities to bring additional value. Become their Trusted Advisor. Know and address their goals.You meet or exceed their expectations. It sounds so simple, but it doesn’t always work out that way. Communicating expectations is so important.
The goal is getting a good solution. That means solving a business problem within your means ($$). Make sure you understand and put the focus on specific internal goals of all of the decision makers. Ex: Tim – need it to work without complaints, that’s not asking much. Matt – wants it to be Adobe LiveCycle or at least almost the same, and for it to mirror Exchange Public Calendars. Jim – wants access for external users, to use it to grow our service business. Melanie – wants UX for adoption, to expand capabilities to grow the company, to leverage expertise and garner more business by automating tasks and saving time spent on multiple systems, connecting disparate parts of the company – local and satellite, TES & TAIT to share expertise
The consultants want to make money. Saving their time = making more money. More money for them, more work for you for the money you have given them, everybody wins. How can you do that? Share as much information as possible, but only information that is helpful to them. Be available and help as much as possible. Watch for and try to determine the break-even point where you are helping and where you can start to slow them down. Helping is awesome, but not if they can’t be as efficient. Ex: if you give them too much to read that’s not necessarily related, if you want to talk too much, etc.
Figure out who the decision makers are, and who INFLUENCES them – those are the real decision makers, the drivers of the decision. Respect the gatekeeper and the Point of Contact though, you’re still working with them
Customize your paperwork! Flatter your clients – show them you know them, that you understand the business problem you want to solve. It’s lip service on paper.
The world is more techy now. People know about templates. Find that happy medium between giving the client deliverables that are totally generic, and between regurgitating everything they’ve told you about the company
It’s a Relationship, so Communication is Key
CLARIFY, CLARIFY, CLARIFY So what I’m hearing you say is…Practice in my personal lifeTeach to couples at MergeIncorporate these techniques in the workplaceWhat I’ve learnedI am assuming what I hear is final, it could just be brainstormingNot every project/job needs to be completed above and beyond, exceeding expectationsNeed to make sure I’m asking for enough details for meMake sure I’ve heard the full messageStop to ask if there is more than one way to interpret the message, then clarify “your place” example