The journal

Leadership Development · 17 July 2026 · 5 min read

Building a Leadership Competency Framework Your Managers Will Use

Build a competency framework for leadership development that turns broad values into observable actions managers can use in feedback, practice and review.

Written by Sarah Murray

Building a Leadership Competency Framework Your Managers Will Use

Photograph: Immersive Leaders programme photography — all rights reserved by Immersive Leaders by ISSET

Your leadership framework looks impressive on the intranet, but managers cannot use it to explain what someone should do differently. Labels such as strategic, collaborative and inspirational leave plenty of room for agreement and very little guidance for a difficult conversation.

A useful framework makes important leadership work observable. It helps people choose development priorities, recognise progress and discuss gaps without pretending that a complex role can be reduced to a collection of adjectives.

Begin with decisions your managers actually make

Collect examples of leadership work that matters in your organisation. Ask about decisions that get delayed, handovers that break down and conversations that make delivery easier. Use real situations to identify the capabilities required, rather than beginning with a generic library.

Include different functions and levels of responsibility. The leadership needed to run a frontline shift is not identical to the leadership needed to allocate investment across divisions. There may be a shared principle, but the expression must fit the work.

Do not build the framework solely from the habits of current high performers. Some succeed through personal expertise, informal influence or unsustainable effort. Ask which behaviours the organisation wants others to adopt and whether those behaviours remain useful under different conditions.

Look for tensions as well as strengths. A framework that praises both rapid decisions and universal consultation needs to explain how managers should judge when each is appropriate.

Replace abstract labels with visible actions

Keep a broad label if it helps navigation, but define it through behaviour. Collaboration might involve sharing relevant constraints before agreeing a plan, inviting affected colleagues into decisions and resolving ownership when responsibilities overlap.

Avoid statements that depend on reading someone's mind. Shows commitment is less useful than follows through on agreed actions or renegotiates them before the deadline. The latter gives a manager and colleague something specific to discuss.

  • Describe an action that someone could observe in ordinary work.
  • State the situation or purpose that makes the action useful.
  • Avoid personality preferences disguised as performance standards.

Review wording for cultural and accessibility assumptions. A preference for highly visible verbal confidence can overlook thoughtful preparation, written influence or effective communication in another style. The framework should describe the required contribution, not a narrow performance of leadership.

Differentiate levels by scope and judgement

Many frameworks make senior levels sound grander without changing what is expected. Replacing supports with champions does not explain how the responsibility differs. Describe the scope, complexity and consequences of the work instead.

A team manager might agree decision boundaries for an assignment. A functional leader might establish how decisions move between teams. An executive might resolve conflicting accountabilities across the organisation. The underlying capability is connected, but the application is meaningfully different.

Avoid implying that senior behaviour is always better behaviour. An executive who intervenes directly in every team decision may be operating at the wrong level, however skilfully they do it. Progression should include knowing what to leave to others.

Check whether the descriptions help someone identify a realistic next step. If the only development advice is to act more strategically, the distinction between levels still needs work.

Test the framework against awkward cases

Take a draft into conversations using anonymised examples of actual work. Ask managers to identify the relevant behaviour and explain what evidence would support their judgement. If people cannot distinguish between categories, simplify or rewrite them.

Use cases where desirable behaviours compete. A manager may need to move quickly while inviting challenge, or support an employee while addressing a persistent performance issue. The framework should support judgement rather than imply that every desirable action can be maximised simultaneously.

Ask users which statements they would struggle to discuss with a colleague. Some language sounds reasonable until someone must explain what it means in practice. That friction is valuable evidence about usability, not resistance to be overcome with a launch campaign.

Make revisions before connecting the framework to consequential people decisions. Ambiguous language becomes harder to change once it is embedded in assessment forms and promotion processes.

Connect the framework to development choices

A framework becomes useful when it helps someone decide what to practise next. Link behaviours to relevant learning, workplace assignments and feedback sources. Avoid producing an enormous catalogue that assumes every gap requires a course.

Someone developing clearer delegation may need to redesign a briefing, practise a conversation and ask a colleague whether authority was understood. A person improving cross-functional judgement may need exposure to another function's constraints rather than another generic module.

  • Choose a behaviour that matters to the person's current work.
  • Identify a realistic opportunity to practise it.
  • Agree what evidence would show progress and who can provide it.

Keep the initial development focus manageable. Asking managers to improve across the entire framework encourages superficial plans and discourages honest prioritisation. Useful development requires choosing what matters now and returning to it with evidence.

Govern the framework without turning it into doctrine

Give someone responsibility for maintaining definitions, gathering feedback and resolving inconsistent interpretation. Explain where the framework applies and where specialist standards or role requirements provide additional detail.

If it informs assessment, provide guidance on evidence, calibration and fair interpretation. A development discussion and a promotion decision have different consequences; people need to know which conversation they are having. Do not assume familiar wording guarantees consistent judgement.

Review the framework when strategy, operating conditions or responsibilities change. Keep elements that remain useful and remove language that no longer helps anyone make a decision. Its value lies in better conversations about work, not in preserving the original document.

Bring this to your team

We run NASA-style simulations, astronaut keynotes and leadership expeditions for organisations that need their leaders to make good calls under pressure.

Book a Call