Skip to main content

How-To by Edition

This page replaces the older mixed persona stories with a cleaner edition-aware map.

The goal is not to show every kind of user. The goal is to show how the same core system behaves differently in Family, Roommate, and future Professional or white-label contexts.

Family​

Common use cases​

  • morning launch
  • after-school landing
  • dinner cleanup
  • weekly reset
  • parent-child handoff clarity

Typical flow​

  1. use Home Clarity to reduce confusion
  2. assign one or two visible responsibilities
  3. use Family Momentum to restart action
  4. use Family Check-In to review what worked

What success looks like​

  • fewer invisible reminders
  • calmer transitions
  • clearer definitions of done
  • easier recovery after hard days

Roommate​

Common use cases​

  • bathroom or kitchen rotation
  • shared supply restocking
  • quiet-hours expectations
  • move-in or move-out coordination
  • fairness review

Typical flow​

  1. make the shared expectation explicit
  2. document the recurring work or agreement
  3. use repeatable flows to reduce renegotiation
  4. use a neutral check-in to review fairness and friction

What success looks like​

  • clearer agreements
  • less resentment
  • better shared-space consistency
  • accountability without parent-child framing

Professional / White-Label​

Common use cases​

  • role-based workflow packs
  • repeatable team rituals
  • operational resets
  • branded support content

Typical flow​

  1. preserve the shared HBK core
  2. adapt role names and workflow labels
  3. keep support no-shame and explainable
  4. branch only where the edition genuinely changes the operating model

What success looks like​

  • stronger clarity
  • less duplicated documentation
  • consistent product standards under different brand surfaces

Rule of Thumb​

If the question is about principle, use the shared docs.

If the question is about tone, examples, or governance, use the edition docs.