Book summary: “ Inspired: How To Create Tech Products Customers Love” — Part 4
Note: If you are truly looking for some valuable resources to learn and understand about modern product management, then I strongly recommend you to read this book twice. Buy link — here.
Part 4 : The Right Process
The right process is more of a combination of techniques, mindset, and culture.
- Most of us are working on solving the hard problems and it usually ends taking some fairly complex system to power these solutions.
Two significant challenges to tackle:
- Finding in detail what the customer solutions should have been. Additionally, make sure we come up with a single solution that works for many customers and not a series of specials.
- Ensure we deliver a robust and scalable implementation that our customers can depend on for consistently reliable value.
So, We need to learn fast and release with confidence.
Many teams get into a lot of grief with the concept of the minimum viable product (MVP) because on hand we are getting the customers to feedback early in the game and learning. On the other hand, When we do get out there fast, people feel like this — so-called product is an embarrassment to the brand and the company. how could we possibly consider launching this?
Purpose of product discovery is to address these critical risks:
- Will the customer buy this, or choose to use it? (Value risk)
- Can the user figure out how to use it? (Usability risk)
- Can we build it? (Feasibility risk)
- Does this solution work for our business? (Business viability risk)
Principles of Product discovery:
- Customers don’t know what’s possible, and with technology products, none of us know what we want until we see it.
- Establish a compelling value.
- Concoct a very good user experience.
- Functionality, design, and technology are inherently intertwined.
- We expect that many of our ideas won’t work and the ones that do will require several iterations. We need to be open to solve underlying problems in different ways.
- We must validate our idea on our real customers and users.
- The goal of product discovery is to validate our ideas fastest and cheapest way possible.
- Validate the feasibility during the discovery, not after that.
- Validate the business viability during the discovery, not after that.
- It’s all about shared learning.
Discovery techniques overview:
- Discovery framing techniques — framing techniques help us to quickly identify the underlying issues that must be tackled during product discovery.
- Discovery Planning techniques — Useful throughout the product discovery effort and help with identifying the bigger challenges and planning how you’ll attack this work.
- Discovery Ideation Techniques — Ideation techniques are designed to provide the product team with a wealth of promising solutions aimed at the problems we’re focused on now.
- Discovery Prototyping Techniques — Our go-to tool for product discovery is typically a prototype.
- Discovery Testing Techniques — Product discovery is mostly about quickly trying out an idea. We are essentially trying to separate the good ideas from the bad. Here we are defining a good idea as one that solves the underlying problem in a way that customers will buy, they can figure out how to use, we have the time and skills and technology on the team to build, and that works for the various aspects of our business.
- Testing feasibility — These techniques are designed for the engineers to address areas where they identify concerns. It could be the technology that the team is not familiar with, performance challenges or some third-party components need to be evaluated.
- Testing usability — These techniques are designed for the product designers to address areas where they have identified concerns.
- Testing value — Most of our time in product discovery is spent validating value or working to increase the perceived value. If it’s a new product, we need to ensure that customers will buy it, at the price we need to charge, and that they’ll switch from whatever they’re using today. If it’s an existing product, and we are improving that product (such as with a new feature or a new design), where the customer has already bought the product, we need to ensure the customers will choose to use the new feature or new design.
- Testing Business Viability — These techniques are about validating the type of risks. Sadly, it’s not enough to create a product or solution that our customers love, that is usable, and that our engineers can deliver. The product also must work for business. This means we can afford the cost of building and provisioning the products and costs to market and sell the product.
Discovery Framing Techniques:
How to frame our discovery work to ensure the alignment and to identify key risks.
Two goals here:
- Ensure that the team is all on the same page in terms of clarity of the purpose and alignment. Focus on objective and specific problems we are trying to solve.
- To identify the big risks that will need to be tackled during the discovery work. Few examples
- Financial risk — Can we afford to build this solution?
- Business development risk — Does this solution work for our partners
- Marketing risk — Is this solution consistent with our brand?
- Sales risk — Is this solution something our sales staff is equipped to sell?
- Legal risk — Is this something we can do from a legal or compliance perspective?
- Ethical risk — Is this solution something we should do?
The technique (Author’s pick)
- An opportunity assessment is designed for the vast majority of product work which ranges from simple optimization to a feature to a medium-sized project.
- Customer letters are designed for larger projects or initiatives that often have multiple goals and a more complicated desired outcome. (example — redesign)
- Startup Canvas for those times you’re creating an entirely new product line or a new business.
Opportunity assessment technique:
- Idea is to answer four key questions about the discovery work you are about to undertake:
- What business objective is this work intended to address (Objective)
- How will you know if you’ve succeeded? (Key results)
- What problem will this solve for our customers? (Customer problem)
- What type of customer are we focused on? (Target market)
Customer letter technique:
- Working backward process — Where you start the effort with the pretend press release. It’s so tempting to the product teams to immediately slip into an enumeration of all the features they plan to build. This will help the team focus on the outcomes, not the output.
- It’s a terrific evangelism technique — if people don’t see the value after reading the press release then the PM has more work to do, perhaps should reconsider the effort.
- Customer letter — The idea is that rather than communicate the benefits in a press release format, you describe them in the format of a customer letter written from the hypothetical perspective of one of your product’s well-defined user or customer persona.
- This includes how the customer describes how it has changed or improved his/her life, and imagined congratulatory responses from the CEO to the product team explaining how this has helped the business.
Startup Canvas Techniques:
- You’re not being asked to improve the existing product, you’re being asked to invent an entirely new product.
- Startup canvas, it’s close cousins to business model canvas and lean canvas are intended to be lightweight tools to call out these risks early and encourage the team to tackle them upfront.
- Startup canvas helps to quickly highlight the key assumptions and major risks facing a startup or a significant new product in an existing business. The idea is to tackle the big risks first.
Discovery Planning techniques:
Story map Technique:
- They are essentially framing and planning techniques, but they are just as useful for ideation.
- Also used a design technique when building prototypes and works great for communication to the team and the stakeholders.
- Many teams consider a high fidelity user prototype and a story map as their go-to techniques.
Customer Discovery program technique
The power of reference customers
- What is a reference customer? — A real customer (not friends or family) who is running your product in production, who has paid real money for the product, and most importantly, who is willing to tell others how much they love your product.
- “We are discovering and developing a set of reference customers in parallel with discovering and developing the actual product”
- This technique takes substantial effort and primarily on the part of PM. But this is the single best leading indicator of future product success.
- Four main variations of this technique for four different situations:
- Building products for businesses.
2. Building platform products (ex — Public API)
3. Building customer enabling tools used by the employee of your company
4. Building products for customers
Single target market and recruiting the prospective reference customers:
- We are looking to develop six reference customers in our specific target market or segment, so the idea is to find six similar customers.
- If you end up targeting two or three customers in two or three different markets, this program will not give you the focus you want and need.
- Example -First develop six references for the financial service industry, then six from the manufacturing industry OR six from the US and the UK.
- The ideology behind this technique is to focus on developing this set of reference customers for a specific target market which then makes it was easy for sales to go after those specific types of customers.
Product Ideation techniques
- Customer Interview: One of the most powerful and important skills for any product manager and very often the source or inspiration for any breakthrough product ideas,
Try to understand -
- Are your customers who you think they are?
- Do they have the problems you think they have?
- How does the customer solve this problem today?
- What would be required for them to switch?
Here are some tips for getting the most out of these learning opportunities:
- Frequency: Establish a regular cadence of customer interviews. This is not a once in a while thingy. 2- 3 hours per week, every week.
- Purpose: You’re just trying to understand and learn quickly. This mindset is critical and needs to be sincere.
- Recruiting users and customers: Be sure to talk primarily to people in your intended target market. You’re looking for about an hour of their time.
- Location: It’s always amazing to see customers in their native habitat. There’s so much to learn just by observing their environment. But it’s also fine to meet them somewhere convenient or have them come to your office.
- Preparation: Be clear beforehand what problem it is you think they have, and think about how you’ll either confirm or contradict that.
- Who should attend: My favorite is to bring three people to these interviews: the product manager, the product designer, and one of the engineers from the team (we normally rotate among those that want to attend). Usually, the designer drives (because they’ve usually been trained how to do this well), the product manager takes notes, and the developer observes.
- Interview: Work to keep things natural and informal, ask open-ended questions, and try to learn what they’re doing today (not so much what they wish they were doing, although that’s also interesting).
- Afterward: Debrief with your colleagues to see if you’ve all heard the same things and had the same learnings. If you made any promises to the customer during that session, be sure you keep them.
Concierge Test technique
A concierge test requires going out to the actual users and customers and asking them to show you how they work so that you can learn how to do their job, and so that you can work on providing them a much better solution.
Power of Customer misbehavior:
Historically, the two main approaches used by good teams to come up with product opportunities have been:
1. Try to assess the market opportunities and pick potentially lucrative areas where significant pain exists.
2. Look at what the technology or data enables — what’s just now possible — and match that up with the significant pain.
3. This third alternative is to allow and even encourage, our customers to use our products to solve problems other than what we planned for and officially support.
The two main types of hack days are directed and undirected.
- In an undirected hack day, people can explore whatever product ideas they like, so long as it’s at least loosely related to the mission of the company.
- In direct hack day, In a directed hack day, there is a customer problem (for example, something is really difficult to learn and use, or it takes too long to do) or business objective we’ve been assigned (for example, “Reduce the customer churn rate” or “Increase customer lifetime value”), and we ask people from the product teams to self-organize and work on any ideas they like that might address this objective.
Discovery prototyping techniques — To be continued.
Disclaimer: At many places, I’ve used the exact phrases from the book to capture the 100% nuances of the information.
If you enjoyed 👌 this story, please click the 👏 button and share it to help others find it! Feel free to leave a comment below ✋.
In the next blog, — let’s discuss more about the discovery protyping, discovery testing techniques and discovery sprint techniques. Stay tuned ❗️⭐️