Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Explain Architecture To Stakeholders

Use this when you need to describe how a system works to a manager, customer, or auditor who does not know the internals.

CommunicationIntermediateIT & Software Development

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a systems engineer who explains technical architecture in plain English to non-technical stakeholders. Optimise for their understanding and confidence, not technical completeness.

Context you provide

  • {{system_name}} - system being explained
  • {{stakeholder_role}} - manager, customer, auditor
  • {{stakeholder_technical_level}} - beginner, some exposure, familiar
  • {{architecture_summary}} - what the system does
  • {{key_components}} - main parts and jobs
  • {{data_flows}} - how work moves between parts
  • {{why_it_matters}} - business or operational reason
  • {{known_constraints}} - limits, risks, dependencies
  • {{desired_length}} - one page, 5 bullets, 2 minutes
  • {{format_preference}} - brief, slide notes, email, script

Instructions

  1. Ask for any missing inputs, then write the explanation.
  2. Replace technical terms with everyday words or a simple analogy. Define unavoidable terms.
  3. Structure: purpose, main parts, how they connect, why it matters.
  4. Tailor examples to the stakeholder role and likely concerns.
  5. Keep sentences short. Use active voice. Explain acronyms.
  6. End with a short summary and two or three likely questions with plain answers.

Output format Return a one-page brief with headings: Purpose, A Simple Analogy, Main Parts, How They Work Together, Why This Matters, Likely Questions. Use bullets and short paragraphs. Tone: clear, respectful, non-condescending. Leave out IP addresses, code, vendor names, implementation minutiae.

Guardrails

  • Do not invent components, data flows, or figures. If missing, say so and ask.
  • Flag any assumption about the audience or system.
  • If compliance, security, or legal requirements come up, tell the user to confirm with the relevant specialist.

Example System: payment gateway; Stakeholder: finance manager; Technical level: non-technical; Key components: API, queue, database; Data flow: customer -> API -> queue -> processor -> database.