The Culture of Risk

During Y2K work, I learned that a risk can look obvious only after someone has named it. In a global team, that naming step can take longer than expected. People may use the same words—risk, control, urgent, acceptable—and still mean different things by them.

That is not evidence that one country or culture is naturally more careful, innovative, or resilient than another. National stereotypes turn a real coordination problem into a flattering story about “how people are.” The useful question is more specific: what assumptions are people bringing to this decision, and have we made those assumptions visible?

A Framework Is a Starting Point

A shared risk framework can create common language: likelihood, impact, control, owner, review date, escalation. That is valuable. It can also create false confidence if a global template is treated as proof that everyone understands the situation in the same way.

Before adopting a control or a threshold across teams, ask:

• What harm are we trying to prevent, and who would experience it first?
• Which signals make this risk urgent in this setting?
• Who is authorized to accept, pause, or escalate the risk?
• What local law, customer expectation, operating condition, or historical experience changes the answer?
• What would tell us that the shared control is not working here?

These are not cultural trivia questions. They are design questions.

Translate, Do Not Stereotype

Translation is more than changing a policy into another language. It means checking whether examples, reporting paths, time horizons, and incentives make sense where the work happens.

For example, a global incident form may require a named individual to raise a concern. In one team, that may be ordinary. In another, the same form may feel like an invitation to blame a colleague. The answer is not to lower the standard for raising risks. It is to provide a reporting path that can surface a concern early while preserving the accountability the organization needs.

That example is illustrative, but the pattern is real: controls work only when people can understand, use, and challenge them.

The Work of Humility

Leaders do not need to become amateur anthropologists before making a decision. They do need to stop treating their own default interpretation of risk as universal.

Invite people closest to the work to explain where the framework fits, where it creates friction, and what it fails to see. Document the answer. Review it when the work, regulation, or team changes.

Risk is not the enemy. Unexamined assumptions about risk are. A good global framework gives teams a common floor and enough room to see the terrain beneath their feet.