A client came to me with a specific problem. Their middle management layer wasn’t performing. Managers weren’t taking ownership. They weren’t leading their teams. They were still behaving like operators rather than leaders, which was trapping senior leadership in day-to-day decisions that should have been handled one level down.
The presenting diagnosis was not unreasonable. The behaviour it described was real and observable. The solution it pointed toward was clear: develop the middle management layer.
That is what they thought they were hiring me to do.
I ran a diagnostic first. Ten interviews with managers across levels, a company-wide staff survey, four weeks of mapping what was actually happening at each level of the organisation before I was willing to conclude anything.
What I found was not a middle management problem.
The organisation had no documented vision, mission, or values. Strategic priorities were inconsistently understood across levels because they had never been formally communicated. There were no standardised processes for core operations, no career progression frameworks, no documented decision rights, nothing that told a manager what they were authorised to decide and what required escalation.
Senior leadership had this clarity. It lived in their heads, in the relationships between them, in the accumulated understanding of people who had built the company together. It had simply never been converted into something the organisation could navigate by.
Middle management wasn’t failing to lead. They were trying to lead without a map.
When I presented this finding, one of the senior leaders said something I have heard in different forms many times since: “We thought everyone understood how things worked here.”
They did not. They were improvising in the absence of structure, and doing it well enough that the gap had been invisible for years. What changed as the company grew was not the quality of the people. It was that improvisation at scale stops working. The same unwritten understanding that functioned at fifteen people breaks down at fifty.
The recommendation was not middle management training. It was build the foundations first. Until those existed, developing middle managers was building on ground that wasn’t there yet.
That is a different prescription from the one the presenting problem implied. The diagnostic found it. But the diagnostic took four weeks.
I have since developed a five-lens framework that would have produced the same conclusion in the first conversation. Not because ten interviews and a staff survey are unnecessary. They aren’t, and for a full engagement they remain the right approach. But the five questions would have identified the correct level of intervention before a single interview was booked, which changes how the next four weeks are spent.
Those five questions are a diagnostic framework called PLACE.
PLACE is a five-lens diagnostic framework — People, Language, Architecture, Capital, Execution — used to identify the correct level of intervention before concluding what a problem is. It is not a framework for solving problems. It is a framework for finding out what the problem actually is, which is a prior and harder question than most leaders stop to ask.
Each letter is a lens.
People: do we have capable people who can reasonably produce this outcome? Not whether they are trying. Whether their experience and track record suit this specific task in this specific context.
Language: do the right words exist and are they shared? Two people can use the same phrase to mean entirely different things. Shared understanding is not confirmed by the absence of disagreement. It is confirmed by testing.
Architecture: do the systems, processes, and decision-making structures support the desired outcome, or work against it? A capable person inside the wrong architecture produces results that look like a people problem. They are not.
Capital and resources: has sufficient investment been made in the right things? Expectation without resourcing is not a strategy. When this lens shows a problem, the intervention is not motivation or accountability. It is resourcing.
Execution: are people actually doing what produces results? This is real, but it is almost always the last lens to show a genuine independent problem. Execution failure that traces back to Architecture or Capital is not an execution problem.
Run all five lenses. Name what each one found. Then conclude.
Applied to the opening case, the framework produces this.
People: senior leadership capable, middle management capable. Not the problem. Architecture: no documented decision frameworks, no standardised processes, no career progression structures. Primary problem. Capital: investment in management development had not kept pace with company growth. Contributing problem. Language: inconsistent communication across levels, but downstream of Architecture. Execution: managers not operating at expected level, but downstream of Architecture and Capital.
Conclusion: Architecture primary, Capital contributing. Not a people problem. Not a management training problem. A foundations problem.
Same conclusion as the four-week process. In a single structured conversation.
The diagnostic is not complicated. What it requires is the discipline to complete it before deciding, which is harder than it sounds when the presenting problem looks clear and the solution feels obvious. The opening case looked like a people problem. It felt like a people problem. Everyone in the organisation had been treating it as a people problem for long enough that the framing had stopped being questioned.
The first diagnosis is almost always wrong. Not because the people making it are incompetent. Because the presenting problem is the symptom, and symptoms look like problems.
PLACE finds the level underneath the symptom. That is the level worth intervening at.
One note on where the diagnostic hits its limits. In family businesses, and in organisations where authority is inseparable from relationship, PLACE finds the same root causes, but what addressing them requires is more complex. A role clarity problem in a family business is not only an architecture problem. It is also a conversation between a parent and a child, or between a founder and a successor who has spent years learning what not to say. The diagnostic is the same. The intervention must account for what is entangled with it.
What would you run PLACE on right now, if you stopped reading?