A video game designer balances a game. The designer sets the coordinates for a wall. The designer sets the coordinates for a character. The character cannot walk through the wall. The character has a hitbox. The wall has a hitbox. When the hitboxes touch, the character stops. This is a rule.

Sometimes the code has a flaw. Two objects try to occupy the same coordinate. The physics engine does not know which object should move. The engine fails. The game freezes. Developers call this clipping. Clipping happens when two correct lines of code meet in one space. The code is perfect in a vacuum. The code is a failure in the game.

The Illusion of the Clean Process

I once watched a person peel an orange. The person peeled the orange in one piece. The skin came off in a long spiral. The person followed a path. The person did not break the skin. The person finished the task. This was a clean process. Most people want a clean process.

They write a manual. They print the manual. They give the manual to a worker. The manual is the spiral. The manual is the path. But the manual assumes the worker is alone. The manual assumes there are no other spirals in the room.

3:00 AM: The Collision in the Lobby

The fire alarm sounds at three in the morning. The sound is loud. The sound is a pulse. The guard is in the lobby. The guard opens the manual. The manual is on page four. Section two says the guard must silence the panel.

The guard must silence the panel to talk to the tenants. The guard must silence the panel to hear the radio. The guard walks to the panel. The panel is a grey metal box. The panel has red lights.

The engineer is in the basement. The engineer hears the alarm. The engineer opens the manual. The manual is on page eleven. Section five says the engineer must not touch the panel.

The engineer must preserve the data. The fire department needs the data. The data shows which sensor triggered the alarm. The engineer walks to the lobby. The engineer sees the panel. The engineer sees the guard.

The guard reaches for the silence button. The guard follows the manual. The engineer moves to the panel. The engineer blocks the hand of the guard. The engineer follows the manual. The guard pushes the engineer. The engineer holds the arm of the guard.

The alarm continues to pulse. The tenants are waiting. The fire department is on the way. Most procedures are written for one actor. The author sits in an office. The author imagines a single guard. The author imagines a single engineer.

The author does not imagine the guard and the engineer together. The author writes a script for a solo performance. The reality is a play with many actors. The actors have different scripts. The scripts overlap. The overlap creates friction.

A lazy guard stays in the chair. A lazy engineer stays in the basement. The lazy people do not follow the manual. The lazy people do not meet at the panel. The alarm stays on. The data stays on the screen. There is no fight.

But these people are diligent. These people are professional. These people are dangerous. They are dangerous because they believe in the procedure. They follow the steps. The steps lead them to the same button at the same time.

The guard believes the silence button is the priority. The engineer believes the data is the priority. Neither manual mentions the other manual. This is a failure of system design. It is a failure of hitboxes. The hitboxes are too wide. The hitboxes overlap. The system crashes.

A building needs a single script. A building is not a collection of rooms. A building is a single unit. The security team needs to know the engineering team. The engineering team needs to know the security team. They must rehearse the alarm. They must rehearse together.

The Shared Protocol Solution

They must find the collisions before the alarm sounds. They must decide who touches the panel. They must decide who talks to the tenants. When fire systems fail, the building is at risk. The sprinklers do not work. The sensors are dark.

This is a high-risk window. The owner needs help. The owner hires Fire watch security. The guards arrive. The guards do not just walk the halls.

The guards are part of a system. The guards use digital reporting. The tool is called TrackTik. The tool tracks the movement of the guards. The tool records the time. The tool records the location.

The guards are trained for the fire watch. They know the building is vulnerable. They do not work in a vacuum. They coordinate with the property manager. They coordinate with the fire department. They use a shared protocol. The protocol is not a solo performance. The protocol is a team effort. This prevents the collision.

The manual for the fire watch is specific. The guard walks a path. The guard looks for smoke. The guard looks for heat. The guard checks the exits. The guard logs the data. The data is visible to the manager. The manager knows where the guard is.

The manager knows the building is safe. There is no confusion. There is no engineer blocking the path. The roles are defined. The roles are rehearsed. Safety is not the absence of an incident. Safety is the presence of coordination.

A manual that works for one person can fail for two people. Complexity defeats competence. It defeats competence by isolating the workers. It gives each worker a perfect set of instructions. The instructions are perfect until they are not. They are not perfect when the hands meet at the button.

I think about the orange peel. The peel was one piece. It was a beautiful result. But the orange was small. The hand was large. There was only one person. If two people tried to peel the same orange, the skin would tear. The spiral would break.

The orange would be a mess. Most buildings are large oranges. Many people are peeling at the same time. They need to know where the other hands are. The guard and the engineer eventually let go. The fire department arrived.

The fire captain looked at the panel. The fire captain was confused. The guard was angry. The engineer was frustrated. The building was safe from fire. The building was not safe from the procedure. The procedure was the fire. The procedure burned the relationship between the departments.

Rewriting the Script for the Room

Property owners must look at their manuals. They must look for the word “I.” They must look for the word “You.” If the manual only talks to one person, the manual is a risk. It needs to talk to the team. It needs to describe the other actors.

It needs to say what the guard does when the engineer is present. It needs to say what the engineer does when the guard is present. Optimum Security trains guards to avoid this. The guards learn the layout. They learn the roles. They learn the communication lines.

They do not just follow a book. They follow a system. The system is dynamic. The system accounts for other people. The guards are part of the building. They are not ghosts in the lobby. They are active participants in a shared safety plan.

The red light on the panel is a signal. It is a signal for action. But action without coordination is just movement. Movement can be destructive. Movement can lead to the collision. The collision is the result of a narrow vision. It is the result of writing for a vacuum.

The world is not a vacuum. The world is crowded. The world has guards. The world has engineers. The world has fire captains. All of them want to do a good job. They want to be competent. They want to follow the rules.

We must give them rules that allow them to work together. We must give them rules that do not clip. We must ensure the hitboxes are clean. A procedure becomes a collision when the hand follows the page but ignores the room.