Redirected Brady to use prioritization tools instead of pushing hard
Situation
Directed Brady Dibble to use the order of operations (prioritization list) as his tool for influencing engineering priorities, rather than pushing uncomfortably hard on individual teams. Emphasized that the prioritization list is his lever to move all of engineering, and if the order of operations is wrong, the fix is to change it formally with Peter, Bjorn, and Justin.
Reasoning
The prioritization system exists specifically to avoid ad-hoc pressure on engineering. Brady has legitimate authority through the prioritization list - he does not need to lobby individuals. Pushing hard bypasses the system and creates noise. If the order of operations is wrong, change it formally rather than work around it.
Additional Context
Brady was apparently trying to push something that conflicted with current priorities (Justin is focused on portal). Peter reinforced that the formal process is THE mechanism for Product/GTM influence.
Related Context
slack
pushing uncomfortably hard doesnt make any sense. You have a prioritization list, put things there where you want them to be and make sure youre in sync with Bjorn. Thats all.
Outcome
Closed without detailed outcome
Decision ID: 70f480dd-2e70-44f8-94ca-5baa2fbf3824