Reforge — Engagement, Habits, and Activation
Summary
Engagement is the depth dimension of retention. While retention answers “were they active or not?” (binary), engagement answers “how active were they?” (spectrum). Together they form the core engine of growth — the power plant that drives acquisition and monetization.
The Organic Habit Loop
Every product has a natural habit loop: Trigger -> Action -> Reward. The trigger is an organic cue (e.g., “I need to meet with remote colleagues”), the action is what the user does in your product, and the reward reinforces taking that action next time the trigger occurs.
The mental model: you can’t create demand for triggers that don’t exist naturally. You can only reinforce existing ones or place yourself closer to where they occur.
Two Strategies to Reinforce Habits
Manufactured Loops — Push triggers through channels (email, push, in-product, etc.) to bring users back. Five trigger types: time-based, location-based, change-based, network/peer-based, and programmatic. Eight delivery channels. Three reward categories: extrinsic (time saved, money, information), intrinsic (completion, delight, leveling up), and social (recognition, confirmation, competition).
Critical constraint: manufactured loops only work when you can influence the organic trigger frequency. Zoom can’t make people have more meetings. Pinterest can send “new pins for you” because browsing is discretionary. If the organic trigger is fixed, manufactured loops just create noise the user tunes out.
Environment Loops — Place visual cues near where and when the organic trigger occurs. Example: Zoom’s calendar integration puts a “Join Zoom” button right where the meeting trigger happens. More costly than manufactured loops (may require new products, partnerships, or extensions) and adds activation friction, but effective when manufactured loops can’t influence the trigger.
The Activation Chain (Work Backward)
Reforge defines four activation moments, designed in reverse order:
- Habit Moment — User has done the core action multiple times within an initial period. They’re in the loop cycle. Define this first because it’s the outcome you’re designing toward.
- Aha Moment — User has experienced the core value prop for the first time. Look for a signal that they took the core action once within some initial window. The aha experience needs four components: core action, warm start (guided momentum), supporting actions, and handling empty states.
- Setup Moment — User has completed the prerequisites to experience the aha moment. Three types of must-haves: user info (company, preferences), permissions (notifications, location), and social (minimum people needed, e.g., Slack requires teammates).
Four Strategies to Accelerate Habit Creation
- Manufactured loops — Best when you can influence trigger frequency
- Environment loops — Best when the organic trigger is fixed but you can be present at the moment it occurs
- Use case transition — For products with infrequent natural frequencies (the “forgettable zone,” less than monthly). Shift users to a more frequent related use case. Credit Karma Tax does this — taxes are annual, but credit monitoring is monthly.
- Grand exit — Create a 10X experience delta vs. alternatives so the reward is so powerful it solidifies the habit immediately. Problem: not sustainable long-term because competition closes the gap.
The Use Case Frequency Spectrum is a key framework: monthly or more frequent = “Habit Zone” (easier to build habits). Less than monthly = “Forgettable Zone” (must reacquire users each cycle or transition them to a more frequent use case).
Relevance to projects:
- 01-projects/squarely-puzzles/index — Puzzle games live in the Habit Zone if daily. The organic habit loop: trigger (boredom/break time) -> action (solve puzzle) -> reward (completion satisfaction, streak). Manufactured loops via push notifications are natural here. The aha moment is completing first puzzle; the setup moment is choosing difficulty/category.
- 01-projects/data-marketplace/index — Data purchasing may be in the Forgettable Zone. Use case transition could work: shift from “buy data when needed” to “monitor data trends weekly.” The newsletter could serve as the environment loop, keeping the marketplace top of mind.
- 01-projects/newsletter/index — The newsletter IS the manufactured loop for other products. The trigger is “new issue published” -> action (read) -> reward (insight). This is the engagement engine.
Connects to 06-reference/2026-04-03-reforge-retention-is-the-output (retention as the output of engagement + activation + resurrection), 06-reference/2026-04-03-reforge-defining-strategy (engagement strategy must align with overall strategy), and 06-reference/2026-04-03-activations-three-moments (parallel framework for activation moments).
Open Questions
- For 01-projects/squarely-puzzles/index, which reward type drives the most engagement — intrinsic (completion/streaks) or social (leaderboards/competition)? Need to test both.
- Can the 01-projects/newsletter/index function as an environment loop for the data marketplace, placing CTAs near the organic trigger of “I need data for this problem”?
- The “grand exit” strategy is interesting for product launches. Could a 10X onboarding experience work for early-stage products where manufactured loops aren’t yet possible?
- What does “use case transition” look like for a B2B data product? Is there a weekly-frequency adjacent use case?