Scenario-Driven Leadership Training.

Leadership programs are often organized around topics or competencies, tied to the organization’s strategy or a leadership competency model.

Coaching. Accountability. Strategic thinking. Developing others. Leading change. Enterprise mindset.

All of those capabilities matter. But leaders rarely deploy them one at a time. They experience them bundled together inside difficult decisions.

Consider this situation: A high-performing employee is ready for a cross-functional opportunity, but losing that person now would significantly hurt the team’s results. What should the leader do?

That is not simply a “coaching” problem. It can’t be met with coaching skills alone.

It involves developing people, succession, internal mobility, accountability for near-term performance, enterprise thinking, and perhaps even the leader’s willingness to absorb some personal risk for the long-term good of the organization.

And that is exactly why it can be such a powerful learning experience.

Instead of building leadership training around isolated competencies, we should build it around the recurring decisions and tensions leaders actually face — and then strengthen the relevant competencies.

Leadership happens when two good things compete.

Many leadership decisions are difficult — not when there is a clearly right option and a clearly wrong one. That’s an easy decision. They are difficult when two legitimate priorities are in tension.

On a recent leadership development project, we worked with our client’s leaders to identify exactly these kinds of moments. They posed questions like:

• What is best for my team is not necessarily what is best for the enterprise. Which should take priority?
• I can make the decision myself or let my people make it. How much autonomy should I create?
• Speed is one of our strategic imperatives. And we can move faster, but doing so introduces more risk. When should we slow down, stop, or escalate?
• I need results now, but developing my team will take longer. When should I coach rather than simply get the work done?
• The existing approach works, but there might be a better one. When should I preserve stability, and when should I push for change?
• I do not have all the information I want, but waiting has consequences too. When is there enough information to act?
• A strong performer is delivering results, but their behavior is damaging the team. What counts as successful performance?
• A change is good for the enterprise but disruptive for my people. What is my responsibility to both?

These real things our clients struggle with reveal an important truth: competencies tell leaders what they should be capable of doing. Real situations force them to decide when, how, and at what cost to apply those capabilities.

Design the module around the dilemma.

Traditionally, we start with a competency, like “Developing People.” We teach the skills involved, a framework for development planning, and eventually use realistic scenarios to practice some of the skills, like coaching conversations.

Now, turn that inside out.

• Begin with a situation the leader might find themselves in, like, “One of your high performers wants a developmental move. Would you let them go?”
• Then complicate the situation. The employee is critical to an important deliverable. There is no obvious successor. This new role would be good for the employee and good for the company. But the leader’s performance goals are still on the line.
• Work through the options, teaching elements of coaching, succession planning, mobility practices, enterprise thinking, delegation, accountability, and talent development.

You’re teaching capabilities, but each capability now has a reason to exist. It helps the leader make a consequential decision.

From a design perspective, you’re using real-life scenarios and teaching skills that support it, not teaching one skill and finding a scenario that requires that skill. You’re turning design inside out.

The leaders in our client project framed this tension as “today’s performance versus tomorrow’s capability“ and used it to pressure-test whether the organization’s leadership principles and competencies actually provided useful guidance.

That is a much stronger foundation for learning than starting with a list of competencies and looking for activities to teach them.

Start leadership program design differently.

Begin with discovery.

Don’t begin by asking, “What leadership topics should we cover?” Instead, ask, “What are the hardest recurring decisions our leaders have to make?”

Talk to leaders at different levels. Interview executives, managers, HR partners, and people who regularly work across functions. Look for moments when priorities compete and reasonable leaders might make different choices.