What Is a Competency Matrix?
A competency matrix maps role-relevant skills to defined proficiency levels and observable evidence. It can make assessment more consistent, but it does not remove judgment: organizations must define the role, rating criteria, evidence period, reviewers, and calibration process.
Treat the matrix as an organization-specific development tool. Record examples of performance, compare ratings across reviewers, and turn gaps into a dated development plan.
Example Four-Level Proficiency Scale
There is no universal four-level scale. The example below works only when each level has observable behavioral anchors and the organization applies them consistently:
Beginner
Requires close supervision; possesses basic understanding of the competency. Can perform routine tasks with guidance. Learning terminology and foundational concepts.
Intermediate
Performs tasks independently under normal conditions. Understands underlying principles and can handle typical situations without assistance. Building practical experience.
Advanced
Deep expertise; capable of mentoring others and handling difficult situations. Adapts approaches to complex scenarios. Recognized as go-to resource within team.
Expert
Recognized authority; leads innovation and enterprise-wide strategy. Sets standards and best practices. Influences direction beyond immediate team.
Core PM Competencies
Use these as example categories, then adapt them to the role and context. PMI's current Talent Triangle groups development into Ways of Working, Power Skills, and Business Acumen; an employer's matrix may use different categories.
Technical Competencies
Scope Management
Defining, documenting, and managing what is—and isn't—included in the project. Creating WBS, managing change requests, and preventing scope creep.
Schedule Management
Developing realistic timelines, sequencing activities, identifying critical paths, and managing dependencies. Proficiency with scheduling tools (MS Project, JIRA).
Cost Management
Budget development, earned value analysis, forecasting, and cost control. Understanding of EVM metrics (CPI, SPI, CV, SV).
Risk Management
Identifying potential threats, assessing probability and impact, developing mitigation strategies. Maintaining risk registers and conducting risk reviews.
Quality Management
Defining quality standards, implementing quality assurance processes, conducting quality control reviews. Understanding of Six Sigma and continuous improvement.
Methodology Application
Applying appropriate PM methodologies (Waterfall, Agile, Hybrid) based on project characteristics. Understanding frameworks like PMBOK, PRINCE2, Scrum.
Leadership Competencies
Strategic Thinking
Connecting project objectives to organizational strategy. Understanding business context and making decisions that maximize business value.
Stakeholder Engagement
Identifying stakeholders, understanding their interests, managing expectations, and building coalitions. Political awareness and influence skills.
Team Leadership
Building high-performing teams, motivating individuals, developing talent, and managing performance. Creating psychologically safe environments.
Communication
Tailoring messages to audiences, facilitating meetings, presenting to executives, active listening. Written and verbal communication excellence.
Conflict Resolution
Addressing disagreements constructively, mediating disputes, finding win-win solutions. Managing difficult conversations and team dynamics.
Emotional Intelligence
Self-awareness, self-regulation, empathy, and social skills. Reading situations, managing stress, and adapting approach to individuals.
Competency Expectations by Career Level
Illustrative expectations only: map each role to its actual scope, decision authority, project complexity, and required evidence:
| Career Level | Technical | Leadership |
|---|---|---|
| Illustrative: Entry-Level (Coordinator) | Level 1-2 across technical competencies | Level 1 in leadership; building awareness |
| Illustrative: Mid-Level (Project Manager) | Level 2-3 across technical competencies | Level 2 in most leadership areas |
| Illustrative: Senior Level (Program Manager) | Level 3-4 in key technical areas | Level 3 in leadership; developing expertise |
| Illustrative: Executive (Director/VP) | Level 4 strategic; delegates tactical execution | Level 4 across leadership competencies |
Key Takeaways
- 1Define competencies for a specific role and context instead of adopting a universal list
- 2Use observable behaviors and work evidence, not labels such as beginner or expert alone
- 3A four-level scale is one option; rating anchors and calibration matter more than the number of levels
- 4Balance Ways of Working, Power Skills, and Business Acumen for project roles
- 5Use self-assessment as one input and compare it with manager, peer, stakeholder, and delivery evidence
- 6Turn priority gaps into a development action, owner, evidence target, and review date