# Technical Design Document

> A written plan for a new part of an app. The team reads it before coding.

**Field:** Software Development  
**Category:** Architecture  
**Also known as:** Design Doc, Software Design Document, Tech Spec, Technical Specification

## Think of it like

It is like a plan for a tree house. You draw it before you pick up a hammer.

## Definition

A technical design document is a written plan for building a feature or system before the coding starts. It says what problem it solves and what is left out. It shows the design, often with diagrams, and the other options that were turned down. Teammates read it and leave comments. Many teams write one for any large change.

## Example

Before building search, Jack writes a six-page design doc. A reviewer sees the index will not fit in memory. The plan changes in a day, not a month.

## Why it matters

Mistakes are cheapest to fix on paper. The doc also tells later readers what was built and why.

## Common mistake

Writing it after the code is done. Then nobody can change the design, and the review is just for show.

## Three principles

- **Before the code.** Plan, then build.
- **Options weighed.** Say what was turned down.
- **Reviewed.** Others comment first.

## Related terms

- [Architecture Decision Record (ADR)](https://learn.benibix.com/term/development/architecture-decision-record)
- [System Design](https://learn.benibix.com/term/development/system-design)
- [Unified Modeling Language (UML)](https://learn.benibix.com/term/development/uml)
- [Software Documentation](https://learn.benibix.com/term/development/documentation)
- [Code Review](https://learn.benibix.com/term/development/code-review)
- [Product Requirements Document (PRD)](https://learn.benibix.com/term/business/product-requirements-document)
- [Design Spec](https://learn.benibix.com/term/design/design-spec)

## Told apart from

- [Architecture Decision Record vs Design Doc](https://learn.benibix.com/compare/architecture-decision-record-vs-technical-design-document): People think an architecture decision record is just a short design doc. A design doc plans a whole change before the code is written, and is read and argued over. A decision record saves one choice and the reasons, at any time, in a few lines. Design docs often go stale once the work ships. Decision records are kept for good, and a new one replaces an old one.
- [PRD vs Design Doc](https://learn.benibix.com/compare/product-requirements-document-vs-technical-design-document): People think a product requirements document and a design doc are the same plan. The first says what to build and why: the problem, the users and how to tell it worked. A design doc says how to build it: the parts, the data and the options turned down. Product managers most often write the first. Engineers write the second, after they read it.

![Three papers side by side. The first, a design doc, has headings for problem, design, options turned down and open questions. The second, an architecture decision record numbered 7, has headings for context, decision and consequences. The third, a UML class diagram, shows two boxes, Order and Customer, joined by a line marked many to one.](https://learn.benibix.com/diagrams/dev6-architecture-docs.svg)

---

Source: https://learn.benibix.com/term/development/technical-design-document
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-18
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
