Every consulting firm sells a methodology: steps, frameworks, deliverables, timelines. On paper, they look similar enough that selection committees end up comparing price and team bios. What they can’t compare is the thing that determines whether the engagement produces lasting value: how the client’s team experiences going through the work. The client’s memory of the engagement is shaped more by how week three felt than by what the final deck contained, and the firm that treats experience as secondary to the deliverables is misunderstanding what it sells.
What the Proposal Can’t Show
A selection committee evaluates four things: the methodology framework, the team’s credentials, the case studies, and the price. All four are visible in the proposal. What is not visible is how the engagement will unfold week by week: how the firm handles the session where a VP’s workstream is three weeks behind and the room knows it, or how the firm navigates the conflict between two functional leaders whose priorities require a tradeoff nobody wants to make.
These are experience design decisions, and they determine whether the work actually holds up three months after the team leaves. But no RFP asks for them, and no reference call surfaces them unless you know what to ask.
Why This Matters to You
Evaluating consulting firms for a cross-functional program is a bet on behavior change. The program will require people across functions to work differently: new decision processes and new dependencies to manage. Behavior change comes from experience, the kind where someone commits publicly to a course of action and then has to follow through.
When the VP of Supply Chain sits in a pre-mortem session and names the three most likely failure modes for her workstream, she’s making a commitment in front of her peers. She’s publicly acknowledging risks she’s now responsible for mitigating. That experience changes how she operates after we leave. No deliverable can replicate it.
A firm that designs for this outcome thinks about the engagement differently from a firm that designs for deliverable quality. What actually separates firms is whether your team comes out of the engagement with the confidence and the muscle memory to run the program independently. That’s what stays after you leave.
The Emotional Arc of an Engagement
An engagement has a predictable emotional arc that most firms ignore: two peaks and two valleys, a W-shaped curve where the dips correspond to the hardest conversations the team has to have. The firms that map this arc and design each session to land appropriately are delivering something the deliverables alone can’t convey. The moments that matter happen in those dips.
What This Looks Like in Practice
Designing for experience means making choices that a deliverable-focused firm wouldn’t make. It means using silent writing before verbal discussion so that every voice in the room is captured, and bringing strawman artifacts that give the room structured ways to surface disagreement instead of asking open-ended questions that produce polite silence. It means structuring every exercise so the facilitator brings the scaffolding and the room generates the substance.
These are design decisions, as deliberate as choosing a navigation pattern for an app. The difference is that the interface being designed is a sequence of human interactions across twelve weeks, and the user experience is a room full of senior leaders who need to leave each session feeling like the work is theirs. A nine-step methodology only differentiates when the experience of going through it is designed with the same rigor as the deliverables it produces.
