← All posts
June 6, 2026 · Avium

Your Scrum Master and your VP shouldn't get the same briefing.

One of them runs a standup. The other runs a portfolio. They're looking at the same sprint, the same tickets, the same data — and they need almost nothing in common from it.

A Scrum Master needs to know what's blocked right now, who's over capacity on the team, and what to clear before the daily. A VP of Engineering needs to know which teams are behind pace, where cross-team risk is building, and who to spend a 1:1 on this week. One is tactical and this-sprint. The other is portfolio and this-quarter.

Most tools hand both people the exact same dashboard and call it visibility. It isn't. It's the same data with the work of interpreting it pushed onto every reader — and the busiest readers are the ones who'll never do it.

Same data, different question

A briefing is only useful through one lens at a time. So Avium picks the lens for you, from the role you tell it you play:

  • Team lens (Scrum Master, Agile Coach, Project Manager) — leads with what's blocked now, including work silently blocked by another sprint, who's over-loaded, and the unassigned or unestimated tickets to clean up before standup.
  • Leaders lens (Engineering Manager, VP, PMO) — leads with which teams are behind pace, cross-team capacity and velocity trends, and where risk is concentrated this week. No ticket-by-ticket noise — a leader delegates that.

Scrum Master

Team lens

Standup view — what to run today

  • Blocked by other sprintsAV-12 waits on AV-7 (in the backlog)
  • Nick Jones143% over — 57 / 40h this sprint
  • Cleanup before standup3 unassigned · 1 unestimated
Utilization % by department · last 6 sprints
EngineeringProductDesign

Run the standup · clear the blockers

VP of Engineering

Leaders lens

Portfolio view — where to look this week

  • Payments team29% done · 30% behind pace
  • Product velocitysharp drop — down 45% over 6 sprints
  • Cross-team risk2 commitments blocked across sprints
What’s putting Sprint 15 at risk
Over-allocation · 3 peopleUnder-utilized · 9 peopleScope creep · 10 itemsBlocked by dependency · 10Stuck / stalled · 7 itemsSprint 1514% done · 7d left

Spot the risk · spend the 1:1

Same sprint, two lenses — the Scrum Master gets a tactical standup (with the team’s utilization trend); the VP gets the portfolio risk fan-in. Same Avium Signals underneath.

Both the numbers and the words adapt

This isn't a relabeled header on the same report. Avium forks the briefing at two layers. The deterministic layer — built on Avium Signals — chooses which risks to surface and in what order for your lens. And for teams on the AI tier, the narrative layerAvium Intelligence — writes the prose for your lens too: portfolio language for leaders, standup language for team leads.

It's the same engine we always run — deterministic detection on the bottom, grounded narrative on top. Every line still traces back to a real Avium Signal, so nothing is invented. The only thing that changes is who it's written for.

Your role is the switch

Set your role once and your briefing — in the app and in your inbox each morning — is tailored to it, and the role-based email briefings that fit your work turn on. Change roles and it follows you. Clear your role and the role-based emails stop. You're never subscribed to something you didn't choose.

Because the honest version of visibility isn't showing everyone everything. It's showing each person the one view that lets them act before the sprint slips.

See the work. Plan the capacity. Catch the risk — now through your lens.

See the work. Plan the capacity. Catch the risk.

Start free →