Mariah escalates Stephen Moody project delays directly to Peter (bypass Wallace)
Situation
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.
Reasoning
Steve Moody reports to Steve Wallace, so the chain technically works through Wallace. But Mariah has been chasing for 6 weeks and Wallace has not escalated, which means the chain is broken for HR-adjacent work. The Rippling/JIRA integration is a small project but representative: a category of work Wallace deprioritizes that has external accountability through HR. Direct escalation from Mariah is a workaround for the Wallace gap — not a permanent restructure but a near-term mechanism while Peter assesses the underlying issue. This connects to the broader performance-review window opened in HR weekly: Moody is now visible to Peter, which is a precondition for any future personnel action.
Additional Context
HR weekly sync this morning included broader review of org performance (Damen, Jeff, Jason, Owen, Amr). Stephen Moody surfaced as a specific issue with 6-week pattern. Same session as Max PTO bookkeeping and Wale-keep-under-Lindsey decisions (both Bjorn-owned).
Observed Evidence
Action item from HR weekly sync explicitly assigning Mariah to notify Peter directly. Reinforced same morning by Mariah DM showing the 6-week pattern; Peter responded that makes it worse.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
Related Context
fathom
Mariah: Notify Peter of any future project delays from Steve Moody. Mariah: Notify Peter Nelson immediately when Steve Moody delays work.
slack
Peter: that makes it worse. I assumed it covered about 2 weeks... and it was bad at that spread. Mariah surfaces 6-week pattern of Moody non-responsiveness on Rippling/Jira integration.
Outcome
No outcome recorded yet.
Decision ID: 5b6ef1bf-b4e2-4f04-8a6a-812a2cf3eddb