Product Prioritisation: How to improve it using the Fogg model
As a product manager, you are constantly faced with product prioritisation—the challenge of deciding what to build next. How do you prioritise the features and improvements that will deliver the most value to your users and your business? How do you balance the needs and expectations of different stakeholders and customers? How do you ensure that your product roadmap aligns with your vision and strategy? One framework that can help you answer these questions is the Fogg Behavioural Model (FBM). Developed by Dr. BJ Fogg, a behavioural scientist and director of the Stanford Persuasive Technology Lab, the FBM is a simple yet powerful model that explains how human behaviour is influenced by three factors: 1. Motivation 2. Ability 3. Triggers. How those FBM help Product Prioritisation? According to the FBM, for a behaviour to occur, a person must have sufficient motivation to perform it, sufficient ability to perform it, and a trigger to prompt them to perform it. If any of these factors are missing or insufficient, the behaviour will not happen. Motivation refers to the degree of desire or willingness to perform a behaviour. It can be influenced by various factors, such as pleasure or pain, hope or fear, social acceptance or rejection, etc. Motivation can vary depending on the context and the individual. Ability refers to the degree of ease or difficulty to perform a behaviour. It can be influenced by various factors, such as time, money, physical effort, mental effort, social deviance, non-routine, etc. Ability can also vary depending on the context and the individual. ALSO READ: Generating Better Ideas for Your Products — Lessons from Teresa Torres Triggers refer to the cues or signals that prompt a person to perform a behaviour. They can be external or internal. External triggers are stimuli that come from outside the person, such as notifications, buttons, reminders, etc. Internal triggers are stimuli that come from within the person, such as emotions, thoughts, memories, etc. The FBM can be represented by a formula: B = MAT. Behaviour = Motivation x Ability x Trigger. The formula implies that for a behaviour to occur, all three factors must be present and above a certain threshold. The higher the motivation and ability, the more likely the behaviour will happen when triggered. Conversely, the lower the motivation and ability, the less likely the behaviour will happen when triggered. How does this relate to product prioritisation? As a product manager, you want to design products that enable and encourage your users to perform certain behaviours that create value for them and for your business. For example, you may want your users to sign up for your service, use your features regularly, invite their friends to join your platform, provide feedback on your product, etc. To achieve these outcomes, you need to understand what motivates your users to perform these behaviours, what makes it easy or hard for them to perform these behaviours, and what triggers them to perform these behaviours. By applying the FBM to your product decisions, you can prioritise the features and improvements that will increase your users’ motivation and ability to perform the desired behaviours and provide them with effective triggers to prompt them to do so. For instance, at Insight7, we are constantly reaching out to users to understand what influences their behaviours and how they utilise our app. This helps us to understand how we can tweak our product to improve the ease of use, and eventually, the speed with which users accomplish their tasks using Insight7. Here are some use cases you can consider: – If you want your users to sign up for your service (behaviour), you need to motivate them by highlighting the benefits and value proposition of your service (motivation), make it easy for them to sign up by reducing friction and complexity in the registration process (ability), and provide them with clear and compelling calls-to-action on your landing page or in your marketing campaigns (trigger). – To get users utilising your features regularly (behaviour), you need to motivate them by showing them how your features help them achieve their goals and solve their problems (motivation), make it easy for them to use your features by providing intuitive and user-friendly interfaces (ability), and provide them with timely and relevant reminders or notifications that nudge them to use your features when they need them (trigger). – If you want your users to invite their friends to join your platform (behaviour), you need to motivate them by rewarding them with incentives or social recognition for inviting their friends (motivation), make it easy for them to invite their friends by integrating with their contacts or social networks (ability), and provide them with prompts or suggestions that encourage them to invite their friends at appropriate moments (trigger). – To get users to provide feedback on your product (behaviour), you need to motivate them by showing them how their feedback matters and how it will improve your product (motivation), make it easy for them to provide feedback by offering simple and convenient ways for them to share their opinions (ability), and provide them with requests or invitations that ask them for their feedback at optimal times (trigger). In summary, product prioritisation is not an easy task. Developing, testing and marketing new features is a gruelling, expensive series of tasks. However, using the right frameworks can improve the speed of decision making and ultimately help product teams make better decisions on what actions to prioritise.
Adopting A Continuous Discovery Process For Building Great Products
Continuous discovery process involves constantly learning about user needs and opportunities through various research activities such as user interviews and usability testing. The goal of continuous discovery is for product teams to have a tight feedback loop that enables the flow of insights to deliver on the best product experience for a user pain point, need or desire. The product discovery process The typical product discovery process starts with defining the domain or problem space (e.g e-commerce payments or ) you’re trying to solve a problem or set of problems in. The next step is to understand the user or customer segment you’re trying to solve these problems for. This helps the team focus the research on the right areas. You are essentially looking for opportunities to create value that users or businesses are willing to pay for. Once the problem space and user segments are defined, the team then moves on to researching the customer needs and opportunities by carrying out various activities such as user interviews, surveys, usability tests, customer feedback sessions and market research to have a better understanding of the most important problems to solve and the best solutions to them. The continuous discovery process There isn’t a perfect process for doing continuous product discovery and it varies across teams, companies and industries but one main benefit of a continuous product discovery process is that it allows for a more agile approach to product development. By continuously gathering customer feedback and incorporating it into the product, product teams are able to quickly pivot and make changes to improve the product and better meet the needs of your customers. This approach is especially useful in today’s fast-paced, technology-driven market which is constantly evolving meaning customer needs and preferences evolve quickly. How to run product discovery continuously The best teams are able to run product discovery in a continuous manner to build great products and continually improve them. These product teams continually search for new information about user needs, using research activities like weekly customer touch points and hypothesis testing, to uncover user and customer experience insights and user behaviour data. Tools for continuous product discovery It can be difficult to do continuous discovery without the right tools In order to implement a successful continuous product discovery process, it is important to have a dedicated team in place. This team should consist of individuals with a variety of skill sets, including product managers, designers, and developers. The team should also have access to tools and resources that will help them gather and analyse customer feedback, such as user testing software and market research tools. Once the team is in place, the continuous product discovery process can be broken down into a few key steps: Identify customer needs: The first step in the process is to identify the needs of your target customers. This can be done through market research, customer surveys, and other methods of gathering customer feedback. Generate ideas: Once you have a clear understanding of customer needs, the next step is to generate ideas for potential products or features. This can be done through brainstorming sessions, design thinking workshops, and other creative techniques. Test concepts: The next step is to test the viability of your ideas. This can be done through user testing, market validation, and other methods of gathering feedback from potential customers. Iterate and improve: Based on the feedback you receive, you can iterate on your ideas and make improvements to ensure that the product is as successful as possible. This may involve making changes to the product design, adding new features, or even scrapping an idea altogether and starting fresh. By following these steps and continuously gathering customer feedback, you can develop a product that truly meets the needs of your customers and stands a better chance of success in the market. A continuous product discovery process allows for flexibility and adaptability, which is essential in today’s fast-paced business environment. Benefits of continuous product discovery Product discovery is an essential part of the product development process. It is the process of identifying customer needs, validating ideas, and testing concepts to ensure that the product will be successful in the market. A continuous product discovery process is one that is ongoing and iterative, allowing for flexibility and constant improvement. Another advantage of a continuous product discovery process is that it can help reduce the risk of developing a product that fails in the market. By continuously testing and validating ideas, you can identify potential issues early on and make changes before investing too much time and resources into a concept that may not be successful. This can save your company time and money in the long run.
7 Product Discovery Books That Teach What You Should Know
[vc_row type=”in_container” full_screen_row_position=”middle” column_margin=”default” column_direction=”default” column_direction_tablet=”default” column_direction_phone=”default” scene_position=”center” text_color=”dark” text_align=”left” row_border_radius=”none” row_border_radius_applies=”bg” overflow=”visible” overlay_strength=”0.3″ gradient_direction=”left_to_right” shape_divider_position=”bottom” bg_image_animation=”none”][vc_column column_padding=”no-extra-padding” column_padding_tablet=”inherit” column_padding_phone=”inherit” column_padding_position=”all” column_element_direction_desktop=”default” column_element_spacing=”default” desktop_text_alignment=”default” tablet_text_alignment=”default” phone_text_alignment=”default” background_color_opacity=”1″ background_hover_color_opacity=”1″ column_backdrop_filter=”none” column_shadow=”none” column_border_radius=”none” column_link_target=”_self” column_position=”default” gradient_direction=”left_to_right” overlay_strength=”0.3″ width=”1/1″ tablet_width_inherit=”default” animation_type=”default” bg_image_animation=”none” border_type=”simple” column_border_width=”none” column_border_style=”solid”][vc_column_text] In product development, so many of our ideas will not work. With product discovery, product teams can limit waste and rebuilds by up to 50%. It is much cheaper to build the right thing the first time by having a clear understanding of the problem and co-creating the solution with customers. Product teams are able to go faster and build greater products by following the right product discovery processes. Here are seven product discovery books that teach you everything you need to know. 7 Must-Read Product Discovery Books 1. Inspired: How to Create Tech Products Customers Love by Marty Cagan In this book, Marty Cagan provides a framework for creating successful products, which involves understanding the customer, identifying a market opportunity, and building a great team to execute on the opportunity. Cagan’s book is essential reading for anyone in the technology industry who wants to create products that customers will love. This book is an essential read for every product manager. Some people call it the product management bible. 2. Continuous Discovery Habits by Teresa Torres In her book, Teresa Torres shares a framework for developing habits that lead to building successful products. According to Torres, there are four main habits that every product development team should adopt: focus on the customer, embrace change, fail fast, and learn constantly. By following these habits, teams can continuously improve their product development process and better meet the needs of their customers. She offers as structured and sustainable approach to continuous discovery and opportunity mapping. She also points out that it is essential to interview your customers regularly (ideally weekly). 3. The Mom Test: How to Talk to Customers & Learn If Your Business Is a Good Idea When Everyone Is Lying to You by Rob Fitzpatrick In this book, Rob Fitzpatrick shares a set of simple rules for crafting good customer interview questions that even a person’s mom can’t lie to them about. The measure of usefulness of an early customer conversation is whether it provides concrete facts about their lives and world views. These facts, in turn, allow us to improve our business. Eventually you do need to mention what you’re building and take people’s money for it. However, the big mistake is almost always to mention your idea too soon rather than too late. The book advises that you shouldn’t ask your mom whether your business is a good idea because she loves you and will lie to you. It is the ultimate guide for interviewing your customers. 4. Jobs to be Done: Theory to Practice by Tony Ulwick In his book, “Jobs to be Done: Theory to Practice,” Tony Ulwick lays out a framework for understanding customer behavior and designing products that meet customer needs. Ulwick’s framework is based on the idea that customers don’t just purchase products, they “hire” them to do a job. By understanding the “job” that a customer is trying to get done, companies can design products that are more likely to be successful. In summary, he shares in the book that people don’t buy products. They “hire” them to do jobs. He also provides insights on how to define and prioritize customer needs. 5. Sprint: How to solve complex problems and test ideas in just 5 days by Jake Knapp This book by Jake Knapp that lays out a framework for solving complex problems and testing ideas in just five days. The sprint process includes four main steps: brainstorming, sketching, deciding, and prototyping. By following this process, companies can quickly and efficiently come up with solutions to complex problems. The book describes a specific Product Discovery technique invented in Google. It is recommended that the ideas in it are compared with Teressa Torres’s approach, particularly interviewing your customers before ideating. You may want to combine those approaches. 6. The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback by Dan Olsen This book by Dan Olsen that lays out a framework for designing and developing successful products. Olsen’s framework is based on the Lean Startup methodology, and it emphasises the importance of validated learning, customer feedback, and continual iteration. By following Olsen’s framework, companies can increase their chances of developing successful products. Key insights from the book include the complete Lean Product Process – discovering and creating products while minimising waste and rework. The author also shares insights around Business Model, Value Proposition, MVP, Product-Market Fit, Product Discovery, and more. 7. Testing Business Ideas: A Field Guide for Rapid Experimentation by Alex Osterwalder In this book, Alex Osterwalder provides a framework for testing business ideas quickly and efficiently. Osterwalder’s framework is based on the Lean Startup methodology, and it emphasizes the importance of validated learning, customer feedback, and continual iteration. By following Osterwalder’s framework, companies can increase their chances of developing successful products. Some lessons from the book include, starting from an idea, then using the design loop to improve it, using discovery experiments to examine your assumptions and information about dozens of tools and techniques anyone can easily apply. Conclusion: What Next After Reading These Product Discovery Books? As you go through these books, you will gain a deeper understanding on how to perform effective product discovery, but your next question might be, what next? [/vc_column_text][/vc_column][/vc_row]
