Explaining technical risk to people who don't speak engineering

DRAFT for Fred to edit.

A council officer doesn’t need to know the gearbox torque rating. They need to know what happens to ratepayers if it fails, what it costs to fix now, and what it costs if you wait.

Swap jargon for consequences

Every technical issue can be translated into three things: cost, time and risk. Lead with those. Keep the technical detail for the people who ask for it.

Know who’s in the room

A principal contractor is protecting its margin. A regulator is protecting compliance. A site crew wants to know it’s safe and practical. A board wants cost and risk in one sentence. Same facts, different conversations.

Try it this week

Pick one technical issue on your current job. Write one sentence on what it costs if it’s ignored. That sentence is your opening line.