Show the half-migrated TPS report to the whole leadership room even though it was not perfect

July 29, 2026 at 9:33 PMoperationallow

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

31/35
Evidence
12/30
Pattern
18/20
Source
11/15
Corroboration

Reasoning Depth Analysis

Org Signal:Work in progress is showable at the staff meeting. Nobody needs to polish before presenting, and an imperfect artifact can be more useful than a finished one.
Who Affected:Ryan Smith, who had to present unfinished work to the full leadership room; everyone in that room, who saw the board divergence firsthand rather than hearing it described.
Precedent:Reinforces that visibility outranks polish, and gives Peter a repeatable way to surface a structural problem to a whole room without singling anyone out.
Consequences:Real, and disproportionate to the size of the act - showing the rough report is what made the board re-ruling land with the full leadership group present.
Timing:Same morning, hours before the meeting - opportunistic use of the migration mess rather than waiting for it to be tidy.

Source

reflection

AI Confidence

72%

Related Context

💬
#department-heads-engineering, 7/28 08:16 PDT

slack

Thank Ryan. Can you show the current state of the report briefly on todays call - even if not perfect?

🎥
Engineering Weekly Sync, 7/28 - the report as shown

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