Re-ruled the two boards from first principles in the room - prioritization vs dates-and-confidence - and told the org to delete any column serving a third purpose

Situation

Seventeen minutes of the 7/28 Engineering Weekly went to re-landing the board doctrine after Ryan reported that Chris Baek had told him all work must move to the Engineering Deliverables (NGD) board. Peter said flatly he is wrong, then re-derived both boards from purpose. Product Priorities board: prioritization only - not work tracking, not delivery dates, not confidence numbers - and engineering continues to own the engineering-order-of-operations column that has existed for nine months. NGD board: only work that must be visible to the company because it is tied through value drivers to go-to-market, with exactly two required fields kept current in real time, a confidence number and an engineering target delivery date, and no statement about whether items are epics, stories or tasks. He also ruled that Wolford does not get to choose whether his work appears in NGD, that internal-quality-only work should not be on NGD at all, and that where duplicate order-of-operations columns exist the answer is derivable from purpose - if there are columns there to serve any other purpose, they are wrong, remove them.

Reasoning

Peter diagnosed the recurring failure as purpose overloading rather than misunderstanding: the reason we are where we are a year after me starting is people keep overloading what boards are for and trying to use them to solve multiple problems. So he refused to answer any specific use case on its own terms and instead made purpose the only decision procedure - you can understand what the solution should be just by asking yourself, what is the point of these two boards. He explicitly rejected letting the tool constrain the design (I dont care how JIRA is set up. If JIRA needs to change, JIRA needs to change), and he defended the two-column split as the mechanism that decouples product reprioritization from engineering churn: product can reprioritize at 9am and again at 11am without flapping engineering, and a genuine drop-everything request becomes an explicit conversation rather than silent thrash.

Additional Context

Follows the 7/24 decision narrowing the NGD board to cross-company coordination and the 7/21 codification of the Product-Engineering operating model. Ryan had duplicated rather than migrated content (nothing deleted, nothing migrated) so the boards had diverged and the TPS report had been repointed at NGD. Justin and Brady both surfaced live nuances about decomposition granularity, which Peter answered with the same purpose test. He capped the segment at 17 minutes and handed the meeting to Wolford.

Observed Evidence

Extended verbatim ruling in the Fathom transcript of the 7/28 Engineering Weekly, including the explicit correction of a directive Chris Baek had given Ryan, the two-required-columns rule, and the instruction to delete purpose-violating columns.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis