Written by Mark Moody
The best-performing projects aren’t built on better contracts. They’re built on better daily habits.
James Clear’s Atomic Habits has sold tens of millions of copies because the core idea is undeniable: small behaviors, practiced consistently, compound into results most people can’t explain. You don’t need a dramatic transformation. You need a 1% improvement, repeated.
But what does that look like on a construction project?
Let’s sit in on a conversation between two people who’ve thought about this a lot — a Project Executive who’s run major infrastructure projects for 20 years, and a Partnering Facilitator who’s watched teams succeed and fail across hundreds of jobs.
Takeaway #1: Small Habits Compound — For Better or Worse
Project Executive: I’ve always thought of project success as the big decisions. The right team, the right contract structure, the right preconstruction investment. Are you telling me that the small stuff actually drives outcomes?
Partnering Facilitator: I’m telling you the small stuff is the big stuff, once it compounds.
Think about what a construction project actually consists of. It’s not a single decision — it’s thousands of micro-behaviors stacked on top of each other. An RFI gets answered in 48 hours or it sits for three weeks. A coordination meeting produces documented decisions or it produces vague commitments nobody tracks. A scope gap gets raised in month two or it gets buried until month ten and shows up as a claim.
Every one of those moments seems minor in isolation. Together, they define the project.
Project Executive: So the RFI response time matters more than I thought.
Partnering Facilitator: The RFI response time is the project culture. When a subcontractor sends in a question and gets a clear answer in 48 hours, they learn that communication works on this job. They do it again. And again. That habit compounds into a team that surfaces problems early — which is how you avoid the $400,000 coordination conflict that nobody saw coming.
The flip side is equally true. A blame culture, a habit of sitting on information, a pattern of late escalation — those compound too. Faster than most people realize.
Takeaway #2: Systems Win, Not Goals
Project Executive: Every project has the same goals. Finish on time. Stay on budget. Zero lost-time incidents. We write them into the partnering charter at the kickoff. Why doesn’t that move the needle?
Partnering Facilitator: Because your competition has the exact same goals. Every contractor, every owner, every project team in the industry is aiming at the same targets. The goals can’t be what separates you — because they don’t.
What separates high-performing projects is the system underneath the goal.
Project Executive: Give me an example.
Partnering Facilitator: Let’s take dispute reduction. Minimizing disputes/claims is a conversation in almost every kickoff meeting. But the teams that minimize disputes have a system: a standing agenda item at every weekly owner-contractor meeting to review open issues, with a named owner and a target resolution date for each one. Issues don’t get to age quietly. They get surfaced, assigned, and tracked.
Or take safety. Zero incidents is the goal on every project. The system is a five-minute tailgate huddle, every crew, every morning, same time, no exceptions. Not because of the content of any single huddle — but because the habit of gathering, checking in, and setting the tone compounds across hundreds of workdays into a culture where people look out for each other.
Goals set direction. Systems create movement. You need both, but only one of them does the work.
Takeaway #3: Identity Changes Behavior
Project Executive: Even with good systems, I’ve watched project teams revert under pressure. A tough RFI, a tight schedule, a cost squeeze — and suddenly everyone’s back to protecting their own corner. How do you get past that?
Partnering Facilitator: Clear’s answer to that is the most counterintuitive idea in the whole book. He says lasting behavior change doesn’t come from wanting a different outcome. It comes from believing you are a different kind of person — or in this case, a different kind of team.
Most project teams operate from the identity of separate companies managing separate risks. That identity is baked in by the contract structure, by past project experience, by the instinct to protect margin. And when pressure hits, people revert to that identity because it’s the one they believe.
Project Executive: So how do you change the identity?
Partnering Facilitator: You don’t announce it. You build it through action.
Every time the GC shares the two-week lookahead before the owner must ask for it, that’s a vote for a different identity — a team that operates with transparency. Every time a subcontractor flags a drawing conflict before it becomes a field problem, that’s a vote. Every time someone says, “here’s the issue and here’s what I think we should do” instead of “that’s outside my scope,” that’s a vote.
Enough of those votes, and the identity starts to feel real. And when it feels real, it holds under pressure.
Project Executive: So, the partnering behaviors aren’t just tactics — they’re how you actually build the identity.
Partnering Facilitator: Exactly. The behaviors are the votes. The identity is what you’re voting for.
Takeaway #4: The Four Laws Make It Automatic
Project Executive: Assuming a team is bought in — they want to collaborate; they believe in the process — why does it still fade? I’ve seen genuinely committed teams fall back into old patterns by month four.
Partnering Facilitator: Because commitment isn’t enough. The environment must support the behavior. Clear’s four laws are about engineering the conditions so that good behavior becomes automatic — not something people have to consciously choose every time.
Let me walk you through each one in construction terms.
Make it obvious. If you want a behavior, make it visible. Post the project commitments in the conference room. Put the open issue count on the dashboard next to the schedule. Begin every major meeting by reading one project value out loud. When the behavior is constantly in front of people, it becomes the expectation rather than the exception.
Make it attractive. People repeat what feels rewarding. When a subcontractor raises a conflict six weeks before it would have caused a schedule impact, name it publicly at the next owner meeting. When a trade team hits a milestone through coordinated effort, take 60 seconds to say so. Recognition is not soft — it’s behavioral programming. It tells people that the behavior they just demonstrated is the behavior this project runs on.
Make it easy. Friction kills habits. If submitting an RFI takes three system logins and a follow-up email, it won’t happen promptly. If raising an issue in the project log takes 20 minutes and nobody ever updates the status, people stop using it. One shared platform. Standard meeting agendas. Clear decision-making authority so a $20,000 change doesn’t wait six weeks for a signature. The simpler the right behavior, the more consistently it happens.
Make it satisfying. Track things that make progress visible. Issue resolution time. Safety leading indicators. Schedule recovery after a collaborative problem-solving session. When a team can see that open issues dropped from 18 to 4 this month, or that their RFI response time is half the industry average, the behavior reinforces itself. Progress is motivating. Make sure the team can see theirs.
Project Executive: And the flip side — using those same laws to break the bad habits?
Partnering Facilitator: Reverse them. Make the bad behavior invisible by removing triggers — move conflict out of email chains and into a structured issue log. Make it unattractive by showing the dollar cost of unresolved disputes. Make it difficult by requiring early escalation as a condition of schedule recovery. Make it unsatisfying by displaying open issue age publicly, so a dispute that’s been sitting for six weeks feels like what it is.
The environment shapes behavior. Design it deliberately, in both directions.
Takeaway #5: Never Miss Twice
Project Executive: Last one. What happens when the habits slip? Because they will — a rough stretch, a personnel change, a crisis that puts the team back in defensive mode. How do you recover without losing everything you’ve built?
Partnering Facilitator: Clear’s answer is simple and practical: never miss twice.
Missing once is human. A coordination meeting gets skipped because of a field emergency. A tense owner interaction breaks the pattern of collaborative problem-solving. Someone responds defensively to an RFI instead of picking up the phone. These things happen on every project. They’re not the problem.
The problem is missing twice. Because the second miss signals that the first miss was the new normal. And the third miss confirms it.
Project Executive: So, the recovery matters more than the slip.
Partnering Facilitator: Always. The mark of a high-performing project team isn’t that they never have bad weeks — it’s that they reset quickly. They acknowledge what happened, they reset expectations, and they come back to the next meeting with the same agenda, the same habits, the same commitment.
That recovery is itself a habit. And like every habit on this list, it compounds. A team that knows how to reset becomes a team that’s resilient under pressure. A team that lets slips become patterns becomes a team that’s defined by its worst weeks.
The Bottom Line
Project Executive: If you had to take all five of these and turn them into one idea — one thing to carry out of this conversation — what would it be?
Partnering Facilitator: Project success is not a moment. It’s a pattern.
It’s not the partnering charter or the kickoff session or the contract language about collaboration. It’s hundreds of small behaviors, practiced consistently, by every person on the team — across every meeting, every RFI, every conflict, every decision.
Those behaviors compound. Slowly at first, then visibly. And eventually, they compound into a project that finishes differently than it started — with stronger relationships, better outcomes, and a team that wants to work together again.
That’s what James Clear figured out about human behavior. And it turns out it applies just as well on a two-year infrastructure project as it does in your personal life.
Small habits. Consistent systems. A clear identity. The right environment. And the discipline to get back on track when you slip.
That’s the whole book. And on a construction project, it’s the whole game.
The five takeaways at a glance:
- Small habits compound — every interaction either builds trust or erodes it.
- Systems win, not goals — reliable processes beat shared ambitions.
- Identity drives behavior — “we are one integrated team” changes how people act under pressure.
- The four laws make it automatic — make collaboration obvious, attractive, easy, and satisfying.
- Never miss twice — recovery speed determines whether a slip becomes a pattern.