How to run a business diagnosis in 4 weeks

Most companies that feel stuck don't need a strategy consultant. They need someone to look at how the business actually works — and be honest about what they find. A proper diagnosis doesn't require months of work or an army of analysts. With the right structure, four focused weeks are enough to get a clear picture of what's broken, what's working, and what to fix first.

Here's the framework we use — built around four weeks with intentional breathing room between phases.

Week 1: Look at the data

Before talking to anyone, look at the numbers. What metrics does the company currently track? Where do they live — in a CRM, a spreadsheet, five different dashboards? Who actually looks at them, and how often?

The goal here isn't to build new reports. It's to understand what information exists, what's missing, and what decisions it's currently driving — or not driving. In most companies, this week alone surfaces two or three surprises.

At the end of Week 1, you should know: what the business measures, what it ignores, and where the data is unreliable.

Week 2: Map the processes

Now talk to the people doing the work. Walk through the core workflows: how does a lead become a client? How does a client request get handled? How does a new hire get onboarded?

The key rule: document what actually happens, not what the process document says should happen. These are almost always different. Ask each person the same questions — where do things slow down? What do you not have visibility on? What decision do you have to escalate that you wish you could make yourself?

By the end of Week 2, you have a map of how work actually flows through the company — and where it breaks.

Week 3: Identify the gaps

This is the synthesis week. Take everything from weeks 1 and 2 and look for patterns. Where is ownership unclear? Where are handoffs breaking down? Where is data missing or misleading? Where are the same problems recurring?

List everything — don't filter yet. Then apply two criteria: impact (how much does fixing this change outcomes?) and effort (how hard is it to fix?). High impact, lower effort items go to the top. Everything else gets deprioritized or parked.

The breathing room between weeks 2 and 3 matters. Letting the observations settle before drawing conclusions leads to sharper priorities.

Week 4: Write the output

A good diagnosis output is short — two to three pages maximum. It covers what you found, what the priorities are, and what the next steps look like. It's not a presentation deck. It's a working document that drives the next phase.

The output answers three questions: what is actually happening, why it matters, and what to do about it — in that order.

A note on objectivity

The hardest part of any diagnosis is staying honest. It's easy to find what you were already looking for, or to avoid conclusions that implicate decisions you made. That's why an outside perspective — even a brief one — is often more valuable than months of internal analysis. Not because the external person is smarter, but because they have nothing to protect.