What does it take
|
Dear Reader,
Together with my friends at Orbital (a company I advise), I recently ran a LinkedIn poll about user interview behaviors. My goal was to get a rough overview of how product teams approach preparing customer interactions.
Here’s what I learned from the 320 total votes:
Most (55%) of participants schedule interviews themselves, which indicates the healthy democratization of research access to scale Discovery in companies. While it requires the right skills and tooling, I have seen many situations where enabling a product team to recruit themselves simply reduces friction. And it creates the capacity for roles like user researchers to focus on the big rocks.
But do teams get the access they need? What's the point of being able to do your research when it takes you ages to get to the next reliable insight? 53% of participants shared that setting up their last five interviews took less than two weeks. Depending on the quality of the participants (and, consequently, insights), this feels good enough. Faster is often better, but you sacrifice interviewee quality for an artificial cadence.
Speaking of which, How do teams ensure they talk to the right people? Product Analytics data (38%) and Screener responses (32%) are the go-to qualifiers for the participants of this poll. This is probably the result of a team's context: The former depends on the available tooling and interview infrastructure, and the latter "only" requires skills to craft revealing screener questions.
Lucky for you, Orbital can help you in these three areas.
Disclaimer: I see the scientific shortcomings of LI survey data and the potential skewing of results. It's one valuable (and, frankly, fun) data point.
Did you enjoy this one or have feedback? Do reply. It's motivating. I'm not a robot; I read and respond to every subscriber email I get (just ask around). If this newsletter isn't for you anymore, you can unsubscribe here.
Thank you for Practicing Product,
Tim
Learn how I helped companies like Deutsche Telekom and Forto hone their Product Discovery practices. I closely work with product organizations through workshops and coaching to introduce and adapt Product Discovery.
Learn more about my Discovery Consulting |
What did you think of this week's newsletter?
As a Product Management Coach, I guide Product Teams to measure the real progress of their evidence-informed decisions.
I focus on better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery.
1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes.
This is the last newsletter before my annual summer writing break. I will be back in your inbox on August 17. Have a wonderful summer! ☀️ Product Practice #370 My 2025 Mid-Year Review READ ON HERBIG.CO PUBLISHED Jul 4, 2025 READING TIME 4 min & 06 sec Dear Reader, What I focused on in the first half of 2025 Writing and Editing My Book After a big writing push from February to April, I was able to share the first complete draft of my book Real Progress - How to Connect Product Strategy, OKRs,...
Product Practice #369 Product Discovery Triangulation READ ON HERBIG.CO PUBLISHED Jun 29, 2025 READING TIME 4 min & 47 sec Dear Reader, To get to an informed conviction through Product Discovery, product teams often need to be creative. It can be challenging for Product Discovery collaborators to make real progress, especially when they lack an environment that provides the right amount of guidance without being too constraining for Adaptable Product Discovery.That’s why today’s newsletter is...
Product Practice #368 How a Product Vision Board saved my Strategy READ ON HERBIG.CO PUBLISHED Jun 20, 2025 READING TIME 3 min & 53 sec Dear Reader, I once led a newly formed product team that aimed to develop a product to increase the monetization of a specific user segment. I co-led a long Discovery effort that validated and scoped this product. At one point during our Delivery journey, my boss approached the team while I was on leave and asked them what they were trying to accomplish....