Skip to content
Illustrative scenarioPre-case study · in development

Huddle — 8 friends.1 plan.147 messages.

Still no plans.

Everybody’s excited. Somebody says “Saturday!” Eight people reply at once. This is the story of one night out — and the product idea it started.

01Illustrative scenario

Then the planning starts.

  1. ?

    The Planner: confused

    Problem 01

    Nobody agrees.

    Three dates, four activities, one very long thread.

  2. The Planner: stressed

    Problem 02

    Who owes what?

    The lane deposit, the snacks, the ride — and nobody’s sure who paid.

  3. The Planner: overwhelmed

    Problem 03

    Who’s bringing what?

    Speakers, the projector, the birthday cake. Everyone assumed someone else had it.

02Illustrative scenario

One person cancels. Everything changes.

  • Tobi
  • Amara
  • Jide✕
  • Kemi
  • Leo
  • Nia
  • Sam
  • Zee
Jide So sorry guys, something came up — I can’t make it 😞
  • Attendance8 going7 going
  • Shared cost$30 each$34.29?
  • ProjectorJideUnassigned
  • OrganizerPlan setDecisions needed

Why is getting together so complicated?

03Early research

From the story to what we actually know.

Preliminary, informal conversations with two people. These are early qualitative observations — not findings validated across a larger sample.

Conversation · 01

Sofiat

  • Has used Partiful.
  • Has experience coordinating event costs.
  • Wants improved coordination and easier access to event information.

Partiful

Conversation · 02

Racheal

  • Has used iMessage and Notes to organize plans.

iMessageNotes

Tools in the picture today

  • PartifulEvent invitations
  • iMessageGroup chat
  • NotesLists & details

A proper competitive analysis — what these and other planning apps already do well — is the next research step.

The emerging opportunity

Planning isn’t just about making decisions. It’s about keeping everyone coordinated when circumstances change.

Still open — to research and test

  • AssumptionInformation scattered across chat, notes and invite tools makes plans harder to follow.
  • AssumptionOrganisers carry most of the coordination work, especially when plans change.
  • QuestionHow comfortable are friends discussing shared costs inside a group app?
  • QuestionShould contributions be equal by default, or always opt-in?
  • QuestionWhat should happen to a cancelled person’s tasks and share — automatically or by decision?
  • QuestionWhich competitors already cover RSVPs, polls and costs, and where do they fall short?
04Concept UI

What if the plan could keep up?

Saturday · 7:00 pmKaraoke nightStudio 9 · Downtown
8 going
Decision · closes Thu 6pmActivity: Karaoke wins 5–3
Your share$30suggested · optional
You’re bringingSnacks2 of 3 tasks taken
📌 PinnedBooking code: STU-9. Doors at 6:45.

Huddle. Less planning. More living.

05Concept UI

How Huddle could work.

Seven exploratory ideas — each one answers a problem from the story. These are concept screens, not final designs.

Fixes: “Can someone scroll up and tell me the plan?”

Create a plan

One place for the activity, date, location and details.

  • Activity, date, place and notes in one event
  • Details stay at the top — not 147 messages up
New plan
Invite friends →

Fixes: Guessing who’s actually coming

Invite friends

Invite through in-app connections and see who’s in at a glance.

  • Going · Maybe · Can’t, visible to everyone
  • Gentle nudges for people who haven’t answered
Invites5 going · 1 maybe · 1 can’t
AmaraGoing
JideGoing
KemiMaybe
LeoGoing
NiaGoing
SamNo reply
ZeeCan’t
Nudge Sam

Fixes: Three dates, four activities, no decision

Decide together

Vote on activities, dates and places — with a clear deadline.

  • Every option and vote is visible
  • A deadline and a stated rule decide the result
Decide: activityCloses Thu 6:00 pm
Karaoke5
Bowling2
Picnic1
Rule: majority at the deadline. Tobi breaks ties.

Fixes: “I sent mine… I think?”

Coordinate contributions

Transparent, optional contributions — with waivers and suggested recalculations.

  • Suggested shares, never automatic charges
  • Waive or opt out without awkwardness
  • Changes need everyone’s confirmation
ContributionsOptional · nothing is charged
Event total$240$30 each suggested · 8 people
Amara$30
Kemi$30
SamWaived
Suggested change$30 → $34.29 each if 7 attendNeeds everyone’s confirmation

Fixes: “I thought YOU were bringing it”

Share responsibilities

Friends volunteer for equipment, supplies and other tasks.

  • Each task has one visible owner
  • Unclaimed tasks stand out
Who’s bringing what
Bluetooth speakerKemi
SnacksTobi
ProjectorI’ll take it
Birthday cakeNia

Fixes: “Wait, which address??”

Keep information together

Event chat, pinned announcements and reminders.

  • Pinned updates don’t get buried
  • Reminders before deadlines and the day itself
Karaoke nightEvent chat
📌 Announcement · TobiStudio 9 · Sat 7pm · code STU-9
LeoParking is on 5th, fyi
Added to details ✓
⏰ Reminder · Tomorrow 7:00 pm

Fixes: Photos scattered across eight camera rolls

Preserve memories

The conversation and shared media stay with the event afterwards.

  • Event chat and photos stay together
  • Easy to revisit — or plan the next one
Karaoke nightMemories · Sat 14
6 photos · 214 messages kept with the eventPlan the next one →
06Illustrative scenarioInteractive concept

What happens when someone cancels?

The principle: Show the consequences before asking people to decide.

Karaoke night · Sat 7pm

8 going

  • Tobi
  • Amara
  • Jide
  • Kemi
  • Leo
  • Nia
  • Sam
  • Zee

Shared cost (optional)

$30each

$240 total ÷ 8 people = $30

Responsibility

Projector + speaker

Jide

Organiser view · Tobi

Everything’s on track. Nothing to decide right now.

Try cancelling someone →

Scenario reset: 8 going, $30 each, projector and speaker assigned to Jide.

Illustrative numbers. In this concept, Huddle never charges anyone or reassigns a task automatically — it shows the consequences and lets people decide.

07Design hypothesis

Why it’s designed this way.

Three choices shape the concept. Each is a hypothesis with real trade-offs — the alternatives are reasonable too, and usability testing will decide.

Group decisions need transparency and deadlines.

How does a group actually reach a decision?

Alternative A

Open-ended poll

Votes trickle in forever; the loudest message wins.

Trade-off Flexible, but never finishes — the organiser ends up deciding alone.

Alternative B

Organiser decides

Fast and clear.

Trade-off Puts all the pressure on one person; others feel unheard.

Current hypothesis

Polls show every vote and a visible deadline with a stated rule (e.g. majority at the deadline; organiser breaks ties).

To test

  • Do people understand the rule before voting?
  • Does a deadline feel helpful or pushy?
  • Who should be allowed to extend it?

Contribution changes should require confirmation.

When the numbers change, who agrees to the new number?

Alternative A

Auto-recalculate

Shares update silently when someone leaves.

Trade-off Convenient, but people discover they owe more without agreeing.

Alternative B

Leave it to the chat

Sort it out in messages.

Trade-off Socially awkward and easy to lose track of.

Current hypothesis

Huddle suggests a recalculation, shows each person’s before/after, and nothing changes until people confirm. No payment is ever taken automatically.

To test

  • Is the before/after clear at a glance?
  • Do people prefer equal splits, opt-in, or the organiser absorbing changes?
  • How should a waiver be shown without singling anyone out?

Attendance changes must be linked to responsibilities.

When someone drops out, what else quietly breaks?

Alternative A

RSVP only

The headcount updates; everything else stays as it was.

Trade-off Simple, but the projector is still “assigned” to someone who isn’t coming.

Alternative B

Auto-reassign

The app hands the task to someone else.

Trade-off Efficient, but assigns work to people who never agreed.

Current hypothesis

Cancelling updates attendance, the suggested cost and any tasks together — then asks the organiser what to do, with options, instead of deciding for them.

To test

  • Does the organiser prompt feel helpful or alarming?
  • Should the person cancelling see the impact first?
  • What do friends expect to happen to the vacated task?
08Intended experience

Same eight friends. A calmer Saturday.

  • Everyone understands the plan
  • Attendance is visible
  • Contributions are transparent
  • Responsibilities are assigned
  • Important information is easy to find
we made it!

The best part of making plans?Actually showing up.

huddle. Less planning. More living.

Intended experience This is the experience Huddle is being designed to create — not a tested or proven outcome.

Coming soon · in development

The story is still unfolding.

  1. Research & DiscoveryIn progressEarly conversations with Sofiat and Racheal
  2. Competitive AnalysisUp next
  3. Information ArchitecturePlanned
  4. User FlowsPlanned
  5. Low-Fidelity WireframesPlanned
  6. Design SystemPlanned
  7. High-Fidelity PrototypePlanned
  8. Usability TestingPlanned