# Technical design doc desk: the proposal, the evidence and the rollback plan

> For Tech leads and software engineers writing a design doc and preparing a release.

the design doc’s claim is backed by the load-test Table and Chart on the same desk, and the rollout and rollback are drawn as a Flowchart before review — so reviewers see the evidence and the way back. Distinct from product-requirements (what and why); this is how.

## What goes on the desk

- Markdown ‘Design doc’ (exports Markdown, HTML or PDF) (/help/widget-markdown)
- Table ‘Load test runs’ (Run, p50, p95, Errors as numbers) (/help/widget-table)
- Chart ‘p95 by run’ (/help/widget-chart)
- Flowchart ‘Rollout and rollback’ (/help/widgets-draw-and-diagram)
- Tasks ‘Before review’ and a release checklist (/help/widget-tasks)
- Browser on the pull request or CI page (/help/widget-browser).

## Set it up

import load-test results as CSV (/help/widget-table-import).

## Use it day to day

add each run; update the doc’s numbers; tick the checklist before release.

## Where Plexii helps

the Markdown widget’s AI drafts points from the desk (/help/widget-markdown); the Flowchart can be generated with AI (/help/widgets-draw-and-diagram); Plexii answers from the desk with sources (/help/ai-assistant).