Capability Mirage

The project team's actual capability doesn't match what governance assumes. The gap is invisible until delivery pressure reveals it, because nobody audits the distance between role requirements and real competency.

Recognition signals

1. Resources are assigned to roles they're not qualified for — and this is discovered weeks or months in. The org chart shows the role as filled. The project plan shows the resource as allocated. Nobody checked whether the person can actually do the work until a deliverable fails.
2. SMEs who know their domain but refuse project discipline. They have the technical knowledge but won't work within governance structures — no status updates, no risk escalation, no adherence to decision frameworks. The capability is real but ungovernable.
3. BAU managers send underperformers to the project to avoid managing them. The project becomes a release valve for performance problems that BAU doesn't want to address. The project gets a warm body; BAU gets relief from a difficult conversation.
4. Capability gaps only surface under delivery pressure. During planning and early execution, everyone looks competent. It's when deadlines compress, dependencies tighten, and quality matters that the gap between the role and the person becomes visible.
5. Role descriptions are generic without mapping to specific project competencies. "Business Analyst" or "Technical Lead" is listed on the resource plan without specifying what BA or tech lead skills this particular project requires. The generic title masks the specific gap.

Structural cause

The "mirage" is that governance assumes the team is capable because roles are filled. Resource plans show names against roles. The project board sees a fully resourced team. But "filled" and "fit" are different things, and the distance between them is invisible in every standard governance artefact. No status report measures the gap between what the role requires and what the person can deliver.

The pattern persists because exposing it is politically expensive. Telling a BAU manager "the person you sent us can't do this work" creates conflict. Telling the project board "we're fully resourced but not fully capable" sounds like the PM making excuses. The easier path is to absorb the gap — redistribute work to stronger team members, lower quality standards quietly, or delay until the gap becomes someone else's problem.

Risk mapping

Self-assessment

Related reading

• Authority Vacuum — when capability gaps aren't addressed, the PM absorbs the work by default
• Compliance Theatre — governance assumes capability because roles are filled, which is its own form of theatre
• Transition Cliff — capability gaps compound at project boundaries when knowledge doesn't transfer
• Proxy Competence — a specific manifestation where the resource conceals the gap by relaying others' expertise