A Clarity Sprint is a fixed two-week diagnostic.
The goal is not to install a new operating system, restructure the company, or introduce more meetings.
It is to understand where execution is actually breaking, then turn that diagnosis into a written report, a draft scorecard, and a 90-day priority plan.
The useful part is that the output stands on its own. You can continue into a longer engagement, use the report internally, or decide that no ongoing external support is needed.
- Days 1–3: Review the Existing Operating Picture
The first few days are about evidence.
I want to see how the company currently operates before suggesting anything new.
That usually means reviewing:
- recent operating numbers
- current priorities
- org structure
- recurring leadership meetings
- existing scorecards
- ownership of major initiatives
The goal is not to judge whether the documentation looks polished.
I am trying to understand how decisions move.
Who owns what?
Which numbers leadership trusts?
Where does information live?
Which questions still end up with the founder?
A company may have dozens of dashboards and still be unable to answer:
Are we on track this week?
Or it may have almost no operating numbers and run mainly on instinct.
Both tell you something.
What matters here
Do not create special reports for the Sprint.
The existing information is more useful because it shows the real operating system rather than a cleaned-up version created for an external review.
- Days 4–8: Observe Leadership and Run One-to-Ones
Documents show structure.
Meetings show behavior.
During this phase, I want to see the existing leadership rhythm as it normally happens.
I pay attention to questions like:
Does the meeting end with decisions?
Does every action have one owner?
Do the same issues return every week?
Who makes trade-off decisions?
What still needs founder approval?
Then I speak individually with leadership team members.
This matters because the same problem can appear differently depending on where someone sits.
One person may say:
Communication is poor.
Another may say:
Priorities change constantly.
Another may say:
Nobody knows who makes the final call.
Those may not be three different problems.
They may all point to unclear ownership or weak decision rights.
What matters here
I am not looking for agreement.
I am looking for patterns.
Repeated friction reported independently by several people deserves more attention than one isolated complaint.
- Days 9–12: Connect Symptoms to Root Causes
This is where the Sprint becomes more than a collection of interviews.
Suppose delivery dates keep slipping.
The obvious answer might be:
We need better project management.
But the actual issue could be:
sales commits dates too early
↓
delivery inherits unrealistic timelines
↓
priorities keep changing
↓
teams wait for founder decisions
↓
deadlines slip
The visible symptom is missed delivery.
The operating issue may be decision ownership.
The same applies to founder bottlenecks.
A founder answering too many questions does not automatically mean they are bad at delegation.
It may mean the organization has never made ownership explicit.
During this phase, I start forming a clearer view of:
where execution slows
what keeps circling back to leadership
which issues are structural
which numbers should be reviewed regularly
what should be fixed first
what should deliberately remain unchanged
What matters here
A useful diagnosis prioritizes.
If the output is just a list of twenty things the company could improve, it has not done enough work.
The hard part is deciding which few things matter first.
- Days 13–14: Produce the Written Readout
The Sprint should end with something concrete.
Not:
We noticed some interesting themes.
The written output should make the operating picture explicit.
A simple report structure might look like:
Current Operating Picture
Execution Gaps
Founder Bottlenecks
Ownership and Decision Gaps
Draft Leadership Scorecard
Priority Risks
90-Day Plan
Recommended Next Step
The point is clarity.
The report should explain what appears to be causing the execution problems and what should happen next.
That next step may be ongoing operational support.
It may also be:
give an internal leader clearer ownership
change the meeting rhythm
reduce active priorities
clarify decision rights
hire a full-time operator
do nothing external yet
That last possibility matters.
A diagnostic should be capable of concluding that no longer-term engagement is necessary.
Otherwise, it is just a sales process disguised as an assessment.
- What the Founder Needs to Prepare
The preparation should be lightweight.
I usually want four things.
Recent numbers
Roughly the last two months of the operating numbers leadership already uses.
Not a new dashboard.
The existing numbers.
Current org chart
It does not need to be visually impressive.
I want to see formal reporting lines and compare them with how decisions actually happen.
Current priorities
Whatever the company calls them:
quarterly priorities
rocks
objectives
strategic initiatives
major commitments
The terminology matters less than understanding what leadership currently believes is important.
Meeting calendar
Which recurring meetings exist?
Who attends?
What are they supposed to accomplish?
How often do they happen?
These four inputs provide enough context to begin without creating unnecessary preparation work.
- What the Sprint Does Not Do
This part is important because diagnostics often become overloaded.
A two-week Clarity Sprint is not the time to rebuild the company.
It does not automatically include:
new software implementation
company restructuring
dashboard development
management replacement
process redesign across every team
long-term execution ownership
full strategic planning
Those things may eventually be useful.
But introducing them during the diagnostic would make it harder to see the existing operating system clearly.
The Sprint should first answer:
What is actually causing the execution problem?
Only then should you decide what needs to change.
Typical / Indicative Effort Across the Sprint
Days 1–3 Evidence ██████░░░░ Medium
Days 4–8 Conversations ████████░░ High
Days 9–12 Analysis █████████░ High
Days 13–14 Readout ██████████ Very High
Prep Inputs █████░░░░░ Focused
Decision Next step ███████░░░ Important
My rough read: collecting information is relatively easy. The real value comes from connecting separate observations into one clear operating diagnosis.
Practical Clarity Sprint Checklist
Before starting:
[ ] Gather recent operating numbers
[ ] Share the current org chart
[ ] List current company priorities
[ ] Share the leadership meeting calendar
[ ] Avoid creating special "perfect" documentation
During the Sprint:
[ ] Observe existing meetings
[ ] Review decision ownership
[ ] Speak individually with leadership
[ ] Look for repeated patterns
[ ] Separate symptoms from root causes
Before closing:
[ ] Write the diagnosis clearly
[ ] Identify the highest-priority execution gaps
[ ] Draft the scorecard
[ ] Define the next 90 days
[ ] Decide whether ongoing support is actually needed
How Consult With Krishna Helps With a Clarity Sprint
Consult With Krishna is our own service, and the Clarity Sprint is designed as a short operating diagnostic before any longer-term engagement is considered. We review the existing leadership rhythm, numbers, ownership, and execution gaps, then turn those findings into a written diagnosis, draft scorecard, and practical 90-day direction.
The main takeaway is simple:
A useful diagnostic should make the next decision clearer, not make the company dependent on the consultant.
I wrote the fuller version here: What Happens in a Clarity Sprint: The Two Weeks, Day by Day.
Top comments (0)