Executive Summary Low productivity is almost always “systemic” (multiple causes at once). The fastest way to determine what’s driving it is to run a structured diagnostic that separates:

1. capability gaps (people can’t perform),
2. structural/role design issues (people are assigned or organized poorly),
3. leadership/management behaviour issues (direction, coaching, decisions, accountability are missing), and
4. process inefficiencies (work is routed, executed, or governed poorly).

Key Recommendations (use a 5-step diagnostic)

1. Define “productivity” precisely (so you measure the right thing)

• Choose 1–2 outcomes that reflect value (e.g., cycle time to deliver, output per FTE, % tasks completed by SLA, revenue per rep, tickets resolved per day, defect rate).
• Break it down by unit and role: team, function, location, tenure bands, and process type.
• Compare trends: is it a sudden drop (change) or a steady underperformance (design/capability/system)?

Why this matters: you’re trying to find patterns (e.g., only one team, only new hires, only one product line, only after a process change).

1. Build a “cause map” using evidence, not opinions

Create a simple matrix and collect evidence for each category:

A) Capability (people can’t execute) often shows:

• Performance variance by skill level/tenure (new hires or specific competency groups are consistently lower).
• High rework, quality issues, or frequent escalation to seniors.
• People ask for instructions repeatedly; time spent “figuring out how.”
• Training/certification gaps or inconsistent job mastery.

B) Organisation structure / role design (work is not routed or owned correctly) often shows:

• Clear work is “stuck” at handoffs; cycle time expands between functions.
• Duplicate ownership (“everyone owns it, no one delivers it”) or conflicting priorities across teams.
• Decision-making is slow because the org doesn’t match the decision rights needed.
• Work moves through too many approvals; unclear role boundaries.

C) Leadership behaviour / management system (management doesn’t steer performance) often shows:

• Low clarity of priorities (teams aren’t aligned on what “good” means this week/month).
• Inconsistent goal setting, weak cadence (no effective standups, reviews, or backlog/priority governance).
• Weak problem ownership (issues linger; no corrective actions with owners/dates).
• Low coaching frequency, low accountability follow-through.

D) Inefficient processes / governance (the system is wasting effort) often shows:

• High defect/rework rates, long cycle time, or variable throughput even for capable teams.
• Bottlenecks at specific workflow steps (measurable wait times).
• Reliance on heroics to bypass constraints; lots of “shadow work” (spreadsheets, manual workarounds).
• Inputs are poor (wrong requirements, frequent changes) or governance is heavy.

1. Run “data triangulation” in a tight 1–2 week diagnostic

You’re looking for convergence across multiple data sources:

• Metrics & workflow data (hard evidence)
• Cycle time, SLA adherence, throughput, rework %, defects %, queue time, handoff counts
• Work observation / shadowing
• Observe one full end-to-end workflow (from request to delivery)
• Stakeholder interviews (structured)
• Ask the same questions to: top performers, average performers, and those struggling
• Use “last 5 incidents” prompts: What caused delays? Where did things break? What would have fixed it?
• Review of artefacts
• Job descriptions, role maps/RACI, org chart vs actual workflow, OKRs/KPIs, meeting cadence, escalation logs
• Capability signals
• Training records, competency matrix vs current skills, assessment results, onboarding effectiveness
• Leadership signals
• Monthly/weekly review quality, decision turnaround time, how managers handle issues/roadblocks

Practical approach:

• If a pattern is consistent across teams regardless of people level → likely process/structure/leadership system.
• If it clusters by tenure/skill groups → likely capability.
• If it clusters at handoffs or approval steps → likely structure/process.
• If issues correlate with absence of cadence/accountability/decision-making → likely leadership behaviour.

1. Perform targeted tests to “prove” the hypothesis (fast falsification)

Instead of trying to solve everything, run controlled interventions that isolate causes:

Capability test

• Provide short, targeted enablement for a specific competency gap (e.g., 2–5 day micro-training + coaching).
• If productivity improves measurably within 2–6 weeks for that group → capability was a major driver.

Structure test

• Clarify ownership using a lightweight RACI/role charter for the workflow.
• Reduce handoffs (or assign a single “process owner”).
• If cycle time/throughput improves quickly → structure/role design was a major driver.

Leadership test

• Introduce a performance cadence: weekly planning + daily/3x-week control (15–20 mins) + escalation with owners/dates.
• Hold managers to measurable behaviours (e.g., coaching hours, action closure rate, decision turnaround).
• If improvement follows → leadership behaviour/process of management was a major driver.

Process test

• Map the workflow and remove the top 1–2 bottlenecks (e.g., eliminate unnecessary approvals, standardize intake requirements, automate a repetitive step).
• If metrics improve immediately (wait time drops) → process inefficiency is a major driver.

This “test then invest” approach prevents you from running expensive training when the real issue is role clarity or workflow design.

1. Use a simple scoring model to prioritize root causes

For each category (Capability / Structure / Leadership / Process), score based on evidence:

• Impact potential (how much productivity could rise if fixed)
• Prevalence (how widespread the issue is across teams/processes)
• Speed to change (can you fix in 30–60 days?)
• Strength of evidence (data + observations + consistent narratives)

Prioritization rule of thumb

• Start with the “high evidence + high impact + fixable fast” items—usually process and operating cadence, sometimes role clarity.
• Train/capability interventions once you confirm the workflow/management system isn’t blocking execution.

Business Impact (what you gain by doing this right)

• Faster improvement (you stop treating symptoms)
• Better ROI on spend (training where skills are truly missing; process redesign where throughput is constrained)
• Reduced churn and frustration (teams know what changed and why)
• Clear accountability (what leaders, what functions, and what systems own the outcomes)

Risks (and how to avoid them)

• Risk: “Capability blame” bias
• Fix: always compare results by team vs by skill/tenure, and look for rework/cycle-time patterns.
• Risk: “Process blame” without leadership clarity
• Fix: ensure decision rights, cadence, and escalation routes exist; otherwise teams will just work harder around a broken system.
• Risk: Running training and org changes simultaneously
• Fix: do 1–2 targeted tests first, then scale.

Immediate Next Steps (practical plan for your first 14 days)

• Day 1–2: Define productivity metric(s) + baseline by team/workflow step.
• Day 3–5: Collect workflow data + job/role clarity artefacts (RACI, decision rights, KPIs/OKRs, meeting cadence).
• Day 6–9: Shadow 1–2 critical workflows end-to-end + run structured interviews (top/average/low performers).
• Day 10–12: Create evidence dashboard and initial cause hypotheses (Capability vs Structure vs Leadership vs Process).
• Day 13–14: Pick the top 1–2 tests (one capability, one structure/leadership/process) and define success metrics.

Three quick questions (only if you want to tailor the diagnostic)

1. What does “productivity” mean in your context—output, cycle time, sales, tickets, quality, or something else?
2. Is the underperformance concentrated in specific teams/process steps or spread evenly?
3. Did productivity drop after a specific change (reorg, new system, new product, leadership change, process update)?

If you need help implementing these recommendations or would like expert guidance tailored to your organization, the team at Zunavish would be happy to assist.