TL;DR: Trying to fix every broken process at once is why nothing gets fixed. List the workflows you touch every week, rank them by pain instead of importance, and commit to just one for two weeks. Skip the scoring matrices and consulting frameworks. They’re built for teams with a room full of people and a meeting to spare, not a 1 to 5 person shop trying to stop the bleeding.

---

Picture six half-built systems open in six browser tabs. A weekend spent wiring up an invoice database, an onboarding checklist, a project handoff flow. Monday morning, a client asks for an invoice, and the old spreadsheet gets used anyway because the new system needs three other systems finished first to actually work.

That’s what happens when you try to fix everything at once. You don’t end up systemized. You end up with more open loops than you started with, and the one thing that was actually costing you money is still broken. If you’re staring at a list of ten broken workflows and can’t figure out which business process to fix first, the answer isn’t a bigger framework. It’s a shorter list and a clearer question.

How Do You Know Which Business Process to Fix First?

Fix the workflow causing the most pain right now, not the one that seems most important on paper. List everything you touch weekly, rank it by time lost, mistakes made, or money left on the table, then pick exactly one. Ignore the rest until that one is running without your attention.

This sounds too simple to be a real answer, and that reaction is worth noticing. Most advice on process improvement pushes toward scoring systems: value versus effort, impact versus readiness, a grid with four quadrants and a facilitator walking a team through it. That works when you have a team and a facilitator. When you’re a solo operator or a five-person shop, the scoring session costs more time than the fix does.

Why “Most Important” Is the Wrong Question

Importance is a guess. Pain is a fact you can point to.

When you ask “which process is most important,” you’re answering from theory. Onboarding feels important because everyone says onboarding is important. Reporting feels important because a client mentioned it once. None of that tells you where your actual hours are going.

Ask a different question instead: which process do you dread the most? Which one made you apologize to a client last month? Which one are you quietly doing wrong every single time and hoping nobody notices? That’s the workflow to fix, whether or not it sounds strategic. You’re the bottleneck in most small businesses precisely because the workflows that hurt the most rarely look impressive enough to prioritize on a spreadsheet.

What Fixing Five Things at Once Actually Costs You

Working on multiple broken systems at the same time doesn’t split your attention evenly. It burns extra time on every switch between them. Research on context switching found it takes an average of 23 minutes to fully regain focus after an interruption, and that cost compounds every time you jump from the invoice system to the onboarding doc to the reporting spreadsheet.

Multiply that across a week of bouncing between five half-finished fixes and you’re not moving five things forward. You’re paying a tax on all five and finishing none of them. Frequent task switching has been shown to eat up to 40% of a person’s productive time, which is close to two full workdays a week disappearing into the gaps between tasks rather than the tasks themselves.

This is the same trap covered in why fixing everything at once guarantees you fix nothing: the intake forms, spreadsheets, and webhooks all looked fixable in parallel, and the parallel approach is exactly what let leads slip through the cracks.

Do You Need an Impact/Effort Matrix to Prioritize Fixes?

No, not for a team this size. An impact/effort matrix plots initiatives on two axes and sorts them into quadrants like “quick wins” and “major projects,” which works well when a team needs a shared visual to align on. For one person or a handful of people, it adds a step that doesn’t change the outcome.

You already know which workflow hurts. The matrix exists to build consensus among people who don’t agree yet. If you’re the only one making the call, or the whole team already feels the same pain point, the scoring exercise is overhead, not clarity. Even a stripped-down version, like sorting problems into high impact, low effort buckets, still asks you to score every candidate before picking one. A ranked list of what actually hurts gets you to the same decision faster.

The same pattern shows up in most process-improvement advice: before you can prioritize anything, you’re told to map and define every process in the business first. That’s useful once you’re systemizing at scale. It’s a detour when you already know exactly which workflow is the problem.

How to Rank Your Workflows by Pain, Not Theory

Start with a plain list. Write down every workflow you touch more than once a month: invoicing, onboarding, delivery, follow-up, reporting, whatever repeats. Not every task. Just the patterns that eat your week.

Now rank them, but skip the scoring columns. Ask which one costs you the most in four ways: time wasted, money lost, mistakes made, or reputation damaged. You don’t need exact numbers. A gut answer, backed by a recent memory of the thing going wrong, is enough.

An issue log makes this ranking almost automatic if you’ve been keeping one. The workflow with the most entries, or the ugliest entries, is your answer. If you haven’t started one yet, that’s fine. A week of noticing which process makes you sigh out loud will tell you the same thing.

Pick exactly one from that list. Not the top two. One. Everything else waits, no matter how tempting it feels to knock out a “quick” second fix at the same time.

How Long Should You Work on One Fix Before Moving to the Next?

Give the fix two weeks of real use before deciding whether it’s working. Use it, let it break in small ways, patch what breaks, then decide if it’s stable enough to leave alone.

Two weeks is long enough to hit the edge cases a first pass always misses, and short enough that you’re not stuck in analysis mode. Once the workflow runs without you thinking about it daily, that’s your signal. Set a weekly review checkpoint to confirm it’s holding, then move to the next item on your ranked list.

This is the exact approach covered in Chapter 2 of The Self-Managing Business, where a founder with six half-built systems was told to scrap the elaborate setup and fix just the invoicing process for two weeks. Nothing else got touched until that one thing stopped being a daily headache. If your list of broken workflows feels overwhelming, that same one-thing, two-week approach is worth reading in full before you try to systemize anything else.

Owners who spend most of their week reacting instead of building rarely have room to fix five things properly anyway. Research from The Alternative Board found the average entrepreneur spends 68.1% of their time working in the business, putting out fires, and only 31.9% working on it. That split gets worse, not better, when your attention is scattered across a pile of half-finished fixes instead of narrowed to one.

If your business still doesn’t feel systemized after picking one thing at a time, it might just mean you haven’t found the real minimum for a small team yet. That minimum is smaller than most advice makes it sound.

---

Fixing your business doesn’t start with a framework. It starts with a short list, an honest ranking by pain, and the discipline to work on exactly one thing for two weeks before touching anything else. Every workflow you’re not fixing right now can wait. It’s waited this long already.

If you’ve made the list and you’re still not sure which one to trust yourself with, or you’d rather have someone map it with you, working with TAW starts with exactly this question before anything else gets touched.

Frequently Asked Questions