Relationships as Infrastructure: When We Don't Have the Answers

What caregiving taught me about uncertainty, trust, and the knowledge we bring into healthcare.

My understanding of relationships as infrastructure did not begin in a boardroom, a research project, or a health system strategy.   It began as a caregiver.

When my daughter Sophia was living with a rare and complex disease, I learned that navigating healthcare was about much more than finding the right clinical intervention. It was also about navigating uncertainty, different perspectives, clinical expertise, systems, and relationships.

And sometimes, the most important thing a healthcare professional could offer us was not an answer.  It was a willingness to stay in the uncertainty with us.

One of the clearest examples was Sophia's experience of pain.

There were periods when Sophia was clearly in pain, but we did not understand why. There was no straightforward explanation. No single test that could tell us where the pain was coming from. Her rare disease was complex and, at times, difficult to understand even for the people caring for her.  From my perspective as her caregiver, however, there was something I did understand.

I knew my child was in pain.

I knew her baseline. I knew how she moved, how she communicated, how she behaved when something was wrong. I knew the subtle changes that could be easy to miss in a clinical encounter.  But knowing that she was in pain and being able to explain why she was in pain were two very different things.  And that difference created enormous tension.

We had many difficult conversations about what her pain meant. Was it physical? Was it related to her underlying disease? Was it emotional? Psychological? Was there something we were missing?  There were also significant discussions and resistance around the use of medications, including methadone and other approaches to managing her pain.

I could understand why those conversations were complicated for clinicians. Without knowing the source of pain, there were legitimate questions about what we were treating, what risks we were taking, and whether medication was the right approach.  But for us as a family, there was another reality that could not be put aside:

Sophia was hurting.

We found ourselves repeatedly advocating for that reality to be recognized, even when we couldn't provide the explanation that people were looking for.  That experience taught me something I have carried into my work ever since.

Uncertainty makes relationships more important, not less

Healthcare systems are often designed around the idea that the right information will lead us to the right answer.

• But what happens when the information is incomplete?
• What happens when the tests don't explain what the person is experiencing?
• What happens when clinical expertise, lived experience, and uncertainty don't immediately align?

These are some of the moments when relationships become infrastructure.  When there is uncertainty, trust becomes essential.  A clinician does not have to agree with a family about every decision to remain in relationship with them.  A caregiver does not have to have the clinical explanation for their observations to be worthy of consideration.

Both can hold expertise.
Both can be uncertain.
Both can ask questions.

And both can continue working toward understanding.

For me, the most important shift is from asking "Who is right?" to asking "What are we missing?"

That is a very different starting point.  It creates room for curiosity rather than defensiveness.  It allows clinical expertise to remain important without dismissing the knowledge that comes from living alongside a person every day.  And it recognizes that sometimes the most responsible thing we can do is acknowledge that we don't yet know.

Caregiver knowledge is knowledge

As Sophia's caregiver, I became deeply aware of the difference between being present in healthcare and being recognized as part of it.  I could not always explain the medical reason for what Sophia was experiencing.  But I knew her.  I knew what she looked like when she was comfortable.  I knew what she looked like when something had changed.  I knew the difference between distress, fear, frustration, exhaustion, and pain as I had come to understand them through years of caring for her.

That knowledge didn't replace clinical expertise.  It complemented it.

This distinction matters.

When we treat lived and caregiving experience as secondary to professional expertise, we can unintentionally create a system where people have to prove what they know before they are listened to.  And when someone is living with a rare or complex condition, that can be particularly harmful.  The people closest to them may be carrying knowledge that the health system does not yet have.  Sometimes that knowledge is the beginning of the clinical question.  Sometimes it is the thing that helps a team notice something they might otherwise miss.  And sometimes it is simply the knowledge that something is wrong, even when we don't yet know what that something is.

Relationships don't require agreement

One of the lessons I continue to carry from those experiences is that relational practice does not mean agreeing with someone.  It doesn't mean that clinicians should automatically accept every interpretation offered by a patient or family.  It doesn't mean that families should always get the intervention they request.  And it doesn't mean that difficult clinical conversations can be avoided in the name of being relational.  Quite the opposite.

Good relationships make difficult conversations possible.

There were times when we had to sit across from healthcare professionals and have very difficult conversations about Sophia's pain and how it should be managed.  Those conversations could be uncomfortable.  There were different perspectives.  There was uncertainty.  There were legitimate clinical concerns.

And there was our lived experience of watching our child suffer.

What mattered was whether we could remain in the conversation.

• Could we ask one another questions?
• Could we acknowledge what we did not know?
• Could we explain our concerns without assuming bad intent?
• Could we hold the possibility that more than one thing might be true?

 Those questions are not just relevant to pediatric care of complex disease.  They are relevant to healthcare everywhere.

​The relationship changes the experience of uncertainty

Looking back, I don't think the most meaningful relationships were necessarily the ones where someone always had an answer.  They were the ones where we didn't feel that we had to navigate the uncertainty alone.  That distinction has stayed with me.  Because relationships don't necessarily remove complexity.

They change how people experience complexity.

A family may still be waiting for answers.

A patient may still be experiencing pain.

A clinician may still be uncertain about the cause.

A treatment decision may still be difficult.

But when there is trust, people can experience those things differently.

• They can ask more questions.
• They can share more information.
• They can acknowledge fear or disagreement.
• They can say, "I'm not sure."
• They can say, "Something doesn't feel right."
• They can say, "I don't agree."

And they can continue the conversation.

That is not a small thing.

Relationships are infrastructure

We often think of infrastructure as the things that hold systems together: policies, technology, buildings, processes, pathways, and resources.  But systems are ultimately experienced through relationships.  A policy is interpreted by a person.  A clinical pathway is navigated by a patient and family.  A research project is shaped by relationships between researchers, participants, partners, and communities.  A healthcare decision happens between people.

The quality of those relationships influences what information is shared, what questions are asked, what concerns are raised, and what possibilities become visible.

This is why I have come to think of relationships as infrastructure.   Not because relationships should replace evidence, expertise, accountability, or good systems.  They shouldn't.  But because those things don't exist independently of people.  Relationships create the conditions in which expertise can be shared, uncertainty can be acknowledged, disagreement can be navigated, and learning can happen.

From caregiving to practice

My experience as Sophia's caregiver continues to influence how I approach my work.  It reminds me that behind every chart is a person whose experience may not be fully captured by the information in front of us.  Behind every clinical decision may be a family carrying knowledge, fear, questions, and years of experience.  And behind every healthcare professional is a person who is also trying to make sense of complexity with the information and resources available to them.

Relational practice asks us to bring those forms of knowledge together.  It asks us:

• To remain curious.
• To notice power.
• To listen beyond the immediate question.
• To make space for uncertainty.

And, perhaps most importantly, to resist the urge to reduce a person or an experience to the explanation that is easiest to understand.

Sometimes we don't know.  Sometimes we won't know for a while.  Sometimes the person experiencing something knows that it is happening before anyone can explain why.  Those moments require more than a pathway or a protocol.  They require people who are willing to stay in relationship while they work toward understanding.

What we build together

Relationships are not a soft addition to healthcare.  They are not the nice thing we do if there is enough time.  They are part of the infrastructure.  They are built through listening, consistency, curiosity, accountability, repair, and trust.  They are strengthened when we recognize that different forms of knowledge can coexist.  And they become particularly important when certainty is unavailable.

I think often about the experience of being Sophia's caregiver and how different healthcare encounters could feel depending on whether we experienced the person across from us as someone we needed to convince—or someone willing to be curious with us.  The clinical questions did not disappear.  The uncertainty did not disappear.  The pain did not disappear.  But the experience of navigating those things could change.
And that, to me, is the power of relational practice.

The relationship may not change the complexity of what a person is facing. But it can change how they experience it and what becomes possible within it.

Perhaps, then, when we think about building better healthcare, better research, and better systems, we should ask not only:  What are we building?

But also:  What relationships are we building along the way?

Because those relationships may be some of the most important infrastructure we create.

---