Coach Brady on 2-step framework (strategy first, tactics second) and enforce live

Situation

Taught Brady the 2-step framework in his weekly 1:1: define strategic What first, then plan tactical How with Engineering. Then enforced it live in the CVE post-mortem group DM with Brady and Brian. When Brady proposed concrete CVE-response solutions (cross-train engineers, designate a quarterback, escalation paths) without first clarifying priority trade-offs, Peter refused to engage on the solutions: Your job, your ONLY job, is prioritization. Step one is answer my question. Step two will never happen absent step one. Never. Not one time. Brady eventually conceded.

Reasoning

Brady is talented but tactical-by-default — he proposes solutions before clarifying the strategic frame. The CVE post-mortem was a perfect test case: Brady listed concrete recommendations without first asking what engineering should NOT be working on while implementing them. Refusing to engage with the solutions until he completes step 1 forces the framework to stick — engaging on the merits would teach the opposite lesson. This is companion enforcement to D1: the structural board change wont hold if Brady keeps operating tactically. The forcefulness signals to Brian (also in DM) and downstream that this is non-negotiable, not preference. Peter is also staging Brady role redefinition (Bjorn-owned, mentioned in C-Suite) — the behavior change needs to be visible BEFORE the role change so Brady has room to grow into PM/PgM rather than feeling demoted.

Additional Context

Companion to D1 (Three-tier board hierarchy). Brian/Brady weekly was the explicit teaching moment; the group DM 90 minutes later was the live enforcement. The DM was triggered by Bradys condensed CVE post-mortem from 7:32 AM with concrete recommendations.

Observed Evidence

Direct quote framing in 1:1, then identical framework enforced in DM 90 minutes later when Brady deviated. Brady eventually conceded: Peter, you make a fair point. Given current resource pressure, operational resilience is worth an explicit roadmap item, regardless of how engineering decides to resolve it. Ill draft tickets and work with Bjorn on prioritization and displacement.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis