Narrow the NGD board to cross-company coordination only - not a deliverables tracker and not a complete decomposition of product acceptance criteria

Situation

In the 7/24 Brian Dawson / Brady Dibble sync Peter ruled against the working assumption that the NGD board is the comprehensive ordered list of engineering deliverables. His ruling: the boards only purpose is coordination across the company for things that drive value. It is not for tracking deliverables, not for holding engineering accountable to delivery dates, and does not need to be a complete decomposition of the acceptance criteria in a product ticket. Anything that should not link to a value driver is a component and belongs in Jira, which Peter will never look at. Engineering may blend several product-priority items into one NGD ticket or ship one top-level ticket, as long as the board forms a palette that overlays the product priority and engineering can say when these are done, this product priority is complete. Separately he fixed the product priorities list as strategic priorities full stop - no delivery dates, plus an engineering order-of-operations column and nothing more.

Reasoning

A tool with two purposes gets used for whichever purpose carries more political weight, so Peter collapsed it to one. He named the tell explicitly - every time Brady, Brian, or Chris Baek explains these artifacts they explain structure (epics, hierarchy, relationships) and Peter explains purpose. He refuses to let tooling shape define the contract because structure invites scope creep and purpose does not. What he wants from the system is a filter, not a report - the process should surface anomalies so the Monday, Thursday, and Tuesday meetings work those instead of reading dates aloud. He also declined to accept the dates need more work as an input, having verified with engineering inside 24 hours that the data is there, and redirected Brady from grievance to specificity: name the line item that lacks what you need, and if you cannot understand why a number is low, dig in with Justin, then escalate.

Additional Context

Peter confirmed this is a fresh decision rather than mere enforcement of the 7/21 operating-model decision. The new content is that NGD is coordination-only and explicitly not a deliverables tracker, and that decomposition completeness is not required. He also disowned Chris Baeks structural Jira model directly - you do not work for Chris Beck, I do not work for Chris Beck - and pointed Brady at the concrete case of a ticket slated for a week out at 60 percent confidence as exactly the anomaly the process exists to surface.

Observed Evidence

Direct transcript quotes across roughly 15 minutes of the 7/24 sync, including Do not overuse the tool, the explicit three-part negation of the boards purpose, the palette-overlay formulation for acceptable decomposition, and the disowning of Chris Baeks structural model.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis