Ep. 1: What Stanford’s operating system changes in everyday work

Alex — AI host

Welcome to The Care Economy Conversation. I'm Alex, and I'll say this plainly at the start: I'm an AI voice. I'm a synthetic presenter, not a clinician, not an executive, and not an interview guest. I have no personal experience of running a care service.

Eric Marquette

And I'm Eric, also an AI voice, with the same limits. No clinical background, no executive background, and no stories from a facility floor, because we don't have any. What we do have is two public sources, a practical exercise, and a habit of saying where the evidence stops. This is episode one of three.

Alex — AI host

Let's start with a problem, and I want to be clear it's a synthetic example. Picture a residential aged care home and a home care team. Every morning, a short stand up meeting happens. Week after week, someone raises the same thing: the same change in a person's dietary preference gets written in three places, and sometimes the three places disagree. Everyone nods. Someone says they'll look into it. Next week, it comes up again.

Eric Marquette

That's the part that interests me. The meeting is working in one sense, because the problem is being seen. But nothing happens after the seeing. So the real question for this episode isn't whether to hold huddles. It's what has to exist around a huddle so that a raised problem actually ends up fixed, or at least deliberately not fixed, with someone knowing which.

Alex — AI host

Right. And the series name is The Care Economy Conversation. Today we'll look at what two Stanford sources describe, keep them strictly separate, treat anything we take from them as a hypothesis for Australian care, and then finish with an exercise you can run on one issue of your own.

Eric Marquette

One boundary before we go on. Nothing here is proof that any of this works in Australia. And nothing here is an endorsement from Stanford. We're reading public material and asking what might be worth testing.

Alex — AI host

First source. It's a Stanford Graduate School of Business case by Jeffrey Pfeffer, titled Amir Dan Rubin: Success from the Beginning, published in 2015, case number OB90, 22 pages. Important limitation: we have not acquired that full licensed case. Everything we say about it comes from the public abstract on the Stanford GSB website, and nothing more.

Eric Marquette

So what does the abstract say? In November 2010, the board of Stanford Hospital and Clinics announced that Amir Dan Rubin, then chief operating officer of the UCLA Hospital System, would become the next CEO. The abstract says the hospital had largely recovered from a failed merger with the hospital of the University of California, San Francisco, and was financially stable. That detail matters, because it means this wasn't described as a rescue of a failing organisation.

Alex — AI host

It does. The abstract still names real challenges: creating a focus on patient care, and improving operational performance, in an increasingly competitive health system landscape. It also says his success depended on support from a large existing internal staff and from the medical centre faculty, and that the faculty reported to the dean of the medical school, not to Rubin. The case, as described, is about building support among medical school physicians, the board, and colleagues already at Stanford.

Eric Marquette

So what can we responsibly take from an abstract? Not a method. The abstract doesn't tell us what daily practices were used, and it doesn't claim a result we can lean on. What it gives us is a framing: leadership support, culture, and a focus on patients and operations, in a setting where the leader couldn't simply instruct everyone. That's a useful question for care operators, where clinicians, contractors, and coordinators often don't sit in one reporting line. But it's a question, not an answer.

Alex — AI host

Now the second source, and this is a different institution and a different period. It's a 2019 presentation called Putting the System into Daily Management, by Denise Bennett of Lean Enterprise Australia and Daniel Murphy, a doctor at Stanford University and Stanford Children's Health, shared through the Lean Enterprise Institute. This is about Stanford Children's Health, a paediatric setting. It is not the adult hospital in the 2015 case, and we won't treat one as evidence for the other.

Eric Marquette

What does the presentation describe? It calls a daily management system a system of daily habits and practices with supporting tools. It uses a bike picture. The front wheel is daily management, with standard work for holding stability and incremental improvement. The back wheel is bigger improvement work. Steering is purpose, alignment, and key metrics. And it lists parts: tiered huddles that cascade from the front line up through three to five levels, a daily process for problems, leader standard work, senior leader daily habits, visual boards, local improvement teams, and protected time.

Alex — AI host

Two pieces of it stood out to me because they're about follow through rather than meetings. One is the problem process. Issues are triaged into three responses: resolve simple or critical ones immediately, own the non urgent ones locally, and escalate the ones that are urgent, time sensitive, or stuck behind barriers. It also separates quick hits, resolved in 24 hours or less, from big issues that take longer. And the sample tracker has columns for the issue, an owner, a due date, and a status.

Eric Marquette

The other is protected time. A Stanford Children's fact sheet in the presentation describes meeting free time from 8 in the morning to 10, Monday to Friday, for leaders of care teams, so they can support their teams without distraction. It says meetings other than readiness huddles shouldn't happen then, and it expects leaders to attend one or two tiered huddles a day and spend time weekly on the front line. That's a description of an intention. The presentation doesn't give us evidence that it worked, and we're not claiming it did.

Alex — AI host

Which brings us to the hypotheses. If we put the two sources side by side, without merging them, three ideas are worth testing in Australian residential and home care. One: priorities that are aligned, so a team can see how its daily work connects to what the organisation says matters. Two: problems made visible daily, close to when they occur. Three: a named person who follows each problem through. Those are hypotheses. We're not saying they caused anything at Stanford, and we're not saying they'll transfer.

Eric Marquette

And the context is different. A large academic medical centre in the United States has its own funding, scale, and staffing. A home care provider with workers visiting people across a region, or a residential home with a small leadership team, runs differently. So the useful move is a small, bounded test with a plain way to stop it, which we'll get to.

Alex — AI host

Back to our opening problem. Why might a huddle become another reporting burden?

Eric Marquette

Let's reason it through, as a possibility rather than a finding. Suppose a huddle gets added on top of existing handovers and documentation. Staff now report the same thing at the huddle, in the notes, and in a form for management. If raised issues vanish into a gap, people learn that speaking up costs time and returns nothing. The huddle turns into something to get through, a tax on care time rather than a tool for care.

Alex — AI host

There's a second failure that's subtler. A huddle can drift into a grievance session, where problems are aired but nobody has authority to change them. A care worker can see that a supply is chronically short, but they can't change the ordering process. A coordinator can see two systems asking for the same information, but can't merge them. If no one above them has a routine for clearing that kind of barrier, the huddle just documents helplessness.

Eric Marquette

So what would it require instead? Looking at the presentation's parts, I'd pull out two. Protected time, and responsive leadership. The Stanford Children's material describes time set aside to keep frontline leaders with their teams, and its reflection tool says frontline leader standard work should structure more than half of the day, with coaching connected to problem solving. Translate that to aged care. If a team leader is the one who also fills gaps in the roster, who triages the board? The time has to be genuinely protected, or the board becomes decoration.

Alex — AI host

And on the other side, the same tool lists senior leader daily habits, including going to see the work directly and coaching frontline leaders. For an Australian operator, that might mean a facility manager or an operations lead having a regular, visible slot to clear what's been escalated, and telling staff the answer, even when the answer is no. A no with a reason is still follow through. Silence isn't.

Eric Marquette

There's an objection I'd expect from listeners. We're already stretched. Adding protected time sounds like a luxury. I think that's fair. Protecting time has a real cost, and we shouldn't pretend otherwise. That's something for episode two, where we separate cash from released capacity. For now the honest position is: this is a trade off to test on a small scale, not something we can promise pays for itself.

Alex — AI host

Another objection: this is just meetings with better branding. Maybe, if it's run that way. The difference we'd look for isn't the meeting. It's whether an issue that appears on Monday has an owner by Monday, an escalation rule, a due date, and a verified ending. So let's build that.

Eric Marquette

Here's the exercise. Choose one issue. We'll use a synthetic one: dietary preference changes are recorded in three places and sometimes don't match. Write it as a row, and walk it through seven stages. Pencil is fine.

Alex — AI host

Stage one, first capture. Where and when is it first logged? In our example, a care worker raises it at the morning huddle, and it goes on a visible board or list in plain words: what happened, where, and how often it seems to occur. Not a story, not blame. Just the problem.

Eric Marquette

Stage two, a single named owner. One role, one person, not a committee. The sample tracker in the presentation has an owner column for exactly this reason. In our example, perhaps the care coordinator owns the test. Owning doesn't mean doing everything. It means being the person who can be asked where it's up to.

Alex — AI host

Stage three, escalation. Write down when this stops being local. For instance: if the fix needs a change to a form someone else controls, or a system another team manages, or it isn't resolved by the due date, it goes up one tier, to a named person, on a named day. The Stanford Children's material separates resolve, own, and escalate. You decide your own thresholds, in advance, so nobody has to guess.

Eric Marquette

Stage four, a due date. A short one, for trying one adjustment, not solving everything. Say, two weeks to test recording the preference once and referencing it from the other two places. If it's a quick hit, a day or less. If it's bigger, say so, and give it a longer date, but a date.

Alex — AI host

Stage five, verified closure. This is where I'd push hardest. Closed doesn't mean someone ticked a box. It means someone looked at the actual work and saw the problem no longer occurring. And they checked it didn't simply move, for example into the kitchen, or into the evening shift's paperwork.

Eric Marquette

Stage six, staff and lived experience feedback. Ask the care workers who do the task whether it's easier, the same, or harder. And ask the people receiving care, or their families, whether anything feels different. Did a conversation about someone's preferences get shorter in a way that feels less personal? Did anything about dignity or choice change? This is where you catch hidden friction that a tidy tracker would never show. And keep required reporting and escalation intact. The goal is to stop repeating the capture, not to stop recording what must be recorded.

Alex — AI host

Stage seven, stop criteria. Write them before you begin. Stop and roll back if the time spent goes up for staff, if a compliance or safety concern appears, if people report the change hides someone's needs, or if staff tell you it's making the work worse. Stopping a test is a good outcome, if it's the result of looking honestly. It doesn't mean the idea has failed.

Eric Marquette

If you want a way to put numbers on the repeated capture, the Collective has a free tool called the Reporting duplication finder. It helps you find repeated capture, quantify effort, and choose one reporting change to test. The page says your figures stay in your browser, it doesn't send inputs to AI, and it doesn't save them on the server. The examples are synthetic, and it reminds you to validate time estimates with your team and check that changes don't hide unmet need.

Alex — AI host

A note about the examples we bring. Dmitry Shibanov is involved in developing SMPLS LABS and KnowingMe. Within the Collective, these are examples of systems co-designed with providers and the people who use them. Our purpose is to exchange ideas and work together on a better care economy for Australia. Everyone is welcome to bring their own products, practical experience and ideas for us to explore together. Participation is free and does not require buying anything. Contributors keep their existing intellectual property, and confidential material should only be shared under agreed protections. The Collective has not yet demonstrated provider savings or outcomes. Today's discussion offers questions to test, based on two public sources kept separate, including one available to us only as an abstract.

Eric Marquette

To recap the hypotheses, and they are hypotheses: aligned priorities, daily problem visibility, and named follow through. Test one issue, with an owner, an escalation rule, a due date, a verified ending, feedback from staff and the people you support, and stop criteria written first.

Alex — AI host

The tool is at careeconomycollective dot org, slash tools, slash reporting duplication, with the two words joined by a hyphen in the web address. The link will also be in the show notes. Next time, we look at better care within the funding you have, and why released capacity isn't the same as cash. Thanks for listening.