Readiness Is a System Condition, Not a Training Event
- Living with SHAPE
- 1 day ago
- 11 min read
Healthcare change often begins with a good idea. A new model. A new workflow. A new partnership. A new requirement. A new way of coordinating care.
But good ideas do not implement themselves.
At Living with SHAPE, we believe healthcare transformation depends on more than strategy, training, or technical rollout. It depends on the conditions within the system that enable people to understand the change, trust the process, coordinate across roles, adapt to one another, and keep learning as the work becomes real.
That is especially true in collaborative care.
Collaborative care asks people to work across boundaries: clinical and administrative roles, behavioral health and physical health, leadership and frontline teams, internal staff and external partners, strategy and daily workflow.
Those boundaries are not problems. They are places where systems need care.
Through the lens of Regenerative Psychology™, readiness is not something a team either has or does not have. Readiness is something a system cultivates. It grows through clarity, trust, shared purpose, role alignment, psychological safety, and the steady ability to notice what is working and what needs to change.
This article is part of Regenerative Healthcare Systems in Practice, a six-part Living with SHAPE series exploring how healthcare and behavioral health organizations can design healthier systems through access, navigation, workflow, measurement, teamwork, and readiness.
The focus of this final story is collaborative care readiness, and the larger regenerative idea behind it:
Readiness is a system condition, not a training event.
Collaborative Care Depends on More Than Willingness
Most healthcare teams want to provide connected care. They want clients and patients to experience less fragmentation. They want staff to communicate clearly. They want information to move well. They want handoffs to feel safe. They want care to be coordinated rather than scattered.
But wanting collaborative care is not the same as being ready to practice it. Readiness requires more than enthusiasm.
It requires shared understanding.
It requires workflow clarity.
It requires role definition.
It requires trust between teams.
It requires leaders who can slow down enough to notice friction before it becomes failure.
It requires space for questions, adjustment, and honest feedback.
When those conditions are missing, collaborative care can place extra weight on already stretched teams. People may be asked to coordinate without clear pathways. Meetings may increase without improving decisions. Staff may hear about a new model without understanding how it changes their daily work. Leaders may interpret hesitation as resistance when it is actually uncertainty, overload, or unclear design.
This is where many change efforts become difficult. Not because people do not care. Because the system has not been prepared to support the change.
A regenerative approach sees readiness differently. It does not treat readiness as a checklist completed before launch. It treats readiness as a living condition that must be built, protected, and renewed throughout implementation.
The Hidden Work Beneath Collaborative Care
Collaborative care is often described in terms of structures: teams, pathways, referrals, care coordination, shared plans, measurement, communication, and follow-up.
But underneath those structures is another layer of work.
Can people name the purpose of the change?
Do they understand how decisions will be made?
Do they know what their role is?
Do they trust that concerns will be heard?
Do they have the capacity to participate?
Do they know what to do when the workflow does not match the reality of care?
Do leaders have a way to learn from the team before small issues become larger ones?
This hidden layer often determines whether collaborative care becomes a sustainable practice or another initiative people work around. A team may receive training and still feel unprepared. A workflow may look clear on paper and still break down in practice. A partnership may be well-intended and still create confusion if expectations are not explicit. A leadership plan may be thoughtful and still miss the emotional reality of change.
Readiness lives in that space between the plan and the people. It is the condition that helps a system move from concept to practice.
In Practice: Preparing Teams for Collaborative Care
In one behavioral health setting, collaborative care required more than introducing a new approach. The work required teams to understand what was changing, how roles would connect, where workflows needed to be clarified, and what support staff needed in order to participate with confidence.
Living with SHAPE helped the organization approach readiness as a system design challenge. Rather than treating implementation as a simple training rollout, the work focused on preparing the conditions around the change. That included listening to staff experience, clarifying team needs, identifying operational friction, supporting role alignment, and creating space for leaders and teams to reflect on what would make collaborative care more workable in practice.
This mattered because collaborative care is not sustained by instruction alone. It is sustained by the system’s ability to coordinate.
When teams are invited into readiness work early, they can name what is unclear before it becomes a barrier. Leaders can see where workflow assumptions need to be adjusted. Staff can better understand how the change connects to the purpose. The organization can move forward with more trust and less unnecessary strain.
The lesson is simple: Readiness is not a box to check before implementation. It is part of the implementation itself.
Why Training Alone Is Not Enough
Training is important. People need information. They need a shared language. They need to understand new expectations. They need time to learn new tools, models, and processes.
But training alone cannot carry a system change. Training can explain what should happen.
Readiness helps people understand whether the system is prepared for it to happen.
A training may describe a new collaborative care workflow. But readiness asks whether staff have enough time, clarity, confidence, and support to use that workflow.
A training may define roles. But readiness asks whether those roles make sense in daily practice.
A training may introduce new meetings. But readiness asks whether those meetings improve coordination or create an additional burden.
A training may explain the model. But readiness asks whether people trust the model enough to engage honestly with it.
When readiness is skipped, training can unintentionally become a substitute for design.
Leaders may believe the team has been prepared because information has been delivered. Staff may leave the training with unanswered questions that only emerge when the work begins. Implementation may then depend on improvisation, over-functioning, and informal workarounds.
Regenerative leaders know that information is only one part of change. The deeper question is:
What conditions does this team need in order to practice the change well?
That question shifts the focus from compliance to capacity.
The Team Readiness Renewal Cycle
Collaborative care readiness is not static. It changes as teams learn, workflows evolve, and real-life complexity shows up.
The Team Readiness Renewal Cycle offers a regenerative framework for preparing and supporting teams through collaborative care implementation.
It includes five connected conditions:
Shared Purpose
Role Clarity
Workflow Fit
Psychological Safety
Learning Rhythm
Together, these conditions help leaders assess whether a team is not only informed about change but supported enough to participate in it.
1. Shared Purpose
People need to understand why the change matters.
Shared purpose connects the initiative to something larger than a new requirement or operational adjustment. It helps teams see how collaborative care supports clients, patients, staff, and the health of the system.
Without shared purpose, change can feel like another task. With shared purpose, teams can connect the work to meaning.
For healthcare leaders, this condition asks:
Why does this change matter now?
What problem are we trying to solve?
How will collaborative care improve the experience of clients, patients, or families?
How will it support staff and system health?
Can team members explain the purpose in their own words?
Shared purpose does not mean everyone feels the same way about the change. It means people understand the reason for moving forward.
2. Role Clarity
Collaborative care depends on people knowing how their work connects.
When roles are unclear, coordination becomes harder. Tasks may be duplicated, missed, or handed off without enough context. Staff may hesitate because they do not want to overstep. Others may over-function because they are unsure who else is responsible.
Role clarity reduces confusion. It helps people contribute with confidence.
For healthcare leaders, this condition asks:
Who is responsible for what?
Where do roles overlap?
Where do handoffs happen?
What decisions belong to which role?
What support does each role need to participate well?
Role clarity is not about creating rigid silos. It is about helping collaboration become safer and more reliable. People can work across roles more effectively when they understand the shape of those roles.
3. Workflow Fit
A collaborative care model must fit the reality of work.
Many implementation challenges appear when a model looks good in theory but does not match the daily flow of care. Staff may be asked to add steps without time. Technology may not support the workflow. Documentation may become burdensome. Communication pathways may be unclear.
Workflow fit asks whether the design can actually live inside the system.
For healthcare leaders, this condition asks:
Where will this workflow happen in the day?
What existing process does it connect to?
What will need to stop, shift, or be redesigned?
Where might friction occur?
What will make this easier to use consistently?
Workflow fit is where strategy becomes practical.
A regenerative system does not expect people to absorb poor design. It studies the work honestly and adjusts the design so the change can become sustainable.
4. Psychological Safety
Collaborative care requires honest communication.
Teams need to be able to say what is unclear. They need to raise concerns. They need to name friction. They need to admit when something is not working. They need to ask questions without fear of being viewed as negative or resistant.
Psychological safety is not softness. It is a condition for learning.
Without it, leaders may only hear what feels safe to say. Implementation risks stay hidden. Staff may comply outwardly while struggling privately. Small problems can become normalized because no one feels able to name them.
For healthcare leaders, this condition asks:
Can staff raise concerns early?
Are questions welcomed?
Do leaders respond to feedback with curiosity?
Are mistakes treated as learning signals?
Do teams have spaces where honest reflection is possible?
Readiness grows when people believe their experience matters.
5. Learning Rhythm
No collaborative care model is perfect at launch. The system needs a way to learn.
A learning rhythm creates regular space to review what is happening, notice friction, make adjustments, and reinforce what is working. This may happen through huddles, debriefs, supervision, implementation check-ins, data review, or team reflection.
The rhythm matters because change is alive. It needs attention after the launch moment.
For healthcare leaders, this condition asks:
How will we know whether this is working?
What feedback will we gather from staff?
What feedback will we gather from clients or patients?
How often will we review the workflow?
Who has the authority to adjust the process?
Learning rhythm turns implementation into adaptation. It helps the system renew readiness over time.
Collaborative Care Readiness and System Health
Collaborative care is often discussed as a better way to organize services. It is. But it is also a test of system health.
A healthy system can coordinate across differences. It can bring roles together without erasing their distinct contributions. It can listen to feedback without defensiveness. It can adjust workflows when reality teaches something new. It can support people through change rather than assuming they should simply absorb it.
An unhealthy system may struggle with collaborative care even when the model is strong. Not because the model is wrong. Because the conditions around the model are underdeveloped. This is why readiness matters.
Readiness reveals whether the system has the trust, clarity, capacity, and learning structure needed for collaboration to become real.
That is also why readiness should not be treated as a one-time pre-implementation activity. It should be part of how healthcare leaders steward change.
Regenerative systems design helps leaders look beneath the surface of implementation. It asks what the system is asking of people, what conditions are supporting them, and what needs to be redesigned so the work can become more human, adaptive, and sustainable.
Collaborative care readiness is not only about preparing for a model. It is about preparing the system to become more collaborative.
A Five-Step Practice for Strengthening Collaborative Care Readiness
Readiness becomes practical when leaders create space to examine the conditions around change.
Here is a five-step process.
Step 1: Name the purpose in plain language
Before asking people to change, clarify why the change matters.
Write the purpose in language that staff, leaders, partners, and clients could understand.
Ask:
What are we trying to make better?
Who will benefit?
What problem are we solving?
How does this support care, staff, and system health?
What would success look like in lived experience?
Plain language purpose helps reduce confusion. It also gives teams something to return to when implementation becomes complex.
Step 2: Map the roles involved
List every role touched by the change.
Include clinical staff, administrative staff, supervisors, leaders, intake teams, care coordinators, billing staff, technology support, community partners, and others who shape the experience.
Ask:
Who is involved before, during, and after the care interaction?
What does each role need to know?
What decisions does each role make?
Where are handoffs needed?
Where might responsibilities overlap?
Mapping roles helps the team see collaboration as a system, not a vague expectation.
Step 3: Test the workflow before relying on it
Before full implementation, walk through the workflow with the people who will use it.
Use a real scenario.
Ask:
What happens first?
What happens next?
Where does information move?
What could get delayed?
What could be confusing?
Where does the process depend on memory or extra effort?
This step often reveals practical issues that would not appear in a training alone.
Testing the workflow protects teams from unnecessary frustration.
Step 4: Create a safe feedback loop
Readiness depends on honest input.
Create a simple way for staff to share what they are noticing as the change unfolds.
Ask:
What is working?
What is unclear?
What is taking more time than expected?
What support is missing?
What should be adjusted?
The key is not only collecting feedback. The key is responding to it. When teams see that feedback leads to learning and adjustment, trust grows.
Step 5: Build a renewal rhythm
Schedule time to revisit readiness after launch.
Do not assume readiness is complete because the change has started.
Ask:
What have we learned in the first few weeks?
What needs to be clarified?
What should be simplified?
What needs leadership attention?
What should we keep strengthening?
A renewal rhythm helps collaborative care mature over time. It keeps readiness alive.
The Final Lesson of the Series
Across this six-part series, one theme has been consistent:
Healthcare systems become healthier when they are designed around the real conditions people need to blossom.
Community access depends on trust.
Family navigation depends on clarity.
Digital engagement depends on workflow fit.
Measurement-based care depends on learning.
Virtual care depends on teamwork.
Collaborative care depends on readiness.
Each story points to the same regenerative truth:
Systems do not become healthier through pressure alone. They become healthier through conditions.
Conditions that support trust. Conditions that reduce unnecessary friction. Conditions that help people coordinate. Conditions that protect capacity. Conditions that allow learning. Conditions that make care more human and sustainable.
That is the work of regenerative healthcare systems.
Not simply adding more. Designing better conditions for what matters most.
Explore the Companion Assets
To see the project summary and key outcomes, view the insights and impact reports. To apply the ideas from this article with your team, use the attached resources, all of which can be found here (supporting collaborative care impact report and resource coming this week).
Closing Reflection
Collaborative care does not succeed because people are told to collaborate. It succeeds when the system makes collaboration possible.
When the purpose is clear.
When roles are understood.
When workflows fit the real work.
When people feel safe enough to speak honestly.
When teams have a rhythm for learning and renewal.
Readiness is not a single moment before change begins. It is the living condition that helps change take root.
And when healthcare leaders treat readiness as part of system health, collaborative care can become more than a model.
It can become a more human, connected, and sustainable way of working together.
Comments