Example: Product Discovery Meetings Calendar

View a real calendar from a remote, work from home cross-functional team. They conducted an intensive one week Product Discovery cycle. They started the week learning about the problems and opportunities at hand and finished the week by showing a solution in the form of a design prototype to 6 users.

The team decided to do most of the usual Product Discovery sessions that I coach teams to use. This helped them learn about the subject more deeply and to do it together. To avoid the pitfalls of waterfall development, every team member was present for every meeting. This cross-functional team included:

• Product manager

• Project manager

• Designer

• Lead engineer

• Marketing analyst

• User research analyst

• Me (their coach)

Too often, I see Product Managers try to learn as much as possible on their own and then do a “reveal” of their research to the team. It’s just not possible for others to consume so much information in one sitting. It’s much easier to learn as you go. This allows each team member to contribute more and different types of research and to influence the direction of the eventual product.

The Product Discovery sessions listed below represent a mixture of my own sessions with others from the Sprint book.

It’s a bit hard to read so I’ve transcribed the calendar below the image.

---

Monday

• 10am - 11:30am — User experience map, Problem definition and Choose target user

• 1pm - 2pm — Subject Matter Expert (SME) interviews

• 3pm - 4pm — Lightning Demos

Tuesday

• 10am - Noon — Crazy 8s, Solution sketching and Voting

• 3:30pm - 5pm — Develop Hypotheses and Storyboard

Wednesday

• 9am - 10am — Develop user recruiting screener and Decide on how to recruit users

• 12:30pm - 1pm — Prototype Check In #1

• 2:30pm - 3pm — Prototype Check In #2

Thursday

• 9am - 10am — Develop Testing script and review the Hypotheses

• 11:30am - Noon — Prototype Check In #3

• 2pm - 3pm — Final prototype demo and User test script sync up

• 3pm - 3:30pm — Launch one user test on UserTesting

Friday

• 9am - 9:30am — Review 1st UserTesting test

• 9:30 - 10am — Modify screener/prototype as needed

• 11am - Noon — Kick off 6 tests on UserTesting

• 3pm - 4:30pm — Review user tests and Decide on next steps