Stop Calling Everything Critical

If everything on your job is critical, nothing is. And I hear it in every trailer I walk into.

"That's critical." "This is critical." By Wednesday, fourteen things are critical, the crew has stopped listening, and the two things that are actually critical aren't getting the urgency they need. The word got used up.

"Critical" has a definition. It's not a feeling. It's not "important" or "loud" or "the boss is asking about it." Here's the actual definition:

The critical path is the longest path through the schedule. The activities on it have zero float. If any one of them slips by a day, the project slips by a day. Day for day. That's what critical means.

Zero float. Longest path. Delays the project.

Now think about how the word gets used in the field. Most of what gets called critical is just loud. It's late, or it's somebody's pet activity, or a super is getting pressure from above and passing it down with the scariest word he knows. None of that makes it critical. An activity with eight days of float is not critical no matter how loudly somebody says it is.

Here's how it usually goes. A super walks the job, sees the electricians behind, and tells the foreman the rough-in is critical. The foreman pushes his crew into overtime. Then the scheduler runs the update and the rough-in had nine days of float. The real critical work was the underground, sitting at zero, and nobody was watching it because the word got spent on the wrong activity. That's not a communication problem. That's a vocabulary problem.

And it costs you twice.

First, the crew stops believing you. They've heard it fourteen times this month and the job didn't slip fourteen times, so they learn to ignore the word. Then the actually-critical work shows up, the work with zero float that will move the end date, and it gets the same shrug as everything else. You burned your alarm on false alarms.

Second, it costs you credibility in the trailer. The day you call something critical and the scheduler pulls up the float column showing six days, you're done. Everybody in that room just learned not to trust your read of the schedule. Words mean things. Use the wrong ones and people stop listening to the right ones.

So how do you use it right?

First, check before you say it. Look at the float on the activity. Zero float on the longest path: critical. Anything with float: not critical. It takes ten seconds and it keeps you honest.

Second, give the almost-critical work its own language. Plenty of activities aren't critical but they're getting tight, or they drive the next milestone, or they're the only thing standing in front of a crew that needs the area. Say that. "It's not critical, but it's driving the concrete pour" is more useful than calling it critical and being wrong. Precision beats volume.

Third, protect the word. The fewer things you call critical, the more power it has when you use it. Say "this is critical" twice in a year, and both times the job would genuinely have slipped, and people listen the third time. That's credibility, and you build it one accurate call at a time.

The schedule already told you what's critical. It's the path with no room. Read it, say it plainly, and save the word for when it's true.

That's the whole lesson, and it's free. If you want it concentrated, that's what The Plan Room is for: the lessons in order, feedback on your own schedule, and a room full of people working through it alongside you. Free group on LinkedIn: https://www.linkedin.com/groups/40982025/