Most digital transformation diagnostics produce a report and a Tuesday morning where nothing happens. They generate findings nobody acts on. McKinsey research found that companies use only 29 percent of the KPIs they define and track in actual decision-making (McKinsey, 2023). The diagnostic is fine. The translation to decisions is broken.
Here's how we structure a diagnostic so the output is a decision, not a binder.
What a diagnostic should actually produce
Three things, in this order.
- A clear statement of where your organization stands relative to its peers, on dimensions that matter for transformation.
- A short list of opportunities ranked by realistic impact and cost, with the trade-offs visible.
- One concrete recommended starting point that the next decision-maker can act on without another six weeks of analysis.
If your diagnostic doesn't end with all three, it didn't do its job.
The six axes we use
There's no industry-standard set of dimensions for digital maturity, which is why every consulting firm uses a different framework. Ours has six axes because that's what we've found correlates with whether a transformation actually ships in Atlantic Canadian organizations of 10 to 500 people.
- Strategy. Clarity of vision, measurable goals, executive alignment.
- Data. Quality, accessibility, ownership, single sources of truth.
- Technology. Stack maturity, integration health, technical debt.
- Ways of working. Process documentation, decision rights, agility.
- Talent. Digital literacy, capacity to absorb change, leadership pipeline.
- Customer. Feedback loops, voice-of-customer rigour, segmentation.
Each axis gets a 1-to-5 score with written justification. The scores aren't the point. The justifications are.
Industry benchmarking that means something
Most maturity reports show your scores against a generic 'industry average.' That's not useful, because the relevant comparison is your size band, your sector, and your region, not all companies named 'healthcare' globally.
We benchmark against companies of similar size in similar sectors operating in Canada. For Atlantic Canadian organizations, we add a regional cohort comparison too. The percentile context is what makes a 3 out of 5 score meaningful or not.
For example: a 3 in technology maturity for a 50-person Halifax nonprofit is roughly the 60th percentile of comparable organizations. The same 3 for a 200-person manufacturer in Saint John is roughly the 40th percentile. Same number, different conclusions, different priorities.
The output: 12 pages, written, charts not slides
Slide decks compress. They force you to oversimplify and they age badly. A six-month-old slide deck makes you miss the reasoning. A six-month-old written report still tells you why you decided what you decided.
Ours runs about 12 pages. Radar charts on the six axes. A short narrative for each, with the evidence. The opportunity list with effort and impact estimates. The recommended starting point with three to five next steps.
Every claim has a source. Internal claims point to interviews or data we collected. External claims point to industry research with the URL.
We also include the things we couldn't determine. A diagnostic that names three blind spots is more useful than one that pretends everything is observable.
The 90-minute readout determines whether the diagnostic worked
The deliverable is the report. The test of whether the diagnostic actually helped is the readout meeting.
Ninety minutes. Your CEO, your senior team, anyone you want in the room. We walk through the findings, the prioritization, and the recommended starting point. Half the time is your team asking questions and pushing back.
If the readout produces a decision (we're starting here, we're doing this in Q2, we're not doing the other thing), the diagnostic worked. If it produces 'thanks, we'll discuss internally,' something failed in the diagnostic itself. Usually it failed because we didn't push hard enough on prioritization, or the trade-offs weren't visible enough.
We rerun the analysis if the readout exposes a gap. That's part of the engagement, not an extra.
How long it takes
The scope drives this more than the calendar. Most diagnostics for Atlantic Canadian SMBs run two to four weeks of part-time effort. Some are a single intensive week. Some stretch to six weeks if there are multiple stakeholder groups or weak data.
What takes the time: stakeholder interviews (six to twelve typically), document and data review, synthesis, drafting, internal review, and the readout meeting. The actual writing is maybe 30 percent of the calendar time.
What we don't do: prolonged discovery for the sake of looking thorough. If we have enough to make recommendations after two weeks, we recommend. Spending an extra month polishing the report doesn't add value. It just postpones the decision.
Where this sits in the pipeline
The Diagnostic Mirror is Stage 1 of our nine-stage methodology. It's the most common entry point for clients because most transformation work goes wrong at the foundation, not in execution. Once the diagnostic produces a clear starting point, you typically move into one of three next stages: Customer Discovery (Stage 2) if the recommendation involves a market-facing change, Strategy & Vision (Stage 3) if it involves a multi-year direction, or Roadmap & Prioritization (Stage 4) if you already have direction and need sequencing.
Sometimes the right next step is not us. Sometimes the diagnostic surfaces a problem that's better solved by an internal hire or a different specialist. We tell you when that's the case. Refusing engagements that don't fit is one of the few real ways to be useful as a consultant.
If you're trying to figure out where to start with a digital transformation, the diagnostic is usually the right first move. A free 30-minute call is the way to scope one, or to find out whether you need one at all.