We put every product manager on a rotating on-call shadow shift for a quarter. The roadmap changed more than the pager schedule did.

Product managers at Helix don't carry the pager. But for one quarter, we had every PM shadow a live on-call shift once a month — not touching the keyboard, just listening, watching, taking notes on what actually happens at 2am.

The gap between the roadmap and the reality

Our Q3 roadmap had eleven feature requests ranked by customer votes. After the shadow shifts, we added a twelfth item that no customer had ever explicitly requested: a one-click "mute this alert for 4 hours" button. Every single PM who shadowed a shift watched an engineer silence the same noisy alert manually, three separate times, because the proper suppression flow took longer than the incident itself.

"I'd shipped two dashboards nobody used and never once shipped the button that would have saved forty seconds, four times a night, for everyone." — PM, after a shadow shift

Turning shadow notes into backlog items

We formalized this. Every shadow shift now ends with a three-line note, not a full report, filed directly against the product backlog.

shadow_shift_note:
  date: 2026-02-11
  shift_owner: on-call rotation, prod
  friction_observed: >
    Suppressing a known-noisy alert requires 6 clicks across 2 screens;
    engineers do it manually via mute instead, losing suppression history.
  proposed_fix: one-click temporary mute, logged automatically
  votes_from_customers: 0
  votes_from_3am: 4

Why this changed how we prioritize

Customer-requested features and on-call-observed friction were competing for the same sprint capacity, and friction was losing every time because it had no voice in the room. Giving it a formal, recurring input — not a survey, an actual shift — rebalanced that. Two quarters later, our top five most-used features by session count include three that came directly from shadow notes and zero customer votes.

  • The people who build the roadmap rarely feel the pain the product causes at 2am — make them feel it on a schedule, not by accident.
  • Shadow shifts work better as short structured notes than long reports; nobody reads long reports at 2am or the morning after.
  • What customers vote for and what on-call needs are different signals — treat them as separate backlog inputs, not one ranked list.