Wrong size, not by much but they can’t fit the rough opening. A miss communication of how the field measured the RO, and the window company capture form resulted in windows that are the same size as the rough opening.

The dominos started falling immediately. Exterior trim couldn’t be set. Insulation couldn’t be finished. Drywall couldn’t start. The HVAC sub was scheduled for the following week and had nowhere to go. Three trades sat idle while we waited six weeks for a reorder. What looked like a simple materials mistake was actually a cascading failure of scheduling, stakeholders, resources, and risk management.

That’s what it looks like when multiple performance domains break down at once. You don’t feel one thing going wrong. You feel everything going wrong, all at the same time.

A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Eighth Edition organizes every project into seven Performance Domains, the seven areas that require active, ongoing attention from kickoff to closeout. Neglect any one of them and you’ll feel it in your schedule, your budget, your client relationship, or all three.

If you’ve been following this series, you’ve seen us work through the six principles that guide how you think about project management. Principles are the foundation, the mindset behind every decision. But principles don’t run a project. A framework does. The seven Performance Domains are that framework.

Here’s what each one means, and what it costs you when you let it slide.

1. Governance: Who Gets to Decide?

I’ve watched projects grind to a halt over a single unanswered question: who approves this change?

Not a big change. Not a structural redesign. A finish upgrade. A window relocation. A door swing reversal. But nobody had documented who had the authority to say yes, so the question bounced between the owner, the designer, the GC, and the lender for a week while the crew waited.

Governance is the domain that answers the foundational questions before work starts: Who approves change orders? What dollar threshold triggers owner review? Who is the single point of contact on the client side? What does the escalation path look like when there’s a dispute? Document it in the contract. Reference it throughout the build. The projects with the fewest conflicts are almost always the ones where these questions were answered before anyone picked up a shovel.

2. Scope: What’s In and What’s Out

Scope creep doesn’t announce itself. It shows up as a reasonable request on a Tuesday afternoon. “While you’re in there, can we add a built-in?” “We’d love to extend the deck a few feet.” “Actually, can we upgrade the countertops?”

Each one sounds small. Collectively, they hollow out your margin, push your schedule, and leave you explaining at closeout why the project is 15% over the original number. Scope is the domain residential projects break down on most often, not because builders don’t know what scope management is, but because the pressure to say yes in the moment is real.

Scope management is not about saying no to every change. It’s about evaluating every change against a documented baseline, pricing it accurately, and getting written approval before the work begins. The builders with the healthiest margins are almost always the ones with the tightest scope management discipline. We’ll go deep on this next week.

3. Schedule: Manage Time, Don’t Just Track It

Back to those windows. When they arrived wrong-sized, the real damage wasn’t the reorder cost. It was the six weeks of schedule collapse that followed, because no one had mapped the dependencies. Every trade that followed the window installation was sitting on the critical path. There was no float. There was no recovery plan. There was just a phone call to the client that nobody wanted to make.

A schedule in residential construction is not a prediction. It’s a management tool. It maps dependencies between trades, identifies the critical path, surfaces resource conflicts before they become delays, and gives everyone involved a shared understanding of what needs to happen and in what order.

The difference between builders who consistently hit their timelines and those who consistently miss them is rarely the trades. It’s the quality of schedule management. More on this in two weeks.

4. Finance: Know Your Numbers Before You Pour

Financial surprises at closeout are almost never the result of unexpected costs. They’re the result of costs that weren’t tracked until they accumulated into something unavoidable.

The Finance Domain covers budget development, cost tracking, cash flow, change order pricing, and financial reporting. In practice, this means tracking actuals against your budget in real time, not at closeout. It means pricing your change orders before you start the work, not after. It means knowing your cash flow position at every milestone, not discovering a shortfall when a draw is due.

The builders who run the cleanest financial closeouts are the ones who treat the budget as a live document, not a filed exhibit. We’ll go deeper on Finance in a coming post.

5. Stakeholders: Manage the Relationships, Not Just the Transactions

A project doesn’t exist in a vacuum. It exists in a web of relationships, with the owner, with subcontractors, with inspectors, with lenders, with HOAs, with neighbors, with suppliers. Every one of those relationships has the ability to slow a project down, stop it, or make it harder than it needs to be.

Stakeholder management is not just communication. It’s understanding what each party needs, managing their expectations proactively, and building the trust that makes the inevitable difficult conversations manageable. An inspector who respects your process moves faster. A lender who understands your draw schedule causes fewer delays. An owner who feels informed makes better decisions.

People are the biggest factor in whether projects deliver, or don’t. This one gets its own dedicated post later in the series, because it deserves it.

6. Resources: The Engine of the Build

Those wrong-sized windows were a resource failure before they were anything else. The right material wasn’t confirmed. The lead time wasn’t tracked. Nobody verified the order before it shipped. When the windows hit the site and the problem became visible, it was already six weeks of consequences too late.

Resources - labor, materials, equipment, and subcontractor capacity - are what actually make a project happen. In residential construction, resource constraints cause more project delays than almost any other single factor. Managing resources proactively means booking subs early, tracking material lead times, and maintaining visibility into your subcontractor pipeline before you need them, not while you need them.

The builders who don’t get caught flat-footed by a backordered product or a sub who double-booked are the ones who’re looking two and three phases ahead at all times. We’ll dedicate a full post to this one as well.

7. Risk: Plan for What You Know Will Go Wrong

If I had built a risk register before that window order went in, “wrong-sized windows” might not have been on the list. But “material order not verified before delivery” absolutely would have been, because I’d seen that happen before. The discipline of writing it down is what forces you to think about what you actually know could go wrong.

Every residential build has risks. The Risk Domain is about managing them systematically rather than reacting to them as they arrive. Identify the risks before the project starts. Assess their probability and impact. Plan your responses. Monitor them throughout the build.

The builders who finish on budget and on schedule are not lucky. They are prepared. We’ll go deep on Risk in a dedicated post, it’s too important for a paragraph.

What Comes Next

Over the coming weeks, we’ll go deep on each of the seven domains individually, Scope and Schedule are up next, followed by Risk, Finance, Resources, and Stakeholders. Practical tools, real scenarios, and approaches you can put to work on your next project.

Seven domains. One framework. Every build.

Which of the seven domains gives you the most trouble on a residential build? Drop it in the comments, I’ll make sure we cover it.

The views expressed here are my own and do not represent the position of PMI or any certification body.

Charlie

The Field PM | thefieldpm.com

That sentence has stayed with me ever since. Because it sounds simple, but what it describes is the hardest thing to build in residential construction. It is not a process. It is not a policy. It is a culture.

The Guide to the Project Management Body of Knowledge (PMBOK Guide), Eighth Edition, has a name for what that GC was doing: Build an Empowered Culture. It is the sixth and final principle in the framework, and it did not end up last because it is the least important. It ended up last because it is the environment in which all five of the principles we have already covered either take root or die on the vine without an empowered culture.

Think about it. A holistic view requires people who feel safe enough to raise issues across phases, not just their own. Value focus requires a team that understands what the client actually cares about, not just what is on the drawings. Embedded quality requires crew members who flag problems before they become expensive, not after. Accountable leadership requires individuals who take ownership of outcomes, not just tasks. Sustainability requires teams that think beyond the immediate task to the long-term result. None of those behaviors happens in a compliance culture. They happen in an empowered one.

What an Empowered Culture Is Not

Let’s clear something up first, because this gets misread in the field. Empowerment is not the absence of standards. It is not a permissive environment where anything goes, and nobody is accountable. It is not a replacement for clear roles, defined quality expectations, or project structure. A job site without structure is not empowered; it is chaotic.

Empowerment is what happens when you have all of that structure in place, and then you trust your people to work within it without constant supervision and second-guessing.

The distinction matters. Compliance cultures often have plenty of rules. What they lack is trust. The rules exist to control behavior because the people in charge do not believe the people doing the work will make good decisions on their own. And that distrust is usually mutual. It affects morale, yes, but it also affects creativity, problem-solving, and the willingness to speak up when something is wrong. The people with the most information about what is happening on site stay quiet because speaking up has never worked out well for them.

There is another version of this mistake worth naming: building a team that is all the same. I have seen companies, usually owner-operators who came up through one trade, hire in their own image. Everyone has the same background, the same strengths, the same blind spots. The framing is immaculate. The cabinetry is crooked. Because the skill that made the team confident in one area left them exposed in another. Diversity in skills, background, and ways of thinking is not a soft concept. It is what gives a team the range to own their work across the whole project, not just the part they are most comfortable with.

What an Empowered Culture Actually Produces

Earlier problem identification. This is the single most valuable behavior on a job site, and it only happens in an environment where speaking up is rewarded, not punished. Empowered team members flag issues when they see them. They do not wait for someone to notice. They do not hide problems to avoid the conversation. Remember the holistic view we talked about in Week 3: the ability to see across phases and catch coordination problems before they become demolition. That instinct is only useful if the person who has it feels safe enough to act on it.

Better decisions at the point of execution. The person closest to the work almost always has the best information about what is happening. When that person has the authority to make appropriate field decisions within defined parameters, as we covered in the accountability principle, the project moves faster, and the decisions are better than when everything has to go up the chain for approval.

Proactive risk management. Empowered teams do not just react to problems. Because the environment allows people to think and process information in their own way, team members begin to spot risks before they hit an obstacle. That is the difference between a crew that manages the current phase well and one that is already thinking about what the next phase is going to need.

Financial accountability. Empowered teams tend to be more fiscally responsible because they care about project success, not just their own scope within it. They manage resources carefully. They flag waste. They engage the client to make sure the company as a whole is delivering on the project, not just the build. When the crew feels ownership, the budget becomes their problem too, not just yours.

Stronger retention. Skilled tradespeople and site supervisors have options. The ones who are good enough to be empowered are good enough to leave if you do not treat them accordingly. Empowered cultures retain people. Compliance cultures cycle through them, and spend enormous time and money recruiting and training replacements who eventually leave for the same reasons.

How to Build It

Hire for judgment, not just skill. When you are building your team, subs, supervisors, and coordinators, evaluate their judgment and their communication, not just their technical ability. Skilled people with poor judgment are hard to empower. You cannot give authority to someone who will not think before they use it. Skilled people with good judgment are the ones who will run toward a problem instead of away from it.

Define the parameters clearly. Empowerment requires clarity about what decisions are within someone’s scope and what require escalation. The tile setter can flag the substrate problem, but they cannot authorize the change order to fix it. Make that distinction explicit before the work starts, not after a misunderstanding forces the conversation.

Model the behavior. This is the non-negotiable one. Leaders build the culture they model. If you want your team to flag problems early, you need to acknowledge problems early yourself. If you want them to own their work, you need to show ownership in how you run your projects. The accountability we talked about in Week 6 is not just a leadership virtue in isolation; it is the signal your team reads every day to understand whether it is safe to be honest here.

Here is a concrete example of what modeling looks like when it is done right. I worked with a company where the owner cared deeply about how the team showed up to clients’ homes, clean vans, organized tools, and a professional presentation from the curb. But instead of just demanding it and leaving it to individuals to figure out on their own time, he scheduled paid time every week for every team member to clean and organize their van. He made it part of the process. He invested in it. What happened over time was not just cleaner vans. The team began to own the standard. Nobody had to talk about it every week. It became part of how they did their work. That is what built-in empowerment looks like: the leader defines the standard, puts real resources behind it, and then gets out of the way.

Reward the right behaviors. When someone flags a problem early, thank them, publicly if the situation allows. When a sub speaks up about a coordination issue before it becomes a conflict, acknowledge it. The behaviors you recognize are the behaviors that repeat. And the behaviors you ignore, or worse, punish, are the ones that disappear, usually right when you need them most.

The Principle Behind the Principles

The PMBOK® Guide, Eighth Edition, gives us six principles for managing projects well. We have spent the last six weeks going through each one: seeing the whole build, delivering real value, embedding quality into every phase, leading with accountability, building for the long term. Each one is a discipline worth practicing on its own.

But culture is not just the sixth principle. It is the condition that makes the other five possible. You cannot have a holistic view if your team is afraid to share what they see across phases. You cannot focus on value if the crew does not understand or care about what the client actually needs. You cannot embed quality if people are motivated to hide defects rather than flag them. You cannot lead with accountability if the culture punishes honesty. You cannot build sustainably if the team is just executing tasks instead of thinking.

That GC I mentioned at the start did not do a perfect job. No job is perfect. What he managed was a team that handled imperfection well, that caught problems early, solved them honestly, and kept moving forward without the friction and defensiveness that kills project momentum. His secret was not a system. It was trust, built deliberately over time.

Next week, we shift from principles to practice. Starting with the seven Performance Domains, the framework that tells you not just how to think about your projects, but what to actively manage on every single one of them.

Charlie

The Field PM

Over to you:

What’s one thing you do, or have seen done, that genuinely builds trust and ownership on a job site? Drop it in the comments. The best ideas in this series have come from readers who’ve lived it.

A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Eighth Edition, changes that framing. By making sustainability one of its six core project management principles, the standard signals clearly: this is not a specialty. It is a baseline expectation of competent project management.

What does that mean for residential builders who are not working on explicitly green projects? More than most people initially expect.

It Starts Before the Dumpster Arrives

I was walking on a pre-construction site visit for a kitchen gut a few years back; full demo, everything coming out. The homeowners had already mentally written off everything in that kitchen. Old cabinets, dated hardware, a solid wood door with ornate molding, they’d stopped seeing years ago.

I mentioned that we could pull the cabinets intact, and they could be donated to the Habitat for Humanity ReStore. The hardware was worth cleaning up and donating to Goodwill. The door, someone would pay for that door.

The response I get most often at that moment is not enthusiasm. It is indifference. They don’t want to make three stops on a Saturday. But they don’t mind if we handle it. So we do.

That is sustainability on a residential job site. Not a solar array. Not a Home Energy Rating System (HERS) score. It is a field PM who notices a reusable cabinet before it gets swung into a dumpster, and who knows where to send it.

PMBOK 8 did not invent that instinct. It just made it a principle, something you apply intentionally on every project, not only when it is convenient or when the client asks.

You’re Already Doing Most of This

Most experienced residential builders already apply sustainable practices. They just don’t always think of them that way.

Material waste reduction is a cost management practice. Durable material selection is a quality practice. Site cleanliness and stormwater management are compliance and professionalism practices. Energy-efficient framing details are increasingly code requirements.

What the PMBOK® Guide does is elevate these habits to intentional principles, things you build into your process systematically, not just when the situation demands it. The difference between a habit and a principle is documentation and consistency. A habit happens when you remember. A principle happens deliberately on every project.

That distinction matters more than it sounds. And it leads to something bigger than the build itself.

Bigger Than the Build

Here is the part that does not always make it into the sustainability conversation, but should.

Surgical demolition; pulling cabinets intact, preserving hardware, protecting a door worth saving, costs more than unleashing a crew to gut everything in an afternoon. The labor takes longer. There is coordination involved in getting materials to a ReStore or a Goodwill. The contractor absorbs some of that cost. That is the honest reality, and anyone who tells you otherwise has not priced a selective demo lately.

But here is what that cost actually buys.

When you approach a project with a genuine sustainability principle, not a checklist, not a marketing talking point, you are doing something that extends well beyond your project budget. You are keeping usable materials out of a landfill. You are putting functional cabinets into a ReStore where a family doing their first renovation on a tight budget can afford them. You are contributing something real to the community your client lives in.

That is not soft. That is the kind of work that builds a reputation in a neighborhood, a city, or a trade. It is the kind of thing a homeowner mentions to their neighbor when the neighbor asks who did the kitchen.

This is also where the connection to two earlier principles in this series becomes visible. If you read the post on adopting a holistic view, you already know that good project management means seeing beyond your current phase, understanding how your decisions ripple forward and outward. Sustainability is the same thinking applied to the project’s impact on the world around it. Not just the organization, not just the financial statement, not just the immediate stakeholders, but the community, the environment, and the people your work touches indirectly.

And if you’ve been following along through the principle of being an accountable leader, there is a direct connection here, too. When your carpenters are empowered to make good field decisions, when they understand what you value and why, they become your eyes on the sustainability question in real time. I cannot be everywhere on a job site. But a lead carpenter who knows we pull hardware before demo, who knows we stack cabinets carefully and not in a pile on the lawn, who flags a piece worth saving that I walked past, that is the sustainability principle working at the field level. That is what empowerment actually produces.

The contractor who builds that culture is not just running better projects; it’s also creating a more effective team. They are building something the community actually benefits from.

The Four Dimensions Worth Managing

Environmental impact during construction. This covers how materials are stored, handled, and disposed of on-site. Soil disturbance and erosion control. Managing dust, noise, and waste in ways that respect the neighborhood and the site. None of it is complicated. Most of it is already expected. The principle asks you to make it deliberate, to have a site waste plan the same way you have a schedule.

Practically, that means: designate a salvage area before the demo starts. Know your local ReStore location and Goodwill drop-off. Know what they accept and what they don’t. If a client is indifferent about what happens to their old materials, decide for them. Most of the time, they appreciate it afterward.

Material choices and durability. The most sustainable building is the one that does not need to be replaced. When you are specifying materials, the conversation with your client should include service life, not just upfront cost. A $2/sf flooring product that needs replacement in five years has a different life-cycle cost than a $7/sf product that lasts thirty. That math is worth running in the planning phase, not as an afterthought when the budget is already set.

This is also where the salvage conversation lives on the back end. A cabinet box that still has ten years of life in it should not be landfilled because the homeowner wanted a refresh. It should go somewhere it can be used.

Energy performance. Building envelope performance, insulation levels, air sealing, window placement, and specifications have a long-term impact on the homeowner’s utility costs and comfort that far exceeds their incremental construction cost. A client who asks why you’re recommending a better insulation spec than code minimum deserves a straight answer: because in fifteen years, they’ll be glad you did, and they’ll still be living in that house.

One element that rarely gets enough attention in residential renovation conversations is mechanical ventilation, specifically Heat Recovery Ventilators (HRV) or Energy Recovery Ventilators (ERV). As homes get tighter through better air sealing and insulation, controlled ventilation becomes critical. An HRV or ERV brings fresh air in while recovering the energy from the outgoing air, improving indoor air quality, reducing humidity-related damage, and delivering the kind of long-term comfort and home health that clients feel every day but rarely know to ask for. If you are touching the envelope on a renovation, this conversation belongs in your scope discussion.

PMBOK® Guide’s sustainability principle asks you to integrate these considerations into the planning conversation, not bolt them on at the end when the budget feels locked. That requires you to bring it up first; most homeowners will not.

Long-term client value. Sustainability ultimately means delivering a building that serves the client well over time, healthy to live in, affordable to operate, and resilient to changing conditions. That is not a green building sales pitch. It is the definition of a well-managed residential project.

The Competitive Angle, and It’s Not Soft

Homebuyers are increasingly asking about energy efficiency, indoor air quality, and durability. That is not a trend confined to high-end custom builds anymore. It is showing up in renovation conversations, in contractor selection, and in how clients evaluate bids.

Builders who can speak to these topics with specifics, actual insulation values, actual material specs, actual service life comparisons, and a real answer when someone asks about ventilation are starting to win bids that builders who can’t are losing. Not because of ideology. Because clients are asking questions and getting different quality answers from different contractors.

The sustainability principle in PMBOK® Guide is not an ethical position dressed up as a management framework. It is a market positioning reality. The builders who treat it that way will have a competitive edge over those who are still waiting for a client to ask for it explicitly.

Making It Systematic

If sustainability is a principle and not just a habit, it needs to show up in your process. A few practical moves:

• Add a salvage assessment to your pre-construction site visit checklist. Walk the demo scope with one question: what here is worth saving?

• Keep a short list of local donation partners, Habitat ReStore, Goodwill, and local architectural salvage shops. Know what they accept and what they don’t.

• Have the durability conversation during material selection, not after. Frame it as a life-cycle cost, not an upsell.

• Make envelope performance, including HRV/ERV, part of your standard scope discussion on every renovation that touches exterior walls or the roof.

• Empower your field team to flag salvageable items during demo. Make it part of how you brief the crew before a gut starts, not an afterthought.

• Document your waste diversion. If you pulled cabinets and dropped them at ReStore, note it. Clients remember that detail, and they repeat it.

Coming Up Next

Next week, we close out the six principles with Principle 6: Build an Empowered Culture. It is the one that ties everything else together, and the one most builders are already living without realizing the PMBOK® Guide gave it a name.

The views expressed here are my own and do not represent the position of PMI or any certification body.

Charlie

The Field PM | substack.com/@thefieldpm

Leadership in construction gets talked about constantly and is rarely defined clearly. Most of us recognize it when we see it: the site lead who calls the owner before the owner hears about a problem from someone else; the PM who takes bad news to the client directly instead of waiting for the next scheduled meeting; the superintendent who says, “That was my call,” instead of, “That was the sub’s mistake.”

That behavior, the instinct to own the outcome before anyone asks, is harder to build than any system and worth more than most credentials.

PMBOK® Guide Eighth Edition gives it a name in Principle 4: Be an Accountable Leader. This principle is not about title, authority, or years of experience. It is about ownership. And the distinction matters more on a job site than it does almost anywhere else.

What Accountability Is Not

In project management, accountability is frequently confused with blame. When something goes wrong, “being held accountable” gets treated as shorthand for criticism, reprimand, or punishment. Someone has to answer for it. Someone has to take the hit.

That version of accountability is not just unpleasant; it is actively harmful to how a project functions. When people associate accountability with punishment, they stop raising problems early. Surfacing an issue starts to feel like volunteering for blame. Teams learn to manage information carefully: share the good, suppress the uncertain, and only acknowledge the bad when there is no other option.

The result is that problems travel upward through a project slowly and arrive at the decision-making level fully formed, expensive, and difficult to reverse. An out-of-square window framing that gets flagged on day two is a repair. On the day of installing that window, that is a rework conversation nobody wants to have. The cost is not just financial. It is the erosion of trust that comes from a team that had to hide something.

Accountability built on blame does not produce honest reporting. It produces skilled concealment.

What Accountability Is

Accountable leadership means owning outcomes, not just tasks. It means saying, “I am responsible for this project,” and meaning it when things go sideways, not just when things go well.

The distinction is important because tasks are finite. A task ends when the work is done. An outcome persists. When a PM signs off on a substitution that later fails, the task was completed correctly. The outcome still belongs to the person who made the call. Accountable leadership means not walking away from that.

In practice, it shows up in small but consequential moments. The site lead who warns the owner early, before the delay becomes a surprise. The PM who documents the rationale behind a difficult decision, not to cover themselves, but so the reasoning is visible and revisable. The superintendent who owns an approved substitution that did not perform as expected, and starts the correction before anyone asks.

These are not dramatic gestures. They are habits. And the cumulative effect of those habits is trust — with clients, with subcontractors, with the crew. Trust is not a soft outcome. It is the operating environment in which strong projects succeed. Clients who trust their PM give more honest feedback, make faster decisions, and are more forgiving when the unexpected happens. Subs who trust a site lead coordinate better and surface problems earlier. The return on accountable leadership is measured in project performance, not just in relationships.

Accountability and Culture

Accountable leaders tend to build accountable teams. Not by mandate, but by example. When the people running a project model ownership, when they acknowledge their mistakes openly, document their decisions transparently, and communicate proactively instead of reactively, those behaviors become the standard. People around them absorb what the expectation is.

This matters at every level of a project. The superintendent who says “I should have caught that” in front of the crew is not just being honest about one situation. They are demonstrating what ownership looks like in this environment. The PM who calls the owner with a problem before being asked is modeling a communication standard. Over time, those demonstrations shape how everyone on the team handles uncertainty, difficulty, and failure.

The reverse is equally true, and equally powerful. A site culture that punishes honesty and rewards blame-shifting trains its people to conceal problems until they can no longer be contained. The unspoken lesson is clear: self-protection first, project second. And that dynamic does not stay isolated to individual interactions. It becomes the way the team works. Issues accumulate quietly. Small corrections that would have cost an hour become major reworks. Disputes arise at closeout over things that were visible for months but never raised.

Culture is not a policy. It is a pattern of behavior reinforced over time by what gets rewarded, what gets ignored, and what gets punished. Accountable leadership is the single most direct input into that pattern. You cannot mandate a culture of honesty. You can model it.

Building Accountability Into the Process

Accountability is an intention. Structure is what makes it durable. Good intentions are not enough when a project is moving fast, information is fragmented, and pressure is high. The leaders who stay accountable under those conditions have built the infrastructure to support it.

Clear roles and decision rights are the foundation. Before work begins, define who can approve changes, who has authority to stop the work, how disputes escalate, and what requires owner sign-off versus field discretion. This is not paperwork for its own sake. Ambiguity about authority creates the conditions where accountability disappears. When no one is clearly responsible for a decision, no one is clearly accountable for its outcome.

Regular check-ins with honest status reporting are equally important. Weekly meetings only work when the team reports actual conditions rather than the version they think leadership wants to hear. Creating that environment requires active effort from the project leader. If the PM responds to bad news with pressure and frustration, they will get less bad news — not because conditions improve, but because the team learns what is and is not safe to say. The job of the meeting is not to project confidence. It is to surface reality early enough to act on it.

Communication norms also matter. When and how information travels through a project determines how quickly problems are addressed. Establishing a clear expectation that significant developments, delays, cost changes, and quality concerns get communicated promptly rather than held until the next scheduled touchpoint is a practical accountability tool. It removes the ambiguity about whether something is worth raising, and it prevents the accumulation of small issues into large surprises.

Documentation is the last piece. When someone commits to a deliverable, a correction, or a decision, it should be recorded. Not to build a case against anyone, but because accountability requires memory. Commitments that are not documented get forgotten or contested. A simple log of what was agreed, what was completed, and what is still open keeps accountability visible. It makes follow-through verifiable for everyone on the project, including the person who made the commitment.

PMBOK 8’s six principles are not abstract ideals. In effect, they are a description of how high-performing project teams actually operate. This one, accountable leadership, is the principle that makes the others possible. Quality requires people willing to flag what is wrong. Holistic thinking requires leaders willing to own the consequences of decisions across the whole project. Value delivery requires honesty about whether the project is actually on track to deliver it.

None of that happens in a culture built on blame-shifting. All of it becomes more likely in a culture built by leaders who own their outcomes, in the easy moments and the difficult ones.

Where does accountability show up most in how you manage projects, and where does it tend to break down? Drop it in the comments.

— Charlie

The Field PM | thefieldpm.com

That approach is not wrong, but it is incomplete. And depending on what it misses, it can be very expensive.

PMI’s principles-based guidance reframes quality as something to be embedded into processes and deliverables, not inspected only at the end: Embed Quality Into Processes and Deliverables.

But here’s where I think the real power of this principle sits, and where many builders miss it. Embedded quality isn’t only about inspection checkpoints or punch list protocol. In practice, it shows up in how your crew works every day: communication, proactivity, professional behaviour, and the consistency of the work itself. In residential construction, quality is not just what gets caught at inspection. It is what is built into the job before anyone has to ask for it.

What PMI Actually Means by Quality

PMI’s definition in PMBOK 8 is worth sitting with. In effect, PMI’s guidance suggests that quality means meeting customers’ and stakeholders’ stated and implied needs consistently and efficiently.

Read that again: stated and implied needs. Not just what the homeowner put in writing. Not just what’s in the contract. What stakeholders reasonably expect, including implied needs not always spelled out in the contract.

Think about what that looks like on a job site.

Nobody told your crew to clean up at the end of every day. Nobody posted a sign about it. But they do it anyway, because that’s the standard, and everyone on the team knows it. That’s embedded quality.

Nobody had to tell the lead carpenter not to park in front of the neighbor’s driveway. It didn’t come up in the pre-construction meeting. But he parks down the street, because that’s what a professional does in someone else’s neighborhood. That’s embedded quality.

The contractor who has to be reminded about these things every time doesn’t have a quality problem; they have a culture problem. Quality isn’t embedded. It’s enforced. And enforced quality is fragile.

That’s the distinction PMBOK 8 is making. Not just systems and checkpoints- though those matter- but behaviors so deeply baked into how your team operates that they happen automatically, without a prompt.

Why End-Stage Quality Control Fails

The problem with evaluating quality only at the end is that by then, most of the work is hidden. The framing is behind the drywall. The rough-in is behind the finishes. The slab is under the flooring. If there is a problem in any of those systems, discovering it at the final walkthrough means tearing out finished work, at full labor and material cost, with the client watching.

The cost to fix a defect increases dramatically at each stage of a project. A mistake caught during framing is a minor correction. The same mistake caught after drywall, tape, texture, and paint is a major rework. The same mistake caught after the client moves in is a warranty claim, a dispute, and a damaged relationship.

Embedding quality means catching issues at the stage where they cost the least to fix, which is always early.

Quality Is Also About Schedule and Cost

Here’s something builders sometimes miss. Quality in practice is not limited to technical scope conformance. Schedule reliability, cost efficiency, and communication quality also shape how stakeholders judge project performance, especially on projects where the value proposition is highly sensitive to those factors.

What does that mean in practice? A kitchen remodel delivered three weeks late may have met every scope specification. But if the homeowner had a family event planned around the completion date, the quality of the delivery (in their eyes) failed. The deliverable was fine. The project experience wasn’t.

Quality in construction isn’t just about the tile being level and the cabinets being plumb. It’s about whether the project was run in a way that the client felt was professional, predictable, and respectful of their investment. That includes the timeline. That includes how surprises were communicated. That includes whether the job site reflected the kind of operation they hired.

What Embedded Quality Looks Like in Practice

Phase-Transition Checkpoints

Before moving from one phase to the next, run a defined quality check. Before pouring concrete, verify the form, the rebar, and the placement. Before closing walls, verify that all rough-in inspections are complete and documented. Before installing finish flooring, verify that the substrate is level, dry, and properly prepared. These are not optional reviews. They are gates.

A Clear Definition of Done

One of the most practical tools from PMBOK 8 is the concept of a Definition of Done- used mainly in Agile practices- a documented, agreed-upon standard that a phase or deliverable has to meet before it can be called complete. In residential construction, this is often informal: the GC eyeballs the work and decides it’s good. That’s not a standard. That’s a guess. A useful way to operationalize embedded quality is a clear definition of done for each phase or deliverable.

Building a simple Definition of Done for each major phase, what does ‘done’ mean for framing? For rough electrical? For drywall?. It gives your team a shared standard to work toward and gives you a defensible benchmark if a client questions whether the work was acceptable.

Subcontractor Quality Standards in Contracts

Most construction contracts specify the scope of work. Fewer specify the quality standard. Define it. Reference the relevant building code. Specify the inspection requirement. Make it clear that work that does not meet the standard will be corrected at the sub’s cost before payment is released.

This isn’t adversarial. Most good subs welcome it. It protects them too — it means there’s no ambiguity about what they’re being held to.

A Culture of Early Flagging

One of the most valuable things you can build on a job site is a culture where anyone, crew member, sub, or delivery driver, feels comfortable flagging a concern without fear of being ignored or blamed. The person who speaks up about the out-of-plumb wall before it gets sheathed saves everyone time and money. Create the environment where that happens.

This comes back to the embedded quality idea. On a site with a real quality culture, the framing lead doesn’t wait to be asked. He flags it, documents it, and the correction gets made. On a site where quality is enforced rather than embedded, the issue gets noticed, and nobody says anything, because nobody wants to be associated with it.

Photo Documentation at Each Stage

Photographs before closing up walls, before pouring slabs, and at every major phase transition serve two purposes. They create a quality record that can be referenced if something comes up later. And the discipline of photographing the work creates a natural moment of review that catches things that might otherwise be overlooked.

The Continuous Improvement Angle

PMI makes another point worth applying here: adopting a continuous improvement mindset optimizes processes, boosts efficiency, and builds maturity across your whole operation, for present and future projects.

For a residential builder, that means every project is data. Every punch list is a record of where your current process has gaps. Every callback is a signal. Builders who treat those signals as information and actually adjust their process in response get better over time. Builders who treat each project as a standalone event don’t.

This is the compounding return on quality. Fewer warranty calls. Shorter punch lists. Faster closeouts. More referrals. And a reputation that attracts the kind of clients who value craftsmanship, which tends to mean better margins and more interesting work.

Quality is not a cost center. It is a competitive advantage.

The views expressed here are my own and do not represent the position of PMI or any certification body.

That’s the scenario that PMBOK 8 targets with its second principle: Focus on Value. And it might be the most important mindset shift in the entire edition for residential builders.

WHAT IS “VALUE” IN RESIDENTIAL CONSTRUCTION?

Value is what the client actually cares about, not just what the contract specifies. It’s the feeling of coming home to a space that works for their family. It’s the kitchen designed around how they actually cook, not just the dimensions on the plan. It’s the living room that actually feels like somewhere a family wants to be. It’s the home office with the window and a hardwired internet connection. They asked about three times and were told it would cost too much to add. We all want to build custom homes that photograph well and win us the next job, but the reality is we work for the homeowners, and we are hired to build them what they need, not what looks good in a magazine.

In effect, what PMBOK 8 is saying here is that project success can’t be measured by the triple constraint alone. It asks a harder question: did the project realize its intended value for the people it was built for?

For a residential project, that question has to be answered before the first nail is driven, because you cannot deliver value you have not defined.

THE VALUE CONVERSATION AT KICKOFF

Most project kickoffs in residential construction cover the contract, the schedule, the budget, and the scope. Almost none of them ask the client a direct question:

What does success look like to you at the end of this project?

That conversation takes fifteen minutes. It produces information worth more than most of the paperwork that follows. You find out what they’re most excited about, what they’re most anxious about, what trade-offs they would and would not make, and what they’ll remember about this project five years from now.

Write it down in the scope statement. Reference it throughout the build. Let it guide your decisions when you hit the inevitable moments where something has to give.

PROTECTING VALUE UNDER PRESSURE

That’s where this principle gets tested on a real job. Midway through a project, the budget is tight, and the schedule is sliding. The easiest place to cut is the custom millwork in the mudroom, the one detail the client mentioned in the very first meeting as the thing they were most excited about.

A cost-focused PM cuts it and documents the savings. A value-focused PM calls the client first, explains the situation, and asks which trade-off they want to make. Sometimes the client agrees to cut it. Sometimes they find a way to fund it. Either way, they feel heard and respected, and that matters more to the relationship than the line item.

I’ve been in both versions of that conversation. The one where I made the call for them and the one where I let them make it. The outcomes were not the same.

AI IS A VALUE ALIGNMENT TOOL, FULL STOP

There’s a version of adopting AI in construction that’s about efficiency, faster proposals, quicker spec lookups, and automated follow-ups. That version is real, and it matters. But it’s not the most important one.

The shift that’s actually underway is this: the builders getting the most out of AI aren’t using it to do less work. They’re using it to stay closer to client intent. It helps document what the client said in the kickoff meeting and keep it visible six weeks later when the budget pressure starts. It flags when a pending change moves the project further from the original vision. It catches the detail that got noted in week one and is now quietly at risk of being cut in week seven.

I use AI in my process the same way I use a rolling look-ahead, not to replace judgment, but to make sure I’m working off accurate information when I exercise it. The value conversation at kickoff means nothing if it gets buried in an inbox by the time framing starts.

The builders who separate themselves over the next five years won’t necessarily be the ones who adopted AI fastest. They’ll be the ones who understand that its highest-value job is protecting what the client actually came to you for.

THE BUSINESS CASE FOR VALUE FOCUS

Clients who feel their project delivered real value do three things: they refer you, they come back, and they leave reviews. Clients who feel the job was technically completed but missed the point do the opposite.

In residential construction, where your next project pipeline is built almost entirely on relationships and reputation, the difference between a client who raves about you and one who shrugs is often a single conversation at kickoff, where you ask the right question.

Not only scope. Not only the schedule. Value.

Mechanical rough-in is done. The HVAC installer has set the furnace. The plumber has the water heater in. The electrician’s panel is roughed. Everyone did their job. Everyone left.

And then someone does a pre-drywall walk and notices the back wall of the mechanical room, right behind the furnace and the water heater, has no insulation. Never did. The framers didn’t know it was needed. The mechanical subs noticed it but figured someone else would handle it. The schedule never called it out as a specific task.

Now it’s a problem. Not catastrophic, but the kind that eats a half-day and starts an uncomfortable conversation about who pays for it.

That’s not a scope problem. That’s not really a scheduling problem. That’s a holistic view of the problem.

What PMBOK 8 Is Actually Saying

PMBOK 8’s first principle- Adopt a Holistic View- sounds like something you’d read in a business school textbook. In effect, what PMI is saying is: stop managing your slice of the project and start thinking about how everything connects.

For a GC, this isn’t a new idea. It’s the job description. But having a framework that names it and validates it is useful, because it gives you a language to use with your team, your subs, and your clients.

A holistic view means you’re not just tracking what’s happening today. You’re thinking about the effect of today’s decisions on next week’s schedule, next month’s budget, and the final inspection.

It means when the plumber and the electrician are on site at the same time, you’re not just making sure they stay out of each other’s way. You’re making sure their sequencing doesn’t create a red tag at inspection. Because if something is in the wrong location relative to another trade’s rough-in, that’s two callbacks, and that’s a week off your schedule at minimum.

A holistic view is what lets you see that before it happens.

The Mechanical Room Problem

The mechanical room is a busy, utilitarian space. Everyone works in it. Nobody really owns it. And the detail that falls through the cracks most often is insulation on exterior-adjacent walls, specifically behind the furnace, the water heater, and similar mechanicals.

The HVAC installer sees it. They’re not an insulation contractor, so they don’t do it. The plumber sees it too. Same answer. The insulation sub may never even enter that room if it’s not specifically scoped, and when they do, it is too late because all the mechanicals prevent them from reaching the exterior walls. It gets to the closeout. The inspector flags it. Now you’re scheduling a callback, delaying the CO, and having a conversation nobody wants.

The fix isn’t complicated:

• A line item in your pre-rough checklist

• A confirmation during your mechanical room walkthrough before subs come in

• One standing question at your coordination meeting: “Is there anything in the mechanical room that needs to happen before the next trade show on site?”

That question, asked consistently, is holistic thinking in practice. It doesn’t require anyone to be an expert in another trade. It just requires someone to hold the whole picture.

Plumbers, Electricians, and Coordination That Actually Works

The mechanical room isn’t the only place this principle plays out. The coordination between plumbing and electrical is one of the most schedule-sensitive relationships on any residential build.

These two trades work in the same walls, the same ceilings, and often the same equipment spaces. When they’re not sequenced properly, when one falls behind, and the other shows up anyway, you get conflict, delay, and red tags.

This isn’t about the trades. They’re professionals doing their work in their lane. The breakdown happens when the PM assumes coordination is happening without confirming it.

A holistic view means you’re not managing two separate trade schedules. You’re managing their relationship. You’re looking at the whole mechanical sequence {HVAC rough, plumbing rough, electrical rough} as one connected story, not three separate chapters.

Who sets the furnace before the electrician runs the service connection? Who pulls permits first? Does the plumbing inspection clear before the electrical rough-in is complete? These questions aren’t on any single sub’s checklist. They’re on yours.

Where AI Fits Into Holistic Thinking

This is where I want to start a conversation about the modern PM’s toolkit, because holistic thinking is hard to execute manually when you’re managing multiple projects, multiple subs, and a schedule that changes every day.

AI tools are starting to make this more manageable. Not in a “set it and forget it” way, but in a way that gives you a second set of eyes on your project data.

The PMs I respect most aren’t going to have one AI tool. They’re going to have a system. A collection of tools that work together and evolve with their company’s process. Maybe it’s an AI-assisted scheduling layer integrated with your project management platform. Maybe it’s a prompt interface on top of your RFI log. Maybe it’s an AI-generated daily summary of what’s behind, what’s at risk, and what needs a decision today.

The specific tools matter less than the discipline of building that system intentionally. The question every PM should ask when evaluating any AI tool is simple:

Does this help me maintain a holistic view; or does it just help me manage my lane faster?

Speed in your lane is useful. But clarity across the whole project is what keeps the mechanical room insulated before the drywall goes up.

AI can help you surface what you’re missing. But you still have to be the one asking the question.

The GC’s Superpower Is a Habit

PMBOK 8 putting a holistic view as Principle 1 is deliberate. It’s the foundation everything else is built on.

It doesn’t require a certification. It doesn’t require new software. It requires the discipline to look up from your lane, regularly, intentionally, and ask: What am I not seeing right now?

For me, that’s always been the mechanical room question. What’s falling through the cracks because nobody owns it?

The GCs who answer that question consistently- before it becomes a punchlist item or a delayed CO- are the ones building sustainable businesses.

What’s your version of the mechanical room insulation problem? Drop it in the comments — I read every one.

Disclaimer: The views expressed in this series are my own interpretation of the PMBOK® Guide Eighth Edition and do not represent the official position of PMI or any certification body.

Not because the content was wrong, most of it was solid. But, I kept thinking about the last job site I had just walked off; a kitchen full remodel with a homeowner who kept changing her mind, a subcontractor who was two days behind, and an inspector who had just flagged a header we’d already drywalled over. And I thought: which of these 12 principles am I supposed to apply right now?

That’s the real test of any framework. Not how it reads in a conference room, but how it holds up when you’re standing in a half-finished kitchen with mud on your boots and three problems to solve before noon.

Twelve Principles were a Lot. Let’s Just Say That Out Loud.

PMI isn’t going to say it, so I will.

The Seventh Edition’s 12 principles were ambitious. They were thoughtful. And for a lot of practitioners in the field, especially those of us in construction who didn’t come up through corporate project management, they were also overwhelming, overlapping, and hard to operationalize in real time.

When you have 12 principles, you have a checklist. And checklists, ironically, are the enemy of principle-driven thinking. You start going through the motions- checking boxes- instead of internalizing a way of working.

Principles are supposed to guide judgment, not tax it.

PMI’s Eighth Edition gets that. By consolidating 12 principles into 6, PMI isn’t watering down the standard. They’re sharpening it. They’re saying: here are the six things that actually matter, at the highest level, across every industry, every project type, every team size. That’s not a retreat. That’s refinement.

And for construction PMs, whether you’re running a $40K bathroom remodel or a multi-phase commercial build, refinement is exactly what we needed.

What the Six Principles Actually Mean on a Job Site

Here’s the thing about PMI frameworks: they tend to be written for people who manage software sprints and stakeholder decks. So let me translate these six principles into language that makes sense if your office has a Porta-John and your stakeholder meeting happens on a tailgate.

1. Adopt a Holistic View: This is thinking beyond your current phase. You’re pouring footings, but you’re already thinking about where the HVAC rough-in is going to land three weeks from now. You’re not just managing today’s task, you’re managing the whole build. Most experienced GCs do this instinctively. Now it’s a principle.

2. Focus on Value: Not scope. Not schedule. Value. Is the client actually getting what they need? Sometimes what they ask for and what they need aren’t the same thing. A good PM catches that before the scope is nailed down, not after.

3. Embed Quality: Quality is not a punch list. It’s not the thing you scramble to fix at the end. It’s the conversation you have with your framing crew on day one, so your finishers can deliver on day 30 of the project. It’s the standard you set before the first nail is driven.

4. Be an Accountable Leader: Own the outcome. Not just your piece of it, the whole outcome. If your sub is behind, that’s your problem too. This is the principle that separates project managers from project administrators.

5. Integrate Sustainability: Build with the future in mind. This one is growing in residential construction faster than most GCs realize. Clients are asking about it. Codes are moving toward it. You can either get ahead of it or get caught flat-footed.

6. Build an Empowered Culture: Your crew performs when they’re trusted. When they know the plan, understand the why, and feel like they have authority to make reasonable field decisions, the job runs better. Full stop.

Why This Matters More Than You Think

Here’s my actual opinion, and I want to be clear, this is mine, not PMI’s: the move from 12 to 6 is a signal that the profession is maturing.

Mature frameworks don’t add complexity. They reduce it to what’s essential.

Construction project management has spent decades fighting for legitimacy, trying to prove that what we do is as sophisticated as what happens in aerospace or IT. And it is. But sophistication doesn’t mean complicated. The best-run jobs I’ve ever seen weren’t run by PMs who had every principle memorized. They were run by people who had a clear mental model of what mattered, and they applied it consistently, under pressure, every single day.

Six principles give you that. Twelve gives you a study guide.

What’s Coming Over the Next Six Weeks

Starting next week, I’m going deep on each of these six principles- one at a time- through the lens of residential construction. Real scenarios. Real friction points. No theory for theory’s sake.

This is the part of The Field PM where we stop talking about project management and start talking about how it actually works when the stakes are real and the clock is running.

If you’re not subscribed yet, now is a good time. This sub-series is going to be worth your time whether you’re a credentialed PM, a lead carpenter stepping into a management role, or a GC who’s been running jobs on instinct and wants a framework that actually fits your world.

Which of these six principles do you already apply without thinking about it? And which one do you honestly struggle with the most?

Drop it in the comments. I read everyone.

Charlie

The views expressed here are my own and do not represent the position of PMI or any certification body.

The 8th Edition was released in 2025, and it’s the most community-driven revision to date, shaped by nearly 48,000 data points from practitioners around the world, followed by two rounds of public feedback. Here’s what changed, and more importantly, what it means for you.

WHAT’S NEW IN PMBOK 8:

1. A shift from constraints to value. Previous editions focused heavily on delivering within the triple constraint: scope, schedule, and cost. PMBOK 8 expands that lens to include value. Are you delivering what the client actually cares about? A house built on time and on budget, but missing key priorities, isn’t a true success. This shift matters in residential construction, where client satisfaction and referrals are everything.

2. From 12 principles to 6. The last edition introduced 12 project management principles. Feedback from the global PM community was clear: that was too many, too overlapping, and too hard to apply. PMBOK 8 consolidates them into 6 clear principles: Adopt a Holistic View, Focus on Value, Embed Quality, Be an Accountable Leader, Integrate Sustainability, and Build an Empowered Culture. We’ll cover each one in this series with real job-site applications.

3. Process Groups become Focus Areas. The traditional 5 Process Groups (Initiating, Planning, Executing, Monitoring & Controlling, Closing) are now called Focus Areas. Why? Because real projects - including residential builds - don’t move in a straight line. You’re often planning while executing, monitoring while closing. The Focus Areas concept gives you flexibility without losing structure.

4. Seven integrated performance domains. PMBOK 8 reorganizes project management into 7 domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, and Risk. Each one is a critical area of every residential project, and over the coming weeks, we’ll map each domain directly to common builder challenges.

WHY THIS MATTERS FOR RESIDENTIAL BUILDERS:

You don’t need to be a PMP to benefit from a structured approach to project management. In fact, many of the best site leaders I’ve worked with already apply these principles intuitively. PMBOK 8 just gives us a shared language and a framework for doing it consistently.

Whether you’re managing a custom single-family home or a 20-unit infill development, the principles of good PM apply. A clearer scope prevents costly changes. Better risk planning reduces surprises. Empowered crews perform better and stay longer.

Over the next 12 weeks, this blog series will translate every major update in PMBOK® Guide into practical guidance for residential construction. No certification required. Just better builds.

COMING UP:

Next week: From 12 to 6. How the PMBOK® Guide 8th edition streamlined principles make you a better project leader on the job site.

Follow along and share this with someone on your team who manages projects.

It revolves around one thing: understanding your project scope and communicating your client’s needs to your team, clearly and effectively enough that the right product gets built. Everything else, the apps, the frameworks, the certifications, those are tools. What separates a great project from an ordinary one is how the project manager uses them.

The field of project management keeps evolving. Methodologies come and go, new ones emerge, and the PMBOK Guide, the industry’s foundational reference, just released its eighth edition. One of its biggest shifts is a move away from tracking numbers and deliverables for their own sake, toward something more fundamental: the value of the project to the people it serves.

Here’s what struck me when I read it: great builders in residential construction have been doing this for years. Long before it was written into any guide.

Because in residential construction, you can’t afford not to.

The product we build is someone’s home. That’s not like software, or furniture, or a piece of equipment. There’s no return policy. No version 2.0. If the kitchen wasn’t what the homeowner envisioned, or the walk-in closet doesn’t function the way they imagined it would, the opportunity to fix that is prohibitively expensive, and often, litigation is involved. The money is spent, the materials are used and installed, the permits are closed, and the trades have moved on to the next job.

That’s why communication isn’t optional in this business. It’s the job.

Not just between the PM and the team, though that’s critical. But between the PM and the homeowner, at every stage, from the first conversation about scope to the final walkthrough. A missed conversation early on doesn’t stay a small problem. It compounds. And eventually, it becomes the reason a homeowner tells their neighbors not to call you.

That’s the idea behind The Field PM.

We sometimes fall into the trap of thinking that because we know how to build things, homeowners should simply trust us to deliver. But that mindset misses the point entirely. This is not our project. We are trustees of someone else’s investment, their hard-earned money, their most valuable asset, the place they’ll spend the next twenty years of their life.

Our obligation isn’t just to build it right. It’s to build the right thing. To deliver something that adds real value to their home and their life. That’s what the best builders have always understood, even if they never used the word “fiduciary” to describe it.

Over the coming weeks, we’ll be breaking down the PMBOK 8th Edition piece by piece, not as an academic exercise, but through the lens of residential construction project management. What changed, what it means for how we manage projects in the field, and where great builders were already ahead of the curve.

If you’ve spent any time in this industry, I think a lot of it will feel familiar. And that’s the point.

Welcome to The Field PM.

Charlie Chamoun, PMP

Subscribe now

If you’ve ever tried to apply a textbook project management framework to a residential build, you know how fast it falls apart.

The PMBOK wasn’t written for your job site. It was written for people managing software teams in air-conditioned offices. The language is different, the workflows are different, and the stakes feel different when you’re standing in front of a homeowner whose kitchen has been torn out for three months.

I’m Charlie Chamoun. I’m a residential contractor, owner’s rep, and a PMP, which means I’ve spent years living in both worlds. I’ve managed custom home builds, renovations, and commercial projects. I’ve also studied the formal frameworks, earned the certification, and learned how to translate what’s actually useful into something you can apply on Monday morning.

That’s what The Field PM is about.

No theory for theory’s sake. Just practical project management for the people who are actually building things.

What to expect

I’ll be posting 2–3 times a week. Each post is short, specific, and built around a single idea you can use right away.

We’re starting with a 12-week series breaking down the biggest changes in the PMBOK 8th Edition, and what they actually mean for residential contractors and builders. If you’ve been hearing about PMBOK 8 and wondering whether it’s worth your attention, this series will give you a straight answer.

After that, we’ll dig into scope creep, client communication, subcontractor management, scheduling, risk, all of it through the lens of residential construction.

One ask

If you know another builder, contractor, or PM who’d find this useful — send it their way. The best thing you can do for a new publication is share it with one person who actually needs it.

Thanks for being here from the start.

— Charlie The Field PM · thefieldpm.com