Making change stick
7 tips for building relational architecture into healthcare quality improvement

Making change stick is difficult. Getting people to trust the process enough to actually change how they work, and stay changed once the excitement of the launch has worn off is challenging. Relational architecture is the human connections, trust, psychological safety, and sense of belonging that your outcomes depend on. Here are seven ways to build it in.
1. Belonging is a requirement, not a nice-to-have
Belonging is more than just being invited to meetings. It’s feeling that you are part of something bigger than yourself and that your contribution is valued. Be alert for “silent unbelonging”: A patient on a ward feeling disempowered and socially invisible. Their spouse who has, over time, lost connection with their community because of caregiving responsibilities. The clinician who is morally injured because they recognise this suffering but the system won't let them alleviate it. These are part of the problem your redesign needs to solve, not side effects to manage afterwards.
Design belonging into your change plans
If your change plan doesn't explicitly nurture connection and foster belonging, you are compromising its success before it launches.
2. resistance is a relational signal
When someone pushes back on a new protocol, process, or system, don’t fall into the trap of labelling it as "resistant to change." You may be witnessing unvoiced moral distress, prior experience with bureaucratic tick-box exercises, or a genuine fear of causing more harm. Treat resistance as a compliance problem, and you'll get compliance-shaped actions (or inaction) in return. Treat it as a relational signal, and you get information you can actually use to fix your plan.
Consider where so-called resistance comes from
Does it stem from feelings of not belonging, scars from a previous experience, or a genuine fear of making things worse?
3. Look to the person behind the role
Role clarity is genuinely useful for coordinating work but it also obscures the lived human experience underneath, and can become defensive armour that suppresses moral distress, grief, or fatigue. When you recognise the person behind the role, you shift from managing behaviour to building shared human presence. That’s what makes change feel welcomed rather than imposed.
Design for people in their actual context
Instead of designing for an idealised version of people based on their roles, build in genuine dialogue and avoid tick-box consultations.
4. Prioritise Relational gaps over compliance
Connection in any healthcare setting depends on team dynamics that intentionally build mutual trust and emotional presence. Where this is absent, relational gaps emerge between staff, patients and families. In healthcare, these gaps drive compassion fatigue, fragmented continuity of care, and burnout.
Protect space for collective sense-making
Structured debriefs and cross-team discussion belong in routine workflow, not on the list of things that get cut first or feature further down the list of actions.
5. Intentionally build psychological safety
When teams share a genuine climate of psychological safety, people can voice unease and challenge assumptions without fear of being shut down or judged. That climate doesn't happen by default. It has to be built into how meetings run, how feedback is given and received, and how disagreement is handled.
Cultivate a speaking-up culture
Flatten hierarchy in meetings so everyone can feel safe to challenge assumptions. Structure this in, don't just hope for it.
6. Aim for relational safety
Psychological safety gets you a team that will speak up. Relational safety goes further: it's what lets people stay genuinely connected through tension and conflict rather than retreating into politeness or silence once things get difficult. Which, at some point, it will.
Care for the people delivering the change
Build peer-support structures that acknowledge the cumulative toll of leading through disruption. Everyone deserves to feel valued, including yourself.
7. Ask relational questions
It's tempting to lead every change conversation with: "What outcome or milestone do we need to hit?" Try leading with this instead: "What relationships, trust, and sense of belonging will let the people affected by this navigate it together?"
Explore relational safety before metrics
This doesn’t replace metrics. It tells you which of your metrics will actually mean something once you've hit them.
Get the relational architecture right, and the outcomes you're accountable for become easier to reach. Skip it, and you'll keep re-running the same exhausting improvement cycle against the same quiet resistance.
References
Baumeister, R.F. and Leary, M.R. (1995). The need to belong: desire for interpersonal attachments as a fundamental human motivation. Psychological Bulletin, 117(3), pp.497–529.
Center for Creative Leadership (2026). Building trust and connection in teams.
O'Donovan, R. and McAuliffe, E. (2020). A systematic review of factors that enable psychological safety in healthcare teams. International Journal for Quality in Health Care, 32(4), pp.240–250.
Bhasin, K. (2025). Relational safety: beyond psychological safety in teams.




Comments