Nothing’s Anything Until It’s Defined

Building Order in the Chaos of Construction

In construction, one truth I’ve learned time and time again is this:

Nothing is anything until it’s defined.

It’s more than just a catchphrase—it’s a core management philosophy I carry onto every job. Because if there’s one thing construction managers can count on, it’s this:

No two projects are ever the same.

<p>Different site. Different schedule. Different budget. Different team. Different risks.&amp;lt;p>And yet, there’s a persistent phrase I hear far too often:

“Well, that’s how we did it on the last project…”

Here’s the hard truth:

It doesn’t matter how you did it on the last project.
It only matters how you’re contracted to do it on this one.

Yes, there are common industry practices that carry over—means and methods, general approaches, lessons learned. But those aren’t the rulebook. The rulebook is the current set of contract documents: the specs, drawings, general conditions, and any agreed-upon clarifications.

Definition Is Your First Line of Defense

Every project has gaps. No design is perfect. The best teams know how to define expectations upfront—so that when the inevitable chaos arrives, you’ve already set the ground rules for how to respond.

If a spec doesn’t define how concrete should be placed, fine—install it using standard industry practices. But if the spec does define a specific placement method, then you follow it to the letter—or risk having to rip and replace it on your own dime.

Unless you know for a fact that the spec is problematic, the correct move isn’t to ignore it—it’s to submit an RFI and propose an alternate method. But again: don’t act until it’s defined.

Words Don’t Mean Anything—Until You Define Them

To explain this to new team members, I often use a simple analogy:

A word, in any language, is just a sound. It doesn’t mean anything until someone assigns it a meaning. Without a definition, it might as well be barking like a dog.

Construction is no different. A process, a detail, a role, a cost code—none of it means anything to the project unless it’s defined.

And defined clearly.

Construction Managers Don’t Live in a Black and White World

In construction, very few questions have simple yes or no answers.

• Should we install it now or wait until the floor cures?
• Is the contractor responsible for this delay?
• Does this meet spec or require an RFI?
• Can we accept this workaround?

It’s almost never black or white.

Construction managers live in the grey.

We don’t just react—we asse

ss. We balance competing priorities. We sift through what I call the “50 Shades of Construction”—the messy in-betweens, the overlapping responsibilities, the real-world implications hiding behind neat lines on a drawing.And we do it on the fly, often with limited information and under pressure.

Because it’s not just about enforcing a spec or chasing a schedule. It’s about choosing the option that’s best for everyone involved:

• The Owner, who needs a quality product without budget creep
• The Contractor, who needs clarity, fairness, and a path forward
• The Designer, who needs to protect their intent without stalling the project
• The End-User, who’s going to live with this system long after the ribbon is cut
• The Budget, which can’t absorb unlimited changes
• The Schedule, which can’t be reset every time the wind changes direction

In other words: you’re not just managing a project—you’re managing a balance.

Sometimes the best solution isn’t the most technically correct—it’s the one that maintains momentum without sacrificing quali

ty. Sometimes it’s holding the line, even when it causes friction. Sometimes it’s allowing a workaround—with guardrails.There’s no flowchart for th

is. There’s no manual.There’s only <strong>judgment—built on experience, communication, and clear definitio

ns.

Definitions Create Freedom

Defining how your team operates doesn’t box you in. It creates freedom.

It gives you and your contractor a shared language.
>It gives your PM the authority to make decisions with confidence.
>It keeps misunderstandings, assumptions, and finger-pointing to a minimum.

It’s the opposite of micromanagement.
It’s proactive clarity.

Final Thought: Define Before You’re Forced To

“Everyone has a plan until they get punched in the mouth.”
– Mike Tyson

Day One on a job can derail everything you thought you knew. That’s why you prepare—not just for what you can see coming, but for how you’ll respond when the unexpected arrives.

If there’s one mindset shift I try to bring to every kickoff meeting, it’s this:

Don’t wait until something breaks to figure out how to fix it.
Define how you’ll fix it—before it breaks.

Because in the world of construction chaos, you’re going to get punched. The question is: will you already know how to respond?

Nothing is anything until it’s defined.
– Nick Parisi