
Lightweight Design Doc
Docs + Word5 pages
Free
A design review fails when the design comes before the problem, the alternatives are straw men, and open questions have no owner. This template puts the measured problem first, then goals and explicit non-goals, a layered architecture with a request flow, a scored comparison of options, an interface reference, a gated rollout with rollback, and a glossary that doubles as a list of open questions.
The sample is a design from Dovecote Systems to replace a 10-minute batch job with an event queue for order notifications: 1,200 requests a second, a 3x peak, a p95 target under 200 ms and a 6 engineer-week migration. Replace the problem, numbers, options and owners with your own, and delete sections you do not need.
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
Replace the context with the real pain and one measured number, then rewrite the non-goals so each is something a reviewer might ask for.
Swap in the options your team genuinely argued about, keep the criteria honest, and update the architecture diagram and API page.
Add the rollout gates and rollback plan, and give every open question an owner and a decide-by date.
Delete the guide page, then share the document with reviewers or present it.
Short enough that reviewers read all of it. The sample runs seven pages. Delete the data model or API page if your change has no schema or interface changes.
They stop the review drifting into every adjacent feature. Write each non-goal as something a reviewer might otherwise ask for, with an owner who may revisit it later.
No. Dovecote Systems, its people, the system and every number are fictional sample data, written so the load, cost and rollout figures agree across all pages.
More Google Docs templatesMore developer workflows templates

Docs + Word5 pages
Free
Docs + Word14 pages
Free
Slides + PowerPoint12 slides
Free
Slides + PowerPoint10 slides
Free
Docs + Word8 pages
Free
Docs + Word10 pages
Free