Complexity and Experience

Executive summary#

• Complexity measures how difficult work is independently of who does it — ambiguity, scale, integration depth, stakeholder count
• This is a 0-4 scale that helps match competency to work requirements
• The most common delivery failure: assigning complexity level 3 work to competency level 2 talent
• High complexity work (3-4) requires technical depth 3-4; mismatches create rework, delays, and client escalations
• Use this framework to staff projects correctly, set realistic timelines, and avoid delivery surprises

Definitions#

Complexity: The inherent difficulty of work based on ambiguity, system scale, integration requirements, stakeholder count, compliance constraints, and criticality — independent of who performs the work.

What it includes: Problem ambiguity, technical scope, integration points, stakeholder complexity, compliance requirements, business criticality, time pressure.

What it does NOT include: Technical depth (that's the person's capability), domain familiarity, or team dynamics.

Key distinction: Complexity is a property of the work, not the worker. The same work has the same complexity regardless of who attempts it. The question is: does the person's competency match the work's complexity?

Why this matters#

Business impact#

Correct complexity-competency matching:

• Reduces delivery risk — work is completed correctly the first time
• Improves margin — less rework, fewer escalations
• Increases velocity — no re-dos or emergency fixes
• Enhances reputation — consistent delivery builds trust

Complexity-competency mismatches:

• Complexity > Competency: Delivery failure, rework, client escalation, margin erosion, creates capability gaps
• Complexity << Competency: Wasted talent, boredom, attrition risk, opportunity cost

Cost reality of mismatches#

Example: Enterprise cloud migration (Complexity 4) assigned to Competency 2 engineer:

• Direct cost: 60% rework rate, 3-4 months of delay, 200k€+ in unplanned effort
• Indirect cost: Client escalation, reputation damage, margin drop from 40% to 15%
• Opportunity cost: Senior engineer spending 80% of time fixing junior mistakes

Fix: Match Complexity 4 work to Competency 3-4 talent. Project delivers on time, 15% rework, 40% margin maintained.

The Complexity Scale (0-4)#

canonical_block: competency_scale
version: 1.0.0
concept_id: scale.complexity_0_4
updated_date: 2026-02-16

scale_name: "Work Complexity"
description: "Inherent difficulty of work based on ambiguity, scale, and integration depth"
range:
  min: 0
  max: 4

levels:
  - level: 0
    label: "Trivial"
    description: "Routine task with clear instructions, single system, no ambiguity"
    characteristics:
      - "Step-by-step instructions exist (runbook, template)"
      - "Single system or service"
      - "No stakeholder coordination"
      - "Low criticality (non-production or isolated)"
      - "Clear success criteria"
    examples:
      - "Update firewall rule from approved change ticket"
      - "Deploy code using CI/CD pipeline following runbook"
      - "Create EC2 instance matching existing pattern"
    required_competency: "Technical 1-2, any Business, any Agency"
    time_estimate: "Hours to days"

  - level: 1
    label: "Structured"
    description: "Standard problem with known solutions, limited integration, clear scope"
    characteristics:
      - "Problem is well-understood (standard pattern applies)"
      - "2-3 systems involved, known integration points"
      - "1-2 stakeholders, clear ownership"
      - "Moderate criticality (affects one team or service)"
      - "Success criteria defined upfront"
    examples:
      - "Build REST API for new feature using team's framework"
      - "Set up VPC for new application following architecture standards"
      - "Implement authentication using existing SSO provider"
    required_competency: "Technical 2, Business 1, Agency 3"
    time_estimate: "Days to 2 weeks"

  - level: 2
    label: "Moderate"
    description: "Some ambiguity, multiple systems, requires design decisions, moderate stakeholder coordination"
    characteristics:
      - "Problem requires research and design (no clear template)"
      - "3-5 systems integration, some unknowns"
      - "3-5 stakeholders with different priorities"
      - "High criticality (affects multiple teams or revenue)"
      - "Success criteria refined during implementation"
    examples:
      - "Design data pipeline integrating 3 sources with different formats"
      - "Migrate legacy monolith to microservices (single service)"
      - "Build multi-tenant architecture for SaaS product"
    required_competency: "Technical 2-3, Business 2, Agency 3-4"
    time_estimate: "2-6 weeks"

  - level: 3
    label: "High"
    description: "Significant ambiguity, many systems, architectural decisions, complex stakeholder landscape"
    characteristics:
      - "Problem is novel or underspecified (requires discovery)"
      - "6-10+ systems, complex integration patterns"
      - "6-10+ stakeholders, conflicting requirements"
      - "Critical (revenue, compliance, or strategic impact)"
      - "Success criteria emerge through iteration"
    examples:
      - "Design multi-cloud architecture for Fortune 500 with compliance requirements"
      - "Build real-time data platform handling 100M+ events/day"
      - "Migrate 50+ applications from on-prem to cloud with zero downtime"
    required_competency: "Technical 3-4, Business 2-3, Agency 4-5"
    time_estimate: "2-6 months"

  - level: 4
    label: "Extreme"
    description: "Severe ambiguity, massive scale, unknown unknowns, executive-level stakeholders"
    characteristics:
      - "Problem is unprecedented or poorly understood (research required)"
      - "10+ systems, greenfield or major transformation"
      - "Executive stakeholders, organizational politics"
      - "Strategic bet (company success depends on outcome)"
      - "Success criteria discovered during execution"
    examples:
      - "Design and implement global infrastructure for unicorn startup scaling 10x"
      - "Re-architect entire platform for AI-first strategy"
      - "Lead technical due diligence and integration for 500M€ acquisition"
    required_competency: "Technical 4, Business 3-4, Agency 5"
    time_estimate: "6-18 months"

How it works#

Complexity assessment process#

Complexity is also shaped by which competency vertical you're assessing and the business context. Six integration points in a greenfield cloud build are different from six undocumented legacy modules. The same dimensions carry different weight depending on the domain. For a data and AI context, ambiguity and business criticality tend to be the dominant drivers; coordination overhead matters when multiple vendors or client teams are involved; scale and integration are more easily managed when the underlying architecture is sound.

Step 1: Assess the three core drivers

Scale and integration depth are worth noting but rarely change the overall complexity rating by more than one level. If in doubt, let criticality lead.

Step 2: Determine overall complexity

Let the highest dimension lead. If criticality is 4 and the rest are 1, the project is still high-complexity — the technical work may be bounded, but the stakes are not. Use judgment to land on a single rating.

Example — data & AI context:

The client wants to build a real-time product recommendation engine. The ML team has never built one before. It will feed the checkout flow, which processes most of the client's daily revenue.

• Ambiguity: 3 — the team is defining the architecture from scratch; no internal pattern to follow
• Business criticality: 4 — failure directly affects the checkout flow and daily revenue
• Coordination: 2 — two internal teams (data engineering + ML) and one client-side data owner

Result: Complexity 3 (driven by ambiguity and criticality; coordination is manageable)

Compare: If the recommendation engine fed an internal reporting dashboard with no revenue impact, criticality drops to 1. The technical work is similar — the complexity is not.

Step 3: Match to competency requirements

Complexity 3-4 requires:

• Technical: 3-4 (can handle novel problems and architectural decisions)
• Business: 2-3 (understands stakeholder priorities and trade-offs)
• Agency: 4-5 (operates autonomously, shields team from churn)

Example: CaseCo Mid#

Learning vs. delivering: Development happens through shadowing, not by assigning over-complex work.

Action: Complexity Assessment Checklist#

Use this checklist when staffing projects:

Pre-Project Complexity Assessment#

Overall complexity: Let the highest dimension lead. A criticality-4 project with low ambiguity is still a high-complexity engagement — the stakes define the required competency, not just the technical difficulty.

Competency Matching Matrix#

Staffing Rule: Match or slightly exceed complexity with competency. Never under-staff by more than 1 level.

Pitfalls#

Next#

• Competency Model — Understand the three-axis assessment framework
• Technical Scale — Deep dive on technical competency
• Talent Readiness — Use complexity matching in staffing decisions
• Competency Matrix & Scoring — Apply at portfolio scale

What decisions this enables#

• Whether to accept a project at the current team's competency level or require additional resourcing
• How to split a project into work packages matched to different competency levels
• When to invest in a senior hire versus partnering for a complexity spike
• Which engineers to assign to which work packages on a mixed-complexity project
• How to structure development plans that grow engineers through complexity levels without risking delivery

FAQs#