Steve Moody
May 21, 2026 - Aug 28, 2026
2
Decisions
0
Active Todos
4
Patterns
Categories
Decisions (2)
Deliver the AI-spend message myself at an engineering all-hands instead of letting the AI committee write a policy
In the 2026-08-27 Ryan Smith 1:1, Ryan argued that the next AI committee meeting should produce a company-wide best practice on AI spend - consensus around spend, do not use Fable for everything, be self-aware of usage. Peter declined the policy framing but conceded the underlying point: the conversation has to happen and has to be delivered directly to engineering rather than routed through a committee or left to individual managers. He committed to an engineering all-hands the following week and flagged it verbally for capture in the moment. He scoped it explicitly to engineering, excluding Ryan own organization.
Moody Citibank card hard cutoff 6/15 — force-action via past-tense framing after 9 months of soft asks
After Kelly Wall described 9 months of soft asks to Steve Moody to switch from the personal-history Citibank card to the Ramp card (forcing manual finance journal entries every month), Peter directed Kelly to send Moody a notice that the card has been disabled and will stop working on June 15. CC Steve Wallace. Phrase it past-tense (has been disabled) plus future-fact (stops working 6/15) — not request language. Peter explicitly affirmed his prior gate (Kelly checks with him before shut-offs) while greenlighting this one because Kelly is giving a month notice — the notice IS the legitimacy gate.
Related Patterns (4)
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.
Purpose Is the Decision Procedure
When someone asks how a process, board, tool or artifact should handle their specific case, Peter refuses to answer on the askers terms. He re-derives the answer from what the artifact is for, states that purpose as the only decision procedure, and lets the answer fall out. Anything found to be serving a second purpose is deleted rather than debated. Tools and views are explicitly subordinate to definitions. He will accept that the askers real problem is simply not solved by this artifact rather than widen the artifact to cover it.
Demonstrate the Standard, Then Collect It
When a new leadership expectation has to land across multiple orgs, Peter does not write a spec. He runs a live exemplar in public with the strongest performer first, says openly that the ordering was deliberate, keeps the form of the deliverable open so the ask stays about the thinking rather than the artifact, lets the delta be self-evident to the people who will have to close it, and then collects the same from everyone else on a named rotation. He prefers showing imperfect work now over polished work later.