Hive's Notifications and Inbox teams are under pressure to reduce missed task updates for enterprise customers before Q4 renewals. Over the last 2 quarters, 18% of high-priority project updates were acknowledged more than 24 hours late, and customer interviews suggest the root cause is split: some teams are overwhelmed by noisy notifications, while others have inconsistent internal workflows for triaging work in Hive Inbox.
You are the Engineering Manager leading a cross-functional effort across 8 engineers, 1 product manager, 1 designer, and shared data support. The VP of Product wants a visible improvement in 10 weeks because 3 large accounts representing $1.9M ARR have flagged collaboration reliability as a renewal concern. The core decision is whether to invest most of the team in a technical solution inside Hive (for example, notification bundling, priority routing, or Inbox automation) or drive a lighter product change paired with a required customer-facing process change and admin guidance.
The VP of Product wants measurable customer impact this quarter. The Head of Customer Success prefers a fast process rollout to protect renewals. The Staff Engineer wants to avoid shipping brittle automation on top of legacy notification rules. The Sales team is pushing for a marketable feature launch in time for the quarterly customer webinar.
You have 10 weeks, a hard budget cap of CAD 220,000, and no additional headcount. Only 5 engineers can work full-time because 3 are committed 40% to reliability work. Data instrumentation for notification acknowledgment is incomplete and will take 2 weeks to clean up. Any change touching notification delivery requires Security and SRE review, with a minimum 7 business day lead time.