Practical method
Clarity Assessment Process
A Clarity Assessment is a structured way to examine the beliefs driving an initiative, decision, project, architecture, methodology, or strategy.
It does not replace the organization’s existing process. It helps reveal the beliefs, claims, assumptions, evidence, confidence, ownership, and reassessment triggers underneath that process.
Clarity is a framework for making beliefs, assumptions, evidence, confidence, ownership, and reassessment explicit so people can adapt when reality changes.
Triggers, thresholds, and responses are also claims. They should be inspected and revised when reality shows they no longer represent meaningful change or risk.
The Seven-Step Assessment
Step 1 — Identify the Claims
Question: What are we acting as if true?
Step 2 — Assign Posture
Question: Is this claim in Discovery, Commitment, or Reassessment?
Step 3 — Review Evidence
Question: What evidence supports this claim, and is it strong enough for the posture?
Step 4 — Surface Assumptions
Question: What must be true for this claim to hold?
Step 5 — Check Confidence Debt
Question: Does confidence exceed evidence?
Step 6 — Define Triggers
Question: What signal are we monitoring?
Question: What threshold matters, and why?
Question: What claim does this trigger represent?
Question: What would require immediate action or reassessment?
Step 7 — Recommend Action
Question: Should we proceed, gather more evidence, reduce scope, reassess, or adapt?
Assessment Output
Monitoring signals and thresholds
Trigger claims and owners
Action triggers and responses
Reassessment triggers and trigger-review conditions
Quick Assessment Format
Claim:
Posture:
Evidence:
Assumptions:
Confidence:
Owner:
Monitoring Signal:
Threshold:
Trigger Claim:
Action Trigger:
Response:
Reassessment Trigger:
Trigger Reassessment:
Recommended Action:
Trigger Model in Practice
Claim → Monitoring Signal → Threshold → Trigger → Response → Learning → Reassessment
A trigger is not a permanent truth. It is a claim about what a signal means and what should happen when that signal crosses a threshold.
Reassessment Trigger
Example: Customer adoption remains below 10% after 30 days.
Response: Reassess the claim that customers want the feature.
Action Trigger
Example: 20 production errors occur within 10 minutes after deployment.
Response: Roll back the deployment, notify the on-call engineer, and begin incident review.
Deployment Example
Claim: This release is production-ready.
Evidence: Automated tests passed, QA completed validation, and no critical defects remain open.
Confidence: Moderate to High.
Monitoring Signal: Production error count after deployment.
Threshold: 20 production errors within 10 minutes.
Trigger Claim: 20 production errors within 10 minutes indicates unacceptable deployment health.
Action Trigger: Threshold crossing after deployment.
Response: Roll back the deployment and notify the on-call engineer.
Reassessment Trigger: Root cause analysis identifies a release-related defect or a gap in test coverage.
Reassessment: Review the claim that the release process was sufficient.
Trigger Reassessment Example
Scenario: Several healthy deployments produce 10 to 20 transient errors with no customer impact.
Assessment: The trigger fired according to its threshold, but the threshold may no longer represent meaningful risk.
Adaptation: Adjust the threshold, change the signal, or add context such as severity, persistence, or affected users.
When To Use It
A team disagrees about direction.
A decision has high uncertainty.
A proposal sounds convincing but untested.
A postmortem explanation feels too simple.
A strategy depends on assumptions.
Reality has changed but the plan has not.
What Makes It Different
Most reviews ask:
What should we do?
Clarity asks:
What do we believe, why do we believe it, what signal and threshold are we watching, what would require immediate action, and what would change our minds or the trigger itself?
