Show the half-migrated TPS report to the whole leadership room even though it was not perfect
Situation
On the morning of the 7/28 Engineering Weekly, Peter asked in #department-heads-engineering for the repointed TPS report to be shown on that days call in its current state rather than held until it was clean - can you show the current state of the report briefly on todays call, even if not perfect. Ryan presented it in the meeting, flagged that there were 33 items and that the report pulled from the Engineering Deliverables board now diverged from the product-priorities view, and that segment is what opened the 17-minute re-ruling of both board purposes in front of the full room.
Reasoning
Showing the broken state was the agenda item. A half-migrated report makes the divergence between the two boards visible to everyone at once in a way a verbal description never would, and that visibility is what created the opening to re-rule board purpose with the whole leadership group present rather than through six separate conversations. It also set the tone Peter reinforced later in the same meeting when Duane Carson owned a cross-team miss - rough and acknowledged beats polished and late - and asking for imperfect output in public is the cheap version of establishing that norm.
Additional Context
Execution choice inside the 7/7 decision to restructure the Tuesday staff meeting to org-by-org TPS ownership and un-fork the report to one shared source, which has an outcome recorded. Ryan had duplicated rather than migrated board content the day before, so the divergence was fresh and concrete. Peter opportunistically used the migration mess as the vehicle rather than waiting for it to be resolved.
Observed Evidence
Direct quote in Slack the morning of the meeting, with the Fathom transcript confirming the report was shown in its rough state and became the trigger for the board re-ruling.
Confidence Breakdown
Reasoning Depth Analysis
Related Context
slack
Thank Ryan. Can you show the current state of the report briefly on todays call - even if not perfect?
fathom
Ryan: So TPS report if you pulled it from priorities or the product board is now different from if you are pulling it from the Engineering Delivery Board. It is not one-to-one. There are several major differences. This is what the report looks like as of today... I think there are 33 items here.
Outcome
Survived to become routine rather than being quietly dropped
Rating: 4/5
Decision ID: 56a475a2-8d1c-4af7-95b8-20f7d0aa95e1