000.1 Introduction. Real experiences, problems, solutions, and lessons meant to be used—not blindly followed. Take what’s useful, challenge what isn’t, and see the thinking behind how I lead, solve problems, and manage operations.
000 Why This Exists. Years of field and construction experience produced lessons worth documenting. The Operating Code captures those lessons, challenges the thinking behind them, and carries them forward.
001 Know Before You Commit. Understand the work, people, resources, prerequisites, and unknowns before making the promise. Once you commit, you own figuring out how to deliver it.
002 Preparation Drives the Result Strong results start before the work begins. Verify the plan, materials, people, tools, and conditions early—because preparation is where preventable problems should be found.
003 Fair Requires Judgment Fair doesn’t always mean treating everyone exactly the same. Good leadership requires understanding the circumstances, applying consistent standards, and using judgment to reach the right outcome.
004 Listen to Understand Listen for what is actually being said before deciding how to respond. Ask questions, understand the problem, and get the facts before jumping to conclusions or solutions.
005 Make the Thinking Visible Don’t just give people the answer—show them how you reached it. Making the reasoning visible builds understanding, improves decisions, and develops people who can think through the next problem themselves.
006 Never Lose Touch With the Work As responsibilities and titles grow, leaders still need to stay connected to the work and the people doing it. Reports and meetings can’t replace seeing the operation firsthand, understanding the obstacles, and supporting the people creating the value
007 The Work Nobody Sees The best-run jobs often look easy because the problems were handled before they became visible. Planning, coordination, follow-up, and prevention are the unseen work behind consistent results.
008 Own the Outcome Ownership means understanding your contribution to the result—not doing everything yourself or assigning blame. Own your part, add value where your responsibility allows, and fix recurring problems instead of repeatedly managing the symptoms.
009 The Numbers Tell You What, Not Why Metrics can show where performance changed, but they rarely explain the cause. Use the numbers to identify where to look, then go to the work and the people closest to it to understand why
010 Communication Needs a Structure Good communication isn’t just about sharing information it needs a clear path. Define who communicates what, to whom, and when so information reaches the right people without creating confusion or unnecessary noise
011 Escalation Has a Purpose Escalation isn’t about passing a problem upward—it’s about getting the right authority or resources involved when they’re needed. Escalate with the facts, what’s already been tried, and what decision or support is required
012 Know Where the Decision Belongs Not every decision belongs at the top. Put decisions with the people who have the knowledge and responsibility to make them, while keeping clear boundaries for when leadership needs to step in
013 Protect What Happens Next Finishing your part isn’t enough if it creates problems for the person or process that follows. Think beyond your immediate scope and leave the next step ready to succeed.
014 Find What’s Different When something that normally works suddenly doesn’t, start by identifying what changed. Compare the successful condition to the failed one, isolate the difference, and let the facts lead you toward the cause.