Product Management Coach & Consultant who helps teams to connect the dots of Strategy, Goals, and Discovery. Subscribe to my weekly newsletter for deep dive.
Europe
Joined January 2011
- Tweets29.4K
- Following669
- Followers3.9K
- Likes22.5K
Pinned Tweet
Give me 5 minutes of your time every Friday, and your Strategy, OKRs, and Discovery will become free of framework fluff.
My free weekly Product Practice newsletter helps you turn product theory ๐ into pragmatic and practical application. ๐ ๏ธ
herbig.blog/nl
Tim Herbig retweeted
"A lot of Product Discovery inputs are simply information. But Product Teams need more than information. They need evidence." via @herbigt in herbig.co/product-discovery-โฆ
Tim Herbig retweeted
Announcing June 4.0
โ a new kind of tool that gets you closer to your customers
producthunt.com/posts/june-4โฆ
help us & spread the word
Tim Herbig retweeted
Check out the Product Thoughts newsletter by @herbigt. Every week, he breaks down complex topics of product management into easy-to-understand chunks with relatable examples and hand-curated content worth your time: herbig.blog/nl
Tim Herbig retweeted
We are really happy that @herbigt will be one of our keynote speakers on September 13th!
Many of you have attended his sold-out pre-conference workshops in the past years and this time we feel it's time that Tim shares his learnings on the big stage.
๐ค productatheart.com/speakers
Is there a checkout tool that integrates with @ConvertKit so that upsells/checkout paths are displayed based on subscriber attributes in CK? When they have purchased this course, offer them this upsell, but not that one, etc.
Tim Herbig retweeted
PRODUCTHEAD: How product teams can measure discovery
This weekโs #ProductManagement newsletter lovingly curated by Jock Busuttil (@jockbu) features @jboogie @ttorres and @herbigt
#prodmgmt #discovery #metrics
imanageproducts.com/producthโฆ
Tim Herbig retweeted
Ever heard from Management: "This takes too long, just build it!"
Well, you are not alone! @herbigt wrote about this topic and how to deal with it.
Read his Thread below and you are good to go ๐
Tim Herbig retweeted
It's key to stay adaptable in product today ๐ @herbigt is running today's ๐ฌ Adaptable Product Discovery ๐ฌworkshop, helping product people implement the latest best practices in discovery - exciting stuff! ๐ #ProdMgmt #mtpcon #London
ALT mtpcon adaptable product discovery workshop
Tim Herbig retweeted
And that's a wrap! ๐๏ธ Our #mtpcon #London workshops have finished for 2023 - what a day! ๐ Just one more sleep til #mtpcon - check out what's happening tomorrow ๐ mindtheproduct.com/mtpcon/loโฆ #ProductManagement #London
Tim Herbig retweeted
That's a wrap!
If you enjoyed this thread:
1. Follow me @KiwiDenny for more of these
2. RT the tweet below to share this thread with your audience
๐๐ก๐๐ญ ๐ข๐ฌ ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐ข๐ฌ๐๐จ๐ฏ๐๐ซ๐ฒ ๐๐ง๐ ๐ฐ๐ก๐ฒ ๐ข๐ฌ ๐ข๐ญ ๐ข๐ฆ๐ฉ๐จ๐ซ๐ญ๐๐ง๐ญ?
I checked out various definitions and got together the best ones.
(Yes @herbigt and @ttorres play a part here!)
Furthermore, you will get 5 reasons why it is important!
Let's start ๐งต
Tim Herbig retweeted
๐๐ก๐๐ญ ๐ข๐ฌ ๐๐ซ๐จ๐๐ฎ๐๐ญ ๐๐ข๐ฌ๐๐จ๐ฏ๐๐ซ๐ฒ ๐๐ง๐ ๐ฐ๐ก๐ฒ ๐ข๐ฌ ๐ข๐ญ ๐ข๐ฆ๐ฉ๐จ๐ซ๐ญ๐๐ง๐ญ?
I checked out various definitions and got together the best ones.
(Yes @herbigt and @ttorres play a part here!)
Furthermore, you will get 5 reasons why it is important!
Let's start ๐งต
Tim Herbig retweeted
โ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.
@JamesClear'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?
If you liked this content, you will love my Product Practice Newsletter. Working with me requires a financial commitment, but the newsletter is free, and anyone can subscribe: herbig.blog/productpractice
"Health Checks" or "Assessments" of your product practices are really just ways to meet someone elseโs success criteria. Instead, test for everyday usefulness: "Does this help me/the team do <what's intended>?"
โ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.
@JamesClear'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?
If you liked this content, you will love my Product Practice Newsletter. Working with me requires a financial commitment, but the newsletter is free, and anyone can subscribe: herbig.blog/productpractice
Do some of these sound familiar to you when debating whether Discovery is an actual helpful practice?
HiPPo-driven decision-making leads to 12-month feature roadmaps.
โWe know best what users needโ-attitude when thinking about options to build something or uncovering customer insights.
Ship-and-forget handling of projects.
No measuring of product success against user or business goals.
Teams may deliver some of the outcomes of Product Discovery โโ like making a somewhat informed decision on what to prioritize building โโ without doing all ๐๐ต๐ฒ ๐ป๐ฒ๐ฐ๐ฒ๐๐๐ฎ๐ฟ๐ ๐๐ผ๐ฟ๐ธ ๐๐ต๐ฎ๐ ๐ฑ๐ฟ๐ถ๐๐ฒ๐ ๐ด๐ผ๐ผ๐ฑ ๐ถ๐ป๐๐ถ๐ด๐ต๐๐. So, teams donโt make strategic decisions or move the needle for critical metrics.
And, look, I'll be honest. I can't fix your entire organization by having you attend ๐บ๐ ๐ญ-๐ฑ๐ฎ๐ ๐๐ถ๐๐ฐ๐ผ๐๐ฒ๐ฟ๐ ๐๐ผ๐ฟ๐ธ๐๐ต๐ผ๐ฝ ๐ผ๐ป ๐ข๐ฐ๐๐ผ๐ฏ๐ฒ๐ฟ ๐ญ๐ต as part of @MindtheProduct London. ๐ฌ๐ง
๐๐๐ ๐๐ต๐ฎ๐ ๐ ๐ฐ๐ฎ๐ป ๐ฐ๐ฟ๐ฒ๐ฎ๐๐ฒ ๐ถ๐ ๐๐ผ๐๐ฟ ๐ฎ๐ฏ๐ถ๐น๐ถ๐๐ ๐๐ผ ๐๐๐ฎ๐ฟ๐ ๐ถ๐บ๐ฝ๐ฟ๐ผ๐๐ถ๐ป๐ด ๐๐ถ๐๐ฐ๐ผ๐๐ฒ๐ฟ๐ ๐ฝ๐ฟ๐ฎ๐ฐ๐๐ถ๐ฐ๐ฒ๐ ๐ถ๐บ๐บ๐ฒ๐ฑ๐ถ๐ฎ๐๐ฒ๐น๐ ๐๐ถ๐๐ต๐ผ๐๐ ๐๐ฎ๐ถ๐๐ถ๐ป๐ด ๐ณ๐ผ๐ฟ ๐๐ต๐ฒ ๐ฝ๐ฒ๐ฟ๐ณ๐ฒ๐ฐ๐ ๐ฐ๐ผ๐ป๐ฑ๐ถ๐๐ถ๐ผ๐ป๐.
Itโs easy to feel like you need to wait until thereโs enough buy-in, a perfect product strategy, better OKRs, etc. ๐๐๐ ๐ฎ๐ ๐ฃ๐ฟ๐ผ๐ฑ๐๐ฐ๐ ๐ ๐ฎ๐ป๐ฎ๐ด๐ฒ๐ฟ๐, ๐๐ผ๐ ๐ต๐ฎ๐๐ฒ ๐๐ต๐ฒ ๐ฟ๐ฒ๐๐ฝ๐ผ๐ป๐๐ถ๐ฏ๐ถ๐น๐ถ๐๐ ๐๐ผ ๐ผ๐๐ป ๐๐ต๐ฒ ๐ฝ๐ฟ๐ผ๐ฐ๐ฒ๐๐ ๐ผ๐ณ ๐ฐ๐ฟ๐ฒ๐ฎ๐๐ถ๐ป๐ด ๐ฏ๐ฒ๐๐๐ฒ๐ฟ ๐ฐ๐ผ๐ป๐ฑ๐ถ๐๐ถ๐ผ๐ป๐ ๐ณ๐ผ๐ฟ ๐ฃ๐ฟ๐ผ๐ฑ๐๐ฐ๐ ๐๐ถ๐๐ฐ๐ผ๐๐ฒ๐ฟ๐. ๐๐ป๐ฑ ๐๐ผ๐ ๐ฐ๐ฎ๐ป ๐ฑ๐ผ ๐๐ต๐ถ๐ ๐ฒ๐ฎ๐๐ถ๐น๐ ๐๐ต๐ฒ๐ป ๐๐ผ๐ ๐ต๐ฎ๐๐ฒ ๐๐ต๐ฒ ๐ฟ๐ถ๐ด๐ต๐ ๐๐ผ๐ผ๐น๐ ๐ฎ๐ ๐๐ผ๐๐ฟ ๐ฑ๐ถ๐๐ฝ๐ผ๐๐ฎ๐น.
A more adaptable and pragmatic Product Discovery approach supports you in taking the first steps toward making Product Discovery an integral part of your work. ๐ก๐ผ ๐บ๐ฎ๐๐๐ฒ๐ฟ ๐๐ต๐ฒ๐ฟ๐ฒ ๐๐ผ๐ ๐๐ผ๐ฟ๐ธ.
The best thing? You can now save 10% on the last few tickets. ๐๐ฟ๐ฎ๐ฏ ๐ผ๐ป๐ฒ ๐ผ๐ณ ๐๐ต๐ฒ ๐ฟ๐ฒ๐บ๐ฎ๐ถ๐ป๐ถ๐ป๐ด ๐๐ถ๐ฐ๐ธ๐ฒ๐๐ ๐๐ผ ๐ด๐ฒ๐ ๐๐๐ฎ๐ฟ๐๐ฒ๐ฑ:
web.cvent.com/event/df420afeโฆ
Many product teams perceive the focus on User Outcomes as arbitrary goal-setting and the opposite of serving users. And itโs easy to understand why.
Many widely shared examples of User Outcomes out there read like this:
โUsers buy more ticketsโ
โCustomers use more integrations. โ
โReturning shoppers add more items to their basket. โ
A product leader recently approached me after a conference talk, sharing his teamโs concerns that Outcomes would just be repackaged business goals. Looking at the above examples, his team would be right. These read like how the company or business wants their customers to behave.
To make Outcomes (aka changes in human behavior) useful, you have to remember that they should describe changes in behavior that are useful to the audience you intend to serve, which requires a proven problem.
Itโs not enough if Outcomes describe โtechnically correctโ changes in behavior. Instead, there should be a clear connection between business-informed research intent and insights generated by qualitative and quantitative techniques.
Another way to look at Outcomes as flipped user problems:
The simple question teams need to try and answer here is, โHow would users whose problems got solved behave?โ This will then be the foundation for finding appropriate measures to set your OKRs.
How to put this Theory into Practice:
Do your prioritized Outcomes read like something the company wants? If yes, dig for a problem worth solving based on first-hand evidence.
Ask team members how youโd know you solved this problem for users to go from problem to Outcome.
Donโt focus on User Outcomes for the sake of it. Make sure you prioritize Outcomes that serve mid-term business goals through Impact Mapping.
If you liked this content, you will love my Product Practice Newsletter. Working with me requires a financial commitment, but the newsletter is free, and anyone can subscribe: herbig.blog/productpractice
ALT How flipping User Problems leads to Useful User Outcomes.
Tim Herbig retweeted
Meet our amazing #mtpcon workshop trainers - happening 19th Oct at @etcvenues ๐
Our in-person, workshops are a must-attend event for any product manager looking to take their skills to the next level ๐mindtheproduct.com/mtpcon/loโฆ #ProdMgmt
ALT mtpcon london workshop trainers
Does the complaint โthis Discovery takes too longโ sound familiar? Iโve heard it throughout my career and from teams Iโm coaching. And, you know what, most Discoveries do take too long.
If you liked this content, you will love my Product Practice Newsletter. Working with me requires a financial commitment, but the newsletter is free, and anyone can subscribe: herbig.blog/productpractice