The request that limits the conversation

At some point in almost every programme design conversation, a sponsor makes a reasonable-sounding request: can we make sure the examples are from our sector? Banking wants banking. Healthcare wants healthcare. Aviation wants aviation. The instinct is understandable. Leaders are busy, and they want material that feels immediately applicable.

In programmes I run, I see this pattern consistently. The belief that only same-sector cases are relevant is widespread, and it is genuinely limiting. Not because sector knowledge is unimportant, but because the assumptions that most need examining are usually the ones the whole sector shares. When every example comes from inside the industry, those shared assumptions never surface. They stay invisible, treated as facts rather than choices.

There is a second problem. The organisations most likely to change the rules of an established sector are rarely inside it. They arrive with a different cost structure, a different relationship with data, or a different idea of what the customer actually wants. A leadership team that studies only its own industry is studying the people least likely to disrupt it.

Why internal context still matters

Before making the case for looking outward, it is worth acknowledging about what sponsors get right. Participants engage most when material connects to their own organisation's internal context: the tools already in use, the decisions already live, the tensions already felt in the room. Examples from distant industries can feel like tourism. Interesting, perhaps, but not quite real.

The answer is not to choose between internal relevance and external provocation. Both are needed, and the sequence matters. An internal anchor case grounds the session in something participants recognise. A deliberately distant case then does work that a same-sector example cannot: it surfaces a structural pattern, strips away the familiar language, and makes it possible to ask whether the assumption underneath the problem is actually necessary.

The practical design I recommend to sponsors is straightforward: one internal anchor case plus one deliberately distant case per session. The internal case establishes shared ground. The external case creates productive distance. Together they produce a conversation that neither could generate alone.

What a deliberately distant case actually does

Consider a hypothetical leadership team in a large logistics company working on real-time decision-making under uncertainty. They could study how other logistics companies handle it. That would be useful. But they might learn more from looking at how an air traffic control system manages competing priorities with incomplete information, or how a hospital emergency department triages when demand exceeds capacity, or how a live broadcast team makes irreversible editorial decisions in seconds.

None of those examples is from logistics. All of them share the structural problem: consequential decisions, incomplete data, time pressure, and the need for a shared protocol that does not require consensus in the moment. The distance from the home sector is precisely what makes the pattern visible. When the surface details are unfamiliar, participants have to think about the underlying structure rather than reaching for the familiar answer.

This approach is underused in leadership development, where pressure to be immediately relevant tends to crowd out the material that is most generative.

A short exercise for your leadership team

This exercise takes around thirty minutes and works well at the start of a session or as a standalone team conversation. It requires no preparation beyond a clear statement of the problem you are working on.

Step one: name the problem precisely. Write one sentence describing the core challenge your organisation is facing. Not the symptom, not the strategic priority, but the actual problem. For example: we cannot get frontline managers to sustain changed behaviour after a training programme ends.

Step two: identify three structurally similar problems in unrelated industries. The industries should be genuinely distant from your own. For each one, name a type of organisation that has faced a problem with the same underlying structure, even if the surface looks completely different. You do not need to know the answer; you need to name the structural similarity.

Using the hypothetical example above, a team might identify: a public health agency trying to sustain behaviour change after a campaign ends; a sports coaching programme where athletes revert to old technique under match pressure; a safety-critical industry where procedural compliance drops once an audit period closes.

None of those is in the same sector. All of them share the structure: a gap between trained behaviour and sustained behaviour when the formal intervention is no longer present.

Step three: write down what you would borrow. For each of the three cases, write one thing you would take from how that type of organisation has approached the problem. It does not need to be a proven solution. It can be a framing, a mechanism, a question they ask, or a constraint they have accepted. The point is to move from observation to implication.

The exercise does not produce a strategy. It produces a different set of options than the ones already on the table, and it surfaces assumptions that were previously invisible because everyone in the room shared them.

What to ask your programme designer

If you are commissioning a leadership programme and find yourself about to request sector-specific examples only, it is worth pausing on what that request is actually protecting. If the answer is participant engagement, the internal anchor case addresses that directly. If the answer is relevance, it is worth asking whether the most relevant insight for your organisation might currently be sitting in a completely different industry.

A well-designed session holds both. It starts where participants are, in their own organisation, with their own language and their own live decisions. Then it takes them somewhere structurally interesting and asks them to bring something back.

One further point worth raising with your designer: organisations in transformation often lack a shared language for digital, AI and innovation concepts. Leaders hear the same words used differently across functions, which means a case study discussion can fragment before it produces anything useful. A simple, organisation-specific glossary, agreed before the programme begins, removes a surprising amount of friction and makes cross-sector material land more cleanly.

Written for this site.