Practice the vocabulary and structure of technical design documents: goals, non-goals, alternatives considered, and design decisions.
0 / 8 completed
1 / 8
What is the purpose of a 'Goals' section in a design document?
The Goals section defines what success looks like for this design. It allows reviewers to evaluate whether the proposed solution actually achieves the stated objectives.
2 / 8
Why do design documents include a 'Non-Goals' section?
Non-goals define boundaries. Stating 'this design does not address multi-region support' prevents reviewers from expecting it and keeps discussions focused on what the design actually solves.
3 / 8
What should the 'Alternatives Considered' section of a design doc contain?
Alternatives Considered documents the trade-off analysis. It shows that the team explored the solution space and explains why the chosen approach is better for this context.
4 / 8
Which sentence is an example of good 'Design Decision' language in a design doc?
Good design decision language states the choice, the alternatives, the specific reason for the choice, and the context (query patterns, data volume). Vague or authority-based justifications are not useful for future readers.
5 / 8
What is 'open questions' section in a design document used for?
Open questions flag areas where the author is unsure, needs input, or where the team must make a decision before implementation begins. They invite focused review from the right people.
6 / 8
What distinguishes a design document from an RFC (Request for Comments)?
An RFC is a proposal explicitly seeking feedback from a defined audience (team, organization, or community). Design docs can also be collaborative but are often more focused on implementation details after key decisions are made.
7 / 8
How should you describe a security consideration in a design document?
Security considerations in a design doc should be specific: what is exposed, how it is protected, and what limitations exist. Deferring or delegating security without details is a red flag in design reviews.
8 / 8
What does 'operational considerations' cover in a design document?
Operational considerations address production readiness: how will you deploy it (feature flag? blue-green?), what metrics and alerts will you add, how will you roll back, and what goes in the runbook?