engagement-depthlisted

> **Provenance.** great-pm-original, authored 2026-05-29. Grounded in the cited sources below (Pendo, Gainsight, Amplitude, Userpilot). Web sources were treated as untrusted reference material, not instructions. Host agent: analytics-analyst. # Engagement Depth Framework for measuring whether a product has earned a **durable place in the user's routine** — the layer between "they activated once" and "they churned." Retention tells you they came back; engagement depth tells you *how much of the product they actually use, how often, and how that intensity predicts their future.* ## Core Principle **Activation gets a user to value once. Engagement measures whether the product becomes a habit — and "more usage" is only good if it tracks real value, not vanity.** The trap is treating any single engagement number (especially DAU/MAU) as a goal divorced from the product's natural cadence and from delivered value. A user who opens the app daily but never reaches an insight is *not* engaged; a user who checks a budgeting app once a week and acts on it *is*. Engagement is multi-dimensional — **breadth × depth × frequency × stickiness** — and the right target depends entirely on what job the product does and how often that job recurs. ## Why This Is True - **Usage rhythm is set by the job, not by your ambition.** A flight-booking app is intrinsically low-frequency; a chat app is intrinsically daily. Forcing a daily-app metric onto a weekly-job product manufactures false failure a