UX CASE STUDY · OTIS EXTENSION
Bridal Party Companion App
A mobile companion app that gives bridesmaids and maids of honor real-time access to the wedding-day schedule, their role, and everything they need to know, without waiting on the bride.

MY ROLE
UX Researcher & Designer
TIMELINE
Summer 2026
TEAM
Myself
TOOLS
Figma, Proven By Users, Granola
01 · OVERVIEW
The problem
On the wedding day, every schedule change, role assignment, and logistics detail routes through one person: the bride. When she's hyper-organized, it works. When she isn't, the bridal party is left guessing, often during fast-moving moments like the gap between ceremony and reception.
Today, bridesmaids piece information together from group chats, Google Docs, emails, and printed packets. Wedding apps like The Knot and Zola are built for the couple, so the people supporting the bride have no direct view into their own role.
I created this app to bridge that gap—a tool designed to keep bridal parties informed and organized so brides can focus on enjoying their day.
The challenge
How might we remove the bride as the sole checkpoint for day-of information, so the bridal party can stay in sync without waiting on her?
02 · RESEARCH
Who I'm designing for
Social, detail-oriented, aesthetically motivated, digital-first planners who are already solving this problem badly.
Demographic
Women in the US, mostly 25–38 (peak US wedding age), middle to upper-middle income, urban or suburban
Pyschographic
Social and detail-oriented; anxious when things are disorganized; aesthetically motivated - looks and function matter
Behavioral
Heavy mobile users already juggling Docs, group chats and Pinterest; know The Knot and Zola only from the bride's side
Generational
Millennials and Gen Z who expect seamless, digital-first experiences
The bridesmaids by the numbers
The average wedding party has about 4 bridesmaids, and each spends $1.2K–$5K+ on the role: hair and makeup, travel, the dress, and the bachelorette. That's a real time and money commitment, and no tool supports it.
4.39
Bridesmaids in the average US wedding party
$1.2K - $5k
Average cost to be a bridesmaid (local - destination wedding)
~$1,300
Spending toward a bachelorette
Sources: Priceonomics, The United States of Bridesmaids; David's Bridal, Perfect Number of Bridesmaids & Groomsmen; The Knot, Average Bridesmaid Dress Cost 2025; SoFi/Ally/Joy bridesmaid-cost breakdowns.
Competitors: built for the couple, not the bridesmaid
The gap: no competitor gives the bridesmaid direct insight into her role.
User Interviews
I interviewed 3 women who had served as a bridesmaid or maid of honor in the last 2 years, a mix of first-timers and veterans, recruited through my network (in-person, Zoom, and phone).
I expected them to want an information hub. Instead, they cared most about a schedule that updates live on the wedding day. In all three interviews, the bride was the only source of truth. It worked when the bride was hyper-organized and collapsed when she wasn't.
Key Insight
The real problem isn't giving the bride a place to type things once. It's helping her distribute information so the party isn't stuck waiting on her.
03 · User Personas
Users
Two personas emerged from the interviews: one who has done this many times and one who is doing it for the first time.

PERSONA 01
The experienced bridesmaid
Mihono · Millennial · High Income | Urban
Bio
Mihono, a deputy DA, runs her life on a schedule - up at 5:30 am, asleep by 9:15 pm. After five weddings, she has no patience for disorganization. She stays disciplined with her workouts, keeps a Google Doc for anything needing coordination
Goals & motivations
Driven to lead a bridal party with zero surprises - reliable schedules, clear roles, no wasted time or money. After one wedding collapsed due to a missing schedule and a no-show officiant, she’d adopt this app the moment she’s named MOH again - as insurance, not a nice-to-have.
Pain Points
No shared schedule
Last-minute role assignment
Zero delegation
Unreliable coordinator
Wasted time, money & energy
Pain Reliever
Reliable schedule & role assignments
Built for the bridal party, not the couple
Shared dress & color coordination
Pre-wedding intros among the party
Tightly outlined, efficient scheduling

PERSONA 02
The first-time maid of honor
Agnes · Millenial · Upper-middle Income | Urban
Bio
By day, Agnes crunches numbers as a CPA. By night, she’s an accidental wedding expert - planning bachelorette parties, decoding what a bridal shower even is, and answering nonstop texts from the bride and her co-MOH. When she’s stuck, TikTok is her search engine. She unwinds with skincare, dog walks, and going to the gym.
Goals & motivations
Motivated to be a dependable maid of honor, keep the bridal party informed, and pull off memorable events - all without letting the bride down or dropping the ball. Most likely to trust a wedding app if she saw it recommended on TikTok or used by a friend for their wedding
Pain Points
Blindsided by last-minute changes
Over-reliant on the bride for every detail
Unclear on event types & etiquette
Decision paralysis on open-ended tasks
Pain Reliever
Live mobile schedule & map
Event glossary in plain English
Broadcast tool for unresponsive members
Style references outlined by the wedding theme
Speech & bachelorette templates
Problem statments
"I am a maid of honor, trying to keep the bridal party organized and support the bride, but the lack of a shared, "live" schedule and logistics information stops me because everything routes through the bride alone, which makes me feel scattered and anxious during key moments like the gap between the ceremony and reception."
"I am a veteran maid of honor, trying to support the bride and keep the day running smoothly, but not knowing my role or the schedule until the last minute — and sometimes getting the wrong information entirely — stops me because there's no reliable, delegated way for that information to reach me, which makes me feel defeated and resentful despite showing up for someone I care about."
04 · Defining the solution
How might we remove the bride as the only checkpoint for day-of information, so the bridal party never has to wait on her?
The idea that shaped the design: instead of making bridesmaids hunt for information, the wedding day pushes updates to them automatically, like a flight app pushing a gate change to a traveler.
Core features
Living Schedule
Updated in real time, with push notifications for changes. The most requested feature
To-do list
Tasks for each assigned role, tracked leading up to the wedding
Resource Center
One source of truth for the party, replacing scattered tools
05 · INFORMATION ARCHITECTURE
Information architecture
I ran a card sort with Proven By Users so participants could group 18 pieces of wedding information the way they think about them. Six categories came out of it:
Category
Grouped information
Wedding Day Schedule
Schedule, reminders
Logistics
Location, expenses, to-do list, event calendar
Style & Beauty
Dress and shoe sizes, hair and make-up inspiration, mood board, theme
Communication
Group chat, bridal party contact info, wedding glossary
Bridal Party Info
Role Assignments
Pre-Wedding Events
Rehearsal dinner, bachelorette party
What the similarity matrix showed: the strongest grouping was bridesmaid prep (dress, shoes, hair, makeup), and participants placed the mood board there too. Group chat, glossary, and role assignments didn't cluster with anything, so they needed clearer homes in the navigation.

06 · TESTING
Test, learn, and refine.
I sketched the user journey for both the bride and the bridesmaid to test the flow before moving into Figma

Usability Testing
Users had five seconds to scan an image of the app and were asked to describe anything they remembered seeing.
I gathered testers regardless of their experience with bridal parties to broaden the scope.
Prototype Screen

Five second test results

Key observations that will inform my next iteration include:
The wrong content stood out. People remembered the welcome message and countdown, but no one noticed the live schedule, the core feature.
Users wanted logistics. When they knew what to tap, they chose location and event details.
No clear first action. Five participants gave four different answers about what they’d tap first.
Too much at once. The screen had too much to take in at a glance.
What I’m changing
Show the user’s role and the wedding name at the top
Make a “Next up” schedule card the main element of the home screen
Put location and event details one tap away
Give one main action the strongest visual weight
Shrink the welcome message and remove anything that isn’t essential
07 · REFLECT
Things I've learned
I am not my user.
I assumed bridesmaids would want help organizing the dress, hair, and makeup. What they actually worried about was being the last to know when the schedule changed, even though their whole job that day is supporting the bride. The people closest to the bride are often the least informed.
Need-to-know only
The bridal party doesn't need the seating chart, but they do need the order of photo sessions. Designing for this group means sharing less, at the right moment.
Next steps
Apply the five-second test changes and retest the home screen
Build a high-fidelity prototype of the live schedule and push notifications
Test the bride's side: how easily she can share updates with the party
A note on AI
I used Granola to take notes during interviews so I could focus on the conversation, ChatGPT to generate persona images instead of using photos of my real bridesmaids, and Claude to organize my thinking and refine written content, which I reviewed and edited myself. The interviews, participants, personas, research, testing and design decisions are all my own.
© 2026 Shai Siao · Made with care.



