The document is finished. The role is not.
A competency framework often arrives as the end of a substantial project. Roles have been mapped, proficiency levels approved and a common language published.
Then the work changes.
A new system alters decisions. A regulation adds a different standard of care. An AI assistant removes one routine task while making verification and judgement more important.
The document remains accurate to the moment in which it was completed. The role keeps moving.
In the World Economic Forum’s 2025 survey, employers expected 39% of workers’ core skills to change by 2030. This is a forecast, not an expiry date for every skill or role. It does show the scale of change organisations are preparing for.
The answer is not to rewrite every framework every month. It is to stop treating publication as completion.
What a baseline changes
A competency document describes an intended model. A capability baseline creates a current point of comparison.
It answers three practical questions:
- What does this role or responsibility require now?
- What relevant evidence do we have about current capability?
- What action follows from the difference?
A baseline is not a permanent judgement about a person. It is a dated, contextual view. A living baseline can be revised when responsibilities, standards or credible evidence change.
This makes the framework useful beyond taxonomy. It can inform a manager conversation, a development priority, a deployment decision, a hiring brief or a career step.
Begin with the work, not the label
Many competency frameworks rely on broad terms such as customer focus, digital fluency or strategic thinking.
These labels create shared vocabulary, but two managers may interpret them differently. An employee may know the definition without knowing what capable performance looks like in a specific responsibility.
A stronger baseline starts closer to the work.
Instead of demonstrates digital fluency, it might describe a current responsibility such as:
Uses approved AI-assisted analysis to identify relevant patterns, checks the supporting evidence and records the judgement behind a recommendation.
That statement creates something the organisation can discuss and observe. It also reveals the knowledge and skills beneath the work.
The NIST NICE Workforce Framework offers a useful domain-specific example. In cybersecurity, it separates task, knowledge and skill statements and maintains components separately for more agile updating. It is not a universal template, but it demonstrates that role architecture can be modular rather than locked inside one document. Explore the NICE Framework.
What makes a baseline living?
Four elements need to remain connected.
- 1
Current work
Define the responsibility, decision or outcome that matters now—not only a role title or an isolated skill.
- 2
Observable standards
Describe what capable performance looks like. Include the context: complexity, independence, risk, available support and the consequences of error.
- 3
Relevant evidence
Use evidence that fits the responsibility: perhaps a scenario, work sample, structured observation, manager review or performance pattern. The strength comes from using proportionate signals and understanding what each can—and cannot—show.
- 4
A next action
A gap should lead somewhere: focused practice, expert feedback, supervised experience, a changed assignment or readiness for broader responsibility.
Without a next action, the baseline becomes another reporting layer.
A living baseline does not merely describe capability. It helps the organisation decide what to do next.
Work
The responsibility or outcome that matters now
Standard
Observable indicators of capable performance
Evidence
Relevant signals showing current capability
Action
The next development, deployment or support decision
Current work, observable standards, relevant evidence and next actions form one connected capability baseline.
Consider a relationship manager using an AI assistant
Illustrative scenario
Imagine a relationship manager who now uses an approved AI assistant to prepare for client conversations.
The existing framework says the role requires commercial awareness, customer focus and digital capability. All three remain relevant, but they do not show how the work has changed.
A current baseline could make the new expectation more concrete:
- Identify which generated insights are relevant to the client’s situation.
- Verify important claims against approved sources.
- Recognise when the available evidence is insufficient.
- Use the analysis to form better questions, not to replace the conversation.
- Record the reasoning behind a recommendation where required.
This is an illustrative scenario, not a reported client implementation.
The manager and employee can now discuss evidence at the level of the work. Can the employee distinguish a useful pattern from a weak inference? Do preparation notes show appropriate verification and judgement?
The response may be narrower than a new course: several reviewed cases, expert feedback and a clear escalation guide.
The baseline has turned a general competency into a visible development path.
A practical operating rhythm
A living baseline needs governance, not constant activity.
Sense meaningful change
Use signals from strategy, technology, regulation, performance patterns and frontline experience. Skills-needs anticipation connects workforce development to current and future demand, not only to an inherited catalogue.
Review the relevant baseline
Ask a role owner, experienced practitioner and appropriate business stakeholders what has actually changed. Do not reopen the entire framework when only one responsibility has moved.
Gather proportionate evidence
Choose evidence according to risk. A low-risk procedure may need a short check; a high-stakes judgement may require simulation, observation and repeated performance.
Agree the gap
Separate missing knowledge from limited practice, weak judgement, unclear process or lack of opportunity. Not every performance gap is a training gap.
Act, then refresh
Connect the gap to development, support, staffing or work design. Record what changed and who owns the next review.
The rhythm can be event-led rather than continuous. A changed system, new regulation, repeated performance issue or strategic shift may trigger review. Stable responsibilities may need little intervention.
Changes in work trigger review, evidence gathering, gap agreement, action and a refreshed baseline. A brief pause before review reflects human ownership of the decision, not automated tracking.
Living does not mean limitless
A capability system can become intrusive or misleading if every digital trace is treated as evidence.
Employees should know what information is used, why it matters, who can see it and how a judgement can be challenged or corrected. Evidence should be proportionate to the decision.
A baseline should also make uncertainty visible. Insufficient evidence is more honest than an artificially precise score.
The aim is not to monitor everything people do. It is to create a fairer, more useful shared view of where capability stands and what support comes next.
A framework that can do some work
Competency documents create valuable language, structure and consistency.
The problem is asking a document to remain current without an operating rhythm around it.
When expectations are connected to observable work, relevant evidence and explicit actions, the framework becomes more than a reference file. It becomes a baseline the organisation can use—and revise.
The leadership question therefore changes.
Not simply
Do we have a competency framework?
But
Do we have a current, shared view of what good performance requires, where capability stands and what needs to change next?
That is the difference between documenting capability and actively developing it.
Sources and reading
World Economic Forum. “Future of Jobs Report 2025 — Skills Outlook.”
Use: the attributed finding that surveyed employers expect 39% of workers’ core skills to change by 2030. Qualification: this is an employer-expectation survey covering 2025–2030. It is not a measured rate of expiry for every skill, occupation, geography or organisation.
National Institute of Standards and Technology. “Getting Started with the NICE Framework.”
Use: the example of a framework organised around task, knowledge and skill statements, with separately maintained components intended to support agile updating. Qualification: NICE is a cybersecurity workforce framework, used here as a domain-specific example, not a universal competency model.
International Labour Organization. “Skills needs anticipation.”
Use: the broader principle of identifying current and future workforce demand so that skills development can respond to changes in work. Qualification: this source addresses skills anticipation at labour-market and system levels; the article applies the principle cautiously to enterprise capability baselines.
Lurny Insights · Capability & Readiness