Strategy

Strategy Documentation

Strategy docs ensure alignment before implementation. We invest time upfront to reduce costly rework and miscommunication.

Purpose: Build consensus on what we’re solving and the high-level approach.

Aspect	Description
When	Before starting significant work
Who writes	Anyone proposing a change
Who reviews	Stakeholders, domain experts
Output	Approved direction or rejection

Purpose: Define how we’ll implement an approved RFC (or standalone feature).

Aspect	Description
When	After RFC approval, before coding
Who writes	Lead engineer for the feature
Who reviews	Engineering team
Output	Implementation roadmap

Idea → RFC (consensus) → TDD (technical plan) → Implementation
                ↓                    ↓
            Rejected           ADR (decisions)

Tip: Not every feature needs both RFC and TDD. Small, well-understood changes can skip the RFC. Use judgment.