CASE STUDY
Salesforce — Dreamforce 2026 Agenda Builder
Hypothesis: Bringing recommendations into the agenda, so it starts partly filled instead of empty, would help more attendees build their Dreamforce schedule.
Dreamforce is Salesforce’s largest annual conference, with hundreds of sessions running in parallel over several days. With that much choice, a blank agenda is a hard place to start. Attendees need help finding the sessions worth their time, and a way to fit them into their day.
Agenda Builder (After): An agenda that arrives partly built, with recommendations already in place.
78.89% add-to-agenda action rate: 6,100+ unique viewers drove nearly 13,000 planning actions
40%+ of attendees who saw a recommendation acted on one
10,702 favorites
Zero incidents at launch
My Role
Product Design Lead · March – September 2026
I designed the Agenda Builder web experience end to end — flows, interaction design, and prototypes through developer handoff, launch, and documentation.
Attendees browsed more than 1,500 sessions in the catalog, where recommendations lived, then built their schedule from scratch in a blank agenda. Half of first-time attendees felt overwhelmed, and nothing helped them choose between sessions that happened at the same time.
The goal for 2026 was an Agenda Builder that arrives partly built: recommended sessions placed on the calendar without overlaps, so attendees start by adjusting a plan instead of making one.
Dreamforce 2025 (Before): Recommendations in the catalog, an empty agenda to fill by hand.
Recommended sessions appear on the calendar as dashed cards, so attendees see them in the context of their schedule and can add one with a single click.
Agenda Builder was designed to integrate with Agentforce, Salesforce’s own AI assistant. Attendees could open Agentforce right beside their calendar and ask it to build their agenda, show recommended activities, or suggest sessions for their industry, without leaving the page. I designed the layout so the agenda and the assistant worked side by side, and checked it in QA before launch.

Agentforce: An AI assistant docked beside the agenda, ready to help build a plan.
Conflict management was the core design challenge. Over several rounds, I worked through how overlapping sessions appear on the calendar and what should happen when an attendee adds a session that clashes with one already on their agenda.
Showing overlaps clearly
I refined the calendar so several sessions in the same time slot stay readable instead of collapsing into a cramped column. I also proposed extending time slots to the edge of the agenda, so the grid uses its full width instead of leaving a large empty area.

Overlapping sessions: Early explorations compared with the final layout.
Logic for conflicts
Beyond the visuals, I defined how the agenda behaves when sessions collide — so attendees always know what’s confirmed on their schedule and what still needs a decision.

Overlap priority logic: When sessions overlap, the card on top is chosen by rule — action required first, then earliest start, then favorites, then most recently added.

Conflict management: How the agenda handles overlapping sessions.
Around the calendar, I designed the features that make a schedule personal:
Favorites — save sessions to decide on later
Personal Time — block time for meetings, meals, or breaks
Calendar Sync — send the agenda to an attendee’s own calendar
Single-day and multi-day views — switch between a focused day and the whole event
Quick-view cards — see session details without leaving the calendar
Empty state — a clear starting point for first-time visitors

Personalization: Features that make a schedule personal.
Where attendees added sessions
Launch data showed the calendar card doing more work than expected. By September 8, it had become the top place attendees added recommended sessions — slightly ahead of the detail modal (39.5% vs. 38.9%). The card gave people enough information to decide without opening anything else.

Cards & quick view: Session details at a glance, right on the calendar.
Every screen size
I designed responsive tablet and mobile layouts so attendees could check and adjust their plans from any device — including on the event floor.

Tablet & Mobile: The same agenda, adapted for smaller screens.
The launch supported the hypothesis. More than 40% of attendees who saw a recommendation acted on one, and the calendar card turned 6,100+ viewers into nearly 13,000 planning actions. Attendees didn’t have to start from an empty agenda.
Bringing recommendations into the agenda meant every feature had to work together — recommendations, favorites, personal time, conflicts, and cards all live on the same calendar.
What I’d carry forward:
Solve the hardest interaction early — for Agenda Builder, that was overlapping sessions
Give people a plan to adjust, not a blank page to fill
Use launch data to check design decisions, like the calendar card
Leave clear documentation so the next team can build on the work

