The Friction Map. Where Is Your System Actually Breaking?
Framework 01 of the Design Intelligence system.
Every system has friction. Most organizations do not know where it lives until users stop showing up. The Friction Map is the discipline of finding it before it compounds — and before the cost of correction has multiplied beyond what a brief can fix.
Before the Framework
Before we look at a product, before we open a research file, before we draw anything, I ask one question.
Where does your system lose people before they ever reach the value you built for them?
Most clients have not answered it. Not because it is complicated — because no one has asked. The standard design brief begins at the interface. It assumes the problem is visible, the user is present, and the gap between intent and reality is a matter of polish or prioritization. It treats friction as a UX problem rather than a systems problem.
What I have found, across a decade of product work at organizations like KOKO Networks, Safaricom, and Ajua, is that the friction which determines whether a product succeeds or fails is almost never where the brief says it is. It is embedded earlier, deeper, and in places that standard research instruments do not reach.
By the time a product is in market and the drop-off data is visible, the friction has already done its work. The cost of correction has multiplied. The window for early-stage adjustment has closed.
The Friction Map is what we use to find friction before that window closes.
Every product has friction. The question is whether you find it before your users do, or after.
What the Friction Map Is
The Friction Map is the first framework in the Design Intelligence system. It is a structured diagnostic that identifies where resistance is structurally embedded in a product, organization, or user journey — before that resistance becomes a retention problem, an adoption failure, or an organizational crisis.
It does not begin with the product. It begins with the user's world. What does the journey to the product look like before the product appears? What decisions precede the first interaction? What alternatives are already in use, formal or informal, and what trust has accumulated around them that a new product must displace or earn? What would have to fail for a user to abandon this product — and how likely is that failure given the conditions they navigate daily?
The output of a Friction Map is not a list of UX problems. It is a ranked picture of where the system is genuinely broken, where intervention will produce the greatest return, and where the team has been solving for symptoms rather than causes.
The Friction Map does not ask where users drop off. It asks what was already true about the user that made dropping off inevitable.
The Five Friction Types
The Friction Map organizes resistance into five types. Each type has a diagnostic question — not a metric to track, but a line of inquiry to pursue. In African markets, each type surfaces differently than imported frameworks anticipate.
01. Entry Friction
Why are people not arriving?
Entry friction is the resistance that prevents users from reaching the product at all — or that reduces the quality of the user who arrives. It includes awareness barriers, but more importantly it includes the behavioral and cultural conditions that determine whether a user would seek this product in the first place. In African markets, entry friction is frequently trust-based rather than awareness-based. Users know the product exists. They are waiting for a signal from their community before engaging with it.
02. Cognitive Friction
Why are people getting lost?
Cognitive friction is where complexity exceeds user capacity — not because users lack intelligence, but because the product's model of how it works does not match the user's existing mental model. In markets where digital product familiarity varies significantly by context, cognitive friction is almost always higher than the brief assumes. Feature richness signals complexity and risk rather than value. Restraint is a trust signal that most products are unwilling to exercise.
03. Trust Friction
Why are people hesitating?
Trust friction is where the system asks for more than it has earned. In African markets, trust operates through different mechanisms than the ones most products are designed around. Institutional trust — trust in a brand, a platform, a certification — is a weaker currency than community trust. A five-star rating from a stranger carries less weight than a single referral from a trusted peer. Products that require a trust deposit before delivering demonstrable value encounter trust friction that no interface improvement will resolve. The intervention is structural, not cosmetic.
04. Infrastructure Friction
Why is the environment breaking the intended flow?
Infrastructure friction is where the conditions of the user's environment prevent the product from functioning as designed. Intermittent connectivity, constrained devices, shared phones, cash-dominant transactions, and unreliable data access are not edge cases to design around. They are primary conditions to design from. At Safaricom, correctly diagnosing infrastructure friction in digital verification flows — rather than assuming it away — was what allowed us to reduce customer support tickets by approximately 40%. The friction was always there. It had simply not been named.
05. Exit Friction
Why are people not coming back?
Exit friction is the resistance that prevents recovery — what makes leaving feel final, or returning feel costly. In high-trust-cost markets, a single failed interaction can close the window on an entire user relationship. The user did not abandon the product because they found something better. They abandoned it because the cost of trusting again, after the product failed to deliver on its implicit promise, was higher than the perceived value of returning. Exit friction is the most expensive friction type, because by the time it appears in the data, it has already been paid.
Running a Friction Map
A Friction Map is not a workshop. It is a structured inquiry that combines behavioral observation, stakeholder mapping, infrastructure testing, and contextual research to produce a ranked picture of where resistance lives in a system.
It begins before the product. We examine what the user's world looks like before they encounter the product — what decisions they make, what trust relationships they navigate, what alternatives they rely on, and what conditions determine whether they are reachable at all. This is the work that most design processes skip. It is also the work that most reliably prevents expensive mistakes.
At Suluhu, a Friction Map session is a standalone two to three week engagement. It consistently reveals the single highest-leverage intervention point. And it almost always surfaces a larger question that the organization had not been asking — about whether they are solving the right problem, in the right sequence, for the right user.
The Friction Map does not just show where to intervene. It shows what class of intervention the problem actually requires — and sometimes, that the problem is not what the brief said it was.
The Dispatch
Most organizations discover friction the expensive way — through retention data that arrives months after the window for early correction has closed, through a launch that underperforms for reasons the post-mortem cannot fully explain, through a product that works technically and fails behaviorally.
The Friction Map is the alternative. It is the discipline of looking for resistance before committing to a direction — not as a precaution, but as a competitive advantage.
The next issue introduces the Signal Stack — the second framework in the Design Intelligence system — and the discipline of separating decision-worthy evidence from comfortable belief in markets where data is sparse and assumptions travel fast.
Before your next build, before your next brief, before you touch a single frame: where does your system lose people before they ever reach the value you built for them? If you cannot answer that question with specificity, the Friction Map is where the work begins.
Want us to run a Friction Map on your product or system? Reach out directly to Rey Mungai or Suluhu Studio to start the conversation.
By Rey Mungai
Design Intelligence Dispatch · Suluhu Studio · Issue 005