Assumption Block
Document project assumptions with validation status, confidence levels, and impact analysis. Track what you believe to be true and what happens if you are wrong.
Assumptions are statements believed to be true but not yet proven. Documenting assumptions explicitly helps teams identify risks early and validate critical beliefs before they cause problems.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Statement | Yes | The assumption being made, expressed as a clear assertion |
| Description | No | Detailed explanation providing context for the assumption |
| Type | No | Category: technical, operational, organisational, business, or environmental |
| Confidence | No | Level of certainty: high, medium, or low |
| Status | No | Current state: unverified, validated, invalidated, or obsolete |
| Validation Method | No | How the assumption will be tested or verified |
| Impact If False | No | Consequences if the assumption proves incorrect |
| Review Date | No | When to re-evaluate the assumption |
| Notes | No | Additional context or observations |
Type Values
Status Values
Example: Database Scalability Assumption
A technical assumption about database capacity that needs validation through load testing.
Example: Third-Party API Availability
An operational assumption about an external service that the architecture depends on.
Example: Team Capability Assumption
An organisational assumption about team skills that affects technology choices.