I have watched this movie so many times I know every line.
It plays in conference rooms and on camera grids with equal commitment. The cast changes. The script does not. And based on hundreds of client engagements across more industries than I care to list – representing multiple employers and clients across 33 years of consulting work – I can tell you exactly how it ends.
Pull up a chair. You have seen this one too. You just might not have realized you were in it.
Scene one. The introduction.
It is week two or three. The executive overview went well. The salesperson – let us call him Confident Kevin- earned access and is feeling excellent about the whole situation. The evaluation begins. The consultant joins the call.
Kevin announces that he is going to introduce everyone.
Eight minutes later- after a detour through last quarter’s pipeline, a comment about the weather in whoever’s city, and a brief personal anecdote that nobody asked for- Kevin remembers he was going to introduce everyone.
He gets to you.
“And this is- she knows the tech side of things so she’s going to ask a few questions so we know what to propose.”
You smile because your camera is on and you are a professional. You make a mental note. The client nods politely and files you under “vendor support staff” before Kevin has finished the sentence.
Kevin moves on, still feeling excellent.
The client has already started deciding.
The introduction is the first tell. Everything after it is confirmation. And Kevin just handed the client a greasy bag somewhere around minute nine.
What Kevin does not understand about introductions.
The correct order is not complicated. Kevin introduces himself- name, role, why he is running this meeting. Then he yields to the client’s team to introduce themselves, in order of position hierarchy. Then Kevin’s team introduces themselves the same way. Self-introductions, around the room or by position hierarchy.
Not Kevin incorrectly narrating everyone’s biography from memory. Not Kevin describing the consultant’s role based on his interpretation of it. Everyone introduces themselves because everyone knows their own role better than Kevin does.
And here is the thirty second rule that Kevin has never been taught. If you announce that you are going to introduce the team- do it. Within thirty seconds. Do not tell the client “let me introduce everyone” and then take a ten-minute scenic route through your own thoughts before arriving at the actual introductions. Say it. Do it. Move on.
The introduction is not administrative. It is as important as a well-framed agenda. Every introduction tells the client how well Kevin knows his own team, how much he respects the people he brought into the room, and whether he can be trusted to accurately represent someone else’s interests.
Getting it right is three sentences per person. Role. Relevant experience. What they will contribute today. That is the whole assignment. The lift is genuinely minimal.
The interesting question is why the lift feels so heavy for Kevin.
What the consultant actually does. Since we are here.
The consultant is not the question lady.
Across thousands of engagements, I have never once been in a discovery conversation where the most important thing I did was ask the questions on my list. The questions are the vehicle. Reading the room is the work.
Who defers to whom. Who goes quiet when the budget comes up. Who is the actual decision maker nobody introduced as the actual decision maker. What the organization says it needs versus what its culture will actually allow it to absorb.
A gap analysis rooted in organizational development is not a questionnaire. It is a clinical assessment of an organization’s genuine capacity and propensity to change. That assessment requires pattern recognition built across years of real rooms with real organizations that did not behave the way the textbook said they would.
AI can generate questions to add texture to the consultant’s framework- and used that way it is genuinely useful. But when Kevin decides the AI generated questions are the discovery process, he arrives at the final presentation with very impressive questions and no idea what the answers actually meant. Very greasy bag forward. No way to make a tasty meal from it. And the beef wellington he was expecting to serve at the final presentation? We will get to that.
The framework belongs to the consultant. AI is a tool inside it. Not a replacement for it.
The slides. Kevin’s voice is the star.
One point. One value. One thing the client needs to understand before you move forward.
Slides are a visual. They are there to accentuate what Kevin is saying – not to replace him, not to serve as a leave-behind, not to contain everything Kevin knows about the topic in case he forgets. Kevin’s voice is the star of the presentation. How easily he can tie function to value, how confidently he connects the solution to what the client said they needed in week two- that is what closes the room.
The detail belongs in an AI-generated PDF sent after the meeting. Let the client focus on Kevin during it. Give them the documentation after. When the client is reading the slide they are not listening to Kevin. And Kevin is the whole point.
I have reviewed RFP responses with fewer words per page than some of the slides Kevin has brought to final presentations. By slide four the client has stopped listening and started reading. By slide six they have formed a quiet opinion about whether a team that cannot get to the point on a slide can handle the complexity of their actual engagement.
One point. One value. Kevin fills in the rest with his voice. That is the job.
The SME situation. A greasy bag and an empty kitchen.
This scene plays with remarkable consistency across industries and organizations I have worked with and for.
Kevin brings in a subject matter expert for the final presentation. Smart person. Deep expertise. Genuinely excellent in their lane. Kevin gives them a ten-minute speaking slot and whatever information made it into the briefing.
The SME steps up. They know their business cold. What they do not know is this specific client, what the consultant found in discovery, or how their expertise connects to what is sitting across the table from them.
They fumble. Not because they are not brilliant. Because they were handed a greasy bag and pointed at an empty kitchen. The ingredients were never there.
An SME who is properly briefed- who knows what the consultant found, who understands this specific client’s gaps, who can connect their deep expertise to this organization’s particular situation – is a closing argument. They are the living proof that what Kevin is proposing actually works.
Give them the ingredients. Brief them fully. Connect the dots. Then get out of the way and let them cook.
The beef wellington is in there. Kevin just has to stop handing people empty bags and expecting magic.
The framework. The thing that works when Kevin lets it.
Discovery informs synthesis. Synthesis informs recommendation. Recommendation informs presentation.
When the framework is honored, the final presentation feels inevitable. The client hears the recommendation and thinks- yes, that is exactly what we said we needed. Because it is. Because someone was listening closely enough in week two to build the whole thing from what they said.
When the framework is bypassed- when discovery is reduced to a prompt, when the consultant is sidelined, when the SME gets the greasy bag and is pointed at a camera- you arrive at the final meeting with a polished presentation that does not quite hold together.
The client feels the seams. They disengage. They are gracious about it.
And then the follow-up call goes to voicemail.
The short version. For Kevin.
Introduce yourself first. Then yield to the client’s team to introduce themselves by position hierarchy. Then let your team introduce themselves the same way. Always. If you announce it, execute it within thirty seconds.
Let the team introduce themselves. Every time. They know their roles better than you do.
One point per slide. One value per slide. Detail goes in an AI-generated PDF after the meeting. Let the client focus on you during it.
Brief your SMEs fully. Connect their expertise to this specific client’s situation. Give them the ingredients. Beef wellington requires an actual kitchen.
Honor the full process. Discovery informs everything that comes after it. Do not shortcut week two and then wonder why week seven did not close.
The client always knows.
They knew when the introduction wandered off for eight minutes before arriving at the names. They knew when the consultant was described as the question lady. They knew when the slide required more reading than listening. They knew when the SME was brilliant in their lane but had clearly never heard their organization’s name before this meeting.
They were gracious. They are professionals.
And then the follow-up call went to voicemail.
The movie always ends the same way when it is run the same way.
The good news is the script can be rewritten. It just requires someone deciding that the people they bring into the room are worth introducing correctly, briefing properly, and trusting completely.
That someone is you, Kevin.
We are rooting for you.
Consultants – has this been your experience? Sales leaders – what would you add? Drop it in the comments.
