Unless It Is Blood, Flood, or Fire, It Can Wait

I can lose an entire morning answering things that never should have made it to me.

Someone marks an email urgent. Somebody asks for five minutes. A problem that has been sitting for three days suddenly needs my answer right now.

Before I know it, I have solved everybody else’s problems and haven’t touched the work only I can do.

That is why I started saying:

Unless it is blood, flood, or fire, it can wait.

In property management, those words are not completely metaphorical. People can be in danger. Buildings can flood. Fires happen. There are moments when I need to stop what I am doing and respond immediately.

But a red exclamation point is not a fire.

Someone else’s anxiety does not automatically make something my emergency. And a problem does not become mine simply because I know how to solve it.

What actually qualifies?

Blood means someone is hurt, unsafe, or at immediate risk.

Flood means active damage is happening or an operational problem is getting worse while we wait.

Fire means there is a serious and immediate threat to people, property, compliance, reputation, or the business.

Everything else can be captured, assigned, scheduled, or handled by the person who already owns it.

The filter is simple. Living by it is harder.

Leaders are often rewarded for rescuing. We become known as the person who can fix anything, and that feels good for a while. Then one day we look up and realize that everybody else’s work has become our work too.

That is not leadership. That is a bottleneck with a title.

Protecting two hours

I recently talked with a woman I mentor about protecting 10:00 a.m. to noon every day.

Two hours.

No routine calls. No dropping by with questions that could wait. No handing her a decision someone else already had the authority to make.

Those two hours were not about ignoring her team. They were about giving her enough uninterrupted time to do the work that required her judgment and focus.

The boundary also gave her team room to think:

• Can I solve this?
• Do I already have the authority to decide?
• What have I tried?
• What do I recommend?
• What actually happens if this waits until noon?

Those questions build judgment.

When I answer every question immediately, my team learns where to find me. When I create a clear boundary and ask better questions, they learn how to find the answer.

That is support too.

The discomfort is part of it

Protecting time can feel selfish when people are used to having immediate access to you.

You worry that you look unavailable. The team tests the boundary. Routine questions still arrive dressed as emergencies because urgency worked before.

That does not mean the boundary is wrong. It means the old habit has not caught up with the new expectation yet.

The leader has to stay consistent long enough for the team to believe her.

Tell people what qualifies as an interruption. Give them the authority to handle routine matters. Create a predictable time for everything that is important but does not need an immediate answer.

When someone brings you a problem, ask what they recommend before providing the solution. Then let them use the judgment you hired them to have.

I still have to practice this

My first instinct is often to step in.

Sometimes I can solve the problem in five minutes. But if I solve it every time, I can almost guarantee the same kind of problem will return to me tomorrow.

Quick is not always the same as helpful.

Sometimes the best thing I can do for my team is answer. Sometimes the best thing I can do is ask a better question. And sometimes the best thing I can do is let it wait.

Ask a Better Question

If you protected two uninterrupted hours tomorrow, what would your team truly need permission to interrupt?

Write down the answer. Make it specific. Share it with the people around you. Then give yourself permission to focus without guilt.

If it is blood, flood, or fire, they know how to reach you.

Everything else can wait.