Challenge
An embedded engineering engagement reports against two parallel narratives — operational delivery (tickets resolved, hours, SLA) and product progress (backlog burn-down, releases shipped) — but stakeholders on either side rarely care about both. Producing two reports doubled the maintenance work without doubling the value.
Approach
I built a single-page snapshot with a clean operations-vs-product split, each side showing only the three or four KPIs that survived stakeholder review. The page is small on purpose: it's the artifact that gets screenshotted into a weekly status email, so it has to read at a glance.
Outcome
The status email now leads with the snapshot instead of paragraphs of prose. Stakeholders get the same picture every week, which makes deviations — good or bad — visible without anyone having to call them out.
