wowprompt

Technical architecture explained in slides for non-technical leaders

Turns a system architecture or technical proposal into a short deck business leaders can follow: what the system does, where the risks and costs are, and what decision is needed, with plain diagrams and no jargon. Use it when an engineering team needs approval, budget or understanding from founders, a board, finance or operations.

An eight-slide outline with plain-language headlines, diagram descriptions using everyday labels, a risk and cost slide, a decision slide and a glossary for the few terms kept
The output this prompt produced, unedited.

The prompt

What to give

  • The architecture or proposal: [paste the design doc, diagram description or notes]
  • Audience: [e.g. founders and finance head, a hospital management board]
  • What you need from them: [e.g. approve cloud spend, choose between two vendors, accept a three-month delay]
  • Costs, timelines and risks known: [figures and dates]
  • Time slot: [e.g. 15 minutes plus questions]

Task

Build a deck that lets this audience understand the system well enough to make the decision.

Checklist for every slide

  1. The headline is a full sentence stating the point, such as "Orders will keep working if one server fails".
  2. Technical terms replaced with what they do: "database" becomes "where customer records are kept"; keep at most five terms and define them.
  3. Diagrams show boxes the audience recognises (customers, app, payments, records), at most seven boxes.
  4. Every technical choice is tied to a business result: speed, cost, risk, compliance or growth.
  5. Numbers in business units: rupees or dollars per month, hours of downtime, days of delay.
  6. One idea per slide.

Deck outline to fill

  1. The decision needed today.
  2. What the system does for customers.
  3. How it works, as one simple diagram.
  4. What changes from today.
  5. Cost: one-time and monthly.
  6. Risks and how each is handled.
  7. Options compared, if there is a choice.
  8. The decision and next steps with dates.

Output format

| Slide | Headline | On screen | Speaker notes |, then a glossary and five questions leaders are likely to ask, with short answers.

Guardrails

  • Do not hide a risk or cost to make approval easier.
  • Do not invent figures; mark missing ones as [to confirm].
architecture presentationexplain technology to executivesnon technical audience slidestechnical proposal decksystem design for leadersit presentation

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity