Problem Statement
The project aims to systematize the creation of one‑page executive decision memos based on a team’s inputs about a decision, available options, constraints, stakeholders, and timelines. The workflow should reliably produce a clear, structured memo that captures tradeoffs and provides a reasoned recommendation. It must support honest, assumption‑explicit communication that helps leaders align and proceed confidently.
Steps
Ingest Decision Inputs
INGESTCollect and parse the provided decision context, options, constraints, stakeholders, and timeline. Identify gaps that require explicit assumptions.
Retrieve Relevant Background
EXECUTEPull any precedent decisions, organizational principles, or constraints that may influence the decision memo. This ensures alignment with historical patterns or expectations.
Evaluate Options and Tradeoffs
EXECUTEAnalyze each option’s pros, cons, implications, and alignment with constraints and stakeholder needs. Identify assumptions, risks, and what could change the recommendation.
Draft Structured Memo
EXECUTEGenerate a one‑page, executive‑friendly memo containing context, option comparison, recommendation with rationale, risks and mitigations, and next steps.
Validate Clarity and Completeness
EXECUTECheck that the memo is jargon‑free, assumption‑explicit, and follows the required section structure. Flag missing information or inconsistencies.
Prompt Configurations
Decision Memo Drafting Prompt
You are producing a one-page executive decision memo. Use the inputs provided (decision, options, constraints, stakeholders, timeline). Instructions: - Be structured, concise, and executive-friendly. - Avoid jargon and do not invent facts. - Be explicit about assumptions. - Include: (1) context, (2) options with pros/cons, (3) recommendation with rationale, (4) risks and mitigations, (5) decision and next steps, and (6) what would change our mind. Tone: honest, direct, and clear. Only use information from the provided inputs and explicitly stated assumptions.
Example Inputs/Outputs
Decision: Choose a vendor for data warehousing. Options: Vendor A (fast setup), Vendor B (lower cost), Vendor C (advanced analytics). Constraints: Budget limit of $250k/year, must comply with security policy. Stakeholders: CTO, Data Engineering Lead, Finance. Timeline: Decide within 2 weeks.
Context: The team must select a new data warehousing vendor within two weeks to support expected scaling needs while staying under $250k/year and meeting security requirements. Options: Vendor A offers the fastest setup but is the most expensive. Vendor B is cost-effective but has limited scalability. Vendor C provides advanced analytics but requires longer onboarding. Recommendation: Vendor A, assuming the organization values speed-to-value over cost savings. Its rapid implementation reduces risk of operational bottlenecks. Risks/Mitigations: Cost overruns (mitigate through negotiated caps). Limited analytics versus Vendor C (mitigate with phased add-ons). What would change our mind: Significant price reductions from Vendor C or an extension of the project timeline. Next Steps: Confirm pricing, initiate legal review, begin implementation planning.