Briefing Demo · Synthetic Data
Briefing Dashboard
S Steer · Monday briefing · May 4, 2026

Good morning, Edward.

Here's your week at Acme Engineering. I read 1,240 Jira issues and 38 GitHub repos over the weekend — three things need you (they map to the actions below):

  1. Delta — start here. It's slid into Critical and won't self-correct.
  2. Beta — 15 minutes pre-empts a quiet planning slip.
  3. Billing dependency — one call to make at Friday's sync.
Org Health At Risk · 70% 3 healthy · 1 at risk · 1 critical ↓ 4 pts vs. Q1
Priorities

Actions this week

3 decisions · ~25 min · ranked by where your time pays off
1 Team Delta Decide now
Delivery + Team Health · Critical
Cut Sprint 5 commitment 30% and put a director review on this week.
CRR 58%↓6 Cognitive load 62%
🔒 Steer acts only after you approve
Why it's #1
CRR fell to 58% (from 64% in March); two engineers left in Q1 and were never backfilled. They commit at the old velocity, then carry ~40% over. This won't recover on its own.
Steer recommends
When CRR sits below 70% for two-plus sprints, the operating model calls for capacity realignment, not exhortation. Re-baseline commitment to delivered velocity, then decide on backfill.
§9.5 — Commitment Reliability →
If you approve, here's what I'll do
  1. Draft the review brief (3-sprint trend + carry-over breakdown) onto Friday's sync.
  2. Re-baseline Sprint 5 to delivered velocity (−30%) as proposed scope, for the lead to confirm.
  3. Message Priya to pre-brief her — draft below.
Nothing changes in Jira until you approve.
2 Team Beta Delegate
Planning · At Risk → trending Critical
Ask Beta's lead to run a backlog refinement before Sprint 5 planning.
Backlog 1.5 sprints
🔒 Steer acts only after you approve
Why it's here
Backlog readiness dropped to 1.5 sprints of ready work (healthy is 2+). Not red yet, but the slope is steady and planning is in 9 days — the cheap moment to fix it.
Steer recommends
One 90-minute refinement restores readiness with no escalation. I'll raise this to a "decide now" only if it slips below 1 sprint.
§3 — Pre-Planning & backlog readiness →
3 Cross-team Bring to sync
Execution · Decision
Decide Friday: re-sequence the billing migration, or lend Alpha an engineer.
2 stories blocked · 11 days
🔒 Steer acts only after you approve
Why it's here
Two Alpha stories have waited 11 days on a Delta dependency. With Delta underwater this won't move unless you sequence it — and it's pulling a healthy team toward at-risk.
Steer recommends
A 5-minute sync decision, not a meeting. I've written it as an agenda item with both options and the blocked-issue links — draft below.
§7 — Governance & dependency management →
Drafts

I prepped these for you

Grouped by channel · tap to preview, then copy or edit
Drafted in your voice — direct, low-formality, no emoji, signs off "Edward." Tone is yours to adjust on any message.
# Slack 1 draft
Hi Priya — before Friday's leadership sync I want to give you a heads-up: Delta's the focus this week, and it's about capacity, not your planning. CRR's been under 70% for three sprints and I don't think it's fair to keep asking the team to commit at the old velocity after losing Sam and Theo. I'm proposing we re-baseline Sprint 5 down ~30% and talk backfill. Want 20 minutes Thursday to shape it together before the room?
Email 1 draft
Subject: Backlog refinement before Sprint 5 planning
Hi Marcus — heads-up that Beta's backlog readiness has dipped to ~1.5 sprints of ready work, and Sprint 5 planning is 9 days out. Could you run a 90-minute refinement with the team before then? That should get you back above two sprints of ready work and keep planning from stalling. If it helps, I can pull a candidate list of the stories that need grooming — just say the word.
31 Calendar 2 drafts
Thu May 7 · 3:00–3:30 PM · with Maya Krishnan (Director) & Priya Nair
30-minute review of Delta's three-sprint CRR trend. Decide the Sprint 5 re-baseline (−30%) and whether to open backfill. I'll attach the brief and carry-over breakdown the morning of.
Fri May 8 · 10:00 AM · adds as item 3
Billing migration — Alpha blocked on Delta (11 days). Decide: (a) re-sequence the migration behind Delta's recovery, or (b) lend Alpha one engineer to unblock now. Blocked: ALPHA-214, ALPHA-219. Owner to confirm in the room.
🗓️
Quarterly Planning for Q3 begins in ~5 weeks.
Two sprints left in Q2, then the Bridge Sprint. Here's what to line up now so the QP room runs clean — I can prep each artifact in your prepped items.
Lock Q3 capacity before you commit
Delta's two open backfills and ~3 weeks of summer PTO land before Q3. Confirm real capacity so next quarter's commitments aren't built on headcount you don't have.
§3 — Pre-Planning & capacity →
Investment mix is drifting from target
KTLO crept to 34% this quarter (target 20–30%) while New Product sits at 28% (target 30–40%). Worth a rebalance decision in the QP room.
§9 — Investment mix targets →
3 of 7 Q3 initiatives aren't QP-ready
Their Strategy and Initiative tickets still need grooming before the room. I can list exactly what's missing per initiative so owners can close the gaps in time.
§4 — Quarterly Planning →
Carry-over risks to take to the QRR
Two risks are still Owned with none Mitigated. Surface them at the Quarterly Risk Review rather than discovering them mid-quarter.
§7 — Governance & the QRR →
Epsilon's PR review time ticked up to 19 hours this week. I'll flag it if it passes 24h or the trend holds three weeks. 19h · ↑ from 14h
Change failure rate, Gamma — one bad deploy Friday, recovered in 40 min. Noise for now. I'll raise it only if a second one lands this sprint. CFR 8% · within band
Alpha's onboarding — two new hires ramping; first PRs merged on day 4. Tracking to plan. I'll let you know if either stalls. on track
  • Team Gamma (90%) — healthy across the board; AI suggestion-acceptance hit 41%, the highest in the org and finally showing up in throughput.
  • Team Alpha (80%) — steady delivery, clean quality; the only watch item is the Delta dependency in action #3.
  • Team Epsilon (80%) — commitment reliability back to 84% after last quarter's dip. Worth a word of recognition to the lead.
I watch Jira and GitHub continuously — this briefing was assembled at 7:00 AM, grounded in your operating model. Next one lands Monday.
Want it shorter, or focused on a team? Reply @Steer tune my briefing.