How to run a rapid strategic diagnostic in two weeks

A two-week strategic diagnostic is not a warm-up to the real work. It is the work, compressed and made precise. Most organisations that commission one already suspect where the problems lie; what they need is a structured method for surfacing the evidence, naming the patterns, and producing a written output that a leadership team can act on without further translation. At Daily Summit Lab, we have run this engagement for manufacturers in the Midwest, regional hospital networks, and mid-size professional services firms, and the structure has stayed remarkably consistent across all of them. What follows is an account of exactly how we do it, including the parts that are less tidy than a methodology slide suggests.

The first three days: access, documents, and a listening protocol ¶

The engagement opens with a document request sent the week before we arrive on site. We ask for the most recent board strategy deck, the last two annual operating plans, any customer or employee survey data collected in the past eighteen months, and the current organisational chart. We are not looking for a comprehensive archive. We are looking for the gap between what the organisation says it intends and what it has actually measured and resourced. That gap is almost always visible by the end of day one.

Interviews begin on day two. We schedule eleven to fourteen conversations over three days, each running fifty minutes. The roster is built deliberately: two or three members of the senior leadership team, four or five people at the middle-management layer who sit closest to operational decisions, and three or four frontline staff or individual contributors whose work is directly shaped by the strategy in question. We use a semi-structured guide with eight anchor questions, but the most useful material consistently comes from the follow-up, not the anchor. When a plant operations director says 'that initiative stalled in Q3,' the diagnostic work is in understanding exactly why it stalled, who owns the explanation, and whether leadership has the same account.

Notes from every interview are written up the same evening and reviewed the following morning before the next round begins. This is not optional. Allowing impressions to accumulate without documentation introduces a confirmation bias that is genuinely hard to correct later in the week.

Days four through eight: pattern analysis across sources ¶

By the end of the interview phase, we have four distinct data layers: the documentary record, the leadership account, the operational account, and the frontline account. The analysis work is essentially a structured comparison of these four layers. Where they converge, there is usually organisational clarity. Where they diverge sharply, there is almost always an underlying structural or cultural condition that the strategy has not addressed.

We use a simple two-axis mapping exercise internally at this stage. One axis tracks the issue by function, the other by whether the root cause appears to be structural (a reporting line, a resource allocation, a process) or interpretive (a shared assumption, a communication failure, a strategic ambiguity that leadership has never resolved). This distinction matters enormously for the recommendations section of the final report. A structural problem can often be addressed with a specific, bounded change. An interpretive problem requires a different kind of intervention, usually a facilitated process, a decision, or an explicit restatement of priorities by the people who hold authority.

We also look hard at what is not in the documents. Missing metrics are as informative as present ones. If a three-year strategy names customer retention as a priority and no one is tracking a retention number, that absence is a finding.

The most instructive gap in any strategy document is the metric that was promised and never defined.

Days nine through twelve: writing the diagnostic report ¶

The written output is a single document, typically between eighteen and twenty-eight pages. It is structured in four parts: a one-page executive summary stating the two or three central findings in plain language; a findings section that presents each issue with the evidence behind it; an analysis section that explains the underlying conditions; and a recommendations section that is explicit about sequencing, ownership, and approximate time horizon.

The findings section is the hardest to write well, because it requires attributing observations to patterns rather than to individuals. We take care here. When an interview reveals that a critical strategic decision was never formally communicated below the VP level, we describe that as a communication architecture gap, not as a failure by a named person. The report will be read by the leadership team, and it needs to be a tool for productive conversation, not a tribunal document.

Recommendations are written in three tiers: actions that can be taken within thirty days and require no additional resources, actions that require a decision by leadership and a modest resource commitment over the following quarter, and longer-horizon structural changes that may require a dedicated workstream. We are specific about what 'specific' means here. Not 'improve cross-functional communication' but 'establish a monthly operations review with a fixed agenda, owned by the COO, with written outputs distributed within forty-eight hours.'

The final two days and what makes the output usable ¶

Day thirteen is a draft review with one or two internal contacts at the client organisation, not to edit the findings but to check for factual errors and to ensure that the language is navigable for the people who will read it. Day fourteen is a readout session with the full leadership team present. We present the findings verbally for approximately forty minutes and then open the room for discussion. The discussion is usually more useful than the presentation.

A diagnostic report earns its keep when it can be picked up six months later and used to evaluate whether the organisation moved on what it identified. That is the standard we write to.

• Request documents one week before the engagement begins, not on day one.
• Interview across three levels: senior leadership, middle management, and frontline contributors.
• Write up interview notes the same evening, before the next round starts.
• Distinguish structural root causes from interpretive ones — the intervention design depends on it.
• Write recommendations in three time horizons with named owners and concrete actions.
• Schedule a draft review with one internal contact before the leadership readout.

A two-week diagnostic is a bounded, repeatable engagement, but it demands real discipline in sequencing and documentation. The value is not in the discovery of surprising facts. It is in the production of a written record that the organisation can test itself against over the months that follow. Daily Summit Lab has run this process across sectors and organisation sizes, and the structure above is what we actually use.