That is hard in a workforce under strain. A 2024 NCSBN survey cited in HRSA's 2025 report found 35% of RNs and 38% of LPNs felt burned out at least a few times a week. Hospitals, ambulatory networks, medical groups, and safety-net providers are redesigning service lines, absorbing digital tools, and trying to cut variation, often at once.
This article defines organization design, separates it from change management, shows how they reinforce each other, and offers a practical roadmap.
Key Takeaways
- Organization design covers strategy, roles, decision rights, workflows, governance, technology, and culture, not just the org chart.
- Change management turns the future-state design into daily behavior.
- Diagnose the current state and frontline experience before choosing a structure.
- Lasting results need adoption measures, clear accountability, and aligned systems.
What Organizational Design Means in Healthcare
Design goes beyond reporting lines
Organizational design is the deliberate arrangement of structure, roles, workflows, decision rights, governance, technology, and people practices to support strategy and care delivery. Structure is the visible framework. Design includes the systems and behaviors that make the framework work.
Healthcare examples include service-line organization, ambulatory network coordination, clinical-administrative leadership pairs, shared services, and cross-functional care teams.
Elements must reinforce one another. Misalignment shows up in familiar ways:
- A structure built for centralized control while leaders expect local responsiveness
- Metrics that reward individual departments when the strategy depends on coordinated care
- Roles on paper that don't match who actually makes the call
Batiste Advisory Group describes this condition as culture and operating systems pulling apart: trust erodes, workarounds multiply, and accountability fragments.
Match the model to your strategy
No structure is universally best. Each fits certain situations and carries its own coordination risk.
| Model | Healthcare fit | Coordination risk |
|---|---|---|
| Functional departments | Specialty depth | Fragmented patient care across departments |
| Service line or institute | Care organized around organ systems or diseases | Requires redrawn boundaries and hierarchy |
| Matrix | Flexibility, faster response | Dual-authority ambiguity |
| Network (IPA, ACO, CIN) | Independent providers sharing risk | Loose integration limits coordination |
| Team-based | Role and workflow redesign at the point of care | Needs staffing fit and role preparation |
Cleveland Clinic's move from traditional departments to clinical institutes is a well-known service-line case, though it is a descriptive example rather than a controlled study. UCHealth's primary care redesign expanded medical assistant roles, and its evaluation reported staffing constraints and incomplete implementation alongside the gains.
Clarify decision rights and accountability
Employees need to know who decides what, where authority sits, how clinical and administrative decisions interact, and how issues escalate. Useful design questions:
- Which decisions are central, and which are local?
- What authority do committees hold?
- Who owns an outcome end to end across handoffs?
- Where does standardization stop and local adaptation begin?
Avera's physician-administrator dyads were tasked with standardizing care delivery, cost, and quality. UCHealth's redesign allowed local adaptation during staffing shortages. Those are different choices, each fitting its context.
Diagnose before you design
Combine organizational data with interviews, frontline listening, workflow observation, and leadership perspectives. The gap between leaders and staff can be wide. In AMN Healthcare's 2026 survey, 58% of executives rated organizational leadership effective, versus 28% of frontline respondents. Measure perception by role.
Batiste Advisory Group's Ground Truth Audit™ is one example of an independent assessment built for this purpose. It separates the official organization shown in dashboards and committee reports from the one staff experience daily, using seven pillars that examine truth, structure, and capability.
Whatever the method, document root causes before selecting a structure, technology, or intervention.
Why Organizational Design and Change Management Must Work Together
The "what" and the "how"
Design defines the future state: roles, structure, workflows, governance, accountabilities. Change management guides people through getting there.
A sound design still fails when staff keep legacy processes, managers interpret responsibilities differently, or systems and incentives reward the old model.
Build the case for change
Leaders should explain the problem the redesign solves, the risk of staying put, the intended benefits, and the link to mission. Frame that case around three questions, in language each group understands: executives, managers, clinicians, and support teams.
- Why change?
- Why now?
- What happens next?
Ground the case in evidence and operational reality, not generic transformation language.
Assess impact on people and work
Map how the design affects people and work across clinical and nonclinical teams:
- Reporting relationships and decision authority
- Workload, skills, and daily routines
- Professional identity and career paths
Resistance often signals something real: unclear accountability, missing capability, lost autonomy, change saturation, or concern about patient care. One study of 521 hospital nurses found change fatigue associated with lower job satisfaction. That finding shows association, not causation.
Align leadership, communication, and involvement
Visible executive sponsorship, consistent manager messages, clinical leader participation, and local champions build trust. Frontline leaders in four community hospitals named planning, timelines, buy-in, trust, and communication as barriers in a Longenecker and Longenecker study.
Favor two-way engagement over announcements:
- Listening sessions
- Co-design workshops
- Targeted stakeholder discussions
- Feedback channels
Managers need talking points, escalation routes, and support to turn enterprise decisions into team expectations.
Enable adoption and reinforce it
Adoption depends on practical supports:
- Role clarity, training, and coaching
- Workflow support and updated policies
- Aligned performance measures
- Removal of legacy approvals
Reinforce the new design through leader behavior, recognition, governance routines, onboarding, and regular review of results.
Separate activity from adoption. Communications sent and training completed are activity. Evidence of adoption is people consistently using the new design, measured through speed of adoption, utilization, and proficiency.
A Practical Roadmap for Designing and Sustaining Change
1. Establish the baseline and desired outcomes
Scope the problem and which parts of the organization it touches. Define measurable outcomes, using established measures rather than invented targets:
- Patient experience: HCAHPS for inpatient care
- Access: CAHPS Clinician & Group appointment timing; ED left-before-seen rates
- Workforce: burnout, turnover, engagement
- Balance across aims: the IHI Quintuple Aim
Document current performance, stakeholder concerns, constraints, and readiness.
2. Map work, dependencies, and stakeholders
Trace how critical work moves across departments, sites, and leadership levels. Look for bottlenecks, duplicated effort, unclear handoffs, and decisions with no owner.
Build a stakeholder and impact map covering executives, clinical leaders, managers, frontline staff, support functions, patients, and external partners. Check workforce capacity, skills, technology, governance, and concurrent initiatives.
3. Co-design and test
Translate strategy into an operating model: the capabilities needed, the work requiring coordination, and authority at each level. Test options with the people who will use them, since they spot unintended consequences.
Pilot before rolling out. UCHealth used two pilot sites to shape how and where its redesign expanded.
4. Sequence the transition
Build one integrated plan covering leadership alignment, communications, role changes, policies, technology, training, staffing, and escalation. Don't ask teams to absorb several disruptive shifts at once. Tell people what is changing, what is not, and where to get help.
5. Measure adoption and performance
Pick a small set of leading and lagging measures. Pair numbers with employee feedback, workflow reviews, and leader observation to explain why performance moves. Set review points during implementation, then adjust training, roles, workflows, or governance.
6. Sustain through governance and capability
Hand ownership from the temporary transformation team to accountable operational and clinical leaders. Embed the future state in policies, job descriptions, onboarding, performance management, committee structures, and technology configuration. Build internal change capability so the next redesign isn't treated as a one-off.
Batiste Advisory Group's Clarity Framework™ follows a similar arc: Assess, Architect, Build, Measure.
Common Pitfalls and Warning Signs
Changing the chart, not the work
Moving boxes or renaming departments without clarifying workflows, decision rights, staffing, incentives, and technology creates confusion. Watch for:
- Duplicated approvals
- Unresolved handoffs
- Shadow processes that persist
- Conflicting priorities
- Unclear decision ownership
Copying a popular structure
A matrix, flat, or agile model that worked elsewhere may not fit your care model, culture, or governance. Clinical realities, professional accountability, patient safety, regulatory duties, and site-level variation all matter. Test fit first.
Treating change as a launch event
A town hall, email, or go-live date is not adoption. A 2026 systematic review linked unsuccessful transformations to inadequate staff buy-in, persistent power differences, and structural changes that discouraged middle-manager support. Those mixed results are not a universal failure rate.
Warning signs include:
- Change fatigue
- Inconsistent messages
- Passive resistance
- Falling engagement
- Workarounds
- Open questions about roles
- Metrics that still reward the old way
Conclusion: Design the Organization You Need and Lead the Change It Requires
Good design aligns strategy with the structures, people, workflows, decisions, systems, and culture needed to execute it. Change management moves employees from the current state to that future.
Start by asking whether your current organization reflects frontline reality. Then:
- Clarify the outcomes the design must enable
- Involve the people it affects
- Build reinforcement into the operating model from day one
Frequently Asked Questions
What is organizational design?
It is the alignment of structure, roles, processes, decision rights, technology, people practices, and culture with strategy and operational goals.
How does organizational design differ from organizational change management?
Design defines the future-state organization. Change management helps leaders and employees adopt, implement, and sustain it.
Why is organizational change management important in healthcare?
Clinical workflows are complex, patient care continues throughout, and workforces are stretched. Leadership alignment, communication, and adoption support keep operations reliable during change.
What are the main elements of organizational design?
Strategy, structure, roles, decision rights, workflows, governance, technology, workforce capability, culture, coordination, and performance systems.
How do you implement organizational design successfully?
Diagnose, define outcomes, assess stakeholders and impact, design with the people affected, pilot, plan the transition, implement, measure, and reinforce.
How do you measure organizational change management success?
Measure both adoption and outcomes: role clarity, behavior change, workflow use, employee feedback, operational and workforce results, and relevant clinical or patient experience indicators.
