Jake Burghardt’s Post

‼️ 𝑻𝑯𝑬 𝑷𝑶𝑾𝑬𝑹 𝑶𝑭 𝑴𝑨𝑹𝑲𝑬𝑻 𝑹𝑬𝑺𝑬𝑨𝑹𝑪𝑯 𝑰𝑵 𝑷𝑹𝑶𝑫𝑼𝑪𝑻 𝑫𝑬𝑽𝑬𝑳𝑶𝑷𝑴𝑬𝑵𝑻 ‼️ Nearly 30,000 new products are introduced each year, and 95% of them fail according to Clayton Christensen, a professor at Harvard Business School. Svafa Grönfeldt, faculty member for MIT Professional Education’s online program Designing High Impact Solutions with MITdesignX—offered in both English and Spanish—explains that “many innovations fail because they introduce products or other solutions without a real need for them. There’s no market for the solutions they’ve created.” The beautiful thing about Product development is that, it’s not just about having a great or super idea; it’s actually about ensuring it resonates with your market. That is why market research is so important in a new product development process. This stage helps product managers to critically evaluate customer needs, preferences and pain-points. Market research in a need product development process, therefore, is 𝒕𝒉𝒆 𝒈𝒂𝒕𝒉𝒆𝒓𝒊𝒏𝒈 𝒂𝒏𝒅 𝒂𝒏𝒂𝒍𝒚𝒛𝒊𝒏𝒈 𝒐𝒇 𝒊𝒏𝒇𝒐𝒓𝒎𝒂𝒕𝒊𝒐𝒏 𝒂𝒃𝒐𝒖𝒕 𝒕𝒉𝒆 𝒕𝒂𝒓𝒈𝒆𝒕 𝒎𝒂𝒓𝒌𝒆𝒕, 𝒄𝒖𝒔𝒕𝒐𝒎𝒆𝒓𝒔' 𝒏𝒆𝒆𝒅𝒔, 𝒑𝒓𝒆𝒇𝒆𝒓𝒆𝒏𝒄𝒆𝒔, 𝒂𝒏𝒅 𝒃𝒆𝒉𝒂𝒗𝒊𝒐𝒓𝒔 𝒕𝒐 𝒎𝒂𝒌𝒆 𝒊𝒏𝒇𝒐𝒓𝒎𝒆𝒅 𝒅𝒆𝒄𝒊𝒔𝒊𝒐𝒏𝒔 𝒂𝒃𝒐𝒖𝒕 𝒅𝒆𝒗𝒆𝒍𝒐𝒑𝒊𝒏𝒈 𝒂 𝒏𝒆𝒘 𝒑𝒓𝒐𝒅𝒖𝒄𝒕 𝒐𝒓 𝒊𝒎𝒑𝒓𝒐𝒗𝒊𝒏𝒈 𝒆𝒙𝒊𝒔𝒕𝒊𝒏𝒈 𝒐𝒏𝒆𝒔. 👉 Understanding Customer Needs and Preferences: This helps product managers to develop products that truly resonate with their target audience. Which includes conducting surveys, interviews, focus groups, and analyzing customer feedback from various sources such as social media, reviews, and direct interactions. 👉 Identifying Market Opportunities: When there’s a gap in the market or a particular trend, product managers use this opportunity to introduce new products that will address these concerns. 👉 Reducing Risks: Developing a new product involves a lot of investment and inherent risk, carrying out Market research helps to reduce these risks by providing data-driven insights into the viability of a product concept, the potential challenges, and the competitive landscape. 👉 Helps Product Design: Market Research helps the design team not to design a replica of a product already in the market and to inform every aspect of product design, from functionality and aesthetics to usability and sustainability. 👉 Product Success Evaluation: Market Research post product launch allows the team to track the success of the product and to identify areas for improvement. Conducting thorough market research is crucial for identifying opportunities, reducing risks, and ensuring the success of a product in the market. Can we share any product that we used to like but left it for something similar and better? Share below 👇 #productmanager #ufuomaokon #customersatisfaction #businessdeveloper #productdevelopment #marketresearch

Qualitative research might seem straightforward at first glance, but it’s much more complex than it seems. It’s certainly an invaluable tool for product teams, yet it requires careful attention to detail. Without precise execution, the insights gathered could potentially mislead product development. In collaboration with super-experienced researchers, we’ve developed a thorough guide that will enhance your approach to qualitative research. And honestly, I wish this guide had been around when I first started out in product! https://lnkd.in/eMR9NyfS

Unlocking the Power of Qualitative Research in Product Management: A Summary of The Insights from GoPractice, Inc GoPractice, Inc's comprehensive guide on "Qualitative Research in Product Management" delves into the intricate process of gathering insightful user information and testing hypotheses, essential for steering product development in the right direction; While acknowledging the inherent limitations of qualitative research—its inability to quantify or generalise findings to a larger audience. The guide emphasises its unparalleled value in uncovering the "how?" and "why?" behind user behaviours and preferences. It lays out a roadmap for conducting meaningful #qualitativeresearch, from setting clear objectives and designing research that aligns with business goals to conducting interviews and synthesising actionable insights. A crucial takeaway is the strategic application of qualitative research across all phases of #productdevelopment. Whether launching a new product, entering uncharted markets, or refining existing offerings, qualitative research provides the context needed to make informed decisions. However, it's equally important to know when NOT to conduct qualitative research - such as when it won't impact decision-making or when it's cheaper to implement and test immediately; highlighting the importance of resourcefulness in #productmanagement. Furthermore, it highlights common pitfalls such as interviewing the wrong audience or overlooking the synthesis stage, underscoring the necessity of a meticulous, goal-oriented approach. It encourages product managers to build a robust #researchprocess, integrate regular user interactions into the product development lifecycle, and create a culture that values user insights as a pivotal component of strategic planning. In essence, it is not just about conducting research; it's about cultivating a research-driven mindset that prioritises understanding users at a fundamental level. This is crucial in today's competitive landscape, where the ability to empathise with and respond to user needs can differentiate successful products from the rest. As #productmanagers and leaders seek to navigate the complexities of user-centered design and development, the insights from the publication serve as a guide towards a more informed, empathetic, and strategic approach to product management. For those interested by the potential of qualitative research to transform product development and decision-making, I highly recommend reading the full blog. #product #qualitativeresearch #productlifecycle

As a product manager, conducting effective research is crucial for understanding user needs, market trends, and competitor offerings. Here's a step-by-step approach to conducting research: 1. Define Research Goals: Start by clearly defining the objectives of your research. What specific questions do you want to answer? What insights are you hoping to gain? 2. Identify Research Methods: Choose the appropriate research methods based on your goals. Common methods include user interviews, surveys, usability testing, market analysis, competitor analysis, and data analytics. 3.Recruit Participants: If your research involves gathering insights from users, recruit participants who match your target audience criteria. Consider factors such as demographics, behavior, and usage patterns. 4.Conduct Interviews or Surveys: If conducting user interviews or surveys, prepare a set of open-ended questions to gather qualitative insights. Be sure to listen actively, probe for deeper understanding, and capture detailed feedback. 5.Analyze Data: Once you've collected data, analyze it to identify patterns, trends, and key insights. Look for common themes or pain points that can inform your product decisions. 6.Stay Updated on Market Trends: Keep abreast of industry trends, emerging technologies, and competitor offerings. Subscribe to relevant blogs, attend conferences, and follow thought leaders in the product management space. 7.Test Hypotheses: Use research to test hypotheses and validate assumptions about your product. This could involve conducting A/B tests, prototype testing, or usability testing to gather feedback and iterate on your product. 8.Iterate and Refine: Continuously iterate on your research process based on feedback and learnings. Stay agile and be willing to adjust your approach as needed to ensure that your product remains aligned with user needs and market trends. By following these steps and adopting a systematic approach to research, you can gather valuable insights that inform your product strategy and drive the success of your product. Dr. Aanu Gopald Africa Agility Foundation Moyinoluwa Adetola Mercy Holumidey

Research always seems to be chasing the product roadmap. This reactive approach leaves researchers scrambling to validate decisions after they've been made rather than informing them from the start. It's like trying to give driving directions to someone who's already halfway to their destination—you might help them avoid a few wrong turns, but you've missed the chance to suggest a better route entirely. Product teams need continuous research insights, not just last-minute validation. When researchers are brought in early and often, they can identify opportunities, surface user needs, and help shape product strategy before key decisions get locked in. But, I realize that shifting from reactive to proactive research requires both organizational buy-in and a systematic approach to gathering user insights. Here are three ways to make that transition: 𝗕𝘂𝗶𝗹𝗱 (𝗮𝗻𝗱 𝘂𝘀𝗲) 𝗮 𝗥𝗲𝘀𝗲𝗮𝗿𝗰𝗵 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆 Create a central hub for storing and accessing research findings. This makes insights discoverable and helps prevent duplicate studies. 𝗘𝘀𝘁𝗮𝗯𝗹𝗶𝘀𝗵 𝗥𝗲𝗴𝘂𝗹𝗮𝗿 𝗧𝗼𝘂𝗰𝗵 𝗣𝗼𝗶𝗻𝘁𝘀 Schedule recurring touchpoints with product teams to understand upcoming decisions and align research priorities accordingly. 𝗣𝗿𝗼𝗮𝗰𝘁𝗶𝘃𝗲𝗹𝘆 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗙𝗼𝘂𝗻𝗱𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗥𝗲𝘀𝗲𝗮𝗿𝗰𝗵 Dedicate time to understanding user behaviors and needs independent of specific feature requests. This creates a knowledge base from which to draw when new opportunities arise. ===== 👋 I'm Ari...a criminal investigator turned customer investigator. 🤝 Need help getting insights fast? DM me. Also, if you liked this post: 👍 Like it 🛟 Save it ♻ Repost it 🔔 Follow me 💌 Subscribe (link in carousel)

There are two distinct types of user research: generative and evaluative. Both play crucial roles in the product development lifecycle, serving different purposes and conducted at different stages of the process. Let's explore the nuances of each and understand their unique roles. Generative Research (aka “Exploratory” or “Discovery” Research): a research method that “generates” a deeper understanding of your user’s motivations, pain points, and behaviors. Often conducted through interviews or observations, the goal of this research is to help you identify a problem statement and gather evidence in the form of big insights so you can move forward confidently. Yes to: questioning, observing, learning, exploring No to: solutioning; gathering specific requirements Evaluative Research: A research method that comes in handy when you already have a solution hypothesis or solution. Use this method of research to test your solution hypothesis or assess a current solution to ensure ease of use and that it is functioning as intended. Yes to: testing concept ideas, hypotheses, or usability; assessing competitor product No to: broad research questions that don’t assess the hypothesis, unless you are getting feedback you didn’t expect The key is to use the right type of research at the right time. Generative research avoids the build trap by ensuring the right problems are solved before development. Evaluative research keeps us honest and grounded, ensuring our execution aligns with user needs. In conclusion, both generative and evaluative research are essential tools in a product manager's toolkit. They complement each other, providing a comprehensive understanding of users and guiding the creation of successful, user-centric products. Start with generative research to explore unknowns and lean on evaluative research to refine solutions for optimal outcomes. Work with your user researchers to learn how to do both well. What strategies do you use to ensure you're incorporating both generative and evaluative research effectively in your product development process? I’d love to hear your insights. Learn more in our Product Institute courses: https://lnkd.in/gKrpruPW #ProductMetrics #CustomerLifecycle #UserEngagement #BusinessSuccess #ProductInstitute #ProductOperations

This explanation of types of user research is worth a bookmark (and Melissa’s course is likely worth a purchase if you want to learn more. I haven’t taken it but would love to) #productmanagement #productresearch #userresearch

This is a concise breakdown of the 2 main types of user research and when to use them. Also a gentle reminder from me that if there is no user researcher on your team, you could hire a freelancer to help you learn to do both well. 😉

When I was new to B2B SaaS design, I landed a project that terrified me. "Design a SaaS for clinical researchers," they said. But there was one big problem. I knew nothing about clinical research. This project excited me. It covered everything I love - from logo and brand identity to the full product experience. I couldn't miss this opportunity. So I dove in headfirst. For weeks, I immersed myself in the world of clinical research. I pored over medical journals. Watched countless lectures. Read books about it. Listened to every relevant podcast I could find. Learning. Applying. Iterating. All under a looming deadline. I focused on what mattered the most. Making researchers' lives easier. Simplifying complex processes. Streamlining data management. Enhancing collaboration. The day of the client presentation arrived. I held my breath. Their eyes lit up, and they liked my work. In that moment, I realized: Great solutions aren't just about technical skills. They're about truly understanding the people you're helping. Now, before I start any project, I dive deep into the world of my clients and users. It's not always comfortable. But it's crucial and always worth it. Because when you deeply understand the problem, the solution often reveals itself. How do you navigate projects outside your expertise? What's your learning strategy? I'd love to know.

What does a tree have to do with your product’s development? The primary research question from one of our Courageous Insights tech clients this week is: What problems, if any, could a new product solve for this particular market? Admittedly, I love early value propositions and exploratory research projects like this—those where we move away from stimulus-response testing and start digging deep into unmet needs, pain points, wants, needs, fears, and existing suboptimal solutions to really define the problem. As a researcher, I take great delight in: -Examining usage and seeing how something may or may not be utilized in the way it was intended or designed. You always see the most surprising things when you look at real-life, in-the-wild usage. -Connecting with consumers about their wants, needs, and fears in their day-to-day lives due to less-than-optimal solutions. I grab a cup of tea and delve into the frustration they may feel about that VLOOKUP error or the denial from their IT department regarding trying out a new project management tool. -Observing how people interact with and experience technology in the most unexpected ways. There’s something quite fascinating about being an observer or interested party in their daily experiences. -Bonus points in this project include examining some unaided beliefs people have about certain tech manufacturers’ brands. Existing brand impressions can be significant barriers to adoption later, so it’s good to identify these from the start. Whenever we are exploring the seed for a new product’s development, I like to start with the roots of the classic "product tree" framework. 🌳 The Product Tree is a metaphor comparing your product to a tree, where the trunk represents the core value proposition, the branches represent the main functionalities, and the leaves represent the specific features, benefits, and user stories. But most importantly, the roots 🌱 represent the problem you are trying to solve in the market. Your roots need to be strong and deep because they symbolize the problem that has yet to be addressed. Every great product is born from a deep and significant problem. This project is about defining the problem or roots with clarity—mapping a potential root system to truly understand pain points and unmet needs. It’s crucial to assess how painful the problem is, which may include evaluating current tech satisfaction, costs, and difficulties. Many clients don’t spend enough time, money, or energy on this phase of product development. I’m grateful this client was able to gain these insights and use them to make informed and impactful decisions. We’ll see where it leads. 😉 #courageousinsights #producttree #marketresearch #valueproposition