Explain an Outage to Stakeholders
Need to tell non-technical stakeholders what an outage means, what caused it and what happens next.
Prompts for your job
Need to tell non-technical stakeholders what an outage means, what caused it and what happens next.
Use this when a broker has questioned an underwriting decision and you need a calm, factual explanation in plain language.
Inherit code you do not understand yet and need a plain-language walkthrough before you change anything.
Inherit an old backend module and need a plain-English walkthrough of what it does before you change it.
Encounter a term or effect outside your specialty and want a plain-language explanation with analogies and key equations.
Are handed a requirement built on a Salesforce feature you have never configured before.
Need to understand or apply normalization rules to clean up a database schema.
Need to justify why a peer set or multiple range makes sense.
Want a quick explanation of squash, anticipation, or follow-through for a specific move.
Need to describe common anxiety signs and body reactions without diagnosing.
Use this when you're stuck on confusing API documentation and need it explained in plain English before wiring it into a no-code platform.
Have a sample JSON response and want to understand how to map it to UI.
Need to explain why the APR is higher than the rate you quoted and what the difference really means.
Need to translate a design into implementation guidance for the team.
Need to describe how a system works to a manager, customer, or auditor who does not know the internals.
Want to describe score ranges and implications to a client or family.
Use this when a client wants to understand why their portfolio is split between stocks, bonds, and cash.
Need a step-by-step overview of an audit process to prepare for or understand different types of audits.
Must explain to stakeholders why some requests are lower priority.
Need to explain how to apply for benefits in simple terms.
Need to describe health, dental, vision, or retirement options without confusing jargon.
Need a plain-language walkthrough of enrollment deadlines, plan options and the exact actions employees must take.
Need to describe your QC metrics and analysis results clearly to a wet-lab scientist or clinician.
Need to explain pain relief, positions, or newborn procedures to an expectant parent in plain language.