Maple
Jan 6, 2026 - Jul 27, 2026
3
Decisions
0
Active Todos
5
Patterns
Categories
Decisions (3)
Let Brady raise the kernel-team cloud-resource block in Engineering Weekly, with the test being whether Justin agrees there is a problem
Brady Dibble DMed Peter saying he intended to surface in the Engineering Weekly a flag from Maple that the kernel team is blocked on cloud resources and is being redirected to Outfitter instead of getting the access it needs. Brady noted he had checked with Justin first, was raising it early because every day is precious for the kernel team, and explicitly offered to drop it if Peter preferred to handle it internally to Engineering. Peter replied: you can raise it, the only question I am going to ask is whether Justin agrees there is a problem.
OPA precedent — three-in-a-row water-carrier tap, not single-event hero pay
In 5/14 Nathan 1:1, with Nathan in middle of CVE response (third consecutive: dirty frag → copy-fail → current embargo), Peter declined to set the precedent of OPA/bonus payouts for single-event heroics. Maple — who carried water across all three events via consistent handoffs and status updates — is THE OPA candidate. David (took over secure-boot kernel build during Tate's absence) is growing into the role you'd want him to grow into normally → no OPA. Sultan (great dirty-frag work, up-late nights) → no OPA this round despite the effort. Nathan retained decision authority (Peter: I'm going to support whatever you decide. But, be cautious.) but the framework was set explicitly.
Leadership 1:1s with Maple, Dieter, Andrew
Decision to begin regular 1-on-1s with Maple, Dieter, and Andrew (when onboarded) to build trust and ensure unified messaging.
Related Patterns (5)
Proactive Talent Pipeline Investment
Invest in building leadership bench and talent relationships before there is an urgent need. Use proven relationships from past experience to create optionality.
Accountability Follow-Through
When you issue a warning or mandate with stated consequences, you follow through. Warnings are not threats - they are commitments. The credibility of future accountability depends on following through now.
Lead by Example with New Tools
When championing new tools or processes, personally use them and share results rather than just advocating. Learning by doing and demonstrating value through example is more effective than mandates.
Protect Engineering Focus Through Process
When faced with requests that would disrupt engineering focus (from sales, governance, product, or other stakeholders), establish processes that protect engineering ability to innovate while still satisfying legitimate concerns. Prefer systematic solutions over ad-hoc responses.
Three-Lever Talent Management
When pursuing a velocity or performance mandate, simultaneously operate on all three talent levers — upgrade (hire better), retain (protect key people), and exit (remove blockers) — rather than sequentially. This creates compounding momentum: exits free capacity for upgrades, retention preserves institutional knowledge during transitions, and upgrades raise the performance bar that justifies further exits.