---
title: Beyond the Group Chat case study
description: A Messenger concept that asks a few people privately before the group ever sees the plan.
canonical: https://angelogonza.com/work/beyond-the-group-chat
---

# Beyond the Group Chat

> Plans die in group chats because a request aimed at everyone is aimed at no one.

- **Role** — Product Designer
- **Timeline** — 4 weeks, Fall 2026
- **Team** — Angelo Gonzalez, Ryanna Jelks, Thejas Mirle, Drew Guthrie
- **Skills** — Figma, Prototyping, User Research, Product Design
- **Surface** — Messenger, concept feature

## Problem

Young adults planning in group chats get silence or deflection instead of clear answers. This is not a logistics problem. It is a social one, and it is about who is being asked.

## Goal

Coordinate with a few individuals first, so that those people give an answer they will stand behind, and the plan already has momentum by the time it hits the group chat.

## Research

- Interviews with young adults about how they actually plan
- An autopsy on Partiful (too much friction for a simple invitation) and Apple Invite (too many barriers to RSVP)
- Markey (2000) and Barron & Yechiam (2002) on the bystander effect: a request sent to one person gets more responses than the same request sent to five

## Insights

- **Lack of clarity** — when people cannot say a clear no, silence leaves the initiator with nothing to act on.
- **Individual vs group** — asking one at a time produces a higher response rate and more yeses.
- **Value of leadership** — every plan that worked had someone coordinating availability and following up.

## Solution

Events: a step inside Messenger that sends an invitation to a handful of people individually before the group sees it.

- Invite individuals before the group
- Declines private by default; making them public is an explicit choice
- The plan stays in the conversation, pinned to the top of the thread

## The trade-off

A private decline gives the initiator something the group does not have. We took that asymmetry deliberately, because a no that costs nothing is worth more than a no that never gets said, and we kept it visible: Public Declines is a checkbox on the event form, off by default.

## Outcome

Usability testing on the Figma prototype was positive on the core idea. Three gaps came back and all three were built: search on the invite screen, date and time in the invite message, and a share button on past events.

## Success metrics

- Fewer plans die in silence — share of plans with zero or one reply
- Plans move faster — time from first invite to first reply
- Plans actually happen — a one-tap post-event check, and whether the initiator starts another plan

## Next steps

Build a beta, interview people who have used it on a real plan, refine, and test again. No new features until the indicators show the first one paying off.

## Scope note

A concept sprint rather than a shipped feature. Testing was on a Figma prototype, so the metrics above are what we would measure, not what we measured.

## Reflection

- **Name the problem correctly before designing against it** — reframing this from logistics to social behaviour changed the question from how to make planning easier to what it costs someone to answer.
- **Adding is the easy part** — the design had not been tested enough to justify the feature list we finished with. Test, refine, and only add once the first idea is paying off.
- **An argument has to be sequenced, not just made** — the problem statement came too late in the deck, so the room met the insight before it had the frame to judge it by.

Read the visual case study at https://angelogonza.com/work/beyond-the-group-chat.