Vision Templates¶
Purpose¶
These templates support ES-101 — Vision and Problem Definition.
Use this family to establish why the system should exist, who it affects, what problem it addresses, what boundaries constrain the work, what assumptions must be validated, and what success should mean before requirements work begins.
Recommended workflow¶
Problem Statement
↓
Vision Statement
↓
Stakeholders
↓
Scope
↓
Assumptions
↓
Success Metrics
↓
Vision Readiness Summary
↓
ES-102 Requirements and ConstraintsCopy location¶
Do not edit the reusable templates directly. Copy completed project versions into:
docs/project-workspace/vision/
Template set¶
Problem Statement
Define the problem before proposing a solution.
02Vision Statement
Describe the intended improvement and trust expectations.
03Stakeholders
Identify users, affected parties, operators, reviewers, and owners.
04Scope
Set boundaries, exclusions, deferred items, and prohibited uses.
05Assumptions
Record assumptions and what must be validated early.
06Success Metrics
Define outcomes, operational indicators, trust metrics, and adoption signals.
07Vision Readiness Summary
Summarize readiness to begin ES-102.
Completion expectations¶
A strong ES-101 vision package should make the following clear:
| Question | Evidence |
|---|---|
| What problem exists? | problem_statement.md |
| What improvement is intended? | vision_statement.md |
| Who is affected or accountable? | stakeholders.md |
| What is included, excluded, deferred, or prohibited? | scope.md |
| What assumptions could invalidate the work? | assumptions.md |
| How will success be recognized? | success_metrics.md |
| Is requirements work ready to begin? | vision_readiness_summary.md |
Do not write the vision as a solution pitch. ES-101 should reduce ambiguity before requirements, architecture, or implementation work begins.
A good vision package does not prove the system should be built. It makes the problem, intended improvement, boundaries, stakeholders, assumptions, and success criteria reviewable.