Daily Pulse Needs
Date: 2026-04-08
This note captures the Head of Delivery daily pulse requirements discussed in chat. The data source or retrieval method may improve over time, but the underlying concerns should remain stable.
Goal
Build a daily morning brief that surfaces the portfolio risks most likely to become sponsor pain if left unaddressed.
Required signal buckets
The morning pulse should explicitly check for:
- Cross-team communication gaps: teams not talking to each other, missed handoffs, or repeated sync confusion.
- Project review delays: project reviews / PRMs delayed, rescheduled, or never completed.
- Client sentiment issues: transcript evidence of confusion, anger, unhappiness, or loss of trust.
- Document review stalls: docs or plans stuck in review, waiting on approval, or blocked by comments.
- Linear tracking drift: work not being tracked in Linear, issues missing updates, or status not matching reality.
- Allocation mismatches: over/under-allocation, wrong owner, or work that is clearly under-resourced.
Operating principle
- The concerns are the source of truth, not the tool.
- If Slack, Linear, transcripts, or another system changes, preserve the same signal categories and the same output sections.
- The daily pulse should stay lean: escalate first, then flag red-risk signals, then summarize health.
Intended output shape
The final morning brief should continue to present:
- Escalations / fires
- Slack red flags
- Health status
- Recommended next actions