Leadership Competency Framework: Turning Expectations into Behaviour
A leadership competency framework describes the observable behaviour expected from leaders at different levels. It should guide development and assessment without turning leadership into a list of vague virtues.
Begin with leadership work
Identify the decisions, relationships and risks leaders must handle in the organisation’s strategy and operating model. Interview people who experience leadership—not only senior incumbents—and review situations where leadership behaviour materially helped or harmed results.
Choose a small set of distinct competencies
Each competency should describe one meaningful area such as setting direction, developing people, making decisions under uncertainty or working across boundaries. Avoid overlapping labels whose descriptions all say communication, collaboration and results.
Write behavioural indicators
Define what effective behaviour looks like in context. “Builds trust” may include explaining decisions, keeping commitments, inviting challenge and addressing breaches consistently. Include ineffective or overused behaviour so assessors can distinguish confidence from good judgement.
Differentiate by level
A first-line manager translates priorities and coaches daily work; an enterprise leader sets direction across systems and allocates resources. Do not create progression by merely adding words such as “strategic”. Show changes in time horizon, ambiguity, scale and stakeholder consequence.
Test for inclusion and realism
Check whether indicators reward one communication style, cultural norm or personality without job relevance. Pilot the framework against real decisions and ask employees whether language is understandable. Provide accessible formats and examples across different functions.
Connect it to people processes carefully
Use the same behavioural meaning in selection, development, succession and performance conversations, but adapt evidence to the process. A development self-assessment should not automatically become a performance rating. Train users and define how competency evidence combines with role results.
Avoid scoring theatre
Rating every indicator can create false precision. Focus discussion on material strengths, risks and next behaviour. Require evidence and allow “not observed”. Calibration should improve consistency, not force a fixed distribution.
Maintain the framework
Name an owner, collect user feedback and review the framework when strategy or leadership work changes. Track whether it improves conversation quality and development actions, not merely completion rates.
Develop examples and counterexamples
For each level, create short situations showing acceptable and ineffective behaviour. In a resource conflict, for instance, a leader may explain trade-offs, seek affected input and decide within authority; avoiding the decision or privately blaming another team are different failures. Examples help users interpret indicators without turning them into scripts.
Roll out through real conversations
Introduce the framework with role scenarios, not a presentation of labels. Let managers practise identifying evidence and agreeing development actions. Provide an appeal or review route where the framework influences consequential decisions. Monitor whether employees can explain expectations and whether feedback becomes more specific.
Separate potential from current performance
A leader can deliver current results yet need development for a broader future role. Define potential, readiness and performance separately if the organisation uses all three. Do not let competency ratings silently become a promise of promotion or a permanent label.
This differs from a skills matrix or job-evaluation framework: it explains leadership behaviour, not workforce skill inventory or the relative size of roles.