# Organizational Development: More Than a New Org Chart > Connect strategy, structure, culture, and people in organizational development. Diagnose the real issue, test changes, and build the capacity to keep learning. - Publisher: OQM International - Language: en - Published: 2025-07-02 - Updated: 2026-09-30 - Canonical: https://oqm-international.com/en/journal/organizational-development-beyond-the-org-chart/ - Image: https://oqm-international.com/journal-images/organisationsentwicklung-transformation.jpg Organizational development is a deliberate process of improving how an organization works, learns, and adapts. It connects strategy, structures, culture, and people's experience rather than treating each as an isolated problem. A new org chart can be useful. It can clarify reporting relationships or reflect a different business model. But moving boxes does not automatically change decision-making, incentives, trust, or the way work crosses departmental boundaries. If the same delays and conflicts return after a reorganization, examine the conditions beneath the formal structure. What work needs to happen, which choices are difficult, and what does the current system encourage people to do? ## Four dimensions to examine together ### Culture: the expectations people learn in practice Culture includes the assumptions and unwritten rules that influence behavior. Employees may hear that initiative matters while learning that only ideas from senior leaders receive attention. Observe what happens when someone raises a problem, misses a target, asks for help, or questions an established process. These situations reveal more than a list of values alone. A structural change should account for the habits that may support or undermine it. ### Structure: how authority and work are organized Structure includes roles, decision rights, processes, interfaces, and formal reporting lines. Ask whether those arrangements fit the organization's purpose and the work it needs to perform. For example, a cross-functional team may have a shared assignment but no authority to resolve competing priorities. A new team name will not fix that conflict. Clarifying who decides, who contributes, and how exceptions are resolved might. See [team development beyond team-building](https://oqm-international.com/en/journal/team-development-beyond-team-building/) for practical work on roles and collaboration. ### People: capability, relationships, and working conditions Employees bring knowledge of how work actually happens. Involving them can reveal constraints that are invisible in a management presentation. Examine skills, workload, access to information, development opportunities, and the quality of relationships. Do not assume a new responsibility is feasible simply because it appears in a job description. People may need time, support, and different resources to carry it out. ### Strategy: the contribution and choices that guide the organization Clarify whom the organization serves, what value it aims to create, and which priorities follow. Strategy requires choices, including what the organization will not pursue. Without that direction, structural redesign can become an argument about status rather than a discussion about the work. Test proposed changes against the intended contribution, available resources, and important obligations. ## What an organic perspective adds OQM's organic perspective emphasizes connected conditions, participation, and learning. It asks how a change in one area affects the wider organization instead of assuming that each function can be optimized independently. The contrast is not between all planning and no planning. Organizations still need clear decisions, expertise, deadlines, and controls appropriate to their work. Nor does participation mean everyone must agree before any action is possible. The useful distinction is between treating a design as a fixed answer and treating it as an informed proposal that must work in practice. Build in ways to detect unexpected effects and adjust. The growth metaphor helps explain that attention to conditions; it is not a biological law applied to a business. ## Use employee surveys as one source of evidence A well-designed survey can provide a structured view of employee experience. It can help identify patterns around leadership, clarity, relationships, or the conditions for contribution. Its value depends on purpose, question quality, participation, and how results are interpreted. Explain confidentiality and its limits, especially for small groups. Do not infer an individual's performance from an organizational score or treat a low score as a complete causal diagnosis. Combine results with conversations, observation, and operational information. A team may report unclear priorities while process evidence shows frequent changes from several managers. Together, those perspectives can inform a more useful question than either source alone. Most importantly, communicate what will happen next. Our [employee survey tool guide](https://oqm-international.com/en/journal/choosing-employee-survey-tool/) explores selection and follow-through in more detail. ## Seven steps for an integrated development process ### 1. Clarify the purpose of the work Define the organizational problem or opportunity and why it matters. Distinguish a symptom, such as slow decisions, from an assumed solution, such as removing a management layer. Keep the diagnosis open long enough to examine alternatives. ### 2. Understand the current situation Gather evidence from several levels and functions. Include less visible work, such as support tasks, night shifts, or remote coordination. Look for differences in experience rather than relying only on a single organization-wide average. ### 3. Develop a practical picture of improvement Describe what would be different in everyday work. For example, routine customer decisions could be resolved closer to the customer while complex exceptions have a clear route. Agree on how success and undesirable side effects will be recognized. ### 4. Connect the four dimensions Check whether strategy, structure, culture, and capability support the proposed change. If employees receive new authority, do they also have information and support? Will their managers still be rewarded for personally approving every decision? ### 5. Test a manageable change Select a bounded area where you can learn without creating unnecessary risk. Name the owner, affected groups, review date, and conditions for expanding, adapting, or stopping the test. A pilot is useful only if its lessons inform the next decision. ### 6. Pay attention to dependencies and capacity Map the relationships around the test: supplier teams, customer commitments, systems, and shared resources. Protect time for learning and account for transition work. What looks like a local improvement may transfer effort or risk elsewhere. ### 7. Review and adapt continuously Compare the intended result with the actual experience. Examine what helped, what failed, and what assumptions changed. Incorporate useful findings into ordinary roles, onboarding, and review routines so the organization does not depend on a permanent special project. For a more detailed implementation sequence, read the [five-stage change management strategy](https://oqm-international.com/en/journal/change-management-strategy-five-stages/). ## An illustrative example: more local decision authority Imagine a mid-sized manufacturer whose customer requests repeatedly wait for senior approval. A simple response would be to remove a reporting layer. A development process first examines which requests stall, why approval exists, and what information local teams lack. The organization might then test delegated authority for a limited class of decisions. It prepares managers to support the change, clarifies escalation rules, provides relevant information, and checks the experience of production and customer teams. Review measures could include decision time, rework, the quality of exceptions, and employees' understanding of the boundary. If speed improves while errors increase, the answer is not to celebrate only the faster decisions. The design needs another look. This example illustrates a process, not a documented OQM client result. ## Leadership and values keep the process credible Leaders need to examine their own decisions as part of the system. Asking teams to collaborate while preserving conflicting targets leaves an important cause untouched. Values can guide trade-offs when they are specific enough to apply. A commitment to responsibility might require explaining who bears the risk of a new arrangement. A commitment to openness should allow people to report that an initiative is not working. The aim is a learning organization: one that can question assumptions, connect perspectives, develop people, and improve its own practices. It does not require permanent enthusiasm for every change or the elimination of all hierarchy. OQM's eight-factor assessment can help establish a shared starting point for this work. [Learn about OQM](https://oqm-international.com/en/#how), explore [values-based leadership](https://oqm-international.com/en/journal/values-based-leadership-five-principles/), or [contact us about your organizational development priorities](https://oqm-international.com/en/#contact). ## Related articles - [OQM in Practice: Organizational Quality, Values, and Improvement](https://oqm-international.com/en/journal/oqm-organizational-quality-values-and-improvement/) - [How to Change Organizational Culture Through Everyday Work](https://oqm-international.com/en/journal/how-to-change-organizational-culture/) - [Organizational Culture: Five Unwritten Rules Worth Examining](https://oqm-international.com/en/journal/organizational-culture-five-unwritten-rules/) ## Languages - [en](https://oqm-international.com/en/journal/organizational-development-beyond-the-org-chart/) - [es](https://oqm-international.com/es/revista/desarrollo-organizacional-mas-que-organigrama/) - [de](https://oqm-international.com/blog/organisationsentwicklung-transformation/)