Value Drivers Board becomes source of truth for engineering dates and confidence; JPD dates become computed

Situation

In the 6/03 working session that Peter recorded (Peter + Nathan + Justin + Chris Baek, during the in-person engineering F2F), Peter locked the architecture that distinguishes the JPD from the Value Drivers Board. JPD stays purely for product strategy and prioritization (not work tracking). The Value Drivers Board is the Engineering-to-GTM coordination instrument that captures context (the why) and dependencies. The concrete decision: engineering target dates and confidence numbers live on the Value Drivers Board engineering lane as the source of truth, kept current on a tight cadence (always right on a Friday), and JPD dates and confidence become computed properties pulled from the Value Drivers Board rather than manually entered.

Reasoning

Stale dates and confidence on the JPD poison cross-functional trust. Peter framed a board that is not kept current as worse than useless, a lie to the rest of the organization. Moving the source of truth into the engineering-owned Value Drivers lane and computing JPD dates from it puts the numbers in the hands of the people who actually know them and stops them going stale from redundant manual entry. This is the concrete design realization of the 6/01 commitment to restructure the Value Drivers Board, and it is a structural attack on the recurring post-deadline date-change failure mode visible in the TPS report. Peter held JPD and VDB as distinct instruments because they answer different questions (prioritization vs dependency coordination) and therefore need different granularity, refusing Baek repeated attempts to collapse them.

Additional Context

Builds directly on 6/01 decision 912340f0 (commit to bring a Value Drivers Board restructure proposal), the 5/29 doctrine that Product owns prioritization of everything in the JPD, and the 5/28 JPD board scope lock. Peter confirmed this is a distinct decision (the architecture itself), not just elaboration of the 6/01 commitment. Existing todo 6a4ed436 (edit value drivers dashboard, Nathan input pass) stays linked to the 6/01 decision rather than being duplicated here.

Observed Evidence

Peter (recorded, driving the session): those confidence numbers and estimated delivery dates must be kept up to date, otherwise this Value Driver board is useless and worse than useless, a lie to the rest of the organization. To Baek who pushed repeatedly to merge JPD and VDB: Again, you are trying to make the system fit the tool, Chris. The goal of JPD is prioritization. The goal of value drivers is to show dependencies. On the cadence: there is going to be some relatively tight window where I want to hold your guys feet to the fire to ensure those two values are right ... they are our signal to the rest of the company.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis