Product Practice #291: Discovery Motions vs. Discovery Decisions

Published:

Estimated Reading Time:  Minutes


My Self-Paced Product Strategy Course is Available

Learn how to connect Strategy Threads into a Seamless Approach. My Path to Product Strategy Course enables you to form, execute, and measure the progress of coherent Product Strategy Choices based on structure and evidence. Prices start at 497€ (excl. VAT).

Explore self-paced only and guided course options

“OK, let’s meet back tomorrow to complete the remaining Actor branches of the Impact Map before we talk about Outcomes.”

What sounds like a usual way to wrap up a meeting among Discovery collaborators represents a misguided prioritization of Discovery Motions over Discovery Decisions.

James Clear’s comparison of Motions vs. Actions inspired me here:

“When you’re in motion, you’re planning and strategizing and learning. Those are all good things, but they don’t produce a result. Action, on the other hand, is the type of behavior that will deliver an outcome.”

Here’s how this translates to a structural Discovery tool like Impact Mapping:

Motions: Mapping out all horizontal levels before “allowing” yourself to go to the next one.

Decisions: Prioritizing actions to execute techniques to reduce uncertainties in identified aspects of Discovery.

Watch out for these Discovery Motions that keep you moving but prevent you from progressing.

Perfecting that JTBD statement one more time before developing and assumption-testing ideas.

Expanding persona details further before starting to recruit.

Getting an AI-based insights repository set up before reviewing the post-its from five interviews.

Selecting a new testing tool before rolling out the split test.

Completing every possible level of the User Story Map before prioritizing the first user stories in your next sprint.

Discovery Motions keep you on a horizontal completion and business path. Discovery Decisions help you get into action to reduce uncertainty.​

 How to put this Theory into Practice:

  • Check your current Discovery activities for “Motions.” Where are you simply trying to complete something (framework or blueprint) before getting into action?
  • Don’t abort helpful work to frame the bigger picture, but focus on preparing and starting activities in areas of uncertainty you have already identified.
  • What decisions (start with…, stop with…, inform…, etc.) can you make NOW in present areas of uncertainty to reduce the lead time to insights?

Thank you for Practicing Product,
Tim


Content I found Practical This Week

Customer Interviews: How to Recruit, What to Ask, and How to Synthesize What You Learn

However, when we synthesize what we are learning down to a research deck with a summary of findings, we often lose critical context. We tend to generalize across our customers, instead of remembering that each of our customers is a unique person with their own story. Instead of relying on these older methods to communicate with stakeholders, I like to share interview snapshots with my stakeholders. The experience map helps them visualize the story. The opportunities help them see how we might put what we learned into action. And the memorable quote helps them build empathy for our customers.

11 lesser-known mistakes PMs make during discovery

Customers can only speak to the existing product and their current needs. Churned users, however, will spotlight the broken shards in your product that aren’t often talked about. High-fit prospects can share how they’re solving problems today and where alternatives perform well. Sure, it’s hard enough to talk to customers, let alone find prospects and churned users. Thus, you need to create workflows that assist you. If you’re in B2B, joining relevant sales demos can give you an opportunity to probe mindsets of prospects and establishing incentivized exit interviews (or surveys) can get you in front of users that cancelled on you. Also, point #8 might help.

Forget Personas

The art of customer segmentation isn’t chasing after the most distinguishing traits but the smallest number of characteristics that cause people to buy or act. How do you do this? Instead of guessing at a bunch of attributes, start with the one distinguishing trait that all early adopters have.


{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}
>