The day push notifications broke
Usage dropped 20–30% in a day. That told us which surface actually held the product together.
the drop
Usage fell 20–30% in a day. The size of the change made the signal hard to dismiss, but the cause was not in the main product flow. Push notifications had stopped doing their job.
We had treated notifications as a channel around the product. User behavior showed that they were part of the product itself.
the hidden surface
A notification did more than bring someone back. It carried context: something changed, now there is a reason to open the app. Without that prompt, the product could still work technically while the habit around it disappeared.
The incident exposed a dependency that the interface did not make obvious. The most visible surface was not necessarily the one holding usage together.
A surface can look secondary in the interface and still be load-bearing in user behavior.
what changed
The lesson was not to send more notifications. It was to treat the delivery path, timing and resulting journey as one end-to-end product system.
When a metric moves sharply, inspect the concrete journey before debating the roadmap. The broken path may reveal the real product faster than another round of prioritization.