01
Draft and pressure-test the brief
Run the compiled prompt to compress the decision into a one-page stakeholder brief while exposing unsupported claims, decision-critical unknowns, and missing ownership.
Made for Engineers
Turn an Architecture Decision Into a One-Page Brief
Also useful for: people in Software Engineering
25 min
Beginner
Software Engineering
Engineer
Communicate Better
Career outcome:
Avoid Professional Risk
Package an architecture decision into a focused one-page brief that non-technical partners can scan, question, and act on.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Make the technical logic, business impact, and remaining uncertainty clear without burying the decision under implementation detail.
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.
Make Your Play
Turn an Architecture Decision Into a One-Page Brief
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
State the architecture decision and whether it is proposed, approved, or already underway.
0/10000
Describe the problem, current constraint, and reason the decision is needed now.
0/10000
List the facts, tests, measurements, incidents, or expert findings that support the decision.
0/10000
Summarize the options considered, why alternatives were rejected, and what the preferred choice doesn't optimize.
0/10000
Describe the expected effects on product delivery, finance, operations, customers, and affected teams.
0/10000
List known ranges, dates, dependencies, and assumptions without turning estimates into commitments.
0/10000
List material risks, mitigations, unknowns, unresolved questions, owners, and decision dates where known.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Draft and pressure-test the brief
Run the compiled prompt to compress the decision into a one-page stakeholder brief while exposing unsupported claims, decision-critical unknowns, and missing ownership.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Gather the decision, the main reason for it, and the evidence already available. Rough notes are fine. If a cost, date, or owner isn’t known, say that directly instead of guessing. Run the prompt, then remove the private editor’s note before sharing the brief.
Advanced instructions
Tighten the brief around the decision’s reversibility, switching cost, and largest source of uncertainty. Replace broad claims with measurable signals, and make every open question traceable to an owner or decision point.
Use this when
You've reached an architecture decision and need product, finance, or operations partners to understand what was chosen, why it matters, and what happens next.
You'll need
- Decision and status
- Problem and timing
- Supporting evidence
- Options and tradeoffs
- Stakeholder impacts
- Cost, timeline, and assumptions
- Risks and open questions
You'll get
- The architecture decision stated in the opening section
- Decision status labeled accurately
- Evidence separated from estimates and assumptions
- Product, finance, and operations impacts covered
- Material tradeoffs and risks stated plainly
- Decision-critical questions clearly marked
By the end of this playbook
You will have:
- The architecture decision stated in the opening section
- Decision status labeled accurately
- Evidence separated from estimates and assumptions
- Product, finance, and operations impacts covered
- Material tradeoffs and risks stated plainly
- Decision-critical questions clearly marked
Examples
Progress 1 of 1