Technical Strategy

Architecture decision record (ADR) review

When to use

Use during architecture reviews or when a tech lead proposes a significant system change. Best used as async review before the meeting.

Prompt Template

Review this proposed architecture decision: Title: {title} Context: {context} Proposed solution: {solution} Alternatives considered: {alternatives} Challenge this ADR by: 1. Identifying unstated assumptions 2. Stress-testing with 10x scale, team turnover, and 'what if we're wrong' scenarios 3. Evaluating operational complexity (who pages at 3am for this?) 4. Checking for reversibility — how painful is it to change course in 18 months? 5. Suggesting what we should prototype or time-box before committing 6. Rating: strong yes, conditional yes (with what conditions), or hold (and why)

Fill & Run

Fill in the variables below, then copy the completed prompt ready to paste into any AI assistant.

Title

Context

Solution

Alternatives

Fill in all fields above to enable copy.

Output Format

Structured review with challenge questions, risk assessment, and go/no-go recommendation

More in Technical Strategy

Tech debt prioritization framework

Use when planning a quarter and negotiating tech debt capacity with product. Having a framework prevents the annual 'we need to stop and rewrite everything' conversation.

View prompt →

Build vs. buy decision framework

Use when evaluating vendors, considering building internal tools, or during architecture reviews. Forces structured thinking instead of engineer-default 'let's build it'.

View prompt →

Platform team pitch to leadership

Use when you've identified repeated toil across teams that a platform team could address. The pitch must speak business language, not engineer language.

View prompt →

Back to PromptsLeadership Prompt