Bake the confidence number on the scope in front of you today - and accept that a 90 percent can slip when scope changes

August 19, 2026 at 8:27 PMoperationalmedium

Situation

In the Engineering Weekly Sync on 2026-08-18, Chris Wolford said he could not settle a confidence figure on the Toyota/RC item because he did not know whether the customer would ask for more after their heavier testing had surfaced bugs. He offered to either bump the number or push the date. Peter supplied the method instead: bake the confidence on the scope you have in front of you today, and let the number or the date move if scope changes. He extended it past the item in hand - Wolford answered that he would apply the same to both Toyotas, and Peter said it was for everybody.

Reasoning

Peter is removing the incentive to pad a confidence figure against unknown future scope, because a padded number carries no information and go-to-market cannot act on it. He named the cost of the rule out loud in the same breath - somewhere a 90 percent will slip and Bjorn will ask how that happened, and the answer will be scope changed. He is choosing a number that is honest about a known scope over a number that is defensively hedged against an unknown one, and pre-accepting the awkward conversation that choice creates.

Additional Context

Same meeting where Peter pushed on a 60 percent confidence figure sitting ten days from its target. Wolford also said he wanted a resync with the customer on next steps in about a week, which is what would surface the scope change the rule anticipates.

Observed Evidence

Wolford: I do not know, are they going to ask for anything else? They started testing it more heavily last week, and that is where those bugs came in. So I can bump it higher. I can push out the date, but I am not quite sure where we go at this point. Peter: bake the confidence number based on the scope you have in front of you today. Wolford: And that is for everybody. And I will update both Toyotas, that same bucket.

Matching Patterns

55%
Purpose Is the Decision Procedure(keyword match on confidence and communication, involves Chris Wolford and Nathan Blackham, same category (operational))
60%
Demonstrate the Standard, Then Collect It(involves Chris Wolford and Nathan Blackham, same category (operational))

Confidence Breakdown

33/35
Evidence
27/30
Pattern
19/20
Source
6/15
Corroboration

Reasoning Depth Analysis

Org Signal:A confidence figure is a statement about a known scope, not a hedge against an unknown one. Padding is now the error rather than the safe move.
Who Affected:Go-to-market, and Lindsay specifically - Peter said in the same meeting that a low confidence figure reads to her as a signal to hold off. Bjorn is the named downstream questioner when a high number slips.
Precedent:Establishes that a slipped high-confidence item is acceptable when the cause is a scope change, which is the counterpart to the existing expectation that confidence rises as a date nears. Together they make the number mean one thing only.
Consequences:Real, and Peter named them himself - a 90 percent will slip and he will have to explain it to Bjorn. He accepted that cost rather than letting the number absorb the risk.
Timing:Now because the sync was short and TPS-driven, and because two separate items in the same report carried figures that were hedged rather than informative.

Source

reflection

AI Confidence

85%

Related Context

🎥
Engineering Weekly Sync 2026-08-18

fathom

So I would bake the date, or I am sorry, bake the confidence number based on the scope you have in front of you today. If scope changes, then your confidence number or date can change. But let us communicate based on what we know today. And it will bite us because there is going to be some place where we communicate 90 percent confidence. And then scope changes, and Bjorn is going to ask, what the hell just happened? How did you slip something that was 90 percent confidence? And we just have to explain. Scope changed.

Outcome

Partial. Aug 31 TPS report flags three date slips logged without a confidence update plus two large confidence drops near deadline.

Rating: 3/5

Decision ID: 51e9adf7-3b42-4872-9367-d7a28430e146