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

What goes on the desk

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

Set it up

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

1. Create a desk named for the real outcome, client or deadline.
2. Add the suggested widgets and rename each one for the job it performs.
3. Bring in the existing files or tables before inventing another copy of the information.
4. Set a due date, add the first visible next action, then save the arrangement as a template if you will repeat it.

Open this desk in the interactive demo

Use it day to day

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

A useful desk should reduce copying. Keep each changing fact in one widget, and let charts, summaries or views read from that source.

A worked starting point

Fictional example. Create the desk, add three real items that are already in motion, then use one full work cycle before changing the layout. At the end, remove anything you did not consult and add only the object that would have prevented a real interruption.

Where Plexii helps

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

Related resources

• demo
• product requirements
• decision log
• asynchronous work