Explain a technical risk to a nontechnical client

“The API has rate limits” is a technical fact. The client needs to know when it matters, what users experience and which decision is required.

Structure one fictional risk

The delivery lab models partner throttling.

from delivery_cases import risk_explanation_case

result = risk_explanation_case()
assert result["complete"] is True
assert result["nontechnical"] is True
assert result["risk"]["effect"] == "some invoices wait longer"
assert result["risk"]["owner"] == "integration owner"

Use: condition, consequence, likelihood, impact, evidence, control, residual risk, owner and decision. Quantify where evidence supports it and label uncertainty. Offer options with cost/time trade-offs, including accepting the risk.

Lead with user/business effect, then explain enough mechanism to make the recommendation credible. Avoid both alarmism and reassurance without evidence. Record the decision and trigger for reevaluation.

The FDE for Freshers course assesses translation between technical systems and stakeholder decisions.

Exercise

Rewrite three technical findings for a sponsor, user and security owner. Ask each what decision they believe is needed; revise if answers differ.

Continue learning

This article is part of the FDE career entry and client-delivery practice sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Estimate a project when external access is uncertain.
• Continue with Demonstrate a broken workflow before proposing AI.

Reference: GOV.UK security risk guidance.