Back

Back

Workflows

What a Whole-Team Interview Surfaces That a Leadership Workshop Never Will

Employee process interviews and leadership workshops answer different questions. Why the room with the most authority knows the least about the work.

Teamwork in a modern office at night, with laptops, sticky notes, and a city view. A mix of focus, collaboration, and a casual atmosphere.

Employee process interviews and leadership workshops are not two ways of doing the same thing. A workshop gathers the people with authority to change a process and asks them to describe it, which reliably produces the official version. Interviews gather the people who run the process and ask what they actually did, which produces the real one. The two outputs differ, and the difference is where the money is.

This is not an argument that leadership is out of touch. It is an argument about where information sits.

Why the senior account is systematically incomplete

A manager's picture of a process is built from summaries. It has to be. They are not in the work every day, so what reaches them is what people report, and what people report is filtered twice before it arrives.

The first filter is significance. Nobody escalates the forty minutes a week they spend rekeying orders, because it is not a crisis and mentioning it feels like complaining. It only becomes visible if somebody asks.

The second filter is presentation. People describe their work to a manager in the form that reflects best on it, not dishonestly, but with the friction smoothed out. The rough version goes to a colleague. The tidy version goes upward.

So the account that reaches leadership is real but partial, and it is partial in a consistent direction: it under-reports waiting, rework, chasing and workarounds, which between them are most of what you would want to find.

What the room does to the answer

Even with the right people present, a group setting changes the output.

The most senior person in the room speaks first or speaks most, and everyone else calibrates to them. Once a version of the process has been stated aloud by someone with authority, contradicting it is a social act rather than a factual one, and most people will not do it over a detail.

Disagreements disappear, which is the worst possible outcome, because disagreements between two accounts of the same handoff are the single most useful thing this work produces. A workshop is a machine for converting them into consensus.

And workshops produce the designed process, because that is what a group can construct together. The real one exists only in fragments, one per person, and no fragment holder has the whole thing.

What individual interviews get instead

Ask one person, privately, about the last specific time they ran a process, and three things fall out that a workshop cannot reach.

The undocumented step. The spreadsheet, the second window, the message to a colleague. People will describe these one to one and will not raise them in a room, partly because they seem too small and partly because they are sometimes technically not allowed.

The honest duration. Away from an audience, people give you the two days, not the two hours. Elapsed time including waiting is what you need and it is the number most distorted by a group setting.

And the workaround, which is the whole prize. The faster route somebody invented when the official one got annoying. This is what actually runs, and there is essentially no chance of hearing about it in front of the person who designed the official route.

Running this across a whole organisation is what abi. FDE does, interviewing everyone by voice or by text and turning what they say into a model of how the business really operates, including where two people's accounts differ and which departments are still guesswork. It runs in the browser on a private link, with no account and no install, and most people finish in under twenty minutes.

The condition that makes it work

None of the above happens if people think the exercise is a headcount review.

Under suspicion, everybody gives you the official version, which means you have spent real money to collect exactly what a workshop would have given you for free. This is the main way whole-team interviewing fails, and it fails silently, because the output looks fine.

So the promise has to come first, it has to be specific, and it has to be kept. The exercise is about the process, not the people. Individual answers are not shown to managers as a performance record. Nothing anyone says here appears in an appraisal.

That last one is a commitment about the following year, not the following week. Break it once and you cannot run this again in that company.

When a workshop is the right tool

Workshops are not useless, they are just aimed at a different question.

If you want to decide what a process should be, get the decision-makers in a room. Design is a group activity, it needs authority present, and it benefits from argument. A workshop is the correct format for that and interviews are a poor one.

If you want a shared understanding of a change, run a workshop. Alignment is a social outcome and it needs people in the same conversation.

The error is using a workshop for discovery, which is an information-gathering problem, and using interviews for design, which is a decision problem. Discover with interviews. Decide in a room. Doing it the other way round is how you get a beautifully aligned team implementing a fix to a process that nobody runs.

The cost, stated plainly

Whole-team interviewing is more expensive than a workshop in the two things small companies have least of.

It costs money, because it is many conversations rather than one. And it costs calendar time from every person interviewed, which for a ten-person company is a working day of collective attention spread across a fortnight.

Under about ten people, do not do this. You can see the whole business from where you sit, and the interviews will tell you what you already know. The value starts when you can no longer say what each person did last week without asking, and it grows from there.

Where to start if you are unconvinced

Do not commit to the whole organisation. Pick one process that crosses two departments, and interview four people about it, separately: the two at the handoff and one either side.

An hour and a half. If the four accounts agree, you have learned that the process is healthy and you have lost ninety minutes. If they do not, you have found the thing a workshop would have averaged away, and you will know which way to spend the rest of the budget.