Are We Fixing the Problem -
or Just Responding to What We Can See?
Organisations often invest in interventions that are well designed and well received, yet the underlying problem remains.
What if the issue we're responding to isn't actually the problem at all?
Elaine Wright · Simply Wright · September 2026
Organisations invest a great deal of time, energy and money trying to improve teams, leadership, culture and performance. We run engagement surveys, leadership programmes, team development sessions, coaching, culture work, away days and change interventions. Some are excellent, some are strongly evidence-based, and some make a real difference.
Sometimes, though, despite all that activity, the original problem is still there.
The workshop may have been well received, the programme may have had great feedback, people may have valued the conversation and the team may even have left with a clear action plan. A few months later, however, not much has really changed.
That raises an uncomfortable question:
Did the intervention fail, or did we misunderstand the problem it was trying to solve?
It is a question I have found myself returning to more and more, particularly because organisations are under pressure to act. Leaders want progress, teams want things to improve, and operational pressures do not stop while people take time to understand what is going on. In that environment, there is often much more appetite for a solution than there is for uncertainty.
When the presenting problem becomes the diagnosis
The presenting problem can therefore quite easily become the diagnosis. We hear that communication is poor, trust is low, the leadership team isn't working, people aren't challenging enough, or that culture is the issue. Those statements matter because they tell us something important about how people are experiencing the organisation, but they do not necessarily tell us what is creating that experience.
Poor communication might genuinely be a communication problem. It might also reflect inconsistent messages, unclear decisions, competing priorities, information becoming stuck between levels, or an organisation changing faster than people can absorb.
Low trust may be the thing people feel most strongly, but the loss of trust may have developed through broken commitments, repeated changes of direction, hierarchy, unclear accountability, or a history of speaking up without seeing anything change.
The label tells us where to look. It does not always tell us why.
Looking beyond the people problem
This is where I think Organisational Development and Organisational Effectiveness need to come together more deliberately.
Organisational Development gives us ways of understanding people, relationships, leadership, culture and change. Organisational Effectiveness widens that view to include the conditions within which people are working, such as structure, decision-making, processes, governance, resources, information, performance measures, technology and the external environment around the organisation.
That does not mean OD needs to own all of those things, and I don't think it should. It does, however, need to be able to recognise when those conditions may be shaping the behaviour and performance we are seeing, because sometimes an issue that becomes visible through people is being created or reinforced somewhere else in the system.
An organisation might say that collaboration matters while continuing to reward leaders primarily for the performance of their own areas. It might encourage empowerment while important decisions still need to travel through several layers of approval, talk about openness while people have learned that challenge carries risk, or ask teams to work differently while leaving the surrounding conditions largely unchanged.
This leads to two questions I keep coming back to:
What is it about the environment that makes this behaviour understandable?
If we changed the people but left the conditions unchanged, how much of the problem would remain?
Neither question removes individual accountability. People still make choices, leaders still influence culture and teams still develop norms. What they do is help us resist the temptation to locate every problem at the level where it happens to become visible.
A signal is not an explanation
They also change how we think about diagnostic tools and measurement. Surveys, interviews and assessments can reveal things we might otherwise miss, but a score is a signal rather than an explanation. A low score for role clarity, for example, tells us that something deserves attention. It does not tell us whether roles themselves are unclear, responsibilities overlap, decision rights are confused, or the organisation has changed faster than the structures around it.
Measurement can help us understand where to look. Diagnosis helps us explore what might be happening there.
Sometimes that exploration begins with a very simple question:
What else could explain this?
When experience helps - and when it gets in the way
I think that question becomes particularly important with experience, because experience can work both for us and against us. Experienced practitioners become good at recognising patterns, which is enormously valuable, but this looks familiar can very quickly become I know what this is. Sometimes that judgement will be right, and sometimes a familiar symptom will have a rather different explanation.
How much diagnosis is enough?
Better diagnosis does not mean endless diagnosis. I am not suggesting that every organisational issue needs months of interviews, workshops and analysis before anybody is allowed to act. The challenge is proportionality, understanding enough to make a sound decision without turning diagnosis into an industry in its own right.
That means asking how much understanding we genuinely need before acting, where the evidence is strong enough to make a reasonable judgement, and where uncertainty matters because an alternative explanation would lead us towards a completely different response.
For me, that is where the opportunity lies. It is not about doing more diagnosis for the sake of it, but about better diagnosis, creating a little more space between what we observe and what we decide to do, connecting Organisational Development more deliberately with Organisational Effectiveness, and being willing to ask one final question before reaching for the intervention:
What are we actually trying to change, and why do we believe this action will change it?