How easily we get work done
Ask people what stops them doing good work and they will rarely name the work. They will name the form, the approval, the system that logs out, the team that has not come back to them, the meeting that could have been a message.
None of it appears in anyone's objectives. All of it is where the day went.
Flow is not about how hard people work. It is about what the organisation makes them push through in order to work at all.
Every organisation has friction. Some of it is necessary - a control that exists for a reason, a check that is worth the delay. The question is not whether friction exists but whether it is earning its place, and whether anyone is keeping count. Friction has a way of accumulating quietly, because each individual piece of it is small enough to work around, and nobody ever proposed the whole.
So the dimension reads the places friction gathers. Four of them are where it comes from: the machinery people use, the way this place expects work to be done, the joins between one person and the next, and the pace all of it adds up to. The fifth asks the question that determines whether the other four get better or simply continue.
Flow is where the cost of everything else gets paid.
A strategy that keeps changing does not show up as a Strategy problem in someone's week. It shows up as rework - the thing built in March that nobody needs in May. A culture where people cannot say a tool is broken does not present as a Culture problem. It presents as a broken tool, still in use, three years on. A service the organisation is trying to improve, with no protected time to improve it, does not read as a Service problem. It reads as a workforce running at a pace it cannot hold.
Read Flow on its own and you find friction. Read Flow alongside the other seven and you can start to ask where the friction is coming from - because the same clogged week can be produced by a strategy nobody can follow, a culture nobody can speak up in, or a change programme that never lets anything settle. The symptom is identical. The cause is not, and the cure is different in each case.
This is also the dimension where the difference between a survey and a diagnostic is at its sharpest. Asking people whether processes work will always produce complaints, and a list of complaints is not a finding. What makes it a finding is the fifth dynamic: whether anything ever gets fixed. An organisation with a lot of friction and a working habit of removing it is in a completely different position from one with the same friction and no such habit - and they can return the same score on the first four statements. The first will be better next year. The second will be worse, and will have a longer list of workarounds to show for it.
That is why Flow is measured in five parts rather than one, and why it is read against the other seven rather than alone.
The Flow score is the mean of five statements. Four of them read where friction accumulates. The fifth reads what the organisation does about it - and it is the one to look at first.
Whether the systems and processes people rely on help them work, or get in the way.
The tools, platforms, approvals and procedures people touch to get anything done. This is the most concrete of the five, and the one people can point at. Where it is reported as less true, the day fills up with clunky systems, duplicated entry, approvals that stall, and procedures that made sense to somebody, once. The work still gets done. It gets done despite the machinery rather than because of it, and the effort spent working around it never reaches the actual job.
Whether the way things work here helps people do a good job, or makes it harder.
Set the tools aside and ask the same question of the culture of work: the norms, the expectations, the unwritten rules, how decisions get made and how long they take. This is the softer twin of the machinery, and it is separable from it - an organisation can have excellent systems and a way of working that means doing a good job requires going against the grain. Where this is reported as true, doing good work is the path of least resistance. Where it is not, people succeed through their own persistence.
Whether work passes smoothly between people and teams, or snags in the handoffs.
Most work is not done by one person. It is passed - and the gaps between teams are where momentum is most often lost. Things fall between two owners, require chasing, arrive without what the next person needed, or sit in someone's queue while the person who sent it assumes it is progressing. This dynamic reads the seams of the organisation, and it is usually where structure shows up: a handoff problem is frequently an org chart problem wearing a process costume.
Whether the pace of work can be sustained without wearing people down.
The first three dynamics are about the organisation. This one is about what they cost. Every piece of friction is absorbed by a person, and this is the statement that reads whether the absorption is sustainable. The distinction that matters is between demanding and unsustainable - a demanding pace can be held, and people frequently enjoy it. An unsustainable one is being paid for out of capacity that is not being replaced, and the bill arrives later.
Whether problems in how things work get addressed, or just worked around.
The dynamic that changes the meaning of the other four. When something is not working, does it get fixed, or does it get a workaround? Workarounds are a form of competence - people build them because they are trying to get the job done - and they are also how dysfunction becomes permanent. Each one absorbs a problem quietly enough that nobody has to solve it. Where this is reported as less true, an organisation will keep accumulating friction indefinitely, because it has no mechanism for taking any of it away.
The assessment asks how often each statement is true. Below is what each end of that scale describes. Neither column is a judgement - both are descriptions of what people report.
Alongside the five scored statements, everyone is asked one open question about flow:
What gets in the way of doing good work here?
Of the eight open questions, this is the one people are most often waiting to be asked. The responses are not scored, summarised or averaged. They appear in the dashboard as written, so the numbers and the words can be read next to each other rather than one standing in for the other.
The five statements will tell you that friction exists and roughly where it gathers. They will not tell you that it is the third approval on the purchase form. This question is where that arrives - and it tends to arrive in specifics, from the people who meet them every day.
Where Flow sits against the other seven dimensions, and how much of the overall shape it accounts for.
Which of the five the score rests on, and which sit further from it. Whether the friction is in the machinery, the way of working, or the joins - and whether anything is being fixed.
Flow is a dimension where department frequently carries more than role level. Friction is rarely evenly distributed: it collects in particular functions, at particular seams, and the dashboard shows that rather than resolving it into one number.
In their own words, unsummarised - and on this question, that usually means specifics.
Five statements, each answered on the same five-point frequency scale: almost always, often, sometimes, occasionally, rarely. The prompt is how true is this in your experience?
That prompt is a deliberate choice. Agreement scales measure opinion - whether someone endorses a proposition about the organisation. Frequency scales measure observation - how often a person reports seeing something happen. Opinion tells you what people think about the organisation. Frequency tells you what they encounter in it.
On Flow, the difference is doing real work. Our processes are efficient invites a view, and views on process are shaped by whether the last one you touched was annoying. The systems and processes I rely on help me get my work done, rather than getting in the way asks about the encounter. It is answerable from the last fortnight, by anybody, without needing an opinion about process design.
The dimension score is the mean of the five. It is reported on the 1-5 scale rather than converted to a percentage, and it carries the language of the scale with it - a Flow score of 3.6 reads often true, and means the average respondent reported these five conditions as often true, not that the organisation scored 72%.
Alongside the mean, the dashboard shows the spread. Two organisations can return the same Flow score with different distributions underneath: one where the five statements cluster tightly, one where two sit high and three sit low. The mean is identical. What it describes is not.
Flow is one of eight dimensions States of Vitality reads across a whole workforce. We can talk through what an assessment would look like - scope, timing and price.