Product teams have spent two decades tracing user journeys and removing unnecessary effort at every touchpoint. We rarely apply the same discipline to the experience our clients have during an engagement, even though every touchpoint between the consulting team and the client organization is a design decision. When the client’s experience is the product, friction mapping becomes essential.
Engagement Friction Becomes Visible Through Deliberate Mapping
The friction in a consulting engagement is different from product friction because the people experiencing it rarely name it. A VP who spends four hours prepping for a readout doesn’t file a complaint; they resent the engagement a little more. A workstream lead who receives a sixty-page governance framework and is asked to “review and provide feedback by Friday” skims it, provides surface-level comments, and disengages from the content. These are friction points: moments where the engagement creates unnecessary work for the client and erodes the sense that the process is designed for them. These are the moments that matter: the ones that shape whether the client trusts the process or endures it.
They accumulate quietly. Mapping engagement friction requires the same discipline as mapping product friction: you trace the client’s journey through the engagement to find every point where they encounter effort that doesn’t produce value, then redesign those moments.
Friction Clusters Around Preparation, Context, Governance, and Handoffs
The most common friction points cluster around four areas:
- Readout preparation. Every hour the client spends prepping for the engagement is an hour away from operational responsibilities. A two-page brief that lands forty-eight hours before the session produces a better-prepared room than a forty-page deck that lands the night before.
- Exercise design that assumes context the room doesn’t have. When a facilitated session opens with a question like “what are the key dependencies between your workstreams?” and half the room has never seen the other workstreams’ scope documents, the exercise produces thin output. The room is being asked to perform at a level the setup didn’t support. This is why intake changes everything: the document audit and interviews in Step 1 build the shared context that later sessions depend on.
- Governance that creates work without enabling decisions. A biweekly integration review that produces a status deck but never surfaces a decision is a friction point. People prepare for it and nothing happens as a result.
- Handoff processes that transfer artifacts without building capability. When the engagement ends with a SharePoint folder full of templates and a final readout deck, the client receives the output but not the ability to use it. The friction surfaces three weeks later when the program team opens a template and can’t understand the logic behind the design choices embedded in it.
Deliverable Quality and Client Experience Require Separate Attention
We tend to optimize for deliverable quality (i.e., the output) rather than the experience of the person consuming it. A deliverable can be analytically rigorous and strategically sound while creating friction for the person who has to use it. The sixty-page governance framework might be thorough, but thoroughness is not the same as usability; the question we should ask is what it’s actually like for the client’s team to receive that artifact, figure out what it means, and do something with it.
Friction mapping requires us to acknowledge that our process can create unnecessary effort for the client. The client’s experience is the product, and our methodology should adapt to minimize that effort. The same principle applies to how stakeholder mapping goes beyond the org chart: the one-on-one interviews are designed to reduce friction for the people being mapped, not to collect data efficiently.
Mapping Friction Produces Compounding Improvements
When we map the friction in our own engagement model, the changes are often small but compounding. Readout decks get shorter because we ask what the room needs to make the decision at hand. Pre-reads get replaced with in-session context-setting because we acknowledge that pre-reads rarely get read. Governance frameworks get built in sessions with the client rather than delivered for review.
Each change reduces the effort the client expends without reducing the quality of the output; in most cases, output quality improves because the client’s participation improves. A room that received a concise brief and was given context at the start of the session produces better input than a room that skimmed a long document the night before. Over time, the engagement feels lighter to the client without being less rigorous. The work is the same, but the experience of going through it is different, and because experience drives ownership, the lighter engagement produces better adoption after the consulting team leaves.
