The value-driver bottom row is the contract, not NGD - approved stripping target dates and confidence from product tickets and pointing them at NGD instead

July 30, 2026 at 10:39 PMoperationalhigh

Situation

Nathan asked whether NGD is the communication mechanism to go-to-market, product and the rest of the company. Peter refused the framing: the reason I am using that language instead of NGD is because I do not care about NGD. The bottom of the value drivers list is purely for communication about our deliverables and their impact to go to market. What he cares about is that the bottom row holds confidence numbers and target delivery dates almost in real time - as long as that is true, what you use to back it, I do not care. And if the thing you use to back it serves a bunch of other goals, great, I do not care. But if NGD cannot serve that because it answers other masters, then something else has to get stood up, or a linkage or filter. Nathan then proposed ripping target dates and confidence numbers out of product tickets entirely, reporting them only from NGD, and having product tickets point at NGD tickets. Peter approved with one amendment: product tickets still want to hold products desired date.

Reasoning

Peter is protecting the interface, not the implementation. The value-driver bottom row is the single place the company reads engineering delivery, so it must hold live dates and confidence; anything behind it is an engineering implementation detail he explicitly declines to govern. Stripping dates out of product tickets removes the duplicate source that made the numbers inconsistent - one place holds engineerings estimate, one place holds products want, and they are no longer confusable.

Additional Context

Directly continuous with the 7/24 decision to narrow NGD to cross-company coordination only and the 7/29 decision that the NGD board never bends to serve the TPS report. Today closes the loop from the other end - the product ticket stops competing as a date source.

Observed Evidence

Direct quotes. Peter: what I care about is the bottom row of the value drivers list and that it holds confidence numbers and target delivery dates almost in real time. On Nathans proposal to remove dates from product tickets: And I think that is totally fine. I think the product tickets still want to have products desired date.

Matching Patterns

58%
Purpose Is the Decision Procedure(2 keyword matches, involves Nathan Blackham, same category (operational), answered a which-tool question by restating what the artifact is for)

Confidence Breakdown

33/35
Evidence
28/30
Pattern
19/20
Source
11/15
Corroboration

Reasoning Depth Analysis

Org Signal:Peter governs interfaces and refuses to govern implementations. Teams get latitude on their own tooling exactly to the extent that the contract stays honest.
Who Affected:Justin, whose product tickets carry the same duplication. Product and go-to-market, who lose a second date source they may have been reading. Brady, whose formula ambitions lose their second foothold.
Precedent:Sets the rule that when a backing system serves multiple masters, the fix is a filter or a replacement - never a compromise of the contract row. Also establishes the split between engineerings estimated date and products desired date as two separate fields that must not be merged.
Consequences:Real and mechanical. Nathan will remove dates and confidence from product tickets, which changes what anyone reading a product ticket sees.
Timing:Now because Nathan came back from two weeks away, is making changes, and asked the question directly - and because the boards were re-derived from purpose two days earlier, so the criterion was already articulated.

Source

reflection

AI Confidence

91%

Related Context

🎥
Nathan <> Peter Weekly 1:1

fathom

The reason I am using that language instead of NGD is because I do not care about NGD. The bottom of the value drivers list is purely for communication about our deliverables and their impact to go to market. As long as that is true, what you use to back it, I do not care.

Outcome

The 2026-08-18 sync ran entirely off target-date plus confidence per item with leaders arguing their own numbers. Wallace reported migrating more team work onto the NGD board.

Rating: 4/5

Decision ID: 401f9d58-a372-43ae-9729-60297d16251e