1.2 The ICB4 Eye of Competence & Competence Concept

1.2 The ICB4 Eye of Competence & Competence Concept

Quick Summary: The Individual Competence Baseline Version 4.0 (ICB4) is IPMA's global standard defining the 28 competence elements required for modern project management. Represented visually as the "Eye of Competence," the framework organizes professional capability into three vital competence areas: Perspective (5 contextual elements), People (10 personal and social elements), and Practice (13 technical elements). Each element is operationalized through Key Competence Indicators (KCIs) that serve as concrete assessment benchmarks.

---

1. The ICB4 Standard and the Definition of Competence

The IPMA Individual Competence Baseline Version 4.0 (ICB4) represents the culmination of decades of international research into what makes project practitioners genuinely effective. Unlike manuals that merely document processes or standardized workflows, the ICB4 serves as a comprehensive inventory of human competence.

The Tripartite Definition of Competence

ICB4 states the definition in one plain-English sentence. Learn it verbatim — it is the single most quotable line in the standard:

"Individual competence is the application of knowledge, skills and abilities in order to achieve the desired results."

ICB4 then defines each of the three terms, using one running example (a Gantt chart) to separate them:

1. Knowledge (The "Know-What" & "Know-Why"): "the collection of information and experience that an individual possesses." ICB4's example: understanding the concept of a Gantt chart. Knowledge provides the intellectual architecture required to diagnose problems and design appropriate solutions.
2. Skills (The "Know-How"): "specific technical capabilities that enable an individual to perform a task." ICB4's example: being able to build a Gantt chart. Skills let an individual operate scheduling software, facilitate a risk workshop, or construct a Work Breakdown Structure (WBS).
3. Abilities (Delivery in Context): "the effective delivery of knowledge and skills in a given context." ICB4's example: being able to devise and successfully manage a project schedule. Ability is where self-control during crises, ethical steadfastness, and judgement about timing actually show up.

ICB4 stresses that the three are cumulative and hierarchical: "having a skill presupposes some relevant knowledge. Having ability presupposes relevant skills and knowledge, but adds to that the use of these in practice, in the right manner and at the right time." Context is therefore not a fourth ingredient of the definition — it is the condition under which ability is judged. The same knowledge and skills produce competence in one organizational culture, regulatory framework, and stakeholder environment and fail in another, which is exactly why IPMA assesses Level D candidates through project scenarios rather than isolated definitions.

       ┌────────────────────────────────────────────────────────┐
       │                       COMPETENCE                       │
       ├────────────────────────────────────────────────────────┤
       │   KNOWLEDGE    +     SKILLS     +      ABILITIES       │
       │  ("Know-What")     ("Know-How")      ("Delivery in Use")│
       ├────────────────────────────────────────────────────────┤
       │           DEMONSTRATED IN A SPECIFIC CONTEXT           │
       │     (Organizational, Political, Cultural & Social)     │
       ├────────────────────────────────────────────────────────┤
       │                 TO ACHIEVE DESIRED RESULTS             │
       └────────────────────────────────────────────────────────┘

---

2. The Architecture of the "Eye of Competence"

To visualize the complete practitioner, IPMA introduced the iconic "Eye of Competence" metaphor. The eye represents human vision, clarity, focus, and the ability to perceive a project environment from multiple complementary vantage points simultaneously.

The Eye of Competence integrates 28 Project Competence Elements organized across three distinct, balanced competence areas. (ICB4 reserves the word domain for project, programme, and portfolio management — a distinction that matters when reading the certification rules in the next section.)

                  ╭─────────────────────────────────────╮
                  │       PERSPECTIVE COMPETENCES       │
                  │             (5 Elements)            │
                  │   Contextual: "Why" and "Where"     │
                  ╰──────────────────┬──────────────────╯
                                     │
           ╭─────────────────────────┴─────────────────────────╮
           │                                                   │
╭──────────┴──────────╮                             ╭──────────┴──────────╮
│  PEOPLE COMPETENCES │                             │ PRACTICE COMPETENCES│
│    (10 Elements)    │     PROJECT PROFESSIONAL    │    (13 Elements)    │
│ Personal & Social:  │       IN PERSPECTIVE        │     Technical:      │
│       "Who"         │                             │   "How" & "What"    │
╰─────────────────────╯                             ╰─────────────────────╯

1. Perspective Competences: The Contextual Domain (5 Elements)

Perspective elements address the broader ecosystem in which the project is conceived, funded, and governed. They answer the questions "Why is this initiative being undertaken?" and "Where does it fit in the strategic and societal environment?"

• 4.3.1 Strategy: Alignment with enterprise mission, vision, strategic objectives, and benefits realization.
• 4.3.2 Governance, structures and processes: Organizational systems, corporate governance, steering committees, decision gates, and PMO structures.
• 4.3.3 Compliance, standards and regulations: Legal statutes, health and safety regulations, ISO standards, labor laws, and data security mandates.
• 4.3.4 Power and interest: Informal political landscapes, authority dynamics, stakeholder agendas, and building supportive coalitions.
• 4.3.5 Culture and values: Corporate identity, organizational values, societal ethics, and cross-cultural communication patterns.

2. People Competences: The Personal & Social Domain (10 Elements)

People elements address the human dynamics, behavioral proficiencies, and interpersonal capabilities required to collaborate with and lead diverse project participants. They answer the question "Who is doing the work and interacting with stakeholders?"

• 4.4.1 Self-reflection and self-management: Emotional intelligence, self-awareness, stress management, work-life balance, and continuous self-improvement.
• 4.4.2 Personal integrity and reliability: Ethical commitment, transparency, adherence to the IPMA Code of Ethics, taking accountability, and keeping promises.
• 4.4.3 Personal communication: Active listening, structured messaging, verbal and non-verbal expression, feedback loops, and open communication channels.
• 4.4.4 Relationships and engagement: Building professional rapport, fostering empathy, creating psychological safety, networking, and sharing your own vision to gain the commitment of others.
• 4.4.5 Leadership: Direction, inspiration, coaching, mentoring, empowering team members, and situational leadership adaptation.
• 4.4.6 Teamwork: Team development dynamics (Forming, Storming, Norming, Performing), managing diverse team roles, and driving collective synergy.
• 4.4.7 Conflict and crisis: Diagnosing root sources of interpersonal friction, conflict escalation models, negotiation, and decisive crisis interventions.
• 4.4.8 Resourcefulness: Creative problem-solving, lateral thinking, root cause analysis, open-minded inquiry, and intellectual curiosity.
• 4.4.9 Negotiation: Interest-based bargaining (Harvard model), establishing BATNA (Best Alternative to a Negotiated Agreement), and achieving sustainable win-win agreements.
• 4.4.10 Results orientation: Relentless focus on deliverables, efficiency, overcoming obstacles, managing scope-cost-time trade-offs, and value realization.

3. Practice Competences: The Technical Domain (13 Project Elements)

Practice elements encompass the specific technical tools, methodologies, techniques, and artifacts utilized to plan, execute, and control projects. They answer the questions "How will the project be delivered?" and "What mechanisms will control its progress?"

• 4.5.1 Project design: Crafting the overarching project delivery strategy, tailoring lifecycles, and choosing predictive, agile, or hybrid models.
• 4.5.2 Requirements and objectives: Eliciting stakeholder needs, defining SMART goals, managing requirements traceability, and acceptance criteria.
• 4.5.3 Scope: Establishing project boundaries, developing the deliverable-oriented Work Breakdown Structure (WBS), and guarding against scope creep.
• 4.5.4 Time: Activity sequencing, schedule network analysis, Critical Path Method (CPM), milestone tracking, and schedule compression techniques.
• 4.5.5 Organisation and information: Defining team roles and responsibilities (RACI matrix), communication management plans, and project management information systems (PMIS).
• 4.5.6 Quality: Quality planning, Quality Assurance (QA), Quality Control (QC), cost of quality, and continuous improvement (Deming PDCA cycle).
• 4.5.7 Finance: Cost estimating, budget formulation, cash flow forecasting, and Earned Value Management (EVM) performance tracking.
• 4.5.8 Resources: Identifying, acquiring, leveling, and smoothing human, physical, and material resources across project schedules.
• 4.5.9 Procurement: Make-or-buy analysis, vendor tendering, contract types (Fixed Price, Cost-Reimbursable, Time & Materials), and supplier oversight.
• 4.5.10 Plan and control: Establishing the integrated project management plan baseline, variance monitoring, and formal integrated change control.
• 4.5.11 Risk and opportunity: Systematic identification, qualitative and quantitative assessment, and proactive response strategies for threats and positive opportunities.
• 4.5.12 Stakeholders: Comprehensive identification, interest-power grid mapping, and continuous stakeholder engagement strategies.
• 4.5.13 Change and transformation: Managing organizational transition, addressing user resistance, Kotter/Lewin change models, and post-project operational integration.

(Note: ICB4 also defines a 14th Practice element, Select and balance — but only in the programme domain (5.5.14) and the portfolio domain (6.5.14). It is marked "n.a." for projects, and there is no 4.5.14. For the project management domain assessed at Level D, exactly 28 elements apply. ICB4 counts 29 competence elements in total across all three domains for this reason.)

---

3. Structural Anatomy of an ICB4 Competence Element

Every single competence element in the ICB4 standard is codified with an identical, rigorous internal structure:

┌───────────────────────────────────────────────────────────────┐
│              ANATOMY OF AN ICB4 COMPETENCE ELEMENT            │
├───────────────────────────────────────────────────────────────┤
│ 1. Element Code & Title (e.g., Practice 4.5.3 Scope)         │
│ 2. Description (Context, purpose, and professional rationale) │
│ 3. Knowledge Items (Concepts, frameworks, tools, principles)  │
│ 4. Skills and Abilities (Observable behavioral proficiencies) │
│ 5. Key Competence Indicators (KCIs) (Assessment benchmarks)   │
└───────────────────────────────────────────────────────────────┘

1. Title and Unique Code: Alphanumeric identifier linking the element to its competence area (e.g., 4.3.X for Perspective, 4.4.X for People, 4.5.X for Practice) within the project domain (chapter 4 of ICB4).
2. Element Description: A concise narrative detailing the nature of the competence, why it is critical for project success, and how it interacts with other baseline elements.
3. Knowledge Items: A detailed catalog of theoretical models, standard frameworks, historical concepts, formulas, and terminology that the practitioner must understand.
4. Skills and Abilities: Specific actions, behavioral traits, analytical skills, and communication patterns required to execute the element in real-world scenarios.
5. Key Competence Indicators (KCIs): The operational core of the element—standardized, measurable indicators that define what competent performance looks like in practice.

---

4. Key Competence Indicators (KCIs) and Their Assessment at Level D

How KCIs Function as Measurable Benchmarks

A Key Competence Indicator (KCI) is a concrete, observable statement describing specific behavior or cognitive demonstration of a competence. Across the 28 project elements, each competence element contains between 3 and 7 individual KCIs — 4.3.4 Power and interest has the minimum of three, while 4.3.2 Governance, structures and processes has the maximum of seven. The project domain contains 133 KCIs in total.

For example, within Practice Element 4.5.3 (Scope), the KCIs include:

• KCI 4.5.3.1: Define the project deliverables
• KCI 4.5.3.2: Structure the project scope (e.g., Work Breakdown Structure)
• KCI 4.5.3.3: Define the work packages of the project
• KCI 4.5.3.4: Establish and maintain scope configuration

For each KCI, the ICB4 details specific measures, such as: "Identifies outputs delivered during the project lifecycle," "Uses a deliverable-oriented decomposition," and "Validates completion criteria with stakeholders."

Level D Cognitive Depth vs. Higher Certification Levels

The fundamental difference between IPMA Level D and higher tiers (Levels C, B, and A) lies in how KCIs are demonstrated:

• At Levels C, B, and A: Candidates must provide verified workplace evidence (written project reports, documented decisions, sponsor references, and panel interviews) proving that they personally led teams, exercised power, managed real crises, and delivered results against these KCIs in complex environments.
• At Level D: Candidates are assessed on broad cognitive comprehension and situational application across all 28 elements. In the written exam, candidates demonstrate that they understand what each KCI means, why it is essential, what tools and techniques are used to fulfill it, and how an associate should respond in realistic project scenarios.

This makes Level D the ultimate holistic foundation: it ensures that before a professional takes on autonomous command of complex projects, they possess a complete 360-degree mental map of every human, technical, and organizational factor that drives project success.