One-Page Technical Decision Note

Made for Engineers

One-Page Technical Decision Note

Also useful for: people in Software Engineering

25 min Intermediate Decisions Communicate Better Need to Compare Options

Document a technical decision in one page without losing the constraints, unknowns, or tradeoffs that shaped it.

We'll use them to write your prompt.

Make Your Play

Give us the situation. We’ll build the prompt.

Make a technical choice reviewable without forcing teammates to reconstruct the reasoning from tickets, chats, and meetings.

Your answers save as you type.

What you'll do

This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.

01 Frame the decision boundary Reduce the situation to one answerable question, then separate hard constraints from preferences and facts from unknowns.
02 Compare options and set the direction Test every option against the same criteria and decide whether the evidence supports a choice or requires a focused investigation.
03 Compile and pressure-test the note Compress the reasoning into a one-page record and check that another engineer can challenge or act on it without extra context.

Use this when

You need to choose between technical options, explain an implementation direction, or record why an investigation should happen before work starts.

You'll need

  • Decision question
  • Problem context
  • Constraints
  • Options
  • Evidence and unknowns
  • Current leaning
  • Decision status

Fill these in the prompt workspace.

You'll get

  • A decision question narrow enough to answer
  • Every viable option compared against the same constraints
  • Facts separated from assumptions and unknowns
  • A selected direction or a bounded investigation
  • Decision-reversal conditions recorded
  • Follow-up checks with owners, triggers, and success signals

By the end of this playbook

You will have:

  • A decision question narrow enough to answer
  • Every viable option compared against the same constraints
  • Facts separated from assumptions and unknowns
  • A selected direction or a bounded investigation
  • Decision-reversal conditions recorded
  • Follow-up checks with owners, triggers, and success signals

Part of a collection

Turn the Vague Problem Into Something You Can Solve

10 playbooks

Clarify requests, expose assumptions, set constraints, investigate unknowns, document decisions, and break risky changes into safer delivery steps.

Next: Break a Risky Change Into Safe Delivery Slices

View collection

Best next playbooks

Suggest an idea

What should we add?

Loading the suggestion form…