Most Productivity Problems Are System Problems
The largest determinant of how much people produce is the system they work in, not how hard they try.
When output is disappointing, attention goes to effort. The variation explained by effort is usually small compared with the variation explained by the arrangement around it.
The process issue in “Most Productivity Problems Are System Problems” is easier to diagnose when effort can be connected to projects without confusing activity with value. Used for remote workforce management software, this product page can add time and workflow context, while the process outcome remains the source of truth for whether the system improved.
What the system contributes
Queues and handoffs, which the waiting note covers.
For an independent perspective related to “Most Productivity Problems Are System Problems”, consult the Microsoft WorkLab; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.
Tools and equipment, including the age of them.
Approvals and the delays they create.
Information availability: whether people can find what they need.
Interruption and fragmentation.
And the match between the work arriving and the capacity to do it.
The common finding
Two teams with similar people produce very differently because of the arrangements around them.
Move a person between them and their output changes.
That is the test: if output depends more on where somebody works than on who they are, the system is the variable.
Why individual measurement obscures it
A per-person figure attributes the result to the person.
Which produces conversations about effort when the cause is a queue.
And the queue persists, because nobody was looking at it, which is the systems note's whole argument.
The flow view instead
Measure the work's journey rather than the worker's output.
Where does it wait, where does it go backwards, where does it get stuck.
This locates causes rather than assigning responsibility, and the causes are usually fixable without asking anybody to work harder.
What this is not
It is not a claim that effort and skill do not matter. They do.
It is a claim about where the variation is, and in most measured organisations the system accounts for more of it.
Which means system improvement has the better return, before any conversation about individuals.
The diagnostic question
If everybody worked ten per cent harder, how much more would be delivered?
In a constrained system, the answer is almost nothing — it would queue.
Asking this once reorients most improvement efforts, because the honest answer is usually uncomfortable.
Where to start
Walk one process end to end, recording time at each stage.
Find the longest wait.
Fix it, measure again.
Two days of work, and it produces more than a year of individual measurement, which is the practical claim this section makes.
What to check
Would output rise if everybody worked harder?
Where does work wait longest in your main process?
Has anybody walked it end to end?
And does your reporting measure people or the work's journey?