Defended Global Prioritization Model with Per-Team Computed Views

Situation

Convinced Greg that product prioritization must remain a single global list, not grouped by team. Agreed to add a computed property showing priority within each team for visibility. Fuzzball was reprioritized into top 20 in Exec meeting; Greg's remaining concern about Fuzzball not being high enough was resolved via the global+computed-property approach.

Reasoning

Global prioritization is the mechanism that reveals whether engineering is structured correctly. Per-team views are useful operationally but dangerous strategically — they let teams rationalize their own importance without facing trade-offs. The only question that matters is 'more important than what', not 'is it important'. The computed property gives Greg the team-level visibility he needs without undermining the model.

Additional Context

Followed Exec Product Prioritization meeting where Fuzzball items were moved into top 20. Greg still had concerns about Fuzzball visibility. Peter resolved via DM with the two-level approach. Greg confirmed satisfaction: 'I feel much better now. Thank you.'

Observed Evidence

Direct quotes from Peter in Slack DM with Greg: 'the problem with that is then you design your strategy based on the team structure you have. which is wrong.' and 'The only thing that matters is more important than what.' Greg confirmed: 'I feel much better now. Thank you.' Exec meeting corroborates: Fuzzball reprioritized, computed property for team views discussed.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis