"We just don't have time to do that right now."
And don't forget the universal follow: "We'll do it later. When things calm down."
How many times have you heard (or said) this in a property operations or corporate support setting?
"We can't stop to organize the shop / roll out the new process / update the tools. We're buried in work orders and emergencies."
Here's why that decision is quietly costing you more than it saves.
I've seen it for years. Teams with great people drowning in their day with reactive actions while tools and parts are scattered in their shop. Every hunt for the right tool or part turns into lost minutes that add up to hours and literally days of lost output.
And it's not just affecting your "hands on" teams. Your knowledge and admin teams burn their time hunting for information or in bad process. Just think about the time you and your teams spend just "looking for stuff". These minutes add up to hours and hours into days of lost productivity.
It can be a tough thing to reconcile: You're not too busy to fix the underlying issue. You're too busy because the underlying issue was never fixed.
If you looked, the numbers would tell you the real story.
It's worth your time to look at the roles in your organization. To see where a person's time goes. You'll see a gap between the hours available vs the hours doing. And what's often in the gap? Transit, searching for parts/tools/information, rework, social interaction (both productive and not).
You have to remember that the "I don't have time" choice isn't neutral. It's an active tax on the very capacity you're trying to protect.
It's the risk of action vs. risk of inaction.
This risk is visible, emotional, and easy to postpone.
Eventually the bill arrives as missed SLAs, safety or compliance issues, higher emergency CapEx, regulatory exposure, or a full crisis that eventually forces change at a multiple of the cost (and with far less control).
Your risk of inaction isn't zero. It's just paid in quiet daily installments you don't notice until the cumulative damage shows up in metrics, morale, or preventable failure. Stephen Covey captured this perfectly in The 7 Habits of Highly Effective People with Habit 7 — Sharpen the Saw. His point:
"We must never become too busy sawing to take time to sharpen the saw."
Stephen Covey
Your "saw" is your team's processes, tools, data access, inspection standards, or continuity plans. Neglect it because you're "too busy cutting," and the saw gets duller. Every future cut takes more effort.
Behavioral science adds another layer: omission bias. We tend to judge harm from taking action (commission) as morally or emotionally worse than equivalent harm from doing nothing. So, we default to preserving the broken system, even when the hidden daily cost of the status quo is higher.
This shows up constantly in operations and risk work deferring proactive inspections, skipping tabletop exercises, or delaying better tools/processes because "we don't have bandwidth right now."
Taking action does require a leap. But it doesn't have to be blind. Start small: one shop organization, one process overhaul, one recurring workflow. Measure the before-and-after friction.
The teams that break the reactive trap aren't the ones with the most spare time on their calendars. They're the ones willing to invest a little time in the system so they can stop bleeding it every single day.
The busiest seasons are often the best time to sharpen the saw — because that's when the pain of the dull blade is impossible to ignore.
What's one process, habit, or literal/metaphorical "shop" in your operation that you've been meaning to organize or improve but keep deprioritizing because the team is "too busy"?
Be honest in the comments — no judgment. We've all been there. Naming it is the first step out of the cycle.
If this hits home for asset managers, property ops leaders, maintenance supervisors, or risk folks in your network, share it.
You can normalize the idea that the highest-leverage move when you're slammed is often carving out time to fix the system itself.
Comments