CbM Across Teams and Projects

Introduction
In the PMI Construction Professional (PMI-CP) body of knowledge, CbM stands for Commitment-based Management. It is a communication and coordination approach rooted in Lean construction. Its basic idea is that projects move forward through conversations that produce reliable promises, not through orders handed down a hierarchy. This topic sits within Communication Tools and Strategy. It covers how CbM grows beyond one conversation or one crew into a network of commitments that links design teams, trade partners, suppliers, owners, and even several projects at once.

1. Why CbM Across Teams and Projects Is Important
Construction projects are temporary, multi-organization systems. Most delays and rework do not happen inside a single trade. They happen at the handoffs between teams, for example:
- design to procurement
- procurement to site
- one trade to the next
- contractor to owner

When commitments at these interfaces are vague or unreliable, the problems add up quickly:
- Workflow becomes unpredictable. One missed promise ripples down to every team that depends on it.
- Waste grows. Crews wait, work is done out of sequence, materials are stockpiled, and rework follows.
- Trust erodes. Teams start padding schedules, protecting themselves, and relying on contracts instead of collaboration.
- Problems surface late. Without a culture of making and tracking promises, issues appear only when they are already expensive.

Scaling CbM across teams and projects addresses these issues in five ways:
- It creates reliable workflow by making promises explicit, visible, and measurable.
- It connects the people doing the work (the Last Planners) directly with each other, instead of routing everything through managers.
- It surfaces risks early through renegotiation rather than silent failure.
- It supports organizational learning by analyzing why commitments were not kept.
- It aligns with collaborative delivery models such as Integrated Project Delivery (IPD), design-build, and alliance contracting, as well as programs and portfolios.

2. What CbM Is
CbM treats every unit of coordinated work as a commitment between a customer and a performer.
- The customer (requester) asks for something.
- The performer (provider) promises to deliver it.
- The commitment is complete only when the customer accepts the result as meeting the agreed conditions of satisfaction.

Key concepts:
- Conversation for action: the structured dialogue of request, negotiation, promise, performance, and acceptance.
- Conditions of satisfaction (CoS): the clear, shared definition of what done looks like, including scope, quality, time, and location.
- Reliable promise: a promise the performer has a sound basis to make and intends to keep.
- Network of commitments: the web of linked customer-performer relationships that together make up a project or program.
- Role duality: every participant is a customer in some commitments and a performer in others. For example, the electrician is the drywaller's customer for open walls and the drywaller's supplier for finished rough-in.

CbM is closely linked to the Last Planner System (LPS). Commitments are made during:
- pull planning
- make-ready / lookahead planning
- weekly work planning
- daily huddles

Commitment reliability is measured through Percent Plan Complete (PPC).

3. How CbM Works

a) The commitment cycle (the action loop)
1. Request: the customer makes a clear request with conditions of satisfaction and a due date.
2. Negotiate: the performer can accept, decline, counter-offer, or commit-to-commit (promise to reply by a set time).
3. Promise: the performer makes a reliable commitment.
4. Perform: the performer does the work. If circumstances change, they renegotiate as early as possible.
5. Declare complete: the performer reports that the work is done.
6. Accept / assess: the customer confirms the conditions of satisfaction are met, or states what is missing. This closes the loop.

b) Criteria for a reliable promise
A performer should commit only when the promise is:
- Well defined: the conditions of satisfaction are clear.
- Capable: the skills and competence exist.
- Resourced: capacity, materials, information, and prerequisite work are in place, meaning constraints have been removed.
- Sound: the work is in the right sequence and size.
- Sincere: the performer genuinely intends to deliver.
- Open to renegotiation: the performer will raise problems immediately if conditions change.

Saying no or not yet is acceptable. It is far better than an unreliable yes.

c) Scaling CbM across teams
- Map the network of commitments. Identify who needs what from whom, especially at interfaces between disciplines and organizations.
- Use pull planning (phase scheduling). Work backward from milestones. Each team states what it needs from upstream teams and what it will hand off downstream. This creates explicit cross-team promises.
- Run make-ready / lookahead planning. Teams jointly identify and remove constraints (RFIs, submittals, materials, permits, prerequisite work) before committing.
- Hold weekly work planning sessions. Trade foremen and design leads make commitments to each other in the room, publicly, with peers as customers.
- Hold daily huddles / stand-ups. Check commitment status and renegotiate quickly.
- Make commitments visible. Use commitment logs, visual boards, Big Room displays, and shared digital platforms where every promise shows its owner, customer, due date, and conditions of satisfaction.
- Measure and learn. Track PPC (commitments completed divided by commitments made). Record reasons for variance. Use root cause analysis (e.g., 5 Whys) and drive continuous improvement.

d) Scaling CbM across projects and programs
- Use common commitment practices, terminology, and tools across the portfolio so that shared trade partners and suppliers experience one consistent system.
- Coordinate shared resources (cranes, specialist crews, design reviewers, inspectors) through explicit inter-project commitments rather than ad hoc competition.
- Aggregate PPC and variance data to spot systemic issues, such as chronic submittal delays from one consultant, and share lessons learned.
- Create escalation paths for commitments that cannot be resolved at team level, while still keeping ownership with the performer.
- Integrate CbM into governance through charters, collaboration agreements, and contract incentives that reward reliability and early warnings.

e) Enablers and barriers

Enablers:
- psychological safety
- leadership modeling of promise-keeping
- co-location or a Big Room
- coaching
- aligned incentives such as shared risk/reward
- integrated digital tools

Barriers:
- command-and-control culture
- fear of admitting problems
- adversarial contracts
- push scheduling imposed from the top
- treating PPC as a punishment metric instead of a learning tool

4. Worked Example
The mechanical contractor needs a ceiling grid layout from the architect by Tuesday so it can begin duct installation Thursday. In the weekly work planning session, the mechanical foreman (customer) requests the layout. The conditions of satisfaction are: coordinated with structure, issued in the BIM model, and covering Level 3 east.

The architect (performer) checks the constraints. The structural clash is unresolved, so the architect cannot reliably promise Tuesday. Instead, the architect counter-offers Wednesday at noon, provided the structural engineer resolves the clash by Monday. The structural engineer commits to that.

The commitments are logged on the board. On Monday the structural engineer finds a problem and immediately renegotiates. The team adjusts the sequence and keeps the crews productive on other ready work. The missed commitment is recorded with a reason for variance (design coordination), which feeds into improvement.

This shows several principles together: clear conditions of satisfaction, reliable promising, the network of linked commitments, early renegotiation, visibility, and learning.

5. Exam Tips: Answering Questions on CbM Across Teams and Projects

Tip 1: Favor the conversation over the command. Choose the answer where the project manager facilitates direct commitments between the people doing the work, such as foremen, trade leads, and design leads. Avoid answers where the PM simply dictates dates or assigns blame.

Tip 2: Reliability beats optimism. If a performer cannot meet a request, the best answer is to decline, counter-offer, or commit-to-commit. Agreeing to an unrealistic date and hoping for the best is never the right choice. An honest no is a valid CbM response.

Tip 3: Renegotiate early. When a scenario says a team realizes it will miss a commitment, the correct action is to notify the customer immediately and renegotiate. Waiting until the due date, quietly working overtime without telling anyone, or escalating before talking to the customer are all weaker choices.

Tip 4: Clarify conditions of satisfaction. If the scenario shows a handoff dispute such as "that is not what we asked for", the root cause is usually unclear conditions of satisfaction. Pick the answer that establishes shared, explicit acceptance criteria before work begins.

Tip 5: Remove constraints before committing. Look for make-ready or lookahead answers: resolve RFIs, submittals, materials, and prerequisite work before teams promise. A commitment made while constraints remain open is not reliable.

Tip 6: Know the metric and its purpose. PPC measures commitment reliability. Low PPC should trigger reasons-for-variance analysis and root cause learning, not punishment. Reject answers that use PPC to penalize individuals or trades.

Tip 7: Think network, not silo. In cross-team or multi-project questions, choose options that:
- map interdependencies
- use pull planning
- make commitments visible to everyone
- standardize CbM practices across projects that share resources or trade partners

Tip 8: Close the loop. A commitment is not complete until the customer accepts it. If an answer stops at performer reports done and another includes customer verifies against conditions of satisfaction, choose the latter.

Tip 9: Culture and contracts matter. When CbM is failing across organizations, strong answers address:
- psychological safety
- leadership modeling
- coaching
- collaborative agreements and incentives (e.g., IPD shared risk/reward)

Simply buying a new software tool is rarely the best answer.

Tip 10: Watch for distractors. These options are usually wrong in CbM contexts:
- The PM updates the master schedule and emails it to all trades. This is push communication without commitments.
- Escalate to the sponsor immediately. This skips direct renegotiation.
- Add buffer to every activity. This hides unreliability instead of fixing it.
- Enforce penalties for missed dates. This produces fear and hidden problems.

Tip 11: Use a quick decision filter. For any scenario, ask:
- Is there a clear requester and performer?
- Are the conditions of satisfaction clear?
- Is the promise reliable, with constraints removed?
- Is the commitment visible and tracked?
- Is there early renegotiation and learning?

The answer that strengthens the weakest link in this chain is usually correct.

6. Quick Summary
- CbM means Commitment-based Management. Work is coordinated through reliable promises between customers and performers.
- The cycle is: request, negotiate, promise, perform, declare complete, accept.
- Across teams and projects, CbM forms a network of commitments. It is managed through pull planning, make-ready planning, weekly work plans, daily huddles, visible logs, PPC, and reasons-for-variance learning.
- Its success depends on psychological safety, leadership behavior, collaborative contracts, and consistent practices across the portfolio.
- In the exam, pick answers that are collaborative, transparent, constraint-aware, quick to renegotiate, and focused on learning.