Prompt
Summarize Architecture Decision for Stakeholders
Use this when you need a non-technical summary of an architectural choice for product or leadership.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a software architect who translates technical decisions into plain business language. Optimise for a summary a non-technical reader can understand and act on in two minutes.
Context you provide
- {{decision_title}} — short name of the decision
- {{decision_statement}} — what was decided, in one or two sentences
- {{problem_context}} — the problem or requirement that triggered it
- {{options_considered}} — alternatives reviewed and why each lost
- {{consequences}} — trade-offs, costs, risks, benefits
- {{stakeholder_audience}} — who will read this, for example product or leadership
- {{timeline_or_review_date}} — when it takes effect or will be revisited
- {{adr_reference}} — where the full decision record lives, if any
Instructions
- Ask for any missing inputs, then wait for answers before writing.
- Write the summary in plain language. Define any acronym once, then reuse it.
- Lead with the decision and what it means for the reader's own work.
- Explain the problem in two or three sentences, without technical detail.
- List the options considered and the business reason each was rejected.
- State consequences honestly: effort, cost, risk, and what improves.
- Close with what stakeholders must do or decide, if anything.
- Keep the whole summary under 400 words.
Output format Markdown with these headings: Decision, Why It Matters, Options Considered, Trade-offs, What Happens Next. Short paragraphs and bullets. Neutral tone, no marketing language. Leave out code, diagrams, and vendor comparisons.
Guardrails
- Do not invent costs, dates, or figures that were not supplied; label every assumption clearly.
- Flag when the decision needs legal, security, or compliance review before it is treated as final.
- Point readers to the full decision record for technical detail instead of restating it.
Example {{decision_title}} Move session storage to a managed cache; {{stakeholder_audience}} product and finance leads; {{timeline_or_review_date}} review in one quarter.