How to Recover Promises that are at Risk

Recovering At-Risk Promises: How to Spot the Signs and Have the Frank Conversation

A construction project is, at its most fundamental level, a network of promises. The trade partner who commits to having the zone ready by Friday. The designer who commits to the RFI response by Tuesday. The superintendent who commits to the pre-construction meeting happening three weeks before the first wagon. When those promises are made well and kept reliably, the project flows. When they are made poorly or broken without honest communication, the costs compound, faulty work packages, schedule slippages, cost overruns, crews waiting, quality problems discovered late.

Most experienced project leaders develop a gut sense for when a promise is failing. The manager who reports hopeful progress with an unusual number of caveats. The delivery date that has been reset twice without any coherent recovery plan. The tone in a trade partner’s update that communicates something different from the words being spoken. These are the warning signals that something is going wrong. The question is whether the leader acts on those signals quickly and directly or waits, hoping the situation resolves itself, while the problem compounds.

The Commitment Loop: Why Some Promises Are Reliably Kept and Others Are Not

Hal Malcomber, one of the founders of the Lean Construction movement, introduced a framework in 2004 called the commitment loop, a four-stage model for understanding how reliable promises are made and kept. The model is simple conceptually and sophisticated enough to apply to the complex network of commitments that a large construction project depends on.

Every reliable promise moves through four stages. Preparation is where the request is genuinely understood where both parties understand what is being asked, what conditions of satisfaction must be met, and what the consequences of the commitment are. Negotiation is where the plan is developed collaboratively, not where one party presents dates and the other passively accepts them, but where both parties work through what is genuinely achievable and commit to an outcome they both believe in. Performance is where the work is executed and problems are communicated honestly as they emerge, not held until the deadline, not surfaced only after failure. And Acknowledgment is where the completion is recognized, feedback is shared, learning is captured, and trust is reinforced for the next round of commitments.

When any one of these stages is skipped or done poorly, the promise is likely to fail. And the failure is usually visible as a warning signal before it fully materializes, if the leader knows what to look for.

The Early Warning Signals

The commitment loop provides a specific diagnostic for identifying at-risk promises before they are already failing. Each stage of the loop, when poorly executed, produces characteristic warning behaviors.

In the Preparation stage, poor listening during the request conversation produces a promise that was never genuinely understood. The person who commits without fully appreciating what was asked has not made a reliable promise, they have made a polite agreement that will not survive contact with the actual work.

In the Negotiation stage, the absence of genuine collaboration produces a plan that nobody actually owns. When dates are set and activities are planned without the people responsible for execution contributing to the design of the plan, the result is a plan that fits the schedule but does not fit reality. Nobody promised the outcome; they accepted the date.

In the Performance stage, the absence of frank communication when problems emerge is one of the clearest signals of a promise in trouble. The person who is falling behind but continues to report on track until the deadline arrives, either out of optimism, pride, or fear of the conversation is not managing a promise. They are managing an appearance. By the time the failure is acknowledged, the window for meaningful recovery has often closed.

In the Acknowledgment stage, the absence of feedback, learning, and recognition after completion is a warning signal for future promises rather than the current one. When completion goes unacknowledged when the effort was simply absorbed without recognition and the team moved immediately to the next task, trust is subtly eroded and confidence in the next round of commitments weakens.

Here are the behavioral signals that indicate a promise is at risk before it is clearly failing:

• The person reports progress but with an unusual number of qualifications and conditions.
• Dates have been reset once or twice without a coherent recovery plan explaining why the new date is more reliable.
• Communication about the commitment has become less frequent or less specific.
• The tone of updates suggests resignation rather than confidence.
• Questions about the commitment produce defensive or evasive responses rather than direct answers.

The Practice That Recovers the Promise

The most common response to a gut sense that a promise is failing is to say nothing to the person responsible, discuss concerns with other colleagues, and quietly begin developing a Plan B. This approach fails on two levels. It adds the waste of the Plan B on top of a deteriorating situation. And it allows the relationship between the two parties to degrade silently, the mistrust builds without ever being addressed, which makes the next round of commitments even less reliable.

The better path is a frank conversation, held immediately, directly with the person making the promise. Not a blame conversation. Not a threat. A frank sharing of the assessment, what has been observed, why it creates concern, and what matters to the person raising it, combined with a genuine request for the other party’s perspective and a commitment to work together on a new promise that both parties can trust.

The assessment-sharing conversation structure provides a practical framework for this:

Ask for permission: “I’d like to share an assessment with you about this commitment. Is that okay?” If permission is given, acknowledge it: “Thank you for allowing me to say what’s on my mind.” Then share the assessment directly and specifically: “The date has slipped twice in three weeks, which puts the whole sequence at risk. I don’t believe the new date is any more reliable than the previous ones.” The person receiving the assessment accepts it at face value, not arguing or defending, but expressing genuine acknowledgment: “Thank you for your sincerity. I can see why you would say that. I’ll reflect on this and come back to you by this afternoon.” The conversation closes with appreciation: “I appreciate the conversation and look forward to talking later today.”

Both a negative and a positive assessment should be shared when possible and the conversation should be reciprocal, inviting the other party to share their own assessments in return. The structure is not a performance script, it is a set of stabilizers for a type of conversation that most people find difficult to initiate. Once the practice of frank assessment-sharing becomes comfortable, the structure fades into the background and the conversation becomes natural.

Why Relationships Are the Foundation

Frank conversations recover promises. Relationships are what make frank conversations possible. When the relationship between two project professionals is built on mutual respect and genuine care for the project’s success, a difficult conversation about a failing promise is recoverable without permanent damage. When the relationship is primarily contractual and adversarial, the same conversation becomes a dispute.

This is why the quality of relationships in the Last Planner System between the general contractor and trade partners, between the superintendent and the foreman, between the project manager and the designer is not a soft consideration. It is the foundation of the reliability of the commitment network the whole system depends on. A technically perfect pull plan with perfect zone sizing and perfect sequencing, executed by teams that do not trust each other enough to speak frankly when a promise is at risk, will produce inconsistent results.

At Elevate Construction, the pre-construction process, the trade partner onboarding, the pull planning session, the conditions of satisfaction alignment exist in part to build the relationship foundation that makes frank promise conversations possible when they are needed. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Reliable projects are built from reliable promises. Reliable promises require frank conversations. And frank conversations are only possible when the relationship can support them.

On we go.

Frequently Asked Questions

What are the four stages of the commitment loop and why does each one matter?

Preparation ensures the request is genuinely understood. Negotiation ensures the plan is collaboratively designed and the outcome is genuinely committed to. Performance ensures problems are communicated honestly as they emerge. Acknowledgment ensures completion is recognized, feedback is shared, and trust is reinforced. Skipping or doing any one poorly makes the promise likely to fail.

What is the most common sign that a promise is at risk before it is clearly failing?

Dates that have been reset without a coherent explanation of why the new date is more reliable, and communication that becomes less frequent or more qualified as the deadline approaches. Both signal that the person responsible may already know the promise is in trouble but is not saying so.

Why is developing a Plan B without speaking to the person responsible a poor response to an at-risk promise?

Because it adds the waste of the Plan B on top of a deteriorating situation while allowing the relationship to erode silently. The mistrust that builds without being addressed makes the next round of commitments even less reliable.

What makes the assessment-sharing conversation effective for recovering a failing promise?

It is direct and specific rather than vague or accusatory, it invites the other party’s perspective rather than delivering a verdict, and it aims for a new promise that both parties can trust rather than just documenting the failure.

Why do relationships determine the quality of promises on a construction project?

Because frank conversations, the mechanism for recovering at-risk promises are only possible when the relationship can support them. Adversarial relationships suppress the honest communication that the commitment network depends on, making the entire Last Planner System less reliable than it should be.