|
You know you need to improve product discovery in your teams. You know what good looks like, some of your leaders as well, but somehow teams are not spending enough time doing proper product discovery. Instead they work off requests from customers, from stakeholders, from the one year kind of promised roadmap. And all that work is important and keeps them busy, so you struggle to push for different ways of working on top of everything else and keep deferring it to 'soon, after xyzzy is delivered' or 'next quarter'. But that voice inside you is correct: without proper product discovery you are leaving impact on the table and it's time to find a quick and simple way to not hold off product discovery for longer. (and if you need a reminder for WHY you should focus on product discovery first: Why product discovery is the first thing to change ) Your next step is to conduct a product discovery surveyWhat you now need is the lazy (and smart) managers tool to find out how to get product discovery going as effectively as possible: a survey! A well-designed survey takes a few minutes to answer and gives you data on where your teams actually are, not where you feel they are. It helps you figure out the fastest unlock to get product discovery going and gives you confidence on where to go next, no more "maybe I expect too much too soon." And equally important: it helps the team reflect and assess where they are so they can start addressing their current state, because they will be taking the actions. Don't look at the survey as a scientific endeavor, see it as a tool for you and your teams to move from thinking to doing. What makes a good survey:
Step 1: Create a survey (or use mine!)Here is the product discovery maturity survey that I use with leadership teams to get them to action on product discovery. For a version with all response alternatives download the pdf free here A PDF with all questions together with answers is downloadable here About You
1. Your role:
2. Time at your company
How Your Team Currently Works
3. How often does your team (PM + Designer + Engineer) talk directly with customers or users as part of deciding what to build?
4. Roughly what percentage of what your team builds comes from:Customer/stakeholder requests, Ideas from your own research and exploration, Maintenance and technical improvements
5. When deciding whether to move forward with an idea (regardless of where it came from), how often does your team test assumptions with customers/users BEFORE engineers start coding?
6. How often do PM, Designer, and Engineer work together to decide WHAT to build (not just HOW to build it)?
7. When your team is deciding what to build, which of these do you typically consider?
Requests
How comfortable are you pushing back on ideas or requests for reasons like: doesn't solve a real customer problem, not technically viable, won't scale well, etc.?
9. When we receive an idea or feature request, we explore what problem it's trying to solve before deciding how to proceed
10. How confident do you feel about your team's current approach to validating ideas before building them?
Reflection Questions
11. What's your biggest challenge when it comes to deciding what to build next?
12. What's ONE thing you hope to improve about your team's discovery practice?
A PDF with all questions together with answers is downloadable here Step 1: Insert the questions into the form tool your company prefersPick the form tool that works best for your setup and what you are comfortable with. Focus on something that lets you group and play with the data over being pretty.
The faster you can get this up, the faster you'll have data. Step 2: Send out the survey to your "product trios"Send it to the people who are accountable for product discovery in your organisation. This is likely a mix of these roles: PMs, Designers, Data leads, Ems, staff engineers/tech leads. Make it clear when you will need the results. Then schedule a follow-up reminder to get more respondents since people are busy and will forget. Keep it anonymous to give space for honesty. If they think their name is attached, you'll get what they think you want to hear. Since it's anonymous, you might end up with less responses, emphasize it takes short time to fill out and that you will actually use the data together with them. This way you put some motivation and accountability back on the leaders. Step 3: Summarize the dataHow many responses you need depends on the size of the group. Aim for at least 70%. And if you risk not having this response rate by the deadline, remind in a clear and nice way (like Mary Poppins: kind but firm) Look for:
Put it all in a slide deck and share with your teamsPackage your findings into a slide deck. Keep it visual and scannable, busy people won't read walls of text. Share the summarized data with the respondents as a pre-read. Give them time to digest it before any discussion. Have them reflect in their teams on what the data means for them specifically. This is where ownership starts to shift from you to them. If you want a more detailed structure for how to reflect on the data, you can [download the free PDF here / link to resource]. What this gets youYou now have a way to move from bottleneck to facilitator. Data gives you the confidence to lead change without guessing. You know where teams are, what they need, and how fast you can realistically move. And teams can own their growth when they see where they stand. That's when change stops being something you push and starts being something they pull. What's your experience with assessing product discovery maturity? Have you tried surveys or other methods? |
I email every Thurday with the latest insights from my work and clients about product, business and tech. Sign up below! I will never spam or sell your info. Ever. Unsubscribe anytime.
You’ve outgrown your current team setup but find it hard to figure out a better one that fits your reality. When setting a new org structure it’s easy to pinpoint a few areas that are cleanly scoped and valuable, but then there is the rest. You still need to maintain the technology you built, there are domains that might be less clear on what value they bring and who their customers are, but you know they’re needed. And you need to figure out where to put your leaders (you probably lack some...
Hand on your heart, are you doing as much product discovery as you should? If there's a gap, you're not alone. I've worked with teams skipping product discovery because they "don't need it" or "don't have time for it" since their backlog is already full of things the business asked for, the users, or tech debt. I've worked with PMs who want to do discovery "right" and therefor never get started, and I've seen seasoned PMs using the same tools and methods who could use a little inspo to...
Yesterday I had a conversation with an R&D leader at a sales-led company making the shift to product-led. They were a profitable retail software company who had grown through the efforts of their sales department. The sales reps built strong relationships with potential clients and closed the deals by promising the new features the clients asked for. As a result their product org was operating from the backseat, mainly project managing the agreed tasks. Only a handful of people in the R&D org...