When a Diagnostic Session is the right fit

This format is strongest when the situation is real, but the structure underneath it is still too unclear to act on confidently.

Typical signals

  • The issue feels important, but still fuzzy or mixed.
  • Several problems may be overlapping, and it is unclear which one matters most.
  • A request exists, but the real constraint is not yet named.
  • The team is moving, but authority, review, or ownership feels unstable.
  • You need a sharper read before deciding whether more work is necessary.

Good use cases

  • AI is already being used, but boundary and review are unclear.
  • A workflow works locally, but feels too fragile to scale cleanly.
  • A service or offer exists, but the actual structure is still vague.
  • Important decisions are happening, but not being held in usable form.
  • One live issue keeps returning, but never becomes clear enough to resolve.

What happens in a Diagnostic Session

The session is less about instant resolution and more about producing a cleaner reading of the issue and a more workable next step.

01

Frame the live issue

Start with what is happening now, where the friction appears, and what feels unstable, overloaded, or difficult to carry.
02

Separate the mixed layers

Distinguish the visible problem from the underlying structure problem: decision, boundary, ownership, review, sequencing, or coordination.
03

Identify the real constraint

Clarify what actually matters most: timing, legal limits, capacity, governance, information structure, or human-AI operating fit.
04

Define the next move

End with the smallest useful next step: a note, memo, issue map, sprint, revised scope, or a decision not to do more yet.

What you may leave with

A clearer diagnosis

A better distinction between the visible issue and the structural issue underneath it.

A named weak point

Clearer language for the boundary, bottleneck, ownership gap, review failure, or decision problem that is actually driving the friction.

A next-step design

A smaller, more concrete next move that fits the real situation instead of a generic or oversized response.

A first-pass artifact

In some cases, a short issue map, boundary note, memo direction, or working outline for what should happen next.

A decision about fit

Clarity on whether the issue is solved well enough here, or whether a sprint or stewardship rhythm would actually be useful.

A cleaner human-AI read

When relevant, a sharper distinction between what AI can support, what must remain human judgment, and what needs review or escalation.

What to share first

A polished brief is not required. A short summary is enough. The most useful starting point is usually a compact description of the live issue as it exists now.

Useful inputs

NowWhat is happening now, or what feels unstable in the current situation
FrictionWhere the ambiguity, bottleneck, confusion, or recurring drag appears
QuestionWhat decision, boundary, responsibility, or direction remains unclear
ConstraintAny legal, timing, audit, capacity, organizational, or security limit that matters
MaterialRelevant documents, notes, workflows, screenshots, or current assets if they help

You do not need

  • a complete brief
  • a finalized theory of the problem
  • perfect language for what is wrong
  • a commitment to a larger engagement
  • a pre-decided solution path

How this relates to other practice formats

Diagnostic Session, Structure Sprint, and Advisory Stewardship are connected, but they serve different moments in the life of an issue.

Diagnostic Session

Best when the issue is still fuzzy, mixed, or not yet cleanly named, and the main need is clarification plus next-step design.

Structure Sprint

Best when the issue is clear enough to turn into a first working structure: a memo, boundary note, workflow logic, governance draft, or comparison.

Advisory Stewardship

Best when a structure is already alive and needs refinement, updating, review, tuning, and sustained support over time.

What a good outcome looks like

A good outcome is not necessarily:

  • a fully solved system in one session
  • a large document set
  • a commitment to longer work
  • a polished answer to every surrounding question

A good outcome is usually:

  • a more accurate reading of the issue
  • a clearer distinction between signal and noise
  • a named boundary or bottleneck
  • a smaller next move that actually fits reality

Closing note

A Diagnostic Session is useful because many important situations do not begin as clean problems. They begin as mixed signals that need a stronger read before more action becomes sensible.

Often, the value is not that everything becomes solved. It is that the issue becomes clearer enough to carry, and the next step becomes small enough to take.

If your situation feels important but still hard to name cleanly, that is usually enough reason to begin here.

Best next step

BringOne live issue that feels mixed, vague, or fragile
AimClarify the real issue and define the smallest useful move
ThenStop there, or move into a sprint / stewardship rhythm if needed
StartContact with a short summary rather than a polished brief