Stephen Moody
Dec 28, 2025 - May 4, 2026
5
Decisions
0
Active Todos
3
Patterns
Categories
Decisions (5)
Mariah escalates Stephen Moody project delays directly to Peter (bypass Wallace)
Mariah will notify Peter immediately when Steve Moody delays HR-relevant project work. Triggered by a 6-week unresponsiveness pattern on the Rippling/JIRA integration that Steve Wallace had not escalated. Direct-escalation bypasses the manager (Wallace) for HR-adjacent commitments while Peter assesses whether this is a Moody problem or a Wallace prioritization problem.
AI Governance Single-Track Pivot for ISO 42001
Pivoted AI governance from dual-track (internal vs products) to single rigorous model because CIQ products (RLCAI, Fuzzball, Werewolf) now directly integrate AI, changing the liability profile.
Require mandatory tagging of all fully AI-generated content
AI Committee established policy that all fully AI-generated content must be tagged to manage user expectations. Applies only to fully AI-generated content, not human-reviewed or AI-assisted work. Format and placement of tags is flexible.
AI Policy Governance Approach
Agreed to collaborative governance approach for AI policy: Peter, Nathan, and Max will present AI exploration findings to the AI committee weekly, ensuring engineering innovation feeds into policy development.
AI Bot Architecture Decision
Decided to build a web app to front the AI bot, allowing curated outputs to be shared with Sarah and others without granting direct data access to underlying Slack/email/Jira data.
Related Patterns (3)
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.
Pragmatic Technical Middle Ground
When facing competing concerns (security vs innovation, access vs protection), find technical solutions that satisfy multiple stakeholders rather than debating policy or picking sides.