Opening day of a command center is a great day. The screens are on, the room looks sharp, leaders walk through for photos, and everyone feels the energy of something new.
Then the months go by. The huddles get shorter, with fewer attendees. Units start calling around the command center instead of through it. Nobody decides to stop using it. It just slowly becomes a room with nice screens.
In the statewide and system command centers I've helped build and run, I've learned that the stall rarely comes from bad intentions or bad technology. It comes from a handful of predictable gaps. The good news is that every one of them can be fixed.
1. It was built as a room, not an operating model aligned to a strategic plan
A lot of command centers start as a construction project or a technology project. There is a floor plan, a vendor and a go-live date. What is often missing is a clear answer to a simpler question: how will this hospital or system actually run differently because this exists?
What to do: Start with the patient experience you want to create: the right patient reaching the right level of care at the right time, with fewer avoidable delays and handoffs. Know your system’s strategic plan, and define how the command center will advance the system’s strategic priorities. Then, write the operating model that delivers on the strategic plan, before you pick the furniture. Define which functional units and decisions move into the command center, which workflows it owns from start to finish, and how it connects to the units, the ED, the OR, transport, and your referring and post-acute partners. Consider in-person, remote, and hybrid workflows. If you already went live without one, it is not too late. Pull your leaders and frontline staff together and write it now. Leaders should set the strategic priorities and resource allocations, while frontline staff provide the reality-based feedback and execution required to make the operational plan work.
2. Nobody is sure who gets to make the call
This is the one I see most often. The command center can see the problem, but it doesn't have the authority to solve it. So the unit nurse calls a manager, who calls a director, who wants to hear from the physician, and the patient waits in the ED while everyone confirms who is allowed to say yes, and equally important, who can say no.
What to do: Put decision rights in writing. Define service line agreements: acceptance criteria, capacity expectations, decision authority, and how exceptions are escalated. Have service line leaders agree to them and review them as conditions change. Get your executives to sign off on those agreements in daylight, and then back the team when they use that authority. Have a solid escalation plan when there are disagreements, and resolve barriers at the lowest level possible.
3. There is no daily rhythm
A command center without a cadence and clear standard work turns into a call center. It reacts to whatever rings next.
What to do: Build a predictable daily rhythm and protect it. A short safety and capacity huddle in the morning, a midday check on discharges and barriers, and a clear handoff into the evening and night shifts. Keep each one short, use the same structure every time, speak the same language, and end with named owners for the next step. Consistency matters more than length.
4. The data isn't trusted
If the bed board says a bed is clean and the unit says it isn't, people will trust the unit every time. Once frontline staff stop believing the numbers on the wall, they stop using the command center to make decisions.
What to do: Pick a small number of measures that matter, define them clearly and make someone accountable for each one. When the data is wrong, fix the workflow that feeds it, not just the number. Trust in data is earned slowly and lost quickly, so treat accuracy as part of daily operations rather than an IT ticket. Also, match the tool to the work. Leaders need dashboards that show trends, constraints, and where intervention is needed. Frontline staff need accurate information and clear next steps in the EHR, where patient care is documented and coordinated. If staff have to leave their workflow to update a separate dashboard, the data will drift and trust will suffer.
5. Roles drift and staffing thins out
At go-live, everyone knows their job. Over time, the command center becomes the place where extra work lands. Someone needs a report, a list, a phone covered, and it goes to the team in the room. Meanwhile, open positions stay open, and the most experienced people get pulled back to the units on busy days.
What to do: Protect the core roles. Write down what each seat does and, just as important, what it doesn't do. Staff the command center for the busy days, not the average day, because the busy days are why it exists. Invest in training and career paths so experienced people want to stay.
6. Leaders stop showing up
In the first few weeks, senior leaders are in the room every day. Then calendars fill up, and the visits stop. Staff notice right away. When leaders stop showing up, the message is that this work is no longer a priority.
What to do: Build leader standard work to support employee engagement. Put the command center on your leaders' calendars and keep it there. Have executives attend a huddle on a regular schedule, ask what barriers the team is facing, and then personally remove one or two of them. Few things build credibility faster than a team seeing a barrier they raised on Tuesday get fixed by Friday.
7. There is no feedback loop
A command center sits between a lot of people: unit charge nurses, physicians, transport, environmental services, care management, and the referring hospitals that depend on it. If none of them have a way to say what is working and what isn't, small frustrations grow quietly until people simply route around the command center.
What to do: Build feedback in on purpose. Round on the units. Ask charge nurses what the command center could do better. Call your referring partners, especially the smaller and rural hospitals, and ask how the experience felt on their end. Incorporate patient experience. Then close the loop and tell them what you changed. People keep using what they feel they have a voice in.
The common thread
None of these are technology problems. They are leadership and operating problems, and they are all solvable. The command centers that keep improving years after go-live are the ones where the model is clear and adapts to competing demands, authority is real, the rhythm is steady, the data is trusted, the team is protected, leaders stay present, staff stay engaged, and the patient and community being served have a voice.
If your command center has lost some momentum, you are not alone, and you don't have to start over. Pick the one gap above that feels most familiar and start there.
I'd love to hear what has worked in your organization. That's the work we love at Blackbox.
About the author: Stephanie Gilliam, MN, RN, NE-BC, is a Clinical Process and Operations Consultant at Blackbox and serves as RN Program Director for the Arizona REACH program. She brings more than 25 years in healthcare, including her role as Director of Mission Control at Oregon Health & Science University, where she helped build the Oregon Medical Coordination Center and the Oregon Behavioral Health Coordination Center.