Learn Clarity Through Examples — Clarity Framework

Introduction

The point is not to memorize terms. The point is to take a simple claim, make the belief visible, and examine what supports it before acting too confidently.

Exercises

Startup Exercise

Scenario

A founder believes customers want a new feature.

Claim

Customers want Feature X.

Questions

Why do we believe this?
What evidence supports this claim?
What assumptions support it?
How confident are we?
What would change our minds?
What is the smallest experiment that could reduce uncertainty?

Key Lesson

Customer enthusiasm is not customer demand.

Insurance Exercise

Scenario

A family is considering switching insurance providers.

Claim

Switching plans will reduce costs without meaningful downside.

Questions

What costs are visible?
What costs are hidden?
What assumptions support this belief?
What would trigger reassessment?
Who bears the consequences if we are wrong?

Key Lesson

The cheapest option is not always the lowest-cost option.

Restaurant Exercise

Scenario

Two cooks call off and a critical ingredient shipment fails to arrive hours before service.

Claim

Tonight’s menu can still be executed as planned.

Questions

What assumptions are no longer true?
Which decisions are reversible?
Which decisions must happen immediately?
What would a successful adaptation look like?

Key Lesson

Adaptation often matters more than planning.

Methodology Exercise

Scenario

A team proposes a new AI-assisted development methodology.

Claim

This methodology will improve software delivery and can be reused across projects.

Questions

What evidence supports the claim?
What assumptions support portability?
What project types have been tested?
What project types remain untested?
What would invalidate the claim?

Key Lesson

Success in one environment does not prove portability.

Architecture Exercise

Scenario

A team believes microservices will solve their scalability problems.

Claim

Microservices will improve scalability.

Questions

What evidence supports this?
What assumptions support this?
What problem are we actually trying to solve?
What happens if the claim is wrong?
What would trigger reassessment?

Key Lesson

Technology decisions are often solutions looking for a problem.

Worked Example

Startup Walkthrough

Claim

Customers want Feature X.

Posture

Discovery

Evidence

Five customer interviews.

Assumptions

Interview responses predict behavior.
Customers interviewed represent the target market.
Interest will translate into usage.
Usage will translate into willingness to pay.

Confidence

Moderate

Reassessment Trigger

Fewer than 10% of pilot users use the feature after 30 days.

Clarity Observation

Confidence exceeds the available evidence. A large commitment is not yet justified, but the team can run a small pilot—or decide now if the cost of waiting is greater—while keeping the uncertainty visible.

Strategy Walkthrough: Decide Without Proving the Future

Claim: We should consolidate two overlapping teams under one leader this quarter.

What we know: Work is repeatedly duplicated, staff report conflicting priorities, and both team leads describe unclear ownership. These observations and reports are relevant evidence even though they are not controlled measurements.

What we believe or assume: A single leader will reduce conflict without losing important domain knowledge. This is informed professional judgment, not a proven fact.

Uncertainty: Customer demand next quarter and the effect on retention remain unclear.

Decision: Waiting through another planning cycle is judged more costly than the remaining uncertainty. Proceed, name the owner, preserve the option to adjust team boundaries, and review after the first planning cycle.

Clarity Observation: The decision is not proven. It is reasoned from the best available information, honest about assumptions, and reviewable.

Historical Clarity Assessments

Historical examples can make Clarity easier to understand because the outcomes are known, but the reasoning failures or strengths are still visible. These examples are not about judging people in hindsight. They are about examining how beliefs, evidence, assumptions, confidence, and reassessment affected adaptation under uncertainty.

Apollo 11

Adaptation under uncertainty

Apollo 11 succeeded not because every uncertainty was eliminated, but because NASA had built a system capable of recognizing problems, reassessing quickly, and adapting under pressure.

Clarity focus

Evidence was accumulated through prior missions.
Confidence was built gradually.
Reassessment was possible during execution.
Unexpected signals were evaluated quickly.
Adaptation occurred when reality changed.

Key Clarity lesson

Success under uncertainty depends less on perfect prediction and more on the ability to recognize and correct error before it becomes irreversible.

Suggested claims

The Saturn V could safely place a crew on a lunar trajectory.
The Lunar Module could land and return safely.
The mission team could respond to unexpected conditions during execution.

Clarity observations

Apollo 11 demonstrates healthy confidence building.
Prior missions reduced uncertainty before commitment.
The 1202 alarm and landing-site issues illustrate real-time reassessment.
The system did not require perfect conditions; it required adaptive capacity.

Challenger

Confidence detached from evidence

Challenger is useful for Clarity because it shows a different failure mode. The issue was not simply that uncertainty existed. The deeper problem was that warning evidence was discounted and confidence exceeded what the evidence justified.

Clarity focus

Evidence existed that should have triggered reassessment.
Prior success may have created false confidence.
Assumptions became normalized.
Schedule and organizational pressure affected interpretation of evidence.
Reassessment mechanisms failed.

Key Clarity lesson

Organizations become fragile when confidence grows faster than evidence and when signals that should trigger reassessment are rationalized away.

Suggested claims

The shuttle could launch safely under the existing conditions.
Prior launches sufficiently demonstrated acceptable risk.
Engineering concerns did not require delaying launch.

Clarity observations

Challenger illustrates Confidence Debt.
It also illustrates normalized assumptions and reassessment failure.
The failure was not only technical; it was also organizational reasoning failure.
Clarity would focus on which claims were being treated as true and what evidence should have changed those beliefs.

What These Examples Show

Apollo 11

Relationship to evidence: Evidence accumulated progressively.
Confidence pattern: Confidence built through staged validation.
Assumption handling: Assumptions were repeatedly tested.
Reassessment behavior: Reassessment occurred during execution.
Adaptation: Adaptation was strong.
Clarity pattern: Healthy adaptation under uncertainty.

Challenger

Relationship to evidence: Warning evidence was discounted.
Confidence pattern: Confidence exceeded evidence.
Assumption handling: Assumptions became normalized.
Reassessment behavior: Reassessment failed.
Adaptation: Adaptation was weak.
Clarity pattern: Confidence Debt and Reassessment Failure.

The goal of Clarity is not to make perfect decisions. The goal is to make beliefs visible, test them against evidence, and adapt when reality changes.

Judge decision quality by the reasoning and constraints visible when the decision was made, not by the outcome alone. A sound decision can end badly, and a weak decision can succeed through luck.

Apollo 11 and Challenger are not useful merely because one succeeded and one failed. They are useful because they show two different relationships between belief and reality. Apollo 11 demonstrates adaptation under uncertainty. Challenger demonstrates what can happen when confidence becomes detached from evidence and reassessment fails.