Before You Start
You must be a Super Admin or an Admin with Competency management permissions
This article is a conceptual overview for step-by-step setup, start with [Creating a Competency Framework]
Overview
Competency management is the foundation of everything performance and development-related in Lumofy. Before you run a performance cycle, assess your workforce, or build a learning pathway, you need to know what skills and behaviors your organization expects and at what level. This article explains the concept, the structure Lumofy uses, and why getting it right early matters.
What Is Competency Management?
Competency management is the process of defining, organizing, and measuring the skills and behaviors your organization needs to achieve its goals. It answers two questions for every role in your company:
What does this person need to be able to do?
How well do they need to do it?
Without a clear answer to both, performance reviews become subjective, development plans become generic, and hiring decisions become inconsistent. Competency management gives your organization a shared language for talent.
How Lumofy Structures Competencies
Lumofy organizes competencies in a four-level hierarchy:
Framework The top level. A Framework is a named collection of Clusters and Competencies. You can have one framework for your entire organization, or multiple frameworks for different functions or regions.
Cluster A group of related competencies. Clusters help you organize competencies into meaningful categories for example, Hard Skills, Soft Skills, or Leadership Behaviors. Every competency belongs to one Cluster.
Competency A single, clearly defined skill or behavior. Each Competency has a name, a description, and a set of Behaviour Indicators that describe what it looks like in practice.
Behaviour Indicators The observable, specific behaviors that define what a Competency looks like at each proficiency level. Behaviour Indicators are what Admins, Managers, and Talents reference during assessments and performance reviews.
Proficiency Levels
Every Competency in Lumofy is evaluated against five proficiency levels:
Level | What it means |
Beginner | Aware of the competency; limited or no practical application |
Knowledgeable | Understands the competency and can apply it with guidance |
Capable | Applies the competency independently in standard situations |
Skillful | Applies the competency confidently across complex situations |
Expert | Mastery level; leads and develops others in this competency |
When you link a Competency to a Role, you set the expected proficiency level for that Role. This expected level becomes the benchmark used in Competency Assessments and performance evaluations.
How Competencies Connect to the Rest of the Platform
Competencies do not live in isolation. Once built, your framework connects to:
Company Structure Each Role in your structure is linked to the Competencies required for that position, with an expected proficiency level for each. This gives every Talent a clear picture of what is expected of them.
Competency Assessments Talents assess themselves and can be assessed by Managers against the Competencies linked to their Role. Results show current levels versus expected levels, surfacing gaps.
Performance Cycles Competencies are included in Performance Sheets. During a cycle, Managers and Talents review competency performance against the expected levels defined in the Role.
Development & Learning Gap analysis from assessments informs which learning content to build or assign. A Talent with a gap in a specific Competency can be directed to the relevant Course, Guide, or Pathway.
Why Getting This Right Early Matters
The Competency Framework is the backbone of your talent strategy in Lumofy. Every other feature assessments, performance cycles, learning pathways references what you define here. A framework built with care produces meaningful data. A framework built in a hurry produces noise.
Three things that make a framework strong:
Specificity over breadth. Fewer, well-defined competencies with clear Behaviour Indicators outperform long lists of vague ones.
Role alignment. Every Role should have competencies that reflect what that role actually requires not a copy-paste of the same five competencies for everyone.
Consistent proficiency expectations. If two Roles at the same level in the organization have wildly different expected levels for the same Competency, your assessment data becomes hard to interpret.
💡 Tip: Involve team leads or department heads when defining competencies for their areas. They know what "good" looks like in their context better than HR alone does.
FAQs
Can we have more than one Competency Framework?
Can we have more than one Competency Framework?
Yes. You can create multiple frameworks for example, one for technical roles and one for leadership roles. Each Role is linked to the relevant framework during setup.
Who can see the Competency Framework?
Who can see the Competency Framework?
Admins and Super Admins manage the framework. Talents see only the competencies linked to their specific Role they do not see the full framework.
Can we change the framework after Talents have been assessed?
Can we change the framework after Talents have been assessed?
Yes, but changes affect future assessments. If you remove a Competency from a Role after assessments have run, historical data is retained but future cycles will reflect the updated framework.
What is the difference between a Competency and a Behaviour Indicator?
What is the difference between a Competency and a Behaviour Indicator?
A Competency is the skill or behavior itself (e.g., "Communication"). Behaviour Indicators are the observable, specific actions that prove someone is demonstrating that competency at a given level.