There is a particular kind of Monday-morning meeting that most organisations know well. Someone is late with a handoff. A client has slipped through. A deadline has quietly collapsed over the weekend, and now a small group of people sit around a table trying to work out whose fault it is. The room has a temperature. Fingers are not quite pointed, but they lean. What almost never happens in that room is a pause long enough to ask a more useful question: is this a process problem, or is this a people problem? The distinction is not academic. Getting it wrong is expensive — in time, in trust, and eventually in the consultants brought in to fix the wrong thing.
The Shape of the Two Problems ¶
A process problem lives in the architecture of how work moves. It is the gap between two desks where a task falls and nobody owns it. It is the approval step that requires a signature from someone who travels forty weeks a year, creating a weekly queue of twelve decisions waiting for one person to land. It is the onboarding checklist that was written in 2019 for a team of four and now governs a department of twenty-six without a single revision. Process problems are structural. They produce the same failure repeatedly, across different people, across seasons. The individual standing inside the broken system is almost incidental — swap them out, and the same error arrives again, punctual as a train. A people problem has a different texture entirely. It concentrates around specific relationships, specific personalities, specific moments of ego or avoidance or misread hierarchy. It appears when one capable team moves smoothly through the same workflow that a second team consistently mangles. It surfaces in the language people use — vague, defensive, territorial — rather than in the gaps on a flowchart.
Why the Misdiagnosis Happens ¶
The misdiagnosis runs in both directions, and each direction has its own politics. Leaders who are conflict-averse reach for process explanations because restructuring a workflow feels cleaner than having a direct conversation with a senior employee who is undermining their team. The process becomes a kind of diplomatic fiction — a way to say something is broken without saying who is breaking it. The opposite error is just as common. Leaders who are decisive and action-oriented reach immediately for the people lever. Someone is moved, managed out, retrained. The process that produced the failure sits untouched, and within a quarter the new person in that role is making the same mistakes. Consultants are often called in at precisely this stage — after the personnel change, when the problem has returned and the organisation is genuinely confused. The most useful thing a good consultant can do in that moment is ask the organisation to sit with the discomfort of not knowing which kind of problem it has, long enough to find out.
Four Diagnostic Questions Before Anything Else ¶
The first question is: does this failure happen with different people in the role, or only with one? If three different project managers over two years have each missed the same client reporting deadline, the role is the problem, not the managers. If only one manager misses it while others in equivalent roles do not, the investigation shifts. The second question is: can a new person, given only existing documentation, complete this task correctly on their first attempt? Run this as a real test where possible, not a thought experiment. The third question is: when the friction occurs, does it happen at the same point in the workflow regardless of who is involved? Consistent location of failure — always at the handoff between operations and finance, always at the third stage of client approval — points strongly toward structural cause. The fourth question is: when the people involved are asked separately to describe the process, do their descriptions match? Significant divergence in how team members narrate the same workflow is itself a process problem, even if it feels interpersonal. People cannot follow a process they have each invented independently in their heads.
What Good Process Design Actually Looks Like ¶
A well-designed process has three properties that are easy to state and genuinely difficult to achieve. It is legible — anyone joining the team mid-stream can understand what the next step is and who owns it without asking a colleague. It is load-bearing — it does not depend on any single person's memory, goodwill, or presence in the office. And it has a failure mode, meaning the design anticipates what happens when a step is missed and routes around it rather than simply stopping. The handoff email that cc's a shared inbox rather than only one person's address is a small example of the third property. The project board that shows status in real time rather than relying on a weekly update meeting is another. These are not sophisticated interventions. They are the kind of small structural choices that reduce the cognitive load on everyone in the system and, crucially, reduce the number of moments in which a person's individual behaviour becomes the single point of failure.
When the Problem Really Is the Person ¶
Having ruled out structural cause through the four questions, the people problem deserves the same unflinching clarity. A people problem might be a skill gap — someone is in a role that has grown beyond their current capability, and the honest intervention is development or reassignment, not a new flowchart. It might be a values misalignment that no amount of process can paper over: a team member who consistently prioritises their own visibility over collective outcome will find ways to reproduce that pattern inside any system. It might be a leadership problem disguised as a team problem — a manager whose ambiguity or inconsistency creates the anxiety that then plays out in the behaviour of reports. Naming these things requires courage and specificity. The language of people problems needs to be concrete. Not 'there are communication issues in this team' but 'in the past three months, Marta has declined to share project updates with the wider group until after decisions have already been made, and that sequencing is creating downstream errors.' The concrete version is harder to say. It is also the only version that can be addressed.
The Hybrid Case, and How to Hold It ¶
Most organisations, if they are honest, are dealing with a hybrid. A structural gap has existed long enough that workarounds have calcified into territory. People have built informal power around the ambiguity — the person who knows how the system actually works becomes indispensable, and has reasons, conscious or not, to resist clarification. Fixing the process in this case surfaces the people problem that was always underneath it. This is not a reason to delay the structural work. It is a reason to do it with eyes open, and to resource the human side of the transition adequately. The sequencing matters: clarify the process first, publicly and collaboratively, so that resistance to it becomes visible rather than diffuse. Then address the resistance directly, with the same specificity recommended above. Running the two tracks simultaneously tends to blur both. Clarity is itself a kind of kindness — it removes the ambiguity that allows people to behave badly and call it improvisation.
Before the Consultant Arrives ¶
An outside perspective has genuine value, particularly when internal politics have made honest diagnosis impossible. But the consultant who arrives before an organisation has worked through the four diagnostic questions will spend the first weeks doing that work at considerable expense. The more useful preparation is to gather the evidence: map the workflow as it actually operates, not as it was designed. Interview people in the same role at different levels of the organisation and compare their descriptions. Track where failures cluster — by person, by step, by season, by team — over at least three months. Then bring that material to any external conversation. The diagnosis becomes faster, the recommendations become more precise, and the organisation retains the understanding it has built rather than outsourcing it entirely. The consultant becomes a thinking partner rather than an oracle, which is a much more durable and honest arrangement.
The Monday-morning meeting with its careful temperature is not going away. But the question asked inside it can change. Whether the friction belongs to the system or to the people moving through it is a question that can be answered — not with certainty on the first attempt, but with method, patience, and a willingness to be surprised by what the evidence shows. That willingness is, itself, the beginning of good organisational thinking.