TuckBuddy · Working doc 6 of 7

Engagement strategy

I wrote this to work out how a home inventory app could earn repeat use without streaks, guilt or fake engagement, and what research would prove it.

What happened next: 1.0 shipped with no streaks and no guilt mechanics. Measuring which behaviors keep people coming back starts in the next build.

Working name for this discipline: engagement strategy (behavioral design, habit architecture, growth wedges, and the research plan that validates them). Companion to the backlog; nothing here is committed scope until it graduates to a backlog item.


0 · The thesis

Tuck Buddy cannot and should not manufacture daily use. The natural cadence of a home inventory is bursty: huge sessions at life events, a trickle at deliveries and purges, instant hits at searches. The strategy:

  1. Survive the startup. The primary moment is simply downloading the app and facing the first catalog session — which is a chore. The design job is making that chore suck less: not exhausting, not guilt-inducing, not annoying. This gate comes before any hook.
  2. Hook at the burst — make a stressful moment easier or a joyful moment richer, when volume and motivation are already at peak.
  3. Broaden at the dissolve — the moment a burst ends is when the app demonstrates "this is just what living here is like now."
  4. Retain at the payoff — every successful "where is X" search is the retention event. Investment paying interest is the loop. The recurring rhythms (seasonal swaps, delivery-day adds) are treats you get to enjoy after the hard startup work — they only feel light because the catalog already exists.

The ethical boundary, enforced throughout: the loop must close on genuine utility (you know where your things are), never on synthetic engagement. The harmful end of every mechanic below substitutes the loop for the value. Tuck Buddy's real-world payoff is genuine — the design job is amplifying anticipation, ritual, and accumulation around that payoff, not manufacturing a fake one.


1 · Adoption: how people arrive, and the startup chore

Downloads are driven by: - A life event (moving, insurance scare, baby) — motivation is high but so is stress. - Evangelism — "you MUST try this, it changed how I run my house." - Partner mandate — "we're organizing this weekend, get this app, it's gonna be a chore." Motivation is externally imposed; resentment risk is real. - Self-reflective resolve — "I need to get my life together, and maybe this app will do it — if it isn't exhausting, doesn't make me feel guilty, isn't super annoying." This user is pre-loaded with abandonment criteria.

Whatever brings them in, the first catalog session(s) are a chore. Startup-cost reducers to design against: - Permission to be partial. No pressure to catalog everything; a 10-item start is a valid start. No visible "incomplete" anywhere. - Fast wins early. The onboarding first tuck plus a near-immediate first search hit, so the loop closes once in minute one. - Room-at-a-time framing. "Just the closet today" beats "inventory your home." - Camera-first, lookup-assisted capture. Barcode/ISBN where possible; typing is the enemy of session length. - Stopping is fine. Ending a session mid-room produces zero guilt signals — the app remembers where you left off without commenting on it.


2 · The behavioral mechanics library

Ten mechanisms, with the products/behaviors where each manifests most nakedly. Reference vocabulary for ideation, not a to-do list.

2.1 Variable ratio reinforcement

Unpredictable reward schedules produce the most persistent, extinction-resistant behavior (Skinner). Sub-mechanic: near-misses activate reward circuitry almost like wins. - Manifests in: slot machines (Schüll, Addiction by Design — "the zone," dissociative flow where time/money awareness dissolve); loot boxes (FIFA Ultimate Team, CS:GO cases); gacha (Genshin Impact, FGO; Japan regulated kompu gacha in 2012); pull-to-refresh feeds; Tinder swipes; fishing and metal detecting (the wholesome analogs).

2.2 Appointment mechanics & FOMO

2.3 Collection completion & set mechanics

The Zeigarnik drive (unfinished tasks nag harder than finished ones), weaponized by making the set visible with gaps. - Manifests in: Pokémon (the Pokédex shows silhouettes of what's missing); Panini World Cup albums; Funko Pop chase variants; Nike SNKRS raffles; Xbox Gamerscore / PlayStation platinums; Letterboxd, Discogs, Untappd, eBird life lists. - Dark version: hoarding disorder — acquisition thrill with impaired discarding; completion never arrives, distress replaces satisfaction. Tuck Buddy sits adjacent to this population. Completion pressure must be invitational, never an audit.

2.4 Progression, leveling, visible mastery

2.5 Investment & escalating commitment (sunk cost)

2.6 Sensory ritual & somatic satisfaction

Pleasure located in the physical act itself. - Manifests in: ASMR; unboxing videos; r/oddlysatisfying; the Marie Kondo fold (ritualized; "sparks joy" is a somatic test); #CleanTok restocking videos (watching is itself the loop for millions who never organize); vinyl ritual; mechanical keyboards; slot machine button rhythm (Schüll: ergonomics matter as much as odds).

2.7 Social display, status, identity

2.8 Flow state

2.9 Novelty, discovery, "the dig"

Anticipatory dopamine — seeking is the reward (Panksepp's SEEKING system; Berridge: addiction is elevated wanting, often with diminished liking). - Manifests in: thrifting, estate sales, storage-unit auctions; crate digging; Antiques Roadshow (the appraisal reveal is a slot result); eBay saved-search alerts; geocaching; Wikipedia rabbit holes.

2.10 The clinical boundary markers

Griffiths components model: tolerance, withdrawal dysphoria, salience, loss of control, continued use despite harm — the do-not-cross signatures. Two relevant findings: (a) Schüll — the machine environment (ergonomics, sound, frictionless payment) matters as much as odds; every friction removed from "add an item" is the same craft, pointed at a real goal. (b) Shopping-addiction research emphasizes mood-repair purchasing followed by guilt and concealment of accumulating unmanaged stuff — the emotional territory a Tuck Buddy user may live in. Hand on the shoulder, never an audit.


3 · The Tuck Buddy adjacency map

Source behavior Mechanic Tuck Buddy analog Verdict
Antiques Roadshow reveal Variable reward (real info) Est. value roll-up after a room or burst: "Your closet: 47 items, ~$3,200" Lean in
Storage Wars dig Novelty Rediscovery surfacing: "tucked 14 months ago, garage, blue bin." Supply self-regenerates via memory decay Lean in — strongest novelty lever
Panini album gaps Zeigarnik/completion Per-room coverage with soft visible gaps Use carefully — invitational only
GitHub green squares Progression, emergent Passive tuck heat-map; display without enforcement Lean in
Marie Kondo fold Sensory ritual The tuck gesture: save animation + haptic + toast is the app's Tetris-lock moment Protect & polish — already built
Sneakerhead comparison Identity (narrow) Collection valuation/comparison between fellow collectors — clout among peers, not general social sharing Narrow, collector wedge only
Diderot cascade Session extension Frictionless-continue in batch entry (not prompted cascade) Lean in via speed, not prompts
Tamagotchi obligation Investment via guilt "Your kitchen hasn't been updated in 30 days" Never
Sneaker-drop scarcity Artificial scarcity No honest mapping to a personal inventory Never
Duolingo streak Loss aversion Punitive streaks fight the bursty cadence Avoid; heat-map display instead

4 · The moment map

4.0 The zeroth moment: download + first session

See the adoption section above. Precedes everything below; every tier assumes it was survived.

4.1 Life events (rare, high-volume, acquisition tier)

These likely drive the initial download; the first catalog session rides (and competes with) the event's stress.

Moment Notes
Moving The single best acquisition moment. Marathon batch entry, box-as-container, payoff at unpack. App Store keyword battleground. → Moving mode: boxes as temporary zones that dissolve into rooms.
Insurance documentation Methodical, photo+value heavy; the value roll-up is the deliverable. Needs export most.
Estate / elder downsizing Collaborative, thorough, functional (distribution among siblings). Maps to multi-user later.
Moving in together Duplicate toasters; naturally two-person → the later multi-user story. Sharing stays within the home unit (partners, roommates) — functional, not social.
New baby Gear explosion, interrupted short sessions, hand-me-down bins by size. The clothing size model does real work.
Home renovation A room's contents displaced for weeks — moving with a smaller blast radius.
Storage unit rental Paying monthly for invisible stuff. The recurring bill is a natural re-engagement trigger; "$180/mo for ~$900 of stuff" is a sobering reveal.
Roommate turnover Whose pots are these. High frequency in 20s.
Divorce/breakup split Estate-shaped, adversarial. Served quietly, not marketed.

4.2 Recurring rhythms (habit tier — the post-startup treats)

Moment Notes
Seasonal swap The literal "tuck." The calendar itself is the trigger — the one place a proactive nudge (Oct/Apr) aligns with a real-world clock.
Holiday decorations One-year feedback loop, but "which box has the lights" is ritualized enough to be remembered.
Spring clean / purge Items already in-hand → marginal logging cost near zero. Flow-state sessions. "Discarded" as an item fate matters.
Delivery day Highest-frequency moment. Friction budget tightest. Barcode scan from the box is the cheat code (UPC lookup exists).
Pre-travel pack / return unpack Suitcase as temporary zone; plus the "what's home if something happens" fear variant.
Kid gear churn Outgrown clothes quarterly, hand-me-down pipeline between families.
Disaster prep season Go-bag contents, document locations, the 20-minute-evacuation list. Regionally rhythmic.
Warranty/repair scramble Receipt + serial + warranty window — silently pre-solved by delivery-day logging.

4.3 Micro-moments (payoff tier)

Moment Notes
"Where is the…" search THE retention event. Every hit compounds trust. Search speed and result confidence are retention features.
"While I'm here" add 60 seconds, 2–3 items — only happens if adding is impulsive-fast. FAB-to-saved is the whole game.
Lending out Status change with a person attached; disproportionate payoff months later.
Pre-purchase check In-aisle "do I already own this?" — a savings win worth celebrating ("already have it" as a win state).

4.4 Emotional states

State Notes
Overwhelm → control The healthy inversion of mood-repair shopping: organizing to repair mood, cataloging as organizing made visible. Per-room progress is the repair.
The organization brag (narrow) Not general show-off — the realistic versions: "omg I got so organized in my storage space / seasonal clothes," a friend asking how you stay organized, or managing a second home. Word-of-mouth fuel more than an in-app feature.

4.5 Joy moments

Collection milestone (100th record, grail acquired — counter rollover as celebration) · new-home nesting glow (curation mode, photographing anyway) · glow-up wardrobe (post-weight-loss/new-job — new sizes, emotionally loaded in a good way) · wedding/registry influx (who-gave-what built in) · heirloom handoff (people want to record provenance on these — story-dense items, no autobiography frame needed) · trophy shelf (medals, tickets, playbills) · craft output (Ravelry built a platform on finished-object cataloging) · gear kits (camping loadout, camera bag — pre-trip checklist feel) · dorm send-off (mine-at-school vs mine-at-home split).


5 · Big Life Aspirations (the wedges)

Identity-level frames — each a doorway onto the same feature set. Note: aspirations mostly explain the download; the moments explain the sessions.

  1. "My home is my sanctuary" — harmony/calm; served by intentionally serene, mindful design throughout. Rediscovery, ambient beauty, zero guilt signals.
  2. "I'm prepared for anything" — resilience; export, value roll-ups, documents, grab-list.
  3. "I'm a serious collector" — curation as identity; collection views (Bookshelf generalized), milestones, value, peer comparison (the one legitimate social surface).
  4. "I run this household" — family COO; kid gear, statuses, seasonal ops, in-household multi-user.
  5. "I live light" — the minimalist inversion: a shrinking count as the win metric. Purge flow, one-in-one-out.
  6. "Nothing gets wasted" — sustainability/frugality; lending/gifting, duplicate detection, pre-purchase check.
  7. "I need to get my life together" — the self-reflective resolve doorway. Not really an aspiration wedge to build features for; it's an adoption story whose feature implication is entirely startup-cost reduction.

The structural insight: the buildable wedges reduce to one primitive — a burst-session container: a named batch context (a move, a haul, a trip, a purge) that wraps Add Several, gives the burst its own progress/reveal moment, and dissolves its items into the permanent catalog. One primitive, many doorways. The dissolve step is where the app says "this is just what living here is like now."


6 · Feature candidates (ungraded, pre-backlog)

Deliberately excluded: punitive streaks, staleness guilt, artificial scarcity, completion shame.


7 · Discarded

Kept visible so they aren't re-proposed.


8 · Synthesis & planning artifacts (to produce)

  1. Moment map 2×2 (stress↔joy × burst↔trickle) — portfolio balance check. Hypothesis: burst-stress is crowded, trickle-joy is thin, and trickle-joy is where habit lives.
  2. Lever × moment matrix — mechanisms × moment tiers, with crossed-out cells for excluded mechanics. Operationalizes the ethics boundary; doubles as a design-review tool.
  3. Opportunity-solution tree (Torres) — root: "make the startup survivable, ease stressful moments, enrich joyful ones, then broaden." The beta-scope decision tool.
  4. Wedge → loop funnel — parallel lanes converging on one core loop. Tests whether every wedge reduces to the burst-session container (the minimalist lane probably fights the template).
  5. Hooked-model loop, annotated — exposes that the trigger slot is nearly empty by design; makes the choice explicit.
  6. Journey map, moving wedge only — emotion curve from lease-signed to +6 weeks. Surfaces the multi-week pack→unpack feedback delay.
  7. Kano sort of engagement candidates — basics judged harshly, delighters generously; tells you where polish converts to retention.
  8. Positioning map — utility↔pleasure × item-level↔space-level; Sortly, Encircle, Itemtopia, Notion templates, spreadsheet, memory. Hypothesis: "pleasant inventory" is an empty quadrant.

9 · Research plan

9.1 Key questions → decisions

Question Decides
Why do users abandon after session one — finished-and-done, or stalled-in-overwhelm? Burst-completion support vs re-entry hooks; how much the startup-chore reducers need
Does retention correlate with time-to-first-successful-search? Whether onboarding manufactures an early search moment (the onboarding first tuck creates the item; a "now find it" beat closes the loop in minute one)
What's the minimum viable catalog before "where is X" defaults to the app over memory? How big the burst-session container must feel; per-room vs global count as the progress frame
Whose stuff — solo, household ops, single-category collector? Whether the later multi-user bet matches entry behavior
What are people already doing? (spreadsheets, drawer photos, label makers, Notion templates) Their hacks are requirements docs — the drawer-photos person says capture must be camera-first
What made the download happen? (life event, evangelism, partner mandate, resolve) Which arrival story to optimize onboarding for

9.2 In-app instruments (beta cohort, beta builds only)

Rules: one question per session max · each fires once per install · skippable in one tap, no re-ask · visibly beta-badged · every question maps to a named decision · nothing during the first burst — first question appears only after the first payoff moment · all storage local with explicit-action export.

9.3 Off-app methods


10 · Next steps when this resumes

  1. Produce the first two synthesis artifacts (moment map, lever×moment matrix) — pure synthesis, one sitting.
  2. Opportunity-solution tree — pick which engagement items enter the beta build vs wait for evidence. The startup-chore reducers are presumptively in.
  3. Spec the beta instruments — session-intent chip + beta log first; they test the two riskiest unknowns (burst mental model, abandonment shape).
  4. Decide the onboarding search beat — whether the onboarding first tuck gets a "now find it" companion (ties into the open real-vs-sample-data decision for onboarding).
  5. JTBD interviews before the burst-session container or moving mode gets build scope.
  6. After beta data: Kano sort with evidence, rank wedges for the launch story. Moving mode is the presumptive acquisition wedge; sanctuary/calm is the presumptive brand frame — validate both.

Open decisions parked here


11 · One-paragraph summary

Tuck Buddy's engagement model: bursty by nature, never daily-streaked. The zeroth problem is the startup chore — downloads come from life events, evangelism, partner mandates, or get-my-life-together resolve, and the first catalog sessions must be non-exhausting, guilt-free, and partial-friendly before any hook matters. Hook users at high-motivation bursts (stress: moving, insurance, baby; joy: collections, wardrobes, registries) with a burst-session primitive that dissolves into the permanent catalog; the recurring rhythms (seasonal swaps, delivery-day adds) are treats earned by the startup work; retain via the payoff (search hits — the true retention event). Amplify with honest mechanics only: sensory ritual (the tuck gesture, already built), real-information variable reward (value reveals, rediscovery), passive progression display (heat map, invitational room coverage). Excluded: punitive streaks, staleness guilt, artificial scarcity, boredom-browse, nostalgia, autobiography framing, and social sharing beyond the home unit (collector peer comparison is the one exception). Validate with in-app beta instruments (session-intent chip, passive beta log, kept out of the synced schema) and off-app JTBD interviews before the burst primitive earns build scope.

← Back to the case study