Organizations have personalities. They have habits, histories, loyalties, blind spots, unofficial rules, and ways of making decisions that are not always written down anywhere. You can change the organizational chart and leave all of that untouched. You can introduce a new software system and discover that everyone still uses the old spreadsheet. You can hire a new executive director and discover that the same problems have simply acquired a new person to blame.
That is part of what organizational development is about.
Organizational development looks at how an organization actually functions: how decisions get made, how people work together, where responsibility sits, how information moves, what leadership looks like, where accountability breaks down, and what happens when the organization is under pressure. It can become relevant during growth, restructuring, leadership transitions, mergers, major changes in strategy, or simply when a team has reached the point where the way it has always worked is no longer working very well.
The term itself can sound suspiciously corporate, and I understand why. Organizational development has a large professional literature, a substantial consulting industry, and enough terminology to make a perfectly ordinary conversation about how people work together sound like a doctoral dissertation. But the underlying questions are not especially mysterious: How well are we functioning? What is getting in the way? What needs to change?
The field also does not have one universally agreed recipe for answering those questions. Organizational development and change practitioners work from different traditions, including organizational design, systems thinking, group dynamics, leadership development, culture work, change management, and participatory approaches. The International Society for Organization Development and Change explicitly describes the field as involving customized interventions shaped by organizational culture and environment rather than a single universal model.
That is important because organizations are not machines. You cannot necessarily diagnose a problem in one department, apply a standard solution, and expect the same result somewhere else.
Sometimes what looks like a communication problem is really a decision-making problem. Sometimes what looks like poor staff performance is really unclear responsibility. Sometimes a board and executive director appear to have a personality conflict when the deeper problem is that nobody has agreed on who is responsible for what. And sometimes an organization really does have a difficult person at the center of the problem. Good organizational work requires being willing to look at the actual situation rather than deciding in advance what category it belongs in.
An outside consultant can be useful precisely because they are outside. Internal people understand the organization better than I ever will, and that knowledge is essential. But they are also part of its relationships, history, reporting lines, and politics. There are conversations that are simply easier to have with someone who is not going to be sitting in the next staff meeting afterward.
That does not mean I arrive as the neutral genius who sees everything clearly. I am still an outsider, and outsiders can misunderstand organizations very quickly if they do not listen. My approach is to spend enough time understanding how the organization actually operates before recommending changes. I want to hear from leadership and staff, understand where perspectives differ, and distinguish between something that is genuinely dysfunctional and something that is simply different from how I would do it.
This work is a good fit when there is a real organizational problem that people recognize but have difficulty addressing internally. It is especially useful when the organization is changing, growing, restructuring, or trying to recover from a period of instability. It can also be useful when leadership knows that something is not working but cannot quite determine whether the answer is structural, operational, relational, or strategic.
It is not a good fit if leadership wants an outsider to “fix the staff” while refusing to examine its own role in the problem. Nor is it useful when the organization expects a consultant to resolve serious personnel, legal, or clinical matters that require specialist expertise. Organizational development can illuminate those issues, but it should not be used as a substitute for the people qualified to deal with them.
I also would not recommend it simply because somebody has decided the organization needs “culture change.” Culture is not a switch that a consultant flips. It is the result of what an organization repeatedly rewards, tolerates, models, communicates, and does. Changing it usually requires changing some of those things.
If that is the work you actually need, I can help you understand what is happening and work with you toward practical changes. If the real need turns out to be an HR specialist, executive coach, mediator, legal adviser, or another specialist, I will say that too.
The goal is not to make your organization look more organized from the outside. It is to make it function better from the inside.
On BE4SI, we’re talking nonprofits/NGOs, social enterprise, philanthropy, civil society, and social impact— filtered through U.S. and Central/Eastern European lenses. We’d be honored to have you as a subscriber! ⚡
Enjoyed our read? Drop a tip to help us stay 100% independent and ad-free! 🫶🏾
Word of mouth is essential to our growth. Please share us with others. 💫
Thank You!
