There is a difference between doing something and doing something well. In construction, that distinction matters more than most people realize, and yet it gets overlooked constantly. Every project has requirements between code compliance, inspection milestones, engineered plans, and amenity packages. Somewhere along the way the goal shifts from delivering something meaningful to simply being able to say it got done. That mindset is a problem, and it shows up in the finished product every single time.
Intentional design and execution is what people remember, and checking a box alone will never get you there.
Checking A Box VS Providing Value
Take apartment amenities as an example. A developer can throw a treadmill and an exercise bike into a spare room on the ground floor, slap a sign on the door that says, “Fitness Center,” and technically deliver on a promise. It meets the requirement and it goes in the brochure, but anyone who walks in there knows immediately that no real thought went into it. It feels like an afterthought because it was one.
Now compare that to a two-story fitness center with quality equipment, proper flooring, mirror walls, ventilation, and a layout that actually makes sense for the people who are going to use it every day. That space has value because residents actually use it, and it becomes part of why people choose to live there and why they stay. Often residents can cancel their old gym memberships because the one they can walk to on site is just as good. The intentionality behind the design makes the apartment feel less like a unit and more like a home.
The difference between those two scenarios isn’t just aesthetics. It’s the thought that went into understanding what the end user actually needs and designing with that in mind. One checks a box and the other creates value, and the cost difference between the two is often far less than the gap in impact would suggest. That reality makes the decision to cut corners even harder to justify.
When a Plan Exists Only on Paper
Engineered plans are another place where this plays out in ways that can derail a project entirely. A plan can be technically compliant, pass review, and satisfy every calculation required by the AHJ, and still be completely useless in the field. If the engineer behind it never stopped to ask how this actually gets built, in what sequence, or by whom, then what they’ve produced is a document and not a solution.
An area I’m struggling with right now is my Erosion control plans. They’re a perfect example of something designed to meet regulatory requirements without any real consideration of how construction sequencing affects implementation. An engineer can lay out a system that looks great on paper, hits all the necessary calculations, and fits within the site boundaries. However, if the grading has not happened yet, if the slopes aren’t established, or if the drainage infrastructure isn’t in place, none of it can be installed the way it was drawn. The contractor is left trying to improvise in the field, the plan becomes irrelevant, and the result is an erosion control system that isn’t functioning as designed during the upcoming phase of site work. This could set back our project schedule significantly and affect our ability to deliver the project.
That kind of disconnect has real consequences. It strains the relationship between the contractor and the engineer, and it puts the project team in a difficult position with the authority having jurisdiction because now you’re explaining why what was approved isn’t what’s in the ground. It erodes trust that takes a long time to rebuild and affects how every future interaction with that jurisdiction goes, all because someone’s only goal was meeting the minimum threshold rather than solving the actual problem.
You Don’t Get Credit for Showing Up
There is a version of every deliverable on a project that satisfies the requirement and a version that actually serves the project, and too many people in this industry have convinced themselves that those are the same thing. They aren’t. Nobody gives you credit for having a bare minimum design that doesn’t provide value to the user. Your plan being stamped and approved doesn’t make it functional or realistic. The standard you’re being held to isn’t whether something exists, but whether it functions the way it was intended to. Meeting a requirement is the floor, not the ceiling.
What separates good project managers, engineers, and designers from forgettable ones is the habit of asking one more question before moving on. Not just “does this meet the requirement?” but “does this actually work?” Not just “can we fit this in the space?” but “will the people using this space get value out of it?” That extra layer of thought is what turns a checkbox into a contribution.
Intentionality Is a Choice
Doing something with intention takes more effort than doing it just to get it done. It requires thinking beyond your immediate deliverable and considering how your work fits into everything around it, understanding the sequence of a project, the needs of the end user, and the downstream effects of the decisions you make early on. That is harder than running the numbers and submitting the drawing, and it is exactly what builds a reputation worth having.
That effort is what keeps relationships with contractors and AHJ’s intact, and it’s what makes a project something people point to with pride instead of something they quietly distance themselves from when it comes up in conversation. You don’t have to be extraordinary at everything, but you do have to give a damn about the quality of what you put your name on. The work you produce is a direct reflection of the standard you hold yourself to, and in this industry, people notice the difference between someone who showed up and someone who actually delivered.
Be intentional about adding value in your work no matter the task. That is the greatest differentiating factor between professionals in this industry.
Tyler Burnette 
Leave a comment