See where work is getting stuck — and why busy teams are not producing enough.
Teams can be fully occupied and the business can still be short of output. Workforce & Productivity Intelligence looks at the system of work rather than the effort inside it — where work waits, where it goes backwards, where it changes hands, and which single stage is setting the pace for everything else. The output is a small number of changes management can make to the way work flows, before adding people or automating anything.
21 days · Baseline → Diagnose → Redesign → Act → SystemiseTwelve points of work. Eighty-eight points of waiting.
Adding people increases the first bar. It does very little to the other four.
ILLUSTRATIVE — SYNTHETIC DATA Index points across one workflow, constructed for explanation only. Not client data, not a benchmark, and not an indication of typical workflow performance.
What this helps management answer
- Where is work actually getting stuck, and for how long?
- Which single stage is setting the pace of the whole workflow?
- How much of our elapsed time is work, and how much is waiting?
- How much capacity is being consumed by rework, and where does that rework originate?
- How many of our exceptions are genuine, and how many have become habit?
- Which approvals actually change an outcome?
- Do we need more people, or do we need the work to move differently?
- If we released capacity tomorrow, what would we do with it?
Activity is not productivity.
Most operational reporting measures how occupied people are. Very little of it measures whether work is moving. A team can be at full utilisation while the workflow it sits in is barely producing, and every measure on the dashboard will look healthy.
What usually gets measured
- Hours worked
- Utilisation
- Tickets or items touched
- Emails and calls handled
- Attendance and presence
- Individual throughput
- Effort visible to a manager
What actually determines output
- Elapsed time end to end
- Time spent waiting rather than being worked on
- The pace set by the constraint stage
- How often work goes backwards
- How much volume leaves the standard path
- What is lost at each hand-off
- Completed units of business output
Busy is not the same as productive. The workflow decides which one you get.
From managing activity to managing the flow of work
- Everyone is busy
- Output is flat
- Escalations repeat
- Lead times have crept up
- Hiring is the proposed answer
- No agreed picture of where work stops
- Each team can explain its own part only
- Where work waits, and for how long
- Which stage sets the pace
- Where rework originates
- Which approvals change an outcome
- Which exceptions are genuine
- The changes worth making first
- Named owners, dates and measures
- What released capacity is for
The shift is from managing activity to managing the flow of work.
From demand to business output, stage by stage
What we look for at each stage
How the 21-day engagement works
Readiness, Scope & Definitions
Day 0Agree what is in scope and what “done” means before anything is measured.
- Workflows in scope
- Start and end points
- Teams involved
- Stage owners today
- Definition of a completed unit
- Business outcomes the workflows serve
- Data sources and access
- Interview slots
- Named operations owner
- Escalation route
Baseline
Days 1–5Establish what happens today, as distinct from what the process document says happens.
- Volume by workflow and stage
- Elapsed time end to end
- Elapsed time per stage
- Queue time
- Rework rate
- Exception rate
- Hand-off count
- Data limitations
Flow & Friction Diagnosis
Days 6–10Separate the real constraint from the loudest complaint. Friction is felt downstream of where it is caused.
- Constraint stage
- Queue behaviour
- Capacity versus decision waits
- Hand-off loss
- Approval load
- Rework origin
- Exception density
- Operational interviews
Prioritise & Redesign
Days 11–16Rank by output released against effort and disruption, then clear the constraint first. Fixing a non-constraint stage produces activity, not output.
- Ranked friction register
- Constraint-stage redesign
- Decision rights
- Approval thresholds
- Standard path versus exception path
- Hand-off design
- Disruption risk
Systemise & Readout
Days 17–21Convert agreed changes into owned actions, then present the findings and the plan to management.
- Action register
- Named owners and dates
- Expected effect per action
- Monthly operating measures
- Measures to stop watching
- 90-minute Management Readout
Measured in output and elapsed time, against the Day 0 baseline
Three later checkpoints, timed to how long workflow changes actually take to read. The engagement is judged on the same measures it started with.
Day 30
Did the changes happen. Action register reviewed against owners and dates, so anything that has quietly not started surfaces while restarting it is still cheap.
Day 60
Is the flow moving. Elapsed time, queue time and rework rate re-measured against baseline, with wrong changes separated from incomplete ones.
Day 90
Has output changed and held. Output per period against baseline, held for a full cycle rather than a good month.
What the client receives
Workflow Baseline & Definition Register
Each workflow mapped stage by stage with volume, elapsed time, queue time, rework rate and exception rate — plus the definitions, exclusions and data limitations agreed before any judgement is made.
Flow, Friction & Constraint View
Where work stops, why it stops, and which single stage sets the pace. Includes hand-off loss, approval load, and the origin of rework as distinct from the stage that absorbs it.
Ranked Improvement Register
Every friction point scored on effect on output, effort to change and disruption risk, then ranked. Separates what is worth doing now, what is worth doing later, and what is not worth doing at all.
Stage & Decision Redesign
The constraint stage and the two next-heaviest points redesigned: sequence, decision rights, approval thresholds, standard path versus exception path, and what must travel with the work at each hand-off.
Action Register & Operating Measures
Prioritised actions with issue, stage, evidence, owner group, action, expected effect, priority and status — plus the short set of measures management should watch monthly, and the ones to stop watching. Owned and executed by your teams.
Two further modules — only where the data is reliable enough
Capacity & Cost-to-Serve View
Where cost data can be attached to workflow stages with enough confidence to support a management conversation. Requires credible allocation, not an average applied evenly across every stage.
Automation Readiness View
Which stages are stable, high-volume and rule-based enough to be worth automating, and which are not. Run after the workflow has been simplified — automating an unnecessary step makes the unnecessary step permanent.
The workflow view management works from
Not a productivity scoreboard. A list of stages, what is happening at each one, and what management should change.
| Workflow | Stage | Queue (index) | Rework | Exception | Owner group | Friction | Management action |
|---|---|---|---|---|---|---|---|
| Order to dispatch | Credit & pricing approval | 184 | 6% | 31% | Commercial | Constraint | Threshold the approval; escalate only above the limit |
| Order to dispatch | Pick & pack | 71 | 4% | 9% | Warehouse | Flowing | No change — adding people here would not move the workflow |
| Order to dispatch | Documentation | 96 | 22% | 18% | Back office | Rework absorbed here | Fix at origin — incomplete order capture upstream |
| Customer onboarding | Document collection | 212 | 11% | 44% | Sales support | Constraint | One request at the point of sale, not four in sequence |
| Customer onboarding | Verification | 88 | 9% | 12% | Finance | Hand-off loss | Context travels with the file; stop rebuilding it at each hand-off |
| Customer onboarding | System setup | 64 | 3% | 7% | Operations | Flowing | Candidate for automation readiness — after simplification |
| Service resolution | Triage | 57 | 8% | 26% | Service desk | Exception habit | Redraw the standard path so it carries the volume it should |
| Service resolution | Second-line review | 167 | 19% | 38% | Technical | Constraint | Delegate two decision types down; keep the third escalated |
| Service resolution | Closure & confirmation | 43 | 5% | 6% | Service desk | Flowing | No change |
ILLUSTRATIVE — SYNTHETIC DATA Constructed for explanation only. Queue and rework are shown as an index and a rate, not as hours or money. Nothing here implies a typical productivity gain, an expected output increase, a guaranteed cost reduction, or a typical return.
Read the table by column, not by row. Three stages carry the constraint. Two carry rework that originates elsewhere. Four are already flowing — and the standard instinct, to add people to the busiest-looking stage, would have landed on at least one of those four.
Released capacity is not a salary saving.
If a redesign frees the equivalent of two people’s time across five teams, nothing has been saved. Capacity has been released. Whether it becomes value depends entirely on what management does with it next.
Released capacity becomes value when
- It absorbs growth that would otherwise have required hiring
- It is redirected to work the business is currently not doing
- It removes overtime or temporary cover that is genuinely being paid for
- It shortens a lead time customers are reacting to
It is not value when
- It is counted as a salary saving while every salary is still being paid
- It is spread thinly and reabsorbed into the same workflow
- The hours are theoretical — a few minutes here and there across forty people
- The same benefit is also claimed elsewhere as a revenue or margin gain
Where a workflow change also improves collections, stock or service, that benefit is counted once, in one place, with one owner. Improvements that appear in three business cases are how an organisation reaches year end having delivered a great deal on paper and very little in the accounts.
We will tell you what capacity has been released. We will not convert it into a rupee saving on your behalf.
Improve the system of work — not monitor people.
This is not a headcount-reduction programme. It is designed to raise what the business produces from the capacity it already has. Where it releases capacity, the recommendation is where to deploy it — not who to remove.
Explicitly excluded
- Keystroke monitoring
- Mouse or activity tracking
- Screen-time surveillance
- Webcam monitoring
- Online-status monitoring
- Covert location tracking
- Covert review of private communications
- Individual productivity league tables
Why the boundary matters
Teams tell you where work is stuck. They stop telling you the moment they believe the answer will be used against them. A workforce engagement perceived as a monitoring exercise loses access to the information it depends on, and the findings degrade within days. The boundary is what makes the diagnosis accurate.
Outputs from this engagement are not the sole or determinative basis for hiring, firing, redundancy selection, compensation, discipline, promotion or demotion. Workflow data describes a system. It is not a performance assessment of the people working inside it, and it is not built to carry that weight. Where a people question genuinely arises, it belongs to your leadership and your HR process, with human evidence attached.
AI assists. Humans remain accountable.
How AI is used — and where it stops
AI and analytics may assist
- Sequence analysis across large volumes of workflow records
- Queue and wait-time pattern detection
- Clustering of exception types described differently but behaving alike
- Rework-origin tracing
- Constraint testing across the full data set rather than a sample
- Prioritisation support
- Summarisation
- Recommendation drafting
Humans remain accountable for
- Process change
- Decision rights and approval thresholds
- Staffing
- People decisions
- Automation investment
- Software selection
- Customer commitments
- Anything with a contractual consequence
Is this the right starting point?
A good starting point when
- Volumes have grown and the organisation is absorbing it with effort rather than with system
- Teams are visibly busy and output is flat
- Hiring is being proposed and nobody has tested whether current capacity is being used
- Lead times have crept up and no single reason explains it
- The same problems are escalated repeatedly with no structural fix
- Automation is being considered and you want the process simplified before it is fixed in software
- At least 90 days of workflow history exists, six months preferred
- At least 100 completed items per workflow exist
- Timestamps exist at enough stages to show where work waits
- A named operations owner is available
Not the right starting point when
- What is actually wanted is a headcount reduction with an operational justification attached
- The requirement is individual performance monitoring
- The business is mid-restructure and these workflows will not exist in 90 days
- No operational data exists and nobody is available to reconstruct it
- The constraint is already known and agreed, and what is needed is implementation
- There is no management appetite to change decision rights or approvals
- The real problem is demand, pricing, stock or collections alone
- The requirement is software implementation
What it costs
India · 21-day engagement
- On confirmation
- 50%
- At the Day-21 Readout
- 50%
- Day-30 / 60 / 90 checkpoints
- Included, and not a payment trigger
India public pricing only — pricing for another geography is published once that country variant has separately cleared pricing.
What one engagement covers
- One legal entity
- Up to 3 workflows
- Up to 5 teams
- Up to 18 workflow stages in total
- At least 90 days of history, six months preferred
- At least 100 completed items per workflow
- Up to 120 exception cases requiring individual judgement
- Up to 40 priority actions
- Up to 6 source exports
- Secondary data cap of up to 250,000 rows
- Up to four 45-minute operational interviews
- One 90-minute Management Readout
- Day 30, 60 and 90 checkpoints
- One round of updates to the deliverables after the Readout
Included
- Workflow baseline and definition register
- Flow, friction and constraint view
- Ranked improvement register
- Stage and decision redesign
- Action register and operating measures
- Management Readout
- Day 30, 60 and 90 checkpoints
Not included
- Implementation of the actions
- Software selection, purchase or configuration
- Automation build
- Building operational data where none exists
- Full process-documentation rewrite
- Day-to-day operational management
- Individual performance assessment
- Employee monitoring or surveillance of any kind
- Employee ranking
- Organisation design, grading or restructuring
- Redundancy planning
- Compensation design
- Recruitment
- Multi-entity workflow harmonisation
- Ongoing monitoring service
What this engagement owns — and what it does not
Workforce & Productivity Intelligence owns the flow of work through the organisation. Where the evidence points to a different cause, that is a different starting point — and a separate engagement requires a separate evidenced problem, not the same value pool counted twice.
We do not blur these boundaries to increase scope. Start focused. Expand where the evidence supports it.
Start focused. Expand where the evidence supports it.
Workforce & Productivity Intelligence must create standalone value. After the engagement, the choice is yours.
Continue internally
Use the baseline method, the improvement register and the operating measures. They are yours and they run without us.
Repeat on further workflows
Apply the same method to the next set once the first changes have held for a full cycle.
Take automation forward
Where a stage has been simplified first and the readiness assessment supports it — not before.
Fix a specific problem elsewhere
Where the constraint turns out to sit in demand, pricing, stock, collections or the store network rather than in the workflow.
Move into broader operating-model change
Where several connected constraints require change to management systems, decision rights, structure, data or automation.
If teams are busy and output is flat, the answer is usually not more people.
Bring us the workflows that are struggling, the operational data you have, and the business output management wants to improve. We will determine whether Workforce & Productivity Intelligence is the right starting point.