You Don't Need to Fix Twenty Things. You Need to Fix Three.

Twenty things. Maybe thirty. All real. All valid. All demanding attention.

And the owner is paralysed. Because where do you start when everything needs fixing?

Here's the answer nobody in consulting wants to tell you. You don't fix twenty things. You fix three. And if you pick the right three, half the others start fixing themselves.

Digital transformation is a lie

I'm going to say something that would get me uninvited from most business conferences. Digital transformation, the way it's sold, is a lie. Not because technology doesn't matter. It does. But because the way it gets packaged and sold to regional businesses is backwards.

Some consulting firm walks in, does a discovery phase, and produces a 40-page report with a 20-item roadmap. New CRM. New ERP. New project management tool. Training program. Change management framework. Culture initiative. Data migration. Integration layer. Twelve months. Six figures. Maybe seven.

And the owner, who started this process because things felt hard and they couldn't quite name why, ends up with a plan so big it's paralysing. So they do what most people do with a 20-item roadmap. Items one through three, slowly. Items four through seven, with diminishing enthusiasm. Items eight through twenty, never.

The problem wasn't that they needed transformation. The problem was that they needed precision. They needed to know which three things mattered most. And nobody told them.

The cascade works in reverse

If you've been reading these posts, you know about the cascade. Frictions feed each other. Trapped Knowledge creates Broken Handoffs. Broken Handoffs create Visibility Gaps. One problem compounds into three.

Here's the part that changes everything. The cascade works in both directions.

Fix the keystone friction, the one feeding the most others, and the downstream problems start loosening. Not instantly. Not magically. But measurably. Because when the root cause weakens, the effects it was generating weaken too.

I watched this pattern play out in a regional operation I worked inside. They had a list of problems as long as your arm. But when you traced the cascades, most of them led back to one thing. Critical process knowledge lived in three people's heads and nowhere else. That's it. Trapped Knowledge, feeding everything else.

They didn't do a digital transformation. They didn't buy a new system. They spent six weeks extracting that knowledge into documented, repeatable processes. Simple. Boring. Unglamorous.

Within three months, handoff errors dropped by half. The weekly status meeting went from ninety minutes to thirty. The owner stopped getting calls on weekends. Not because they told people to stop calling. Because the team had what they needed to handle things themselves.

One fix. Multiple downstream improvements. That's how cascades unwind.

The Priority Framework

If you've been doing the diagnostics from the earlier posts, you already have your raw material. The Holiday Test from post 5. The Meeting Audit from post 6. The Handoff Trace from post 7. The Friction Cascade Map from post 8. If you did even two of those, you've got a list.

Now let's turn that list into a plan. Grab your list of frictions and a pen.

Step 1: List every friction you've identified.

Everything. From every diagnostic. Every "that's broken" moment. Every "we've always done it this way" process that makes you wince. Get it all on paper.

Step 2: Score the cost of each one. (1-5)

Not just dollars. Time, energy, opportunity, stress. A friction that costs you $50,000 a year in rework is a 5. A friction that annoys you but doesn't really cost much is a 1. Be honest, not dramatic.

• 1 = Minor annoyance
• 2 = Noticeable drag, low cost
• 3 = Real cost, regular impact
• 4 = Significant cost, affects multiple areas
• 5 = Major cost, constant drain

Step 3: Score the cascade impact of each one. (Count the arrows)

This comes from your Friction Cascade Map. How many other frictions does this one feed? If a friction causes or worsens three others, its cascade score is 3. If it sits on its own and doesn't feed anything else, it's 0.

Step 4: Multiply.

Cost score times cascade score. That's your priority number.

A friction that costs a 4 and feeds 3 others scores 12. A friction that costs a 5 but feeds nothing scores 0. The expensive problem that sits alone is less important than the moderate problem that's creating three others.

This is the part that surprises people. Your most expensive single friction isn't always your highest priority. The one that's breeding other frictions is.

Step 5: Sort. Fix the top three. Ignore the rest. For now.

Sort your list by priority number. The top three are where you start. Everything else goes on the shelf. Not forever. Just until the top three are handled.

Here's an example.

Friction	Cost (1-5)	Cascade (arrows)	Priority
Only one person knows the pricing model	4	3	12
Weekly report takes 6 hours to compile	3	2	6
Owner approves every purchase over $200	3	2	6
Client onboarding is inconsistent	2	1	2
Office printer jams constantly	1	0	0

The pricing model knowledge is the keystone. Fix that first. The report and the approval bottleneck are next. The onboarding and the printer can wait.

Why three, not one

One fix is good. But three gives you enough coverage to break the cascade properly. The keystone friction is your starting point, but it usually has one or two accomplices that reinforce the loop. Fix the keystone and its top two feeders, and you've disrupted the cascade from multiple angles.

Think of it like this. If you're trying to stop a leak in a dam, plugging the biggest crack helps. But if two smaller cracks are feeding water pressure back to the big one, you need to address those too. Three targeted fixes. Not a new dam.

Why this beats a roadmap

A 20-item roadmap gives you paralysis. Three targeted fixes give you momentum.

You can start this week. Not next quarter. Not after the budget cycle. Not after the new system is implemented. This week. Pick the top friction from your list. Figure out the smallest thing you could do to reduce it. Do that.

Momentum matters more than perfection. A business that fixes one keystone friction this month and two more next month is further ahead than a business that's been "planning their transformation" for eighteen months.

The whole toolkit

Over the last nine posts, I've given away every diagnostic tool I use.

Post 2. The real cost of being the most expensive person in the building. Post 3. Why hiring won't fix a systems problem. Post 4. The spreadsheet that's costing you fifty grand. Post 5. The Holiday Test for Trapped Knowledge. Post 6. The Meeting Audit for Visibility Gaps. Post 7. The Handoff Trace for Broken Handoffs. Post 8. The Friction Cascade Map. Post 9. What a Clarity Conversation actually looks like.

And now, the Priority Framework. Cost times cascade impact. Sort. Fix three.

You have everything you need to diagnose your own business. Some of you will do exactly that, and it'll work. Genuinely. I hope it does.

But if you want the full picture

There's a difference between self-diagnosis and having someone who's done this a hundred times sit across from you with fresh eyes. Not because you can't see the problems. You can. But because you're inside the system. And from inside the system, it's hard to see the connections. Hard to see the cascade. Hard to see which friction is the keystone and which one just feels like it is.

That's what the Clarity Conversation is for. One conversation. Six dimensions. A scored friction map. The cascade. And the three things that matter most.

Not twenty. Three.

Found your three? The Priority Framework gets you close. The Clarity Conversation gets you certain. All six dimensions scored, the cascade mapped, and the three that matter most identified. Four hours, $2,000, and you stop guessing.