You've Already Fixed This. So Why Is It Back?
Consider a nursing unit staff meeting where bedside reporting is back on the agenda.
It has been addressed before. There are laminated signs in the patient rooms describing exactly how it should happen. The expectation has been communicated. People know what is supposed to occur at the bedside before the outgoing nurse leaves.
And yet the conversation is happening again.
Someone suggests retraining. Someone else suggests monitoring compliance more closely. Maybe the expectation needs to be reinforced again. All of these things are available, but before adding anything, I would want to understand why the organization is having this conversation again.
There are four questions I use to work backward through a performance problem like this:
What decision or priority set this in motion?
What conditions did it create?
How did people adapt to keep the work moving?
What remains in place to produce it again?
The order matters because each question takes the conversation a little farther away from the performance everyone can see and closer to what may have produced it.
What decision or priority set this in motion?
Bedside reporting didn't appear on the unit by accident. Someone decided handoff should happen differently, and there was a reason for it. Maybe the goal was safer transitions, better patient experience, fewer errors at shift change, or some combination of them. That decision established an expectation for how the work should happen.
Before talking about why people aren't consistently meeting the expectation today, I want to understand the decision that created it. What problem was bedside reporting intended to solve, and what did leadership expect to change because of it? What assumptions were made about how the process would fit into the work already happening at shift change?
Then I want to know what has changed since that decision was made. Staffing models change. Huddles get added at shift change. Documentation requirements change. New priorities get added. Work that once fit together reasonably well begins competing for the same people and the same minutes.
The expectation may have stayed exactly the same while the operation around it changed considerably. That matters because the recurring problem we're looking at today began somewhere before today's missed bedside report.
The next question helps us find out where.
What conditions did it create?
A decision made in a meeting eventually becomes somebody else's operating environment.
Imagine bedside reporting in an actual shift change. Both nurses need to be available at the bedside. The patient becomes part of the conversation, adding an element neither nurse completely controls. Other patients continue needing care, documentation still has to be completed, and the incoming nurse may be receiving several patients at roughly the same time.
Now imagine that staffing is below plan, acuity is higher than expected, a patient needs immediate attention, someone is coming back from a procedure, or the outgoing nurse is already beyond the scheduled end of the shift. The expectation hasn't changed, but the environment in which someone has to meet it has.
That's what I want to understand. What does the process require from the people doing the work? How consistently do the conditions give them what the process requires? What else is competing for the same time, attention, and people?
A leadership decision can make perfect sense when it is made. What matters next is what that decision becomes when it reaches the work, because the people standing in those conditions must figure out how to operate inside them.
How did people adapt to keep the work moving?
This is where the conversation can change.
The unit doesn't stop because the conditions aren't ideal. People adapt. The handoff may happen at the station. The essential information still gets communicated, the outgoing nurse leaves, and the incoming nurse moves to whatever requires attention next. The patient isn't involved, but the work keeps moving.
On that shift, the choice may make complete sense. Then another difficult shift happens, and the same adaptation works again. A workaround that helped people get through one difficult shift becomes useful whenever the same conditions appear. When those conditions keep appearing, the workaround starts becoming part of how the unit operates.
Now imagine what each level of the organization sees. The people doing the work know why report moved away from the bedside. Their manager may know bedside reporting becomes difficult on certain shifts. Eventually, a compliance report shows something much simpler.
Bedside reporting isn't happening consistently.
That statement can be completely accurate while missing the part of the story that would change the conversation about what to do next.
That is Truth Drift™: the loss of meaning as information travels upward.
By the time bedside reporting is back on the agenda, the organization may be discussing a compliance problem while the people doing the work have been responding to an operating problem. That difference matters because whatever leadership decides next is going right back into the same operation.
What remains in place to produce it again?
This is the question I would spend the most time on because the organization has already responded. Staff were retrained. The expectation was reinforced. Compliance was monitored. The process was made more visible, which is how the laminated sign ended up in every patient room.
That's a lot of activity, and here we are again.
So what is still there? Is the staffing model the same? Are the competing demands at shift change still competing? Has acuity changed? Do nurses have the time the process requires on a normal shift? As responsibilities have been added, has anything been removed? Are the circumstances that made the workaround useful still showing up?
Those questions take us somewhere another round of training cannot. They tell us how much of the condition producing the behavior actually changed the last time the organization addressed the problem. If those conditions remain, the workaround still has a reason to exist.
The sign on the wall describes what should happen. The conditions on the floor describe what does.
That doesn't tell us bedside reporting should be abandoned. It tells us there is still something to understand, and I would want to understand it before adding anything else.
The performance chain worth keeping in mind is simple.
Leadership decisions → conditions → how people adapt → performance → measurement
Most performance conversations begin at the end of that chain. Something happened. A measure moved, an expectation was missed, or a process wasn't followed consistently. Leadership sees the result and starts deciding what to do about it.
The four questions take the conversation in the other direction. What set this in motion? What did it create? What did people do in response? What is still there?
Sometimes working through them will lead right back to training. Sometimes the process needs to change. Sometimes someone knew exactly what was expected, had everything required to do it, and chose not to. Accountability belongs in that conversation. The point is to know which problem you're actually solving before you solve it again.
When an organization has already trained, monitored, clarified, reinforced, and redesigned, the return of the same problem is information in itself. Something is still producing it.
Spend some time with the last question.
You have already fixed this. What did you leave untouched?
When the same performance problem keeps coming back
The return of a problem your organization has already addressed is information in itself.
The Organizational Performance Diagnostic helps healthcare leadership teams work backward from the performance they can see to understand the leadership decisions, organizational conditions, and adaptations that may still be producing it.
If your team has already trained, monitored, clarified, reinforced, or redesigned and the same problem keeps returning, that's a useful place for us to start.
Comments