When something is not working consistently in healthcare, we often look first at the people involved. Do staff feel confident? Do they know what to say? Do they need more training? Are patients satisfied with the support they receive?

These are useful questions, but they can lead us to see an organizational problem as being strictly about individuals.

Consider a clinician who says they do not feel comfortable talking with patients about intimacy. More education might help but their hesitation could also have very practical reasons. They may not know whether these conversations are expected as part of their role. They may be unsure where to refer a patient who needs more support. Good resources may exist but might be difficult to find. Or everyone on the team may have been left to develop their own approach.

Looking at the clinician tells us that they feel uncertain. Looking at the organization helps us understand why.

The same difference appears when we look at patient experiences. One patient may receive helpful information about intimacy, have several opportunities to talk about concerns, and be easily connected with additional support. Another patient receiving care in the same organization may never be asked about intimacy and have no idea that support is available.

We could explain the difference by looking at the clinicians involved. Perhaps one is simply more comfortable with the topic. But once we look at the organization, other possibilities appear. One department may routinely introduce intimacy-related resources while another does not. One team may have a clear referral process because someone took the time to create it. Conversations may happen regularly in survivorship but rarely during active treatment. An experienced social worker may know exactly where to send patients, while newer staff have no idea those services exist.

From inside an organization, these differences can be surprisingly difficult to see. People know how their own department works. Experienced staff learn whom to call and where to find things. Informal workarounds become so familiar that they stop looking like workarounds. A process may function reasonably well for the people who know the system while remaining confusing to everyone else.

Patients encounter these differences from another perspective. They do not know that one clinic has developed a better process than another or that a particular nurse has spent years building relationships with community providers. They simply experience whether someone raises a subject, whether useful information is easy to find, and whether the clinician or team member knows what to do next.

This is where looking at the organization can change our understanding of the problem.

An organization might hear that staff are uncertain about discussing intimacy and decide to provide more training. Training may be exactly what is needed, but it will not clarify a confusing referral process. Creating another patient guide will accomplish little if several good guides already exist and staff cannot easily find them. Teaching clinicians new ways to begin conversations will have limited effect if they remain unsure what to do when a patient says, “Yes, I need help with this.”

Looking at the organization allows these different problems to be separated. Where are conversations already happening? Where are they being missed? What happens after a patient raises a concern? Can staff easily find the resources they need? Do people understand what belongs within their role and when another professional should become involved? Would staff in different departments describe a similar process, or has each team developed its own way of doing things?

These questions can also uncover strengths that might otherwise go unnoticed. An organization may already have excellent patient resources, knowledgeable clinicians, strong community relationships, or a department where intimacy-related concerns are being handled particularly well. Once those strengths become visible, the organization can learn from what is already working rather than assuming that improvement has to begin by creating something new.

This way of looking at care is central to the CancerEVOLVE Framework. The framework considers individual knowledge and confidence, but it also looks at the conditions surrounding them. It asks how culture, conversations, capability, pathways, resources, and integration work together to shape what patients and staff actually experience.

Sometimes that closer look confirms the original assumption. Staff really do need more education. At other times, the problem turns out to be unclear roles, hard-to-find resources, weak referral pathways, or too much dependence on a few experienced people who know how to make the system work.

The people have not changed, but the questions have.

And once the organization itself comes into view, the possibilities for improving care often become much easier to see.