Summary
If you've ever tried to give an employee feedback and realized you couldn't articulate what "good" actually looks like, you're not alone. A competency framework turns your "gut feel" into precise, shared language: observable behaviours and outcomes.This Insight explores how building a practical framework makes hiring more consistent, feedback clearer, and growth paths easier to explain. You'll also see how competencies strengthen performance management, remove bias, and make performance improvement conversations objective rather than argumentative.
In our previous Insight, we talked about taking the dread out of performance reviews by shifting to continuous feedback. But establishing a steady rhythm of 1:1s is only half the battle. If you're having more frequent conversations but still can't articulate what "good" actually looks like, that feedback will still fall flat. That's where competency frameworks come in.
The Cost of Ambiguity
If you haven't defined what "good" looks like, performance reviews and Performance Improvement Plans (PIPs) become arguments about interpretation instead of discussions based on evidence. This ambiguity is an organizational risk: subjective decisions about promotions and compensation are breeding grounds for unconscious bias and can easily lead to costly human rights complaints under the BC Human Rights Code.
The Subjectivity Trap: Three Typical Scenarios
Without a shared framework, leaders constantly rebuild the wheel, relying on personal definitions of success that vary from manager to manager. Consider these three typical scenarios:
The Solution: If any of those scenarios sounded familiar, a competency framework is the antidote. It addresses these exact issues by shifting the conversation from personal opinions to observable facts. Here is how you apply it to solve them.
The Core Principle: Making Success Observable
Competency frameworks work when they make expectations observable, teachable, and repeatable. While it requires strategic thinking at the outset, it saves leadership from countless clumsy and difficult conversations in the future.
1. Split "Performance" into Outcomes and Behaviours
This principle directly addresses Scenario 2 (The Stagnating Performer). When you separate what someone does (technical tasks) from how they do it (collaboration), you can explain to that tenured employee exactly why their past "very good" ratings don't automatically translate to a promotion today.
Outcomes (The "What"): The measurable results the role must deliver (e.g., sales targets, project completion).Behavioural Competencies (The "How"): The ways of working required to achieve those results while protecting company culture (e.g., judgment, collaboration, initiative).The Take Away: A usable competency is an observable action, not a personality trait.
2. Use it in the Moments that Matter
A framework is useless if it sits in a drawer. You must integrate it into the employee lifecycle to prevent the other scenarios from occurring:
Hiring: Map job postings and interview questions to competencies so selection is objective and not based on "gut feelings."(This mitigates the "Culture Fit" trap from Scenario 1).Onboarding: Show new hires exactly what success looks like and how growth is measured.(Provide clear and actionable expectations to the new hire in Scenario 1.)1:1s and Check-ins: Anchor quarterly feedback with the same shared definitions all year long.(Help the stagnating employee in Scenario 2 by giving clear and consistent feedback.)Development & Succession: Provide a transparent rubric for self-study and growth.(This gives the Eager Successor in Scenario 3 a clear roadmap without requiring you to shadow them 24/7.)Performance Reviews: Ensure annual ratings reflect a year of objective coaching against defined standards—reducing the risk of bias and providing defensible proof for compensation decisions.(This gives the Stagnating Performer in Scenario 2 a precise map for growth, while helping managers discover and correct their own unconscious biases).
What Does a Competency Look Like in Practice?
To be effective, competencies must scale across levels. Let's look at how a core competency like "Collaboration" moves from vague to actionable using a Behaviourally Anchored Rating Scale (BARS). (This is the exact tool you would use to show the Stagnating Performer what they are missing).
Swipe to see more →
| Level | Behavioural Indicators (Collaboration) | Application |
|---|---|---|
| Needs Support | Withholds context, works in silos, or escalates issues to management without first attempting peer resolution | Used to identify PIP requirements or coaching opportunities |
| Foundational | Shares information when asked; participates in team meetings; completes their portion of group work on time | Expected baseline for junior or individual contributor roles |
| Proficient | Shares information proactively; checks assumptions; actively seeks input from other departments to avoid bottlenecks | Expected for intermediate roles and specialized professionals |
| Advanced / Leading | Anticipates cross-departmental friction; builds systems to improve team communication; mentors others on collaborative problem-solving | Required for senior leadership and management positions |
What Leaders Are Navigating Today
Without a framework, executives and HR leaders are left navigating:
Aurora's Perspective
At Aurora HR, we build minimum-viable competency frameworks: short, plain-language definitions that leaders can actually use. We do not believe in huge documents sitting on your shelf. We focus on observable behaviours, clear progression by level, and behavioural anchors where fairness matters most.We help organizations transition from subjective "gut feelings" to evidence-based performance cultures. When expectations are clear, managers feel more confident giving feedback, and employees feel trusted and empowered to navigate their own career paths.
Employer Checklist
If you're building (or refreshing) a competency framework, start here:
- Select Core Competencies: Choose 5–7 core competencies tied directly to your organizational values (e.g., accountability, client care).
- Define Behaviours, Not Traits: Define each competency in plain language, adding 3–5 observable actions.
- Create Level Progression: Map the progression (Foundational → Proficient → Advanced) with clear, concrete examples.
- Add Role-Specific Add-Ons: Identify specific competencies for priority roles (e.g., leadership, technical).
- Calibrate with Your Team: Ask managers, "Is this what success actually looks like here?"
- Integrate Systemically: Use the framework to make interview scorecards, onboarding materials, and performance check-ins.
Talk to an HR Consultant
Reach out to discuss how this applies to your organization.
Talk to an HR Consultant
