<aside> 💡 This TDD template is meant for medium-large projects that require scoping out and a solid plan.

*Note: Every company and culture will be different. You don’t need to follow this exact structure. Use what makes the most sense for your particular scenario.

Some bonus articles:

• Design Docs at Google by Malte Ubl
• Driving progress forward on design docs by Raviraj Achar (Staff Eng at Meta)
• 5 Mistakes that made my Design Docs Terrible by Raviraj Achar (Staff Eng at Meta)*

</aside>

Technical Design Doc (TDD) Example

Another example from Maxi Ferreira

About this doc

Metadata about this document. Describe the scope and current status.

This doc describes the technical approach, milestones, and work planned for the [Project name linked to Product Requirements Doc]

Sign offs

• [x] Name 1
• [ ] Name 2
• [ ] Add your name here to sign off

[Project name] Design Doc

Context

A sentence or two on the “what.” What is being built.

Then include the “why” (metrics we intend for). Link off to Product Requirements Doc for details.

Out of scope

What is out of scope for this project that we don’t want to focus on?

• Out of scope detail 1
• Out of scope detail 2
• …