Room standardisation can work, I’ll tell you how

If the rooms are the same, the adjacencies are the same, the equipment is the same, and the technology is the same; surely the way the hospital works should be broadly the same too.

And yet, we know it isn’t.

Put two hospitals with almost identical physical environments side by side and you can see very different things happening. One may have smooth patient flow, confident staff and well-understood processes. The other may have delays, workarounds, duplicated effort, and staff who have quietly developed their own ways of making the building work for them. The interesting question is: why do we ask too much of the building?

A building is not an operation

We spend an enormous amount of time getting the physical environment right. We think about clinical adjacencies, room sizes, circulation, visibility, infection prevention, equipment, technology and logistics. We standardise wherever we can because standardisation brings familiarity, efficiency and the opportunity to learn from previous projects. But there is a point where the drawing stops. The building might be complete, but the operation isn’t.

A ward can be designed around a particular model of care, but that doesn’t mean the model of care will automatically happen. A medication room can be positioned perfectly, but that doesn’t mean medicines will flow through the ward efficiently. A clinical workspace can be designed to support multidisciplinary working, but that doesn’t mean the multidisciplinary team will actually work together in that space. A new digital system can be installed, but that doesn’t mean people will use it in the way it was intended. The physical environment creates the conditions for something to happen. It doesn’t make it happen.

Look at it as a workflow

This becomes much clearer if we stop looking at the hospital as a collection of rooms and start looking at it as a series of workflows. Take a patient arriving on a ward. The building provides the bedroom, clinical spaces, staff base, storage, equipment and circulation routes.

When the patient arrives at the hospital, who receives them and who takes responsibility for them?  Where is information recorded, who records it, where is it shared? Who assesses them? Who else needs to be involved in their care? Where is the equipment needed? When does the multidisciplinary team review them? What happens if their condition changes? Who makes the decision? How is that decision communicated? Where is it documented? What happens next? None of these questions are answered by the floor plan alone.

The building influences the answers, certainly. A poorly positioned store might create unnecessary walking. Poor visibility might affect observation. The location of a clinical room might make a particular workflow awkward. But even a beautifully designed hospital can perform badly if the operational workflow doesn’t align with the building design. And this is where the distinction becomes important.

We can standardise the environment. We cannot assume that we have standardised the operation.

Two identical buildings with different workflows will produce different outcomes

Imagine two wards with exactly the same layout. Same number, size, layout and arrangement of patient rooms, clinical spaces, staff bases and all the identical equipment and technology. On Ward A, the team has rehearsed how admissions work, so everyone understands their role. Equipment is available where it is expected to be and staff know how to use the technology. The multidisciplinary team understands when and where decisions are made. The escalation processes are clear. The physical environment supports the workflow.

Now imagine Ward B. The building is identical. However, staff haven’t had the opportunity to work through the new processes together. Responsibilities are unclear. Some equipment is stored differently because the team has developed its own preferences. Staff use workarounds for parts of the digital system. Escalation processes vary between shifts. Suddenly the same building is producing a very different experience.

It’s highly likely that patients and staff are walking more to get where they need to be. Clinicians and are experiencing more interruptions to their workflow. More handovers, more duplication, more uncertainty, more variation in processes. The building hasn’t failed. The system around the building hasn’t been brought together. This distinction matters enormously when we talk about standardisation.

So what are we actually standardising?

When we’re wondering how to standardise a hospital, maybe, instead, we should be considering which parts of the hospital should be standardised.

There is huge value in standardising inputs – physical environments, equipment approaches, technology, and design principles. However, the outcome we actually care about is what happens when a patient enters the building. We care about safe care, patient flow, staff experience, productivity, resilience, and whether the clinical model can actually operate as intended. To achieve a high standard of care we need to connect the dots between the physical building and the people who operate it.

This is where the operational readiness and activation process becomes so important.

Operational readiness and activation – the missing connection

Operational readiness and activation is sometimes treated as something that happens towards the end of a project and is oversimplified with a checklist, training programme, and move plan, then one final push before opening day. This really undersells the importance role it plays in achieving the best out of a new healthcare facility.

At its best, it is the process of asking a much more fundamental question: “Can this organisation actually operate this building on day one, in the way it was designed to operate?”

To get to the answer you have to test the essential working order of the hospital – clinical pathways, operational workflows, workforce model, equipment and technology, interfaces between teams, what happens when things don’t go according to plan. And, critically, doing this before the building opens rather than discovering the problems after the staff and patients arrive.

From drawings to reality

This is where simulation becomes particularly powerful. You can take a workflow from the clinical model and physically walk it through the building to understand patient flow, how staff work, the information and equipment they require, who needs to be involved in various activities. You work through the escalation process. You see what happens during peak periods or when the ward is full. You find out what goes wrong during an outbreak or when technology doesn’t work.

Suddenly, things that looked perfectly reasonable on a plan start can look very different. There’s no logical place for a necessary piece of equipment. Two teams need the same space at the same time. There may not be an appropriate place for clinicians to handover. A digital process could add an extra step rather than removing one. While these aren’t necessarily design failures, they are system integration issues. And the earlier we find them, the easier they are to fix.

The real opportunity

For me this is the most interesting part of standardisation. The goal shouldn’t necessarily be to create identical hospitals but rather to create consistent outcomes from well-designed systems. Sometimes that will require standardising the building or the workflow or allowing local variation. Often it will require all three.

The real measure of success isn’t whether two hospitals look the same. It is whether they can reliably deliver the intended clinical model.

It requires a very different way of thinking about a capital project, where the building is no longer the end product but rather one component of a much bigger operating system.

It means moving beyond:

Building → Equipment → Open

And moving towards:

Clinical Model → Workflow → Building → Equipment & Technology → Workforce → Simulation → Activation → Continuous Improvement

So if we standardise a hospital building, should we always get the same clinical and operational results? Of course not. Because a standardised building doesn’t create a standardised operation. People do. Processes do. Technology does. Workflows do. Preparation does. And bringing all of those things together is what the 0perational readiness and activation process is really about.

The building may be ready to open. But is the organisation ready to operate it?