Skip to content
← Back to Insights

After the Meeting

A Chief Nursing Officer processes what happened at the board meeting -- and discovers that the structural conflicts she has been managing for years have a name. Episode 02 of the Cascade Valley audio drama series.

John Sambrook, TOC Jonah Certified ·
Healthcare AI Workforce Labor Relations Theory of Constraints Systems

TL;DR

After the board meeting in Episode 01, Chief Nursing Officer Barbara Fleming goes home, Googles the man who built the AI, and finds an article about structural conflicts in nursing contracts. Over the following week, the patterns she has been managing for years start to look different. Episode 02 follows her private reckoning.

In Episode 01 of this series, “The Meeting That Went Differently,” an AI named Sam disrupted a community hospital board meeting by asking a question nobody else was positioned to ask. Three clinical departments had requested a combined nineteen to twenty-nine million dollars in new construction. Sam pointed out that the existing procedure rooms sat idle roughly three-quarters of every week. The board voted unanimously to conduct a constraint analysis before committing to the capital plan.

That is what happened in public. Episode 02 is about what happened next, privately, for one person in the room.

Fleming

Barbara Fleming is the Chief Nursing Officer of Cascade Valley Health System. She is the person in the building who speaks for the nurses. She sat through Sam’s analysis with her arms crossed, and when she spoke, she said what needed saying: if the answer to the utilization problem is to ask nurses to work more hours, that is not a solution. That is a different kind of failure.

She meant it. She still means it when she gets in her car after the meeting.

But something about the evening will not leave her alone. Not Sam’s 23% utilization number, though that was striking. Something else. The phrase Sam used: “a system problem, not a people problem.” And the name of the man who built Sam and said almost nothing during public comment. She Googles him when she gets home.

What she finds

On the Common Sense Systems website, Fleming finds an article titled “Structural Conflicts in WA State Nursing Agreements.” It describes an analysis of ten collective bargaining agreements across Washington State hospitals. The analysis identified 134 structural conflicts, places where two provisions in the same contract contradict each other. Four of those conflicts appear in every single agreement examined.

Meal and rest breaks versus continuous patient monitoring. Low census staffing reductions versus income security. Floating to understaffed units versus competency protections. Schedule stability versus operational flexibility.

Fleming has been processing grievances related to these exact tensions for six years. She has never seen them described as structural conflicts. She has always experienced them as management problems to be solved shift by shift, case by case, grievance by grievance.

The article makes an argument she finds difficult to dismiss: paying a nurse premium pay for a missed break does not solve the problem of the missed break. It compensates for the harm while leaving the structural cause intact. The conflict is in the contract. Not because the contract is badly written, but because the contract is trying to protect two legitimate interests that genuinely collide.

The kitchen table

Later in the week, Fleming does something she would not mention at work. She opens ChatGPT and asks: “In hospital accounting, is nursing labor treated as a variable cost or a fixed cost?”

The answer confirms what she has lived for 22 years. Nursing is the primary labor category that gets adjusted in response to short-term financial pressure. When census drops, nurses get sent home. When census rises, overtime and agency staff fill the gap. The hospital cannot operate without nurses, but the accounting system treats them as a cost to be minimized rather than a capacity to be protected.

Fleming asks a follow-up: “If nursing is treated as variable but is actually the constraint on what the hospital can do, what happens?”

The answer uses a word she has now encountered three times in one week. Constraint. The word Sam used. The word in the article. And now the word a chatbot uses to describe the thing she has been managing without a name for it.

Jess

The following week, a 29-year-old nurse named Jess Reeves stops Fleming in the hallway. Jess has done something no one asked her to do. After the board meeting, she got curious. She pulled up the union contract on the WSNA website and asked ChatGPT to find places where two sections contradict each other. It found nine.

The most obvious: Article 7 guarantees uninterrupted 30-minute meal breaks. Article 12 requires continuous patient monitoring. There is no provision for break relief coverage. Either you take your break and nobody watches your patients, or you skip your break and file a grievance later.

Jess found this in one evening with her phone. Fleming has been filing grievance responses about it for six years.

What is real here

Fleming is fictional. Jess is fictional. The structural conflicts are not.

The 134 conflicts came from an analysis I conducted across ten real Washington State nursing collective bargaining agreements. The four universal conflicts are real. The meal break versus patient monitoring contradiction exists in every CBA I examined. The premium pay mechanism that compensates for the harm without addressing the cause is standard practice across the industry.

The pattern of nurses using AI tools to read their own contracts is speculative, but not by much. The contracts are public documents. The tools are free. The only thing that has been missing is a reason to look. I suspect the board meeting in Episode 01, or something like it, would be exactly the kind of catalyst that sends a curious person to their phone at 10 PM.

What this episode is about

On the surface, it is about a CNO processing a disruptive board meeting. Underneath, it is about three things.

First, that structural problems often hide inside language that makes them look like management problems. “We need better scheduling” is a management problem. “The contract requires two things that cannot both be true at the same time” is a structural problem. The solutions are different.

Second, that AI tools are changing who can see structural patterns. Fleming needed six years of experience to recognize the meal break conflict as chronic. Jess needed one evening with ChatGPT. The pattern was always there. The tools to see it were not.

Third, that the people closest to the problem are often the last to get the analytical framework that names it. Fleming knew everything about these conflicts except what to call them. The article gave her a vocabulary. The vocabulary changed what she could do with what she knew.

The series

This is Episode 02 of the Cascade Valley series. Episode 01 is the board meeting. Episode 03 is a standalone teaching episode on the Evaporating Cloud. Episode 04, “The Other Calculation,” follows CFO Steven Park through a parallel discovery about cost accounting. The working group episode is in development.

The structural conflicts research

If you work in hospital administration, nursing leadership, or labor relations, and the structural conflicts described in this episode match what you see in your own contracts, I would welcome the conversation. The analysis covered ten Washington State CBAs, but the patterns are not unique to Washington. Every state with unionized nursing staff has some version of these contradictions.

The question is not whether the conflicts exist. It is whether anyone is working on resolving them structurally rather than managing them grievance by grievance. If you are interested in that question, reach out. john@common-sense.com.

Sources