The Three-Axis Competency Model

Executive summary#

• Competency in consulting is multi-dimensional — technical skill alone doesn't predict delivery success
• The three-axis model evaluates Technical (0-4) × Business (0-4) × Agency (1-5) to produce a holistic competency score
• High technical depth with low business context creates client frustration; high agency with low technical depth creates delivery risk
• Use this model to assess internal talent, external hires, and partners on a comparable scale
• Typical successful consultant profiles: (Technical 3, Business 2, Agency 4) or (Technical 2, Business 3, Agency 4)

Definitions#

Competency Model: A structured framework for evaluating capability across multiple dimensions, producing a holistic assessment that predicts delivery success better than any single dimension alone.

The Three Axes:

• Technical (0-4): Mastery of domain-specific skills and knowledge
• Business (0-4): Understanding of how work connects to business outcomes
• Agency (1-5): Degree of ownership over problems and solutions

What this includes: Observable, assessable dimensions that predict delivery performance, client satisfaction, and project profitability.

What this does NOT include: Personality traits, cultural fit, leadership style, or non-work factors.

Key distinction: This model measures delivery capability, not potential, likability, or seniority. Someone can be senior by title but score low on all three axes.

Why this matters#

Business impact#

The three-axis model solves critical business problems:

Problem 1: Hiring mismatches

• Symptom: Strong technical interview, poor delivery performance
• Root cause: Hired for Technical only, ignored Business and Agency
• Cost: Rework, client escalations, potential contract loss
• Fix: Assess all three axes before hiring

Problem 2: Delivery risk from misalignment

• Symptom: Project delays, scope creep, client dissatisfaction
• Root cause: Technical depth doesn't match work complexity, or low agency creates bottlenecks
• Cost: Margin erosion, team burnout, reputation damage
• Fix: Match competency profile to work requirements

Problem 3: Wasted budget on "wrong" seniority

• Symptom: Expensive senior engineer produces junior-level output
• Root cause: Seniority ≠ competency; inflated titles without capability
• Cost: Paying senior rates for junior delivery
• Fix: Assess actual competency, not resume claims

Value of multi-axis assessment#

Organizations using this model report:

• Fewer hiring mistakes — better 6-month retention and performance outcomes when assessing all three axes upfront
• Improved project margins — less rework and better staffing decisions when competency profiles match work requirements
• Higher client satisfaction — fewer escalations and better client communication when business context and agency are assessed alongside technical skills
• Stronger bench strength — systematic competency assessment identifies ready-now successors for critical roles

The Model: Three Axes#

canonical_block: competency_scale
version: 1.0.0
concept_id: framework.competency_architecture
updated_date: 2026-02-16

model_name: "Three-Axis Competency Model"
description: "Holistic consulting capability assessment combining technical depth, business context, and agency excellence"

axes:
  - axis: "Technical"
    scale_reference: "scale.technical_0_4"
    range: "0-4"
    description: "Domain-specific technical mastery"
    weight_recommendation: 0.50
    link: "/competency-architecture/technical-scale"

  - axis: "Business"
    scale_reference: "scale.business_0_4"
    range: "0-4"
    description: "Business context and stakeholder awareness"
    weight_recommendation: 0.20
    link: "/competency-architecture/business-scale"

  - axis: "Agency"
    scale_reference: "scale.agency_1_5"
    range: "1-5"
    description: "Problem ownership and autonomous execution"
    weight_recommendation: 0.30
    link: "/competency-architecture/agency-scale"

scoring_formula:
  formula: "(Technical × wT) + (Business × wB) + (AgencyNorm × wA)"
  agency_normalization: "(Agency - 1) / 4"
  explanation: "Agency is normalized to 0-1 scale to match Technical and Business ranges"

recommended_weights:
  technical: 0.50
  business: 0.20
  agency: 0.30
  rationale: "Technical depth is foundational; agency creates delivery velocity; business context differentiates consultants from contractors"

score_interpretation:
  minimum_viable: 1.5
  good: 2.0
  excellent: 2.5
  exceptional: 3.0

How it works#

The scoring mechanism#

Step 1: Assess each axis independently

• Technical: Use domain-specific exercises and work samples
• Business: Use stakeholder interaction examples and trade-off discussions
• Agency: Use behavioral interviews and reference checks

Step 2: Normalize Agency to 0-1 scale

AgencyNorm = (Agency - 1) / 4

Examples:
- Agency 1 → 0.00
- Agency 3 → 0.50
- Agency 5 → 1.00

Step 3: Apply weights and calculate score

Competency Score = (Technical × 0.5) + (Business × 0.2) + (AgencyNorm × 0.3)

Maximum possible: 4.0
Minimum possible: 0.0

Why these weights?#

Technical (50%): Foundation of delivery capability

• Can't solve problems you lack skills to execute
• Highest single predictor of "can they do the work?"
• Justifies higher weight

Agency (30%): Multiplier of effectiveness

• High agency makes teams more efficient (less management overhead)
• Low agency creates bottlenecks regardless of technical skill
• Critical for consulting where autonomy is expected

Business (20%): Differentiation factor

• Separates consultants from contractors
• Critical for client satisfaction but not all roles need high levels
• Can be developed faster than technical depth

Customization: Adjust weights based on role. Internal engineers may need Technical 60%, Business 10%, Agency 30%. Client-facing consultants may need Technical 40%, Business 30%, Agency 30%.

Scores are directional, not verdicts#

The score gives you a starting point — not a hiring decision.

A 2.1 and a 2.2 are not meaningfully different. What matters is where the score sits relative to the role's requirements, and which axes are driving it. A 2.1 built on strong agency is a different hire than a 2.1 built on technical depth with low agency.

Pair every numeric score with a qualitative read:

• What does this person do when the work gets ambiguous?
• Which axis is the limiting factor for this specific role?
• Is that limitation one that develops quickly, or is it foundational?

This applies throughout the framework. On the financial and operational side, numbers can be relatively definitive — cost is cost. On the competency and talent side, numbers clarify direction; judgment closes the decision. Use the score to structure the conversation, not replace it.

Example: CaseCo Mid#

Action: Competency Assessment Worksheet#

Use this worksheet to assess candidates or existing team members:

Assessment Template#

Calculation:

AgencyNorm = (Agency - 1) / 4 = ___

Competency Score = (Technical × 0.5) + (Business × 0.2) + (AgencyNorm × 0.3) = ___

Interpretation:

• < 1.5: Not viable for consulting work
• 1.5-2.0: Junior/mid-level roles with supervision
• 2.0-2.5: Strong mid-level, some senior roles
• 2.5-3.0: Senior/principal level
• > 3.0: Exceptional, rare

Quick Reference: Typical Profiles by Role#

Role Assessment Template: Data Engineer#

Use this template to assess a data engineer against all three axes. Select the level that best describes current observable behaviour — not aspiration or potential.

How to use: Assess each axis independently using the observable signals below. Record scores in your team matrix. Reassess quarterly or after major project delivery.

Delivery-ready formula (normalised to 0–1):

Delivery-Ready Score = (T × 0.35) + (B × 0.2) + (A × 0.35) + (C × 0.1)

Where:
  T = Technical score (0–4), divided by 4 to normalise
  B = Business score (0–4), divided by 4 to normalise
  A = (Agency score − 1) / 4 to normalise 1–5 range to 0–1
  C = Complexity fit (0–4), divided by 4 to normalise

Example scores — CaseCo Mid data engineering team:

Pitfalls#

Next#

• Technical Scale — Deep dive on technical depth assessment
• Business Scale — Deep dive on business context evaluation
• Agency Scale — Deep dive on problem ownership measurement
• Complexity & Experience — Match competency to work complexity
• Competency Matrix & Scoring — Apply the model at portfolio scale

What decisions this enables#

• Whether a candidate meets the bar for a specific role based on evidence, not gut feel
• Which axis to prioritise developing in a given engineer's next growth cycle
• Whether to adjust hiring criteria when a role's requirements change
• How to staff a project when no one perfectly matches the required profile
• When to reject a strong technical performer because their agency or business scores create delivery risk

FAQs#