World 1 of Organisations, level 2: underground
Before changing an organisation, you need to know where it stands. The diagnosis, the maturity levels and the report that gets decision-makers to act.
Part 2 of 3 of the series World 1 of Organisations.

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).
World 1 of Organisations — level 2 of 5: level 1 · level 2 · level 3 · level 4 · level 5
The second level of Super Mario’s first world takes the player underground. The screen goes dark, the ceiling drops low and the blocks scattered along the way hold things that only appear after a knock: sometimes a coin, sometimes nothing, sometimes exactly what was missing to carry on. Whoever runs past without hitting the blocks reaches the end faster, though they arrive weaker.
Something similar happens in an organisation. Before changing anything, someone has to knock on the blocks and see what is inside. That work has a name: diagnosis.
What is an organisational diagnosis?
An organisational diagnosis is a picture of where the company stands, taken before deciding where it is going. It looks at processes, people, systems, controls and results, and searches for two things: what works and deserves protecting, and what is missing or broken.
The value of the diagnosis lies in coming first. Whoever changes without one solves the problem they imagined they had, while the real problem stays exactly where it was, waiting for the next meeting.
In level 1, the question was what problem the company solves, and for whom. The diagnosis checks whether it actually solves it, at what cost and with what risk.
What is a maturity model, and what is a level for?
A maturity model is a ruler. It describes, in levels, how a practice evolves: from improvisation, where everything depends on whoever happens to be there, to a practice that is defined, measured and continuously improved.
The level is useful in two ways. The first is a shared language: saying that contract management is at level 2 is more useful than saying it is “so-so”. The second is showing the next step. It rarely makes sense to jump from level 1 to level 4, even if that is exactly what many transformation projects promise.
The risk with a maturity model is that it becomes an end in itself. Moving up a level is only worth it when the next step solves a business problem.
Technical finding or business impact: what gets decision-makers to act?
We have a business in the ecosystem that is a technology consultancy. In that business we developed a product for auditing Salesforce instances, OrgAudit 360. The technical idea and the development are my business partner’s; my part was the concept of the executive report and the chain that leads from the technical finding to the business impact.
We had enormous difficulty explaining the technical findings to decision-makers. When we created a report designed for decision-makers, the understanding of the problem changed completely.
Decision-makers need data to decide, not sad and cryptic stories. Or, in a phrase of mine: whoever decides doesn’t care about CRUD, they want to know where the impact is.
A good diagnosis therefore has two layers. The bottom one is technical and complete, for whoever is going to fix things. The top one translates each finding into consequence: what it costs, what risk it creates, which client it affects, what happens if nothing is done. Without the second layer, the diagnosis is correct and nobody acts.
Who does the diagnosis: someone from inside or from outside?
Someone from inside knows the history, the people and the shortcuts. For that very reason they find it hard to see what has become normal, and sometimes have an interest in not seeing it.
Someone from outside arrives without those filters and asks what nobody has asked in years. On the other hand, they need time to understand the context and may mistake a deliberate choice for a defect.
A combination usually works best: someone from outside leads, someone from inside opens the doors and confirms what is the exception and what is the rule. Asking the department under review to assess itself and present the result to the board tends to combine the worst of both sides.
So what comes next?
With the diagnosis in hand, a new problem appears: the list of things to fix is longer than the capacity to fix them. Level 3 deals with that, the triage of where to start when everything demands attention at once.
Quick questions
What is an organisational diagnosis? A picture of where the company stands, taken before changing it: processes, people, systems, controls and results, with what works and what is missing.
What is a maturity model for? To give a shared language about the state of a practice and show what the next realistic step is.
Why do so many diagnoses fail to lead to action? They usually stay at the technical layer, and decision-makers need each finding translated into cost, risk and impact on the client.
Is an internal or an external diagnosis better? Usually a combination: someone from outside leads and someone from inside opens the doors and confirms the context.