Craft the agenda

The workshop is an opportunity not only to create alignment but also to educate and become inspired about what we can do and what our clients can accomplish. Feature the keynote on the screen while the team collaborates through exercises and a clear agenda that includes short breaks. The structure of the workshop varies depending on the maturity of the product idea.

043 workshop breakdown

Here’s a sample agenda for a two-day workshop:

Day 1

  • 8:00 a.m. Introduce the team
  • 8:45 a.m. Vision setting, landscape
  • 9:30 a.m. System roles
  • 10:00 a.m. User journeys
  • 10:45 a.m. Break
  • 11:00 a.m. Story mapping
  • 12:30 a.m. Lunch break
  • 13:00 p.m. Story mapping continued
  • 15:00 p.m. Cocktails and dinner

Day 2

  • 9:00 a.m. Technical feasibility, system deep dive
  • 10:00 a.m. Stakeholder, working team identification
  • 10:30 a.m. Break
  • 10:45 a.m. Prioritization of story map
  • 12:15 p.m. Lunch
  • 1:00 p.m. Risks and metrics
  • 1:30 p.m. Retrospective

Some sessions start with an overall risk and opportunity overview, whereas others dive right into a specific product/application—it is our job to pivot as we see fit. Always try to set aside at least a day and a half for a workshop; however, a team that works well together could potentially identify enough detail in a single day.

The Secret Source by Aurimas Adomavicius

About the author

Aurimas Adomavicius is the president and co-founder of Devbridge. When not in the trenches working with clients, Aurimas is an active speaker and writer on product design and engineering best practices.

Get in touch