Proxy Competence
A resource presents borrowed expertise as their own and doubles down when challenged because admitting uncertainty would expose the dependency.
A resource presents borrowed expertise as their own. They can't think critically about the domain, so they relay other people's positions without understanding them — and double down when challenged because admitting uncertainty would expose the dependency.
Recognition signals
- Can never answer a direct question in a meeting — always needs to "check and get back." The pattern is consistent: any question requiring domain reasoning triggers the same response. The answers arrive later, polished, sourced from someone else.
- Makes calls after meetings to get positions from others. The proxy's first action after a governance meeting is to phone the person who actually knows. The delay between question and answer is the transit time to the real source.
- Cannot debate at the fact level — repeats position louder when challenged. When pressed on reasoning, the proxy can't explain the "why" behind their position because they didn't produce it. The response to challenge is volume and certainty, not evidence and reasoning.
- Gap between written output (polished, sourced) and verbal contribution (vague, deflecting). Deliverables look competent because they were assembled from others' input. But in meetings — where real-time reasoning is required — the gap is visible to anyone paying attention.
- Colleagues learn to bypass the proxy and go directly to the source. The team figures out who actually knows things. The proxy becomes a bottleneck that people route around, which further reduces the proxy's visibility into what's actually happening.
Structural cause
Why this happens
The resource was placed in a role that exceeds their capability — often a Capability Mirage consequence — and governance doesn't surface the gap because outputs are assessed, not the process of producing them.
The proxy survives because deliverables are the unit of measurement. A status report that reads well, a risk assessment that covers the right areas, a recommendation paper that reaches a reasonable conclusion — all look adequate on paper. Nobody audits how the deliverable was produced. The proxy assembles outputs from the people who actually understand the domain, adds structure and formatting, and presents the result as their own work.
The concealment is self-reinforcing. The proxy can't admit the gap because it would retroactively invalidate everything they've produced. Each deliverable deepens the commitment to the fiction. And the people being proxied often don't realise the extent of it — they think they're helping a colleague, not propping up an incompetence structure. The pattern only breaks when delivery pressure creates a situation that requires real-time domain reasoning with no time to phone a friend.
Risk mapping
| Risk | Description |
|---|---|
| Risk mapping for this pattern is under development. The closest existing risk is G7 (competency gap), but the concealment mechanism is distinct. | |
Self-assessment
When to worry
- A team member consistently needs to "check and get back" on direct questions in their domain
- Written output quality is conspicuously higher than verbal contributions
- Colleagues bypass someone and go directly to their information sources
- Someone doubles down on positions they can't explain when challenged
When you're OK
- Resources can demonstrate first-principles reasoning in meetings
- Deliverable provenance is transparent — sources are attributed, not concealed
- Team members engage in fact-level debate and adjust positions based on evidence
Related reading
- Capability Mirage — the upstream pattern that places resources in roles exceeding their capability
- Information Fog — the proxy creates a fog layer between the real source and the governance structure
- Narrative Capture — the proxy's polished outputs can become the accepted narrative, displacing more accurate but less formatted information
- Incentive Inversion — the proxy's rational self-interest (concealment) produces collectively irrational outcomes (uninformed decisions)
The proxy survives because outputs are assessed, not the process of producing them — until delivery pressure reveals the dependency.
A programme health check assesses team capability at the reasoning level, not just the deliverable level. 10fifteen — programme governance assessments.