Organisational Development That Improves Work
- Aug 11
- 8 min read
A client came to me after six months of being pulled in every direction, and his situation is a good starting point for talking about organisational development in practice. He worked for a mid-range retail company and had been managing five teams, a role that had grown considerably since his salary was doubled in his third year with the business. On paper, he was doing well. In practice, he was at capacity, and the organisation had just made it harder.
A new stock despatch system had been introduced, and it added hours to his week rather than saving them. He was also carrying part of the responsibility for reshaping the organisational structure around it, on top of running his existing teams. He found the whole situation genuinely difficult. He did not leave, partly because he enjoyed the job, and partly because he doubted he would find anything else that paid as well. But the frustration was real, and it was building.
We sat down and worked through his options properly, looking honestly at what was actually being asked of him against what one person could reasonably carry. What became clear fairly quickly was that this was not a confidence problem or a skills gap. It was a structural one. Nobody had stepped back and asked whether five teams, a system change and a restructuring project were a sensible workload for a single manager to hold at once.
That is not a criticism of the organisation so much as a common blind spot. Growth and change tend to land on the person already closest to the work, because they are competent and available, not because anyone has checked whether they have the capacity to absorb it.
A team can meet its targets and still be quietly buckling in exactly this way. Decisions take too long, skilled people hold back in meetings, managers avoid difficult feedback, and the same problems reappear because no one addresses the conditions creating them. This is where organisational development earns its place. It is not a programme added to an already crowded calendar. Done well, it improves how work actually happens.
For organisations, the real test is simple. Are people clear about what is expected, able to use their strengths, and equipped to make sound decisions together? If the answer is inconsistent, performance will eventually suffer, even where talent and ambition are high.
What Organisational Development Is Really For
Organisational development is the deliberate work of improving an organisation's effectiveness through its people, leadership practices, culture and ways of working. It focuses less on isolated events and more on the everyday behaviour that shapes how work actually gets done.
That distinction changes what leaders should actually invest in. A leadership workshop may create momentum, but it will not solve a culture where priorities are unclear or managers lack the confidence to hold honest performance conversations. Equally, a new process will not deliver its intended value if people do not understand why it matters or feel unable to challenge what is not working.
The purpose is not to make work feel permanently comfortable. Healthy organisations still have pressure, disagreement and high standards. The aim is to reduce unnecessary friction so that energy goes into useful judgement, meaningful progress and better results.
For leaders, this means looking beyond broad questions such as, "Do we need more training?" A more useful question is, "What is getting in the way of people doing their best work here?" The answer may sit in manager capability, unclear decision rights, competing priorities, poor communication habits, or simply too much being asked of one person at once.
Why Good Intentions Often Fail in Organisational Development
Organisational initiatives usually begin with a sensible ambition: improve accountability, strengthen leadership, retain talented people, or create a more collaborative culture. They lose traction when the response is broad and unspecific rather than built around what is actually happening.
A values poster cannot tell a manager how to raise an underperformance issue with fairness and clarity. A capability framework cannot make a newly promoted leader comfortable with making a decision that will disappoint someone. A staff survey cannot, by itself, fix the trust lost when employees repeatedly share concerns without seeing a meaningful response.
Change becomes credible when people can connect it to their own day-to-day work. They need to know what to do differently, what support is available, and how progress will be recognised. This is why strengths-led organisational development is particularly valuable. It starts with the reality that people do not all contribute, communicate or make decisions in the same way.
Strengths insight is not about putting people in boxes or excusing gaps in performance. It offers practical language for understanding where someone naturally creates value, where they may overuse a strength under pressure, and what conditions help them perform at their best. A detail-focused manager, for example, may bring valuable rigour but delay action when certainty is impossible. A highly relational leader may build trust quickly but avoid direct challenge. Neither tendency is a flaw. Both require awareness and deliberate adjustment.
Start With the Friction, Not the Solution
The most useful organisational development work begins with diagnosis. Before designing a programme, establish what is happening now and why.
This means listening beyond the most senior voices. Managers can often identify the point at which work gets stuck: priorities change without explanation, handovers fail, decisions are escalated unnecessarily, or experienced team members wait for permission they should not need. Employees may describe the same problem differently, through a loss of confidence, heavier workloads or uncertainty about what good performance looks like.
There is a balance to strike here. Too little diagnosis creates a fashionable but irrelevant intervention. Too much analysis can become another way of delaying action. The right approach is focused: identify the few issues that have the greatest effect on performance, then address them directly.
For instance, an organisation may think it has a communication problem when the deeper issue is unclear accountability. It may assume morale is low because people need more recognition, when the real frustration is that strong work is repeatedly blocked by slow decisions, or by one person carrying far more than their role was ever designed to hold. The practical response changes once the cause is properly understood.
A useful diagnosis usually comes down to a small number of honest questions, worked through together rather than answered in isolation. Where are decisions slowing down, and why do they keep stalling at the same point. What conversations are managers avoiding, and what would it cost to have them properly. Which expectations are simply assumed rather than made clear to the people carrying them. Where is workload quietly concentrating on one or two people rather than being distributed sensibly across the team. And where are experienced, high-performing employees becoming less visible, less confident or less willing to contribute, when a year earlier they would have spoken up without a second thought. These questions move the conversation away from vague claims about culture and towards observable behaviour, which is where meaningful change actually begins.
Build Stronger Managers, Not More Dependent Teams
Managers sit at the point where organisational ambition either becomes practical or gets lost. They translate strategy into priorities, set the tone for performance conversations, notice early signs of disengagement, and create the conditions for people to contribute well.
A Gartner survey found that three in four HR leaders believe managers in their organisation are overwhelmed by expanding responsibilities. My retail client's situation was a clear example of exactly that. He was not failing as a manager. He was carrying five teams, a system change and a restructuring brief simultaneously, with nobody above him checking whether that combination was sustainable. Organisations often assume that a skilled manager can simply absorb more, right up until the point they cannot.
This absence of scrutiny creates dependency further down the chain too. Team members wait for answers, managers become overloaded, and development stalls. Organisational development should help managers build stronger judgement rather than hand them scripts they cannot sustain, and it should also ask honestly whether the role itself has been allowed to grow beyond what one person can reasonably do well.
Practical manager development may involve improving the quality of one-to-ones, setting clearer expectations, preparing for difficult conversations, or separating urgent issues from important development work. These can sound basic, but consistent execution is what employees experience as good leadership.
There is also a trade-off. Standardising core expectations for managers creates fairness and clarity. Over-standardising every interaction can make leadership feel mechanical. The goal is shared quality, not identical personalities.
Make Performance Conversations More Useful
Performance management often becomes difficult because it is treated as an annual process instead of an ongoing leadership responsibility. By the time a formal review arrives, feedback may be vague, resentment may have built, and both parties may feel defensive.
Better performance conversations are specific, timely and connected to the work. They address what has happened, the impact it has had, and what needs to change next. They also make space for the employee's perspective. A manager does not need to have every answer, but they do need to be direct enough to remove ambiguity.
Strengths-based practice adds depth here. It asks not only, "What needs to improve?" but also, "What conditions would allow this person to contribute more effectively?" Sometimes the issue is a skill gap or a behaviour that must change. Sometimes it is role design, unclear priorities, or a lack of opportunity to use an employee's strongest capabilities.
This does not lower standards. It makes the route to improvement more precise. When people understand both the required outcome and how they can best move towards it, accountability becomes more constructive.
Measure What Changes in the Work
Organisational development only earns its keep when it changes something observable in the work itself, not just how people feel about a session they attended. That is the real test of whether the investment was worthwhile. Organisational development can be difficult to measure if success is limited to attendance, satisfaction scores, or positive comments after a session. These indicators have value, but they do not show whether behaviour has changed.
Look instead for evidence in the work itself. Are managers addressing issues earlier? Are decisions being made at the appropriate level? Do team members understand priorities and ownership? Has the quality of feedback improved? Are high-performing employees taking greater responsibility rather than becoming quietly disengaged?
The right measures depend on the organisation and the problem that started the work, because what matters looks different depending on where the pressure actually sits. A team working through rapid growth may need faster, clearer decision-making above almost anything else. A professional services team may need stronger delegation and sharper client communication instead. A retail business facing a system change, like my client's, may simply need to check who is actually absorbing the extra hours that change has created, and whether that is sustainable for them long term.
Short feedback loops are usually more helpful than waiting for an annual survey. Notice what managers are doing differently, ask employees what feels clearer, and adjust the support where it is not landing. Sustainable progress is rarely perfectly linear.
Treat Organisational Development as Part of How Work Is Led
The strongest organisations do not reserve development for people who are struggling, or for a small group identified as high potential. They build it into normal working relationships. Managers make expectations explicit. Leaders examine their own habits. Teams discuss what helps them work well and what gets in their way.
This requires an honest look at where friction really comes from. Some of it comes from systems, but some comes from workload that has been allowed to build on one person's shoulders without anyone questioning it. Addressing it may involve redistributing responsibility, adjusting a role's scope, or conversations that have been postponed for too long. That is not always easy, but clarity is kinder than ongoing uncertainty.
My retail client's situation improved once the conversation moved from "how do we get through this" to "what should actually sit on one person's plate." Some of the restructuring responsibility was shared out. The despatch system stayed, but the expectation that he absorb every extra hour it created did not. Within a few months, he described feeling like himself again at work, not because anything about him had changed, but because the role around him had finally been sized to fit a human being.
A role should be reviewed as the work around it changes, not fixed once and left alone. The organisations that develop confident leaders are not necessarily the ones running the best training. They are the ones willing to look honestly at what they are actually asking one person to carry, and to fix it, wee bit by wee bit, before it breaks something that mattered.
By Paula Donnan
Strength at Work - Better judgement. Stronger leadership. Higher performance.
Comments