Season 1 asked: What happened to what was known?

When this publication began, the question was deceptively simple. If information exists — if people observe patterns, document concerns, conduct research, describe experiences, and raise warnings — why does that information so often fail to become recognition, response, or change?

Over this season, we followed that question through different parts of the pathway. We began by examining the systems that shape what becomes visible. Categories, diagnoses, specialties, departments, and policies help organize complexity. They allow knowledge to be communicated and acted upon. They also create boundaries, shaping what information is easier to recognize and what information requires additional translation before it can be understood.

We then turned toward the central dilemma of this publication: the gap between information existing and information being recognized. A warning can be accurate. A pattern can be real. Evidence can accumulate. Yet knowledge does not automatically become action. Recognition depends on whether the information is interpreted as credible, relevant, and worthy of response.

We explored what happens when information moves. A clinical observation becomes documentation. A research finding becomes a guideline. A frontline concern becomes a report. A lived experience becomes data. At each transition, information must be translated into the language and structures of the next system. Meaning can be preserved, but it can also be compressed, softened, or separated from the context that made it matter.

We examined what happens when no one person holds the entire picture. A clinician sees one part of the terrain. A researcher sees another. A policymaker sees another. A person living through the system sees something no outside observer can fully access. The knowledge is often not absent. It is distributed across people, roles, and institutions that do not always have reliable ways to connect what they know.

We explored how systems produce outcomes through more than individual decisions. People generally make choices based on the information, incentives, responsibilities, and constraints available to them. Those choices can be reasonable from each individual position and still combine into outcomes no one intended. Without understanding the structures surrounding those decisions, systems repeat patterns without understanding why they occur.

Finally, we examined who gets heard. Information does not move based only on whether it is accurate. It also moves through structures of credibility, authority, access, and proximity. The person closest to a problem may hold essential knowledge while having the least direct pathway to influence the decisions that shape it.

Information does not simply disappear. It moves through systems. Those systems determine what is preserved, what is transformed, what is recognized, and what becomes actionable.

So now, at our conclusion of season 1, the pattern is clearer: Information does not simply disappear. It moves through systems. Those systems determine what is preserved, what is transformed, what is recognized, and what becomes actionable.

While season 1 examined the patterns and paths, season 2 will examine the mechanisms that shape it.

The Mechanisms of Misalignment

As we’ve established, the name Cassandra comes from an ancient warning unheeded. The tragedy of Cassandra was not that knowledge was absent. The warning existed. The information was present. The failure occurred in the space between knowing and responding. The Cassandra Dilemma explores that space.

Season 2, The Mechanisms of Misalignment, will be a series of deep studies naming, describing, and examining the recurring processes through which systems lose, delay, distort, or exclude information they need. Each study will examine three questions:

What is the mechanism?

We will define the pattern, examine the research and theories that help explain it, as well as the fields that are currently studying similar concepts. We’ll explore how it operates within complex systems.

What does it look like in the world right now?

We will connect each mechanism one current issue affecting healthcare, mental health, education, organizations, policy, and communities — examining how these patterns appear in the lives of people navigating systems today.

Who is on the frontlines?

We will look at the people closest to these patterns: the individuals impacted by system failures, those with lived experience and their loved ones, professionals working within constrained resources, the researchers documenting what is happening, and the advocates working toward change.

The goal is not simply to identify failures, nor is it to point a finger of blame. It is to understand why these patterns persist, how they become embedded, and what becomes possible when we recognize the structures shaping what systems can see, hear, and act upon.

A Note for Those on the Frontlines

Many of the patterns explored in The Cassandra Dilemma are first recognized by people closest to them — those living them, working within systems, researching, or advocating for change. Some of the most important knowledge about systems does not begin in reports or institutions. It begins with people noticing patterns before they have a name.

Letters from Cassandra will be an ongoing collection of perspectives from those on the frontlines — individuals sharing what they are seeing, what they have learned, and what they wish systems understood.

If you have experienced, studied, or worked on issues connected to the patterns explored in The Cassandra Dilemma, I welcome your perspective. You can share your thoughts by commenting below or emailing: dispatchesfromcassandra@gmail.com1

… Up Next in The Cassandra Dilemma

Season 2 begins Fall 2026.

Subscribe to The Cassandra Dilemma to receive new essays when The Mechanisms of Misalignment begins.

Subscribe now

Explore The Cassandra Dilemma

Continue exploring the questions, research, and work behind this publication.

Start here:
→ Start Here: Understanding The Cassandra Dilemma

Learn more about the publication and author:
→ About The Cassandra Dilemma

Read more essays:
→ Browse all essays from The Cassandra Dilemma

Explore concepts and research:
→ Library: Terms, Research, and Foundations

Mental health resources:
If you are seeking mental health support, crisis resources, or treatment information:
→ Mental Health Resources

Professional services:
Amber Young, LMHC provides consultation, education, training, and speaking services focused on OCD, neurodivergence, mental health systems, clinical practice, and translating knowledge into action.
→ Professional Services

Continue Exploring The Cassandra Dilemma

If you’re new here, start with Start Here for the map of this publication and how the seasons fit together.

If this essay named something you’ve experienced from inside a system — or from just outside one — consider sharing it with someone who might recognize the pattern.

Not all accurate information travels equally well. That’s a harder thing to sit with than it first appears. It means the previous essays in this publication, true as they may be, remain incomplete on their own. A system can have working translation pathways, genuine goodwill, and no single villain anywhere in the chain—and information can still fail to reach where it needs to go, simply because of who is holding it.

Knowing something and having the authority, access, or permission to act on that knowledge are not the same thing. This essay is about the difference.

Credibility Is Not Distributed Evenly

Some voices are treated as evidence, and others are treated as anecdote, even when they’re describing the exact same reality. A physician’s observation, documented in a chart, is treated as clinical data. A patient’s identical observation, describing the same symptom in the same detail, is more likely to be logged as a subjective complaint—something to note, rather than something to act on with the same weight. A researcher’s finding, published in a peer-reviewed journal, is treated as knowledge. A community’s collective observation of the same pattern, accumulated over years of lived experience, often has to fight for the status of “anecdotal” before it’s taken seriously enough to be studied at all.

None of this is to say the physician or the researcher is wrong to be trusted; expertise exists for real reasons, and this isn’t an argument against it. What it suggests, instead, is that credibility is a structural position, not just a property of accuracy—something assigned by study, title, setting, and institutional role, rather than solely earned through being correct. Two people can be equally right and still be heard completely differently, depending on the role they’re speaking from, and credibility often decides whether information gets heard at all before it ever has the chance to be evaluated on its own merits. Even once it clears that filter, a second hurdle is waiting: how close the person holding it is to the room where a decision actually gets made.

Proximity to Decision-Making

Information also has to travel a physical and institutional distance to reach the people who can act on it, and that distance isn’t the same for everyone. A hospital administrator’s concern reaches leadership because they’re already in the room where leadership meets. A frontline nurse’s identical concern has to travel through several layers of hierarchy to reach the same room, and something typically gets lost—reframed, softened, shortened—at each layer it crosses. A policymaker’s staff member has direct access to draft the language of a bill, while a community member affected by that bill often only gets access to a public comment period, months after most of the real decisions have already been made.

This shows up sharply around workforce and administrative decisions specifically, where the people doing frontline work are often the first to notice second- and third-order effects of a staffing change, a new protocol, a shift in caseload, budget cuts, or priority shifts—effects that are frequently foreseeable from where they stand, well before they show up in any report. That foresight is valuable in specific, concrete ways: it can flag inefficiencies before they become expensive, predict which parts of a new protocol won’t survive contact with an actual caseload, or surface the real reason an initiative isn’t working when the official metrics still look fine. It usually reaches decision-makers, if it reaches them at all, through an intermediary—a manager or administrator summarizing on their behalf, rather than the frontline person’s own ongoing feedback being integrated as the decision unfolds. Each time that happens, the information passes through someone else’s language, someone else’s constraints, someone else’s priorities, another point where something can thin out before it ever reaches the room where the decision gets made.

A person can hold the most accurate account of a problem in the room and still be the one furthest from the door that leads to a decision, simply because of the seat they were given, or weren’t given, before the conversation started.

Proximity isn’t earned by being right; it’s usually a function of role, institution, and access, things that exist independently of whether the information itself is correct. A person can hold the most accurate account of a problem in the room and still be the one furthest from the door that leads to a decision, simply because of the seat they were given, or weren’t given, before the conversation started. It also has limits worth naming plainly, since it’s easy to imagine as something you either have or don’t have, permanently, when it’s really scoped and situational. A hospital administrator has real proximity to hospital leadership, and almost none to the legislators writing the policy that determines hospital funding. A policy staffer has genuine access to the language of a bill as it’s being drafted, and little proximity to the clinical reality that bill is meant to address. A researcher has proximity to funding bodies and journal editors, and often very little to the frontline settings where their findings are eventually meant to be applied. Being close to power in one room says nothing about being close to it in the next one, and almost everyone occupies both positions somewhere, proximate in one direction and distant in another, including the administrators and leaders used as examples here, which is part of why this pattern is so easy to miss from any single seat.

That kind of advantage can sometimes open a door in another room too, through professional networks, shared associations, a referral from one credentialed voice to another, though the transfer isn’t guaranteed and isn’t the same as direct access. When it does happen, it usually arrives filtered through different terms, different priorities, different professional lenses than the ones the information started in, which points toward a related problem: even once information reaches the right room, it still has to be translated into a language that room already knows how to hear.

Language as a Filter

Even when information does reach the right room, it has to be translated into the language that room recognizes as legitimate. A patient’s description of their experience often has to be converted into clinical terminology—diagnostic codes, standardized symptom checklists, the specific fields an electronic health record recognizes—before an insurer will authorize treatment, a specialist will accept a referral, or a care team will treat it as something requiring action. A community’s account of a policy’s harm often has to be converted into statistics and formal metrics before a legislature will treat it as evidence solid enough to justify a hearing, a bill, or a change in funding.

None of this is necessarily malicious, since institutions genuinely need standardized language to function at scale, and the conversion still carries a real cost. Something is usually lost in translating lived experience into the vocabulary an institution already knows how to hear, and the people best equipped to do that conversion—researchers, advocates, credentialed professionals—are not always the people who lived the experience in the first place. That creates its own quiet distance between the knowledge and the people who hold it most directly.

When Lived Experience and Institutional Categories Disagree

Perhaps one of the most disheartening versions of this problem is when someone’s lived experience doesn’t match the categories, objectives, priorities, or budget an institution currently has available to receive it. A patient describes something real that doesn’t fit any existing diagnostic framework cleanly. A community describes a harm that doesn’t map onto any existing policy category. A caregiver’s account of what a family actually needs doesn’t match the objectives a program was funded to measure. A frontline concern doesn’t fit inside a budget line that was set before the problem was fully understood. In these moments, the person holding the most accurate, most detailed knowledge—the person who is actually living the thing being described—is often the least equipped, structurally, to make that knowledge move, not because they’re wrong, but because the institution doesn’t yet have a category built to receive what they’re saying, and building new categories is slow, political, and rarely prioritized until enough institutionally credible voices have already said the same thing.

What that actually costs is worth saying plainly, since it’s easy to let this stay abstract. It’s years of a person’s life spent being told the thing they know to be true isn’t real, isn’t urgent, isn’t yet legible to anyone with the power to help. It’s relationships strained by having to fight, again and again, to be believed about your own body, your own child, your own experience. It’s watching a field slowly build the language to describe what happened to you, only after you’ve already lived through the worst of it, sometimes only once you’re no longer the one who needed it most. For some people, the category never arrives in time, and I want to acknowledge that explicitly: sometimes the wait outlives the person waiting. That’s heavy to sit with, and yet it’s a needed reminder of perspective.

What Happened to What Was Known?

We’ve been building on this theme of what happened to what was known, and before the final essay and conclusion of Season 1, it’s worth revisiting how we got here.

We learned that knowing and doing gaps occur across systems and industries with little else in common (Episode 1: Why I Started Looking At Systems). We learned that boxes help organize, but can also make information outside them harder to see (Episode 2: The Problem With Boxes). We learned that accurate information can exist and still fail to become recognized action (Episode 3: Who Is Cassandra?). We learned that information changes shape as it travels through institutions, without anyone intending it to (Episode 4: Playing Telephone With Institutions). We learned that true, partial information held by different vantage points can go unassembled into a whole picture (Episode 5: Everyone Is Holding a Piece of the Map). We learned that reasonable decisions, each made without full visibility into the whole system, can still combine into outcomes no one intended (Episode 6: Systems Do Not Need Bad Intentions to Produce Bad Outcomes). This essay adds one more layer: who had the authority, access, or permission to be heard shapes whether accurate information moves at all.

We know now that information is often available, but that whether it actually moves depends on categories, translation, perspective, incentive structures, and now, credibility and access—not only whether information existed or changed shape along the way, but whether the person holding it had the authority, access, or permission, at that moment, for the system to receive it as something worth acting on.

One essay remains before Season 1 closes and Season 2 begins naming the mechanisms underneath all of this.

… Up Next in The Cassandra Dilemma

If knowledge requires credibility, authority, and access in order to move through systems, the final question of Season 1 is:

What happens when the information was there — but the outcome did not change?

In the Season 1 conclusion, we bring the pieces together.

What Happened to What Was Known? examines how information can exist, warnings can be made, and evidence can accumulate — while systems still fail to respond.

→ Continue with: What Happened to What Was Known?

Explore The Cassandra Dilemma

Continue exploring the questions, research, and work behind this publication.

Start here:
→ Start Here: Understanding The Cassandra Dilemma

Learn more about the publication and author:
→ About The Cassandra Dilemma

Read more essays:
→ Browse all essays from The Cassandra Dilemma

Explore concepts and research:
→ Library: Terms, Research, and Foundations

Mental health resources:
If you are seeking mental health support, crisis resources, or treatment information:
→ Mental Health Resources

Professional services:
Amber Young, LMHC provides consultation, education, training, and speaking services focused on OCD, neurodivergence, mental health systems, clinical practice, and translating knowledge into action.
→ Professional Services

Continue Exploring The Cassandra Dilemma

If you’re new here, start with Start Here for the map of this publication and how the seasons fit together.

If this essay named something you’ve experienced from inside a system — or from just outside one — consider sharing it with someone who might recognize the pattern.

Share

Subscribe now

If you ask why a system failed someone, the first question people usually reach for is: Who’s responsible?

It’s a fair question. Sometimes there’s a clear answer, and accountability matters. But over the years, I’ve found myself asking a different question alongside it: What about the structure made this outcome possible?

Those are not competing questions. They answer different parts of the same problem. Understanding how systems produce outcomes is not an alternative to accountability. It is what allows accountability to reach beyond the person closest to the consequence and examine the conditions that made that consequence likely in the first place.

I’ve sat with enough of these situations now to notice something less satisfying than a single mistake. Often, when I trace a bad outcome all the way back through every decision that led to it, I can’t find a single point where someone obviously chose badly. Every person along the way made a decision that made sense, given what they could see, what they were responsible for, and what the person before them had handed off. And yet the outcome was still bad. Sometimes, profoundly so.

That is the harder problem this essay sits with. Not who failed. But how a system can produce harm while the people inside it are trying, competently, to do their jobs.

Reasonable Decisions, Made Locally

Most decisions inside large systems are made with local visibility. Complex systems can produce outcomes that emerge from many ordinary interactions rather than from a single decision.

A clinician sees the person in front of them. A case manager sees the cases assigned to them. A department director sees their budget. A policymaker sees population-level data. Each of those perspectives is real. Each is also limited. No one person is positioned to see the entire chain of consequences their decision will eventually become part of.

A clinician may recommend the right treatment without seeing that the referral leads to a six-month waitlist. An administrator may approve a budget that appears responsible without seeing how that decision will shape staffing years later. A policymaker may rely on the best available evidence without seeing how implementation will unfold differently across communities.

Taken individually, these are reasonable decisions, made from one point on a map no single person can see in full. That isn’t a personal flaw. It’s what it means to work inside something larger than yourself.

When Incentives Drift Away From the Goal

Systems rarely behave according to their intentions. They behave according to their incentives. Sometimes those are the same thing. Sometimes they quietly diverge.

A hospital measured on readmission rates has an incentive to reduce readmissions. That sounds aligned with good care until someone genuinely needs to come back. A program funded by the number of people served has an incentive to serve more people. That sounds aligned with access until the people requiring the most time become the hardest to serve well. A clinician paid per visit has incentives that do not automatically align with every patient’s ideal pace of treatment.

None of this requires bad faith. It only requires that the thing being measured is not exactly the same thing as the outcome everyone hopes to achieve. Systems tend to optimize for what they can measure. The things we care about most are often harder to measure. This creates a misalignment between intentions, processes, and outcomes.

Feedback That Never Finds Its Way Home

One of the defining characteristics of healthy systems is feedback. When something isn’t working, information about that failure should eventually reach someone who has the authority to change it.

In practice, that loop often breaks. The consequences of a decision frequently appear somewhere far removed from the person who made it. A reimbursement decision made today may shape access to care years later. A policy’s unintended consequences may become visible only after thousands of people have moved through it. A clinical protocol’s blind spot may emerge only after enough people quietly stop seeking care altogether.

By then, the connection between cause and consequence has become difficult to see. Sometimes the people experiencing the problem disappear from the data entirely. The feedback the system most needed never reaches the place where change could occur.

A system without functioning feedback loops can continue producing the same outcomes indefinitely — not because anyone wants those outcomes, but because the information needed to correct them never completes the journey back.

The Difference Between Blame and Understanding

This took me a long time to understand.

Early on, I wanted every failure to have a single explanation. Someone missed something. Someone ignored something. Someone should have acted differently. Sometimes that is exactly what happened. There are situations where negligence, misconduct, or abuse require direct accountability, and nothing in this essay argues otherwise.

But much of what I’ve watched unfold looked different. It looked like thoughtful people making thoughtful decisions inside structures that limited what any one of them could see.

That doesn’t remove responsibility. It expands it. Alongside asking who should have acted differently, systems thinking asks another question: What about the structure made it so difficult for anyone to see clearly enough to act differently in the first place?

Those questions belong together. Without accountability, systems repeat harm. Without systems analysis, they repeat it with different people. Systems thinking asks us to look beyond individual actions and examine the relationships, structures, and patterns that shape outcomes.

Making Sense Is Not the Same as Right

This is close to the reason I went into psychology in the first place.

Human behavior, examined closely enough, is rarely random. It is usually the logical output of someone’s history, incentives, fears, and the information available to them at the time. That’s true of the people this essay has been describing — clinicians, administrators, policymakers — working from what they could see, doing what made sense given the vantage point they had.

It is also true of people making decisions I don’t agree with.

Understanding why a decision made sense to the person making it is not the same as agreeing with the decision or excusing what it produced. It’s a clinical habit as much as a personal one — the training to ask what does this behavior make sense in service of? before asking is this behavior acceptable? Those are two different questions. Conflating them either lets harm go unexamined or turns understanding into a kind of loyalty to whatever was understood.

I want to be honest about where this essay’s argument has a limit. Not every decision inside a system is the product of limited visibility and misaligned incentives. Some decisions are made by people optimizing for something other than the outcome they claim to want — protecting their own position, their own ideology, their own advantage — and calling that “reasonable, given their vantage point” would be its own kind of distortion.

I’m not a neutral observer of every outcome this publication touches. I have views, as each person does. What I try to hold onto professionally is the discipline of asking the structural question first, because most of the harm I’ve actually witnessed didn’t come from someone choosing badly on purpose. It came from something closer to what the rest of this essay describes.

That discipline isn’t the same as pretending everything is equally understandable, or equally excusable. It’s a starting question, not a verdict.

Why This Matters

One of the easiest mistakes we make is assuming that good intentions naturally produce good systems. They don’t. Good intentions matter. Competence matters. Integrity matters. But they are not enough on their own.

Systems produce outcomes through relationships, incentives, information pathways, feedback loops, and the limits of what any one person can know from where they stand. If we want different outcomes, we cannot only ask people to try harder. We also have to understand the structures within which they are trying.

What Happened to What Was Known?

Often, the information about what was going wrong already existed.

Someone saw the consequence. Someone noticed the pattern. Someone raised the concern. Someone documented the unintended effect. The knowledge was there. It simply never completed the journey back to the place where it could change the system that produced it.

No single person needs to have failed for a great deal to have gone wrong. That isn’t a comforting conclusion. But it is a more useful one — because once we understand that systems can unintentionally produce predictable outcomes, we can begin asking a different question: not only who should have acted differently, but how we build systems that learn from what they already know.

… Up Next in The Cassandra Dilemma

If systems do not need bad intentions to produce harmful outcomes, the next question is:

Why does some information move through systems while other information does not?

In the next entry, we examine the role of credibility, authority, and access in determining what knowledge is recognized and acted upon.

Who Gets to Be Heard? explores the difference between knowing something, being believed, and having the pathways necessary for that knowledge to influence decisions.

→ Continue with: Who Gets to Be Heard?

Explore The Cassandra Dilemma

Continue exploring the questions, research, and work behind this publication.

Start here:
→ Start Here: Understanding The Cassandra Dilemma

Learn more about the publication and author:
→ About The Cassandra Dilemma

Read more essays:
→ Browse all essays from The Cassandra Dilemma

Explore concepts and research:
→ Library: Terms, Research, and Foundations

Mental health resources:
If you are seeking mental health support, crisis resources, or treatment information:
→ Mental Health Resources

Professional services:
Amber Young, LMHC provides consultation, education, training, and speaking services focused on mental health systems, clinical practice, and translating knowledge into action.
→ Professional Services

Continue Exploring The Cassandra Dilemma

If you’re new here, start with Start Here for the map of this publication and how the seasons fit together.

If this essay named something you’ve experienced from inside a system — or from just outside one — consider sharing it with someone who might recognize the pattern.

Subscribe now

Share The Cassandra Dilemma

When something goes wrong inside a complex system, the instinct is predictable: find the piece that’s missing. Find the error. Find the person who should have caught it. Somewhere, we assume, there is a puzzle with a hole in it, and if we just locate the missing piece, the picture will finally be complete.

I understand the instinct. I’ve had it myself, more times than I can count.

But after years of sitting inside these systems from multiple angles, I’ve come to think the puzzle is usually the wrong metaphor. A puzzle assumes one correct image, a fixed number of pieces, and a single moment when the picture becomes whole. Most systems I’ve spent time inside are not like that. They’re closer to a map — except no single person is holding the whole map.

Each person is holding a piece of terrain, seen clearly from where they stand, shaped by what they are close enough to observe, and largely invisible from anywhere else. The problem is not that someone has the wrong piece. The problem is that we rarely have a reliable way to assemble the map.

What a Clinician Sees

From inside a clinical relationship, you see a person over time. You see patterns, history, context, and the specific way a condition shows up in someone’s life. You see the difference between what diagnostic criteria describe and what a person actually experiences. You notice the details that rarely fit neatly into a checkbox — the hesitation before someone answers, the contradiction between what someone reports and what their life suggests, the small details that change how a presentation should be understood.

What you don’t usually see is what happens once that person leaves your office and moves through the rest of the system. You may not see the insurance denial that prevents the treatment you recommended. You may not see the months-long waitlist for the specialist you referred them to. You may not see the policy decision made in a building you’ve never entered that determines whether the care you know would help is actually available.

Your piece of the map is detailed. It is also bounded.

What a Researcher Sees

From inside research, you see patterns across many people at once — things no single clinical relationship could reveal, because no individual clinician sees enough cases to identify every trend that only becomes visible at scale. You see what works, on average, under defined conditions. That knowledge is essential. Without it, systems cannot distinguish between what feels helpful and what has evidence behind it.

But research has its own boundaries. A researcher may not see what happens when a finding leaves the controlled environment where it was studied and enters the complexity of real life. They may not see the ways implementation becomes complicated by access, resources, culture, competing demands, or the fact that the person receiving care does not look exactly like the population represented in the study.

The finding may be true. The challenge is what happens when truth meets terrain it was not designed to map.

What a Policymaker Sees

From inside policy, you see scale. You see the consequences of decisions multiplied across thousands or millions of people. You see resource constraints, competing priorities, legal requirements, budgets, and the practical limits of what any single policy can accomplish. Those constraints are real — a policy decision cannot be made as though resources are unlimited or tradeoffs do not exist.

But policy also creates distance. The person making a decision about a population rarely sees every individual experience contained inside that population. A statistic can reveal a pattern while hiding the person inside it. A policy can improve outcomes overall while still creating a serious problem for people whose circumstances do not match the assumptions built into it.

Neither the policymaker nor the person affected is necessarily wrong. They’re looking at different parts of the terrain.

What Lived Experience Sees

From inside the experience itself, you see something none of the other vantage points can fully access: what it actually feels like when the system does not work. You see the difference between what a system says it does and what it actually feels like to move through it. You notice friction points that may not appear in formal reports.

You often detect patterns before they are visible to people studying them from the outside. While lived experience does not replace research or expertise, proximity creates a different kind of knowledge. You are standing closest to the place where the map stops matching the terrain.

The challenge is that noticing a pattern and moving that pattern through a system are different skills. A person can understand something deeply and still lack the institutional language, credibility, access, or path required for the system to respond. The knowledge can be present. The path for you may still be missing.

Different Coordinates, Not Contradictions

I’ve spent a long time occupying more than one of these positions, sometimes in the same week. What I’ve noticed is that these perspectives rarely contradict each other as much as we assume they do. More often, they describe different coordinates on the same map.

The clinician sees the person in front of them accurately. The researcher sees real patterns across populations. The policymaker sees genuine system constraints. The person living through it knows exactly what it felt like when the system failed to meet them. Each is right about what they’re standing close to.

The problem isn’t that one person holds the truth and everyone else doesn’t. It’s that no single person holds the whole terrain and most systems were never built with a reliable way to assemble the pieces.

Why This Matters More Than It Seems

Puzzle-thinking leads somewhere specific: find the missing piece, find who lost it, fix the mistake, move on.

Map-thinking leads somewhere else: no one has the whole picture, so the work is integration. That is a harder project. It requires building pathways between perspectives that do not naturally communicate with each other — clinical rooms and research journals, lived experience and policy meetings, frontline observations and institutional decisions.

Most systems are not currently built to perform that integration well. That is not a moral failing. It is an infrastructure gap. But naming it as an infrastructure gap changes what kind of solution becomes possible. Instead of asking “who had the missing piece?” we can ask “how do we build a system capable of seeing the whole map?”

What Happened to What Was Known?

Often, when something goes wrong, every relevant piece of the map already exists somewhere.

The clinician knew something. The researcher knew something. The policymaker knew something. The person living it knew something different — something no one else could know in quite the same way.

The map was never actually empty. The knowledge was never completely absent. It was fragmented — held by different people, in different languages, inside different parts of the system.

The question was never whether anyone knew. It was whether anyone had built a way for what was known to come together.

… Up Next in The Cassandra Dilemma

If everyone holds a piece of the map, the next question is:

What happens when the system itself creates patterns no single person intended?

In the next entry, we examine why system failures do not require bad intentions.

Systems Do Not Need Bad Intentions to Produce Bad Outcomes explores how ordinary decisions, structures, incentives, and limitations can combine to create outcomes that no individual person designed or intended.

→ Continue with: Systems Do Not Need Bad Intentions

Explore The Cassandra Dilemma

Continue exploring the questions, research, and work behind this publication.

Start here:
→ Start Here: Understanding The Cassandra Dilemma

Learn more about the publication and author:
→ About The Cassandra Dilemma

Read more essays:
→ Browse all essays from The Cassandra Dilemma

Explore concepts and research:
→ Library: Terms, Research, and Foundations

Mental health resources:
If you are seeking mental health support, crisis resources, or treatment information:
→ Mental Health Resources

Professional services:
Amber Young, LMHC provides consultation, education, training, and speaking services focused on mental health systems, clinical practice, and translating knowledge into action.
→ Professional Services

Continue Exploring The Cassandra Dilemma

If you’re new here, start with Start Here for the map of this publication and how the seasons fit together.

If this essay named something you’ve experienced from inside a system — or from just outside one — consider sharing it with someone who might recognize the pattern.

Subscribe now

Share The Cassandra Dilemma

Do you remember the game telephone?

Picture a circle of kids at recess — let’s say it’s Jessica, Ashley, Matthew, Brittany, and Michael. (If you’re reading this and you know exactly why those names, hello, fellow elder millennial). Jessica leans over and whispers a sentence into Ashley’s ear. Something simple. The dog buried a bone under the porch. Ashley whispers what she heard to Matthew. Matthew whispers what he heard to Brittany. Brittany whispers to Michael. And by the time Michael says the sentence out loud to the group, it’s become something else entirely — the frog carried a phone under the door — and everyone laughs, because nobody meant to change it. It just changed.

Nobody is surprised by this. It’s the whole point of the game.

What’s surprising is how often we expect institutions to behave differently.

Inside organizations, the stakes are no longer a silly sentence but a diagnosis, a policy, a life. I have watched accurate information enter a system at one end and arrive at the other changed — not wrong, exactly, but different enough that it no longer carries the weight it started with.

This essay is about that gap: not why people fail to communicate, but what happens to information simply by virtue of moving.

Information Rarely Moves Directly

Almost everything we know reaches us through intermediaries.

A clinical observation doesn’t travel straight from a provider’s understanding into a policy decision. It moves through documentation, built around fields designed to capture certain things and not others. Then through billing codes, built around what insurance will reimburse, not necessarily what happened in the room. Then through committees, where it competes for attention against a dozen other priorities. Then through summaries of summaries, each one shorter than the last, each shortening deciding what mattered enough to keep.

By the time information reaches a decision-maker, it may still be technically accurate. It may also no longer contain the thing that made it matter in the first place.

This isn’t a story about carelessness. Most of the people at each step of that chain are doing their jobs competently, often well. The distortion doesn’t require anyone to do anything wrong. It is a consequence of movement itself. Information does not simply move from one person or system to another unchanged. Every transition requires translation.

Where the Signal Changes

A therapist writes a clinical note. The note has to fit the fields the electronic record provides, so nuance gets compressed into checkboxes and diagnostic codes. Something true gets left out — not because the therapist didn’t notice it, but because there was nowhere in the form to put it.

What this means: the next provider who reads that chart inherits a flattened version of a real person. A pattern the therapist could see clearly — the specific shape of someone’s anxiety, the context behind a behavior — becomes a code that could describe a hundred different people. The next clinician isn’t working from what was true. They’re working from what fit.

A researcher publishes a finding, carefully qualified, full of the specific conditions under which it holds. By the time that finding reaches a clinical guideline, the qualifications have often been trimmed away for the sake of a usable rule. The rule is easier to apply. It is also, quietly, less true than the research it came from.

What this means: somewhere downstream, a clinician follows the guideline exactly as written, on a patient the original research never actually accounted for. Nobody broke a rule. The rule itself already left the room where the nuance used to live.

A frontline worker raises a concern in a meeting. The concern gets logged, summarized, and passed upward, each summary shorter than the conversation it came from, because summaries are supposed to be shorter. By the third or fourth handoff, the concern is still technically present in the record — but the urgency that made someone raise it in the first place has usually been left behind. Urgency is difficult to put into a bullet point.

What this means: the concern shows up in a report, eventually, as one line among many, competing for attention with a dozen other one-liners that also used to be urgent conversations. By the time anyone with the authority to act reads it, it doesn’t read as urgent. It reads as routine. And routine things wait.

None of this requires anyone to fail. It is what happens when a system built for efficient movement processes something that was never simple to begin with. However, these moments can create a misalignment between what is known, what is communicated, and what is ultimately acted upon.

Loss Doesn’t Require Villains

This is the part that takes a moment to sit with: how rarely there's a single point of failure to name. Sometimes there is a clear decision — a clear person, a clear place where something should have gone differently. More often, each individual decision made sense from where that person stood. The clinician filled out the form correctly. The committee summarized accurately, for a summary. The policy reflected the guideline it was given. And somewhere in that chain, without any single failure, the thing that mattered most quietly stopped being visible.

That's a harder problem than blame. Blame has an ending.

What This Means for Where We Go Next

Once you start looking for this pattern, it shows up everywhere information has to cross a boundary — between roles, between departments, between a lived experience and the language a system has available to describe it.

Some information gets compressed to fit categories that were never built to hold it. Some gets reframed until it means something adjacent to what it originally meant. Some simply waits, because no path currently exists to move it forward at all. This publication will spend real time with each of those, one at a time, later on.

For now, the more important thing to notice is simpler: the game doesn’t require a villain. It only requires enough handoffs.

What Happened to What Was Known?

The sentence that started the telephone game was accurate. So was the clinical note. So was the research finding. So was the frontline concern.

The question was never whether the information existed. It was a question of information fidelity, how much meaning is preserved? what happened as that information became documentation. Then evidence. Then guidance. Then policy. Then practice. How much of what mattered most disappeared between one translation and the next?

… Up Next in The Cassandra Dilemma

If information changes as it moves through systems, the next question is:

What happens when everyone holds part of the information — but no one holds the entire picture?

In the next entry, we explore how complex problems are often experienced from different vantage points. Each person, profession, and institution may hold a piece of the map, but those pieces do not always come together into a shared understanding.

Each of Us Holds a Piece of the Map explores what happens when knowledge exists across many places, but the connections between those pieces are difficult to see.

→ Continue with: Each of Us Holds a Piece of the Map

Explore The Cassandra Dilemma

Continue exploring the questions, research, and work behind this publication.

Start here:
→ Start Here: Understanding The Cassandra Dilemma

Learn more about the publication and author:
→ About The Cassandra Dilemma

Read more essays:
→ Browse all essays from The Cassandra Dilemma

Explore concepts and research:
→ Library: Terms, Research, and Foundations

Mental health resources:
If you are seeking mental health support, crisis resources, or treatment information:
→ Mental Health Resources

Professional services:
Amber Young, LMHC provides consultation, education, training, and speaking services focused on mental health systems, clinical practice, and translating knowledge into action.
→ Professional Services

Continue Exploring The Cassandra Dilemma

If you’re new here, start with Start Here for the map of this publication and how the seasons fit together.

If this essay named something you’ve experienced from inside a system — or from just outside one — consider sharing it with someone who might recognize the pattern.

Subscribe now

Share The Cassandra Dilemma

The story begins with a gift that became a curse.

In Greek mythology, Cassandra was a princess of Troy, daughter of King Priam. The god Apollo offered her the power of prophecy, the ability to see what was coming. She accepted the gift. When she refused him in return, he could not take it back.

So he changed it instead. Cassandra would still see the future clearly. She would still describe it accurately. But no one would ever believe her. Cassandra warned Troy about the wooden horse. She warned her brother Paris about the war his choices would bring. She warned her own family, in the last hours, about what was about to happen to the city.

Every warning was accurate. Every warning went unheeded.

The tragedy of Cassandra was not simply that she saw what others could not. It was that her ability to see clearly did not translate into the ability to change what happened next. That is the detail most retellings skip past too quickly. We tend to remember Cassandra as a symbol of being ignored. But the myth is more specific than that, and the specificity matters. Cassandra’s information was available, her knowledge was not recognized.

Cassandra was not disbelieved because she was wrong. She was disbelieved despite being right, in a system that had no pathway for her accuracy to become anyone else's action.

What the Myth Gets Right About Now

I didn’t come to this story through literature. I came to it by recognizing the same pattern in rooms that had nothing else in common, a clinician’s accurate note routed somewhere it couldn’t help, a well-documented finding that took a decade to change practice, a patient’s own body proven right years after being told it was just stress, a policymaker watching a program get renewed despite frontline data showing it wasn’t working.

None of these people were wrong. None of them lacked information. What they lacked was a path, a way for what they knew to become something the system around them could act on. That is the modern parallel. Not a curse, but a structural gap between accurate information and the ability of a system to receive it. The felt experience from the inside, however, is remarkably similar to the myth: the specific loneliness of being correct and watching it not seem to matter.

The Lived-Experience Side

I have been on both sides of this gap, sometimes in the same year.

I have been the clinician who caught something a colleague missed. Simply because category happened to be familiar to me and unfamiliar to them. I have also been the clinician who missed something, later, that someone else caught. Both experiences taught me the same lesson from opposite directions: recognition is not simply a property of perception. It is also a property of whether a system's categories happen to line up with what's actually in front of it.

I have also been the patient. I have sat across from providers and described something accurately, in detail, over years, before receiving an explanation that actually fit. I remember what that specific waiting feels like: confusion about what was happening in my body, but also confusion about why an accurate description of it kept failing to be understood.

That is the part of the Cassandra story that doesn't fully land until you've lived a version of it. It is not simply frustrating to be right and unheard. It carries a particular kind of grief — watching something true be said clearly, fail to travel, and understanding, eventually, that the failure wasn't really about you at all.

What This Publication Means by The "Cassandra" Dilemma

To be precise about what this framework is and isn't:

This is not an argument that people are never listened to when they're being inconvenient. Sometimes people are dismissed because what they're saying is genuinely unwelcome, untrue, or inappropriate, and that is a real and separate problem.

This is not an argument that experts are always right. Expertise is valuable precisely because it is not infallible. It is a structured, evidence-based way of being right more often, not a guarantee.

This is not an argument that institutions are intentionally harmful. Nor is it an argument that institutions are never intentionally harmful, or that bias and -isms don't shape real decisions — they do, and they matter. But most of what this publication examines happens without anyone deciding to cause harm.

What this publication means by involving Cassandra in its language is narrower and more specific than any of those things. It’s what happens when accurate information exists, is communicated, and still fails to move through the pathways required for recognition and action.

Sometimes that failure looks like complete disbelief. Sometimes information exists, but it’s a matter of whose information is considered credible and worthy of action. Sometimes the system believes the information completely and still doesn't act — because acting would require a category, a process, or a decision pathway that doesn't yet exist. Both are part of what this publication studies.

A Note on the Other Cassandra

"Cassandra syndrome" is also used informally to describe a specific relational dynamic, often in neurodivergent partnerships, where one partner's accurate observations are repeatedly dismissed by the other. That usage is real and it matters to the people who use it.

It is not what this publication is about. Here, the Cassandra dilemma names a systems-level pattern — not a relationship diagnosis. If you arrived here carrying that other meaning, the underlying intuition is the same one this publication takes seriously, just at a different scale: I am seeing this clearly, and I feel like no one is acting.

What Happened to What Was Known?

Troy fell because seeing clearly and responding effectively turned out to be two different capabilities. Between knowing and acting is a translation process — the movement from information to understanding, and from understanding to response. That gap is what this publication studies, essay by essay, across healthcare, research, policy, and the systems built to hold all three. Not why didn't anyone know — but what happened between knowing and doing.

That distinction is the heart of the Cassandra dilemma.

… Up Next in The Cassandra Dilemma

If Cassandra’s warning could be true and still ignored, the next question is:

What happens when information moves through a system — but changes along the way?

In the next entry, we follow information as it travels between people, professions, and institutions.

Playing Telephone With Institutions explores what happens when knowledge passes through multiple layers of translation — and why meaning can shift before it reaches the people making decisions.

→ Continue with: Playing Telephone With Institutions

Explore The Cassandra Dilemma

Continue exploring the questions, research, and work behind this publication.

Start here:
→ Start Here: Understanding The Cassandra Dilemma

Learn more about the publication and author:
→ About The Cassandra Dilemma

Read more essays:
→ Browse all essays from The Cassandra Dilemma

Explore concepts and research:
→ Library: Terms, Research, and Foundations

Mental health resources:
If you are seeking mental health support, crisis resources, or treatment information:
→ Mental Health Resources

Professional services:
Amber Young, LMHC provides consultation, education, training, and speaking services focused on mental health systems, clinical practice, and translating knowledge into action.
→ Professional Services

Continue Exploring The Cassandra Dilemma

If you’re new here, start with Start Here for the map of this publication and how the seasons fit together.

If this essay named something you’ve experienced from inside a system — or from just outside one — consider sharing it with someone who might recognize the pattern.

Subscribe now

Share The Cassandra Dilemma

Every system I have ever worked inside asks the same question first:

What kind of thing is this?

The answer determines almost everything that follows. A diagnosis is a category. A job title is a category. A department, a specialty, a funding line, a policy area—all categories. They tell us where something belongs, who is responsible for it, and what kind of attention it should receive.

Categories make complexity workable. Without them, a clinician could not specialize. A researcher could not ask a precise question. An organization could not divide labor across the people who make it function. Categories are what allow expertise to exist in the first place.

Yet every category does something else at the same time. It draws a line. And whatever sits close to that line, whatever doesn’t fit cleanly on one side or the other, becomes harder to see.

This essay is about that line—and what happens to the people, problems, and information that fall near or outside of it.

What a Box Is Built to Do

A box is a form of compression. It takes something complex and gives it a name simple enough to think about, communicate, and act on.

A diagnosis like “OCD” is a box. It lets a clinician recognize a pattern faster, communicate with a colleague in shorthand, and select a treatment approach with evidence behind it. That box has helped an enormous number of people receive care they might not otherwise have received.

A “policy area” is a box. It allows governments and organizations to divide responsibility across issues such as housing, education, healthcare, transportation, or public safety. Without those distinctions, coordinating work at scale would be nearly impossible. Categories help determine who owns a problem, which resources can be used to address it, and where decisions are made.

A “specialty” is a box. It allows professionals to develop deep expertise rather than knowing a little about everything. Cardiologists, trauma surgeons, forensic psychologists, infectious disease researchers, and ERP specialists all exist because complexity requires depth. Specialization advances knowledge, improves quality, and makes sophisticated work possible.

A department is a box. Finance, Human Resources, Information Technology, Quality Improvement, Operations, and Communications each develop their own goals, language, and workflows. Dividing work this way allows organizations to function efficiently. It also means that problems crossing departmental boundaries can become harder to recognize or resolve.

Even a job title is a box. Titles clarify expectations, authority, and expertise. They help people know who to contact and who is responsible for particular decisions. At the same time, they can shape assumptions about who is expected to notice a problem—or whether someone believes it is theirs to address.

Each of these is an example of a system working as intended, not a flaw in it. Complexity requires division, and categories make that division possible.

In fact, you are moving through boxes right now. Even this essay is organized into them. Headings separate ideas into sections. Paragraphs group related thoughts. Individual words compress entire concepts into symbols we can recognize and share. Without those structures, reading this essay would be nearly impossible.

We navigate much of life through nested boxes. A publication contains essays. Essays contain sections. Organizations contain departments. Departments contain teams. Disciplines contain specialties. Diagnoses contain patterns. Each layer reduces complexity just enough that people can understand it, communicate about it, and coordinate action.

What matters is remembering what a category actually is: a simplification of something more complex, and — by the same act — a boundary. That boundary makes some information easier to recognize, communicate, and act on. It can also make other information harder to see, especially when it falls between categories, moves across them, or never quite fits inside them.

What a Box Cannot Hold

The trouble with boxes starts at their edges.

A box is designed to create clarity. It defines what belongs inside and, by doing so, creates an outside. Most of the time, this is useful. The center of a category is where patterns are easiest to recognize, communication is easiest, and action is most straightforward.

The difficulty appears when reality does not arrive in clean categories.

A presentation that looks like three different diagnoses at once and doesn’t sit fully inside any of them. A problem that belongs to two departments, and therefore, in practice, belongs to neither. A person whose experience doesn’t match the criteria closely enough to qualify for the box that would actually help them.

This isn’t the result of anyone’s error. It happens because categories are built around recognizable patterns — around what appears consistently at the center of a category, not necessarily what appears at the margins. The tighter and more useful a box is at its center, the more selective it becomes at its edges. That’s the tradeoff that comes with creating structure, and every tradeoff carries a consequence.

At the edges of categories, information often requires translation. A person may have to explain their experience differently depending on which professional they are speaking with. A problem may need to be reframed depending on which department, funding stream, or decision-making process receives it. A finding may need to be converted into the language of another field before it is considered relevant.

Each translation introduces the possibility of loss.

A detail may be minimized because it does not fit the expected framework. A concern may be redirected because it does not clearly belong to one person or team. A pattern may remain visible to those experiencing it but invisible to the structures designed to respond.

This is where I keep returning to the same theme, from several directions:

As a clinician, wondering how something so clearly present managed to sit outside the categories I had been trained to see.

As a person navigating a system from the other side, wondering why an accurate description of my own experience did not seem to fit anywhere the system knew how to respond.

As someone who has sat in policy and advocacy conversations, watching real and urgent problems get quietly reshaped to fit the boundaries of the meeting, the organization, or the framework available.

Different rooms. Different stakes. Same edge.

Outside of the Box, A Person Does Not Disappear

Something outside a box doesn’t stop existing. It simply becomes harder to translate. Systems often mistake difficulty translating information for absence of information.

A patient still has the experience, whether or not a diagnostic category captures it cleanly.

A problem still produces consequences, whether or not any department has been assigned to own it.

A finding is still true, whether or not it fits neatly into the framework a given field currently uses to research or evaluate it.

Categories organize reality. They don’t create it. What changes is not the reality — what changes is how easily that reality can move through a system built to recognize only what fits its existing categories.

This is where accurate information starts to fall out of the pathway that would otherwise carry it toward recognition and action. Rarely as an intentional act by one person, group, or organization. More often, the box simply wasn’t built to hold it, and nobody built a second box in time.

This Is Not an Argument Against Boxes

It would be easy to read all of this as a case against categories, specialization, or expertise. That’s not the point.

Categories are what make it possible to develop real expertise instead of shallow familiarity with everything. Specialization is what lets a clinician actually know a condition well enough to treat it precisely, instead of just recognizing that something is wrong. Systems need this structure to function at any scale beyond a single room.

We have to have boxes. The real question is what happens to the people, the findings, and the problems that don’t fit neatly inside the ones we’ve already built — and whether systems built to work in categories can develop the capacity to notice their own edges.

What Happened to What Was Known?

Somewhere in nearly every story like this, the information already exists.

Someone describes a pattern. Another person documents a finding. Still another lives an experience closely enough to recognize that something is being missed.

The information exists and is communicated, but it doesn’t always arrive in a form the system knows how to recognize, prioritize, or act upon. Somewhere along the way, it crosses a boundary and loses context. It enters a category where it does not fully belong. It reaches a person, department, or structure that does not have the authority, language, resources, or framework to carry it forward.

Once information falls outside the pathways a system is built to recognize, it can begin to look like uncertainty, complexity, or absence — even when the underlying reality has been present all along.

That is the Cassandra dilemma: the space between what is known and what becomes recognized, between what is communicated and what becomes actionable.

… Up Next in The Cassandra Dilemma

If categories shape what systems can see, the next question is:

What happens when someone sees something important — but the system does not recognize it?

In the next entry, we return to the story of Cassandra: the person who could see what was coming, but whose knowledge could not become action.

Who Is Cassandra? explores the gap between information existing and information being believed, valued, and acted upon.

→ Continue with: Who Is Cassandra?

Explore The Cassandra Dilemma

Continue exploring the framework, resources, and work behind this publication.

Start here:
→ Start Here: Understanding The Cassandra Dilemma

Read more essays:
→ Browse all essays from The Cassandra Dilemma

Explore concepts and research:
→ Explore the Library

Mental health resources:
If you are seeking mental health support, crisis resources, or treatment information:
→ Mental Health Resources

Professional services:
Amber Young, LMHC provides consultation, education, training, and speaking services focused on mental health systems, clinical practice, and translating knowledge into action.
→ Professional Services

Continue Exploring The Cassandra Dilemma

If you’re new here, start with Start Here for the map of this publication and how the seasons fit together.

If this essay named something you’ve experienced from the inside of a system/box, or from just outside one, consider sharing it with someone who’d recognize the shape.

Subscribe now

Share The Cassandra Dilemma

I remember the moment I finally understood Obsessive Compulsive Disorder (OCD) — really understood it, past the checklist version I’d been trained on. It was over a decade into practice. The feeling wasn’t simply “I learned something new.” It was closer to a punch to the gut, with a weight on the heart to match.

It was the realization that something important had been there all along and I’d missed it. People had described it. Research had documented it. Individuals had lived it. Yet somehow, the information had not been received, understood in context, and translated into action.

I’ve sat with other clinicians in that same moment since — the surprise, the discomfort, and most of all, the grief. Most people do not enter helping professions because they want to overlook suffering. They enter because they want to understand it, reduce it, and respond well.

The question for me then, and often the one I hear echoed now, is: “How did I not know?” That question matters, deeply. Yet it is part of a much larger picture.

That question could have stayed personal. Instead, it kept finding company.

The Question That Changed My Lens

Over time, I noticed the same question emerging across places that appeared unrelated.

A client describes symptoms for years before receiving an explanation that fits.

A clinician recognizes a concern but struggles to move that information through systems built around different priorities.

Researchers publish findings that take years — or decades — to meaningfully change practice.

Frontline workers identify problems that never reach the people making decisions.

Communities raise concerns repeatedly and wonder why the response does not match the urgency they are describing.

The details were different. The settings were different. The structure felt familiar. The question that began to follow me was: What happens to information as it moves? That question began to change my focus and the way I looked at mental health, individual care, and systems.

Complex systems are not built from one person’s decisions. They are built from pathways: categories, documentation, professional roles, policies, incentives, workflows, and assumptions about what information matters. Those structures exist because complexity requires organization.

A healthcare system cannot function without specialization. Research cannot advance without defined questions. Organizations cannot operate without processes and decision pathways. Without specialist providers, certain conditions, presentations, and groups may not be fully understood and treated with the nuance and care they deserve.

And yet, every structure creates boundaries. Every boundary changes what is easier to see, to communicate across and through. This is where my attention increasingly shifted. The issue was not simply whether information existed. It was what happened after.

How was it translated?

Who recognized it?

Where did it go?

What changed along the way?

The Structures That Shape What We See

My attention shifted from individual moments to recurring patterns. A missed diagnosis. A delayed treatment. A system unable to meet the needs it was designed to serve. A policy that does not produce the outcome it intended. A problem identified by people closest to it that does not reach the people positioned to address it. These situations are often discussed as isolated events. Sometimes they are. Other times they represent something larger: a gap between what a system is designed to capture and what is actually occurring within it.

Categories help us organize information. Documentation helps us communicate. Specialization allows expertise to develop. These are necessary parts of complex systems. They also shape what information moves easily, what requires additional translation, and what may become harder to recognize.

The Same Pattern, Different Vantages

I encounter this dilemma from multiple positions. I am a Licensed Mental Health Counselor and have spent the last decade specializing in OCD and anxiety-related disorders, helping people recognize patterns that had previously been misunderstood, and now teaching that nuance to providers, universities, and mental health centers. I understand the value of specialization deeply.

I have also experienced healthcare systems from the other side of the clipboard. I have received diagnoses later in life that changed how I understood myself and my history. I have seen how systems can struggle to recognize what does not fit expected patterns. Those experiences deepened my interest in the relationship between expertise, lived experience, and institutional decision-making.

Each vantage point — clinical, research, policy, lived experience — contains real information. The challenge is how those pieces connect, or fail to.

What Happened to What Was Known?

This publication began with one question: What happened to what was known?

Not every missed diagnosis has the same cause. Not every complex problem has a simple explanation. Across nearly every system involving people and information, a recurring theme is typically found: information can be known, communicated, documented, and experienced — but still fail to become meaningful action.

The essays that follow explore that gap between information and response across healthcare, mental health, policy, education, and organizations. They examine the moments when something important appears to be missed and ask a broader question: What happened between knowing and doing?

…Up Next in The Cassandra Dilemma

If systems are built to organize complexity, then the question becomes: what happens when the process of organizing also changes what can be seen?

In the next entry, we explore the problem with boxes — how categories, labels, and frameworks help systems function while also shaping what information is preserved, what is lost, and who becomes visible.

Because before we can understand why information disappears, we first have to understand how we decide what counts as information in the first place.

→ Continue with: The Problem With Boxes

Continue Exploring The Cassandra Dilemma

If you are new here, begin with Start Here for an overview of this publication and how the seasons fit together.

Subscribe to receive future essays exploring the gap between what is known, what is recognized, and what becomes possible.

If someone in your network has ever asked, “Why did nobody see this sooner?” consider sharing this essay with them.

Subscribe now

Share The Cassandra Dilemma