Product Discovery is by far the most critical area for a Product Manager.

But, it is largely misunderstood. Teams waste time and energy delivering ideas that fail to drive the outcomes they expect.

Too often, teams spend months building features that fail to meet user needs or drive business impact. If you’ve ever launched something that barely got used, you already know why Product Discovery matters.

In this Product Discovery 101 guide, you’ll learn:

• What Product Discovery is

• Why Product Discovery is important

• The difference between Continuous and Initial Product Discovery

• How to apply Product Discovery: techniques, frameworks, and tools

• Pros and cons of Jira Product Discovery

• Where to find Product Discovery courses, templates, and resources

1. Why do We Need Product Discovery?

1.1 Managing risks

Let me tell you a secret: In product management, most ideas won’t work as expected. As Marty Cagan says in Inspired:

„The first truth is that at least half of your ideas are just not going to work”

Good teams assume at least three-quarters of their ideas won’t perform as they hope.

But why does it happen?

Product management is, at its heart, about managing risk. And for every product, 5 essential risks can materialize:

• Value Risk: Will this idea truly create value for customers?

• Usability Risk: Will users figure out how to use it?

• Viability Risk: Can our business support it?

• Feasibility Risk: Can we build it with our current technology?

• Ethical Risk: Should we build it at all? Are there ethical considerations?

Addressing these questions before you code helps avoid the costly trap of building the wrong thing.

1.2 Learning by delivering

Many teams adopt Agile frameworks to deliver software iteratively and adapt quickly.

For example, in Scrum, we have a Sprint Review. During this workshop, we discuss the progress with the stakeholders and decide how to adapt:

But what will happen if we throw random ideas into the Product Backlog?

Some might work, but most won’t. This is "learning by delivering." Unfortunately, this approach results in waste and rework.

Some might say it’s not a problem, as the Sprint is often 1-2 weeks long.

But this will happen every Sprint. Every Sprint, the product team selects ideas, implements them, and delivers a production-ready increment to discover those were not good ideas.

And the best ideas might not even be on the list.

So, we’d like to understand:

• How can we come up with better ideas?

• How can we test those ideas before the implementation?

And the answer is Product Discovery.

2. What is Continuous Product Discovery?

Continuous Product Discovery is a special type of Product Discovery for an existing product. It’s all about regularly exploring opportunities and identifying and testing your assumptions.

Instead of a single, upfront research phase, you keep the discovery going in parallel with delivery.

2.1 Continuous Discovery and Continuous Delivery

You might have heard about Dual-Track Development or Dual-Track Agile. It simply means having two streams running in parallel:

• Continuous Discovery: Discover and validate what product to build.

• Continuous Delivery: Implement and deliver the validated product to the market

What's important here is that this is not a waterfall. Some team members talk to the customers, explore people's problems, brainstorm solutions, identify assumptions, and perform experiments. At the same time, the team implements and delivers validated ideas to the market.

By testing ideas early, you dramatically reduce waste and rework. Product Discovery results in a validated Product Backlog. In particular, high-risk assumptions are tested upfront.

2.2 The Product Trio

There is a common misconception. Some say that the Product Manager decides what to build, and Engineers and designers should focus on how to build it.

Have you heard that before?

It hurts my ears because Product Discovery is not a task for a single person. I deeply believe that instead of building those silos and stage gates, we should embrace a collaborative approach.

In Continuous Discovery Habits, Teresa Torres introduced the concept of a Product Trio: Product Manager, Product Designer, and Engineer working together. This will help you build a shared understanding and stay open to different perspectives.

In particular, I have repeatedly found that the best ideas often come from my engineers. They know what’s technically possible.

Tip: Please remember that the Product Trio is not a rigid framework. It’s the default recommendation that can expand and contract. For example, you might include a Product Marketing Manager or exclude a Product Designer for an API product.

2.3 Inside Continuous Product Discovery

Think of Continuous Product Discovery as a series of iterative cycles, often visualized with the Double Diamond model:

Tip: Critically, Product Discovery is not a linear process. For example, you can loop back at any time if an experiment fails or you need more research.

Here, we explore the problem space to understand and define opportunities (problems, needs, desires) that, when solved, will drive the desired outcomes.

The two stages of divergent and convergent thinking:

• Stage 1: Explore

  • Performing customer interviews (e.g., weekly)

  • Interviewing stakeholders

  • Learning from usage analytics (collecting and analyzing data on how users interact with a product or service, e.g., Pendo.io)

  • Exploring data analytics (analyzing large datasets to uncover trends, patterns, and relationships, e.g., Microsoft Power BI)

  • Leveraging other sources of insights in Product Discovery: surveys, market trends, SEO, and SEM reporting

• Stage 2: Define

  • Mapping opportunities (e.g., Opportunity Solution Tree by Teresa Torres)

  • Prioritizing opportunities (e.g., Opportunity Score by Dan Olsen, ICE score)

The Right Diamond

Here, we explore the solution space to identify the right ideas to build.

The two stages of divergent and convergent thinking:

• Stage 3: Ideate

  • Brainstorming solutions to identified opportunities

  • Formulating testable assumptions related to those ideas

• Stage 4: Test

  • Perform experiments to prove or disprove identified assumptions

Continuous Product Discovery Example

In this example, we started with the desired outcome of increasing customer engagement for a video streaming platform by 20%. The team decided to map their steps with the Opportunity Solution Tree.

Stage 1, Stage 2: Explore and Define

After interviewing customers, analyzing product analytics, and talking to support and customer success, the Product Trio identified opportunities and child opportunities related to the desired outcome, e.g.:

• I can’t find anything to watch,

• I can’t figure out how to search for a specific show).

Next, they prioritized opportunities that are important for the users, where their satisfaction with their ability to achieve a specific outcome was low.

Stage 3: Ideate

After prioritizing opportunities, everyone on the Product Trio brainstormed individually. The team members met to discuss their ideas.

They immediately rejected a few ideas for one of the opportunities (“I can’t figure out how to search for a specific show”). The two most promising ideas left were:

• Displaying a search box,

• Displaying recommended shows.

Stage 4: Test

The team used User Story Mapping to identify assumptions related to value, usability, and feasibility. They identified some as risky and planned experiments to test those assumptions.

For example, they created a user prototype in Figma to test whether users understand how a search box works. They gave selected users a task to accomplish, tracked every user's click, and assumed the assumption was correct if at least 70% of the users would complete their task on the first attempt.

The test was successful, so there was no need to consider alternative solutions or talk to the users again.

Previously, the Product Manager ensured with the stakeholders the the solution would also work for the business (she talked to CSM, Marketing, and Sales).

A few days later, the engineers selected this idea for implementation.

3. What is Initial Product Discovery?

Initial Product Discovery comes into play when creating a new product.

In this phase, you define your Product Vision, draft a Business Model, and identify the right market. You’re not worrying yet about continuous iteration.

You’re trying to figure out if there’s a market at all.

Initial Product Discovery follows a very similar workflow with different activities possible in each stage:

Again, there is no “Product Discovery Process,” but rather a series of iterative cycles.

4. Jira Product Discovery: Pros & Cons

If you work with Jira, you might have heard about Jira Product Discovery. It offers some handy features like a Now-Next-Later roadmap, which is a perfect choice for visualizing big-picture plans:

But JIRA Product Discovery misses the critical aspects of Continuous Product Discovery and encourages some bad practices:

• No built-in way to map opportunities

• No straightforward way to plan experiments

Some try to hack it, but I have a strong opinion: it’s not a Continuous Product Discovery tool. You will do much better creating the Opportunity Solution Tree in tools like Miro, Notion, or FigJam.

Recommended Books on Product Discovery

The two most important titles every product person should read:

• Inspired by Marty Cagan

• Continuous Discovery Habits by Teresa Torres

Final Thoughts

Product Discovery doesn’t have to be complicated. The key is to stay curious about your users, test ideas early, and collaborate with your team to build solutions people actually want.

Every product team loves a well-crafted persona: a neat profile that neatly summarizes who they’re designing for. But all too often, that persona is less “real user” and more “wishful thinking.” We scribble down demographic details—age, family status, job title—and voilà: our roadmap is set, our designs are approved, and our marketing copy writes itself. Yet these static snapshots can mask the messy, unpredictable realities of people’s lives. When those realities emerge, it can feel like the rug has been pulled out from underneath your roadmap.

📌 Case Study: The “Ideal” Indian Teacher Persona

A few years ago, I consulted in a major EdTech in India. Their target user was crystal clear on paper:

Name: “Priya”
Age: 35
Family: Married with two kids, ages 4 and 7
Job: Government school teacher in a Tier‑3 town
Lifestyle: Supportive husband and in‑laws help with childcare
Motivation: Eager to adopt new classroom tools

To anyone glancing at these bullet points, Priya seemed like a dream user: mature enough to understand pedagogy, curious enough to embrace innovation, and well‑supported enough to find the time. It felt like we had struck gold—or so we thought.

🔍 Uncovering the Reality: Primary Research Insights

When we finally sat down with real teachers, everything about our Priya persona began to unravel.

AssumptionRealityAge: Mid‑30sMost women teaching with kids aged 4 and 7 are actually in their late 20s—early marriage and early careers are common.Supportive Home LifeInstead of help, many teachers return home to a “second shift” of cooking, cleaning, and childcare—no in‑laws in sight.Job by ChoiceTeaching is often a necessity—a steady salary that fits within societal expectations, not a passion project.Tech CuriosityComplex tools threaten classroom authority. If students master a tool faster, the teacher’s role feels undermined.Leisurely Learning TimeThere are no 30‑minute coffee breaks. Any “learning” has to happen in stolen 5‑minute windows between classes and chores.

Key Takeaways

1. Misaligned Motivations: Teaching isn’t “fun.” It’s a job that fits cultural and financial needs.

2. Scarce Time & Energy: At best, a five‑minute gap to explore a new feature—never a half‑hour deep dive.

3. Authority Preservation: Tools must reinforce the teacher as the expert, not expose them to potential embarrassment.

💥 What It Broke

The original persona had shaped everything:

• ✍️ Copy assumed curiosity.

• 🧭 Onboarding assumed available time.

• 🔧 Feature complexity assumed confidence.

Once we saw the reality, we had to reframe everything:

• Simplify interfaces—no learning curve, no ambiguity.

• Design for low attention spans—5-minute windows, not 30-minute explorations.

• Reinforce teacher authority—tools had to feel like enhancements, not risks.

What we had built made sense for the imagined persona. But for the real one, it added stress.

🧭 The Real Lesson

Most teams don’t ignore users—they just rush to define them. And once a persona is blessed, it becomes gospel.

Here’s the blind spot:

⚠️ Teams guess their way into personas. Then build real products on imaginary users.

⚠️ They focus on surface traits—age, job title, family—without understanding what life actually feels like.

⚠️ And once a persona is socialized, it becomes sticky. Even when the truth emerges, changing course feels hard.

👉 A persona is not a user. It’s a hypothesis.

👉 A real persona includes constraints, context, and coping strategies.

👉 The job of the product team is to stay curious—especially after the first draft.

Wrapping It Up

It’s easy to fall in love with a persona that sounds good in a slide deck. But product decisions don’t happen in the abstract—they hit the ground in real people’s lives.

When you skip context, you don’t just miss nuance—you risk building entirely for the wrong person.

So treat personas as living documents. Pressure-test them. Revisit them often. Because the cost of getting them wrong shows up where it hurts most: in adoption, trust, and usability.

User interviews are a vital element in creating exceptional UI/UX design, particularly for B2B SaaS products. These interviews uncover the real needs, preferences, and pain points of users, allowing designers to craft intuitive, user-centered interfaces. Whether you’re a product manager, designer, or developer, understanding how to conduct effective user interviews is key to building products that solve real-world problems.

This comprehensive guide will walk you through the importance of user interviews, how to conduct them effectively, and how to turn insights into actionable strategies for improving your product design.

Why User Interviews Matter for B2B SaaS

1. Understanding the User’s Context

B2B users often have unique workflows, industry regulations, and technical requirements. User interviews provide deep insight into these nuances, ensuring your product aligns with their operational needs and business goals.

2. Identifying Pain Points and Opportunities

Interviews reveal the specific pain points users face, enabling designers to create features that directly address these challenges. Additionally, they help uncover opportunities for innovation that may not be evident through analytics or surveys.

3. Building Empathy for User-Centric Design

Hearing users describe their challenges, goals, and frustrations fosters empathy among your design team. This emotional connection leads to designs that are not just functional but also enjoyable to use.

When to Conduct User Interviews

Optimal Scenarios for User Interviews

• When the target audience or their needs are unclear.

• To understand the current user experience in detail.

• When release costs are rising, and mistakes could be costly.

• To uncover insights that analytics alone cannot explain.

• When the product is stuck in a local maximum (a point where further improvement seems unclear).

• To identify opportunities for profitability or innovation.

When to Avoid User Interviews

• To test solutions (use usability testing instead).

• If the same data can be obtained through analytics or surveys.

• If there is already sufficient data from prior research.

• When time or resources are severely limited.

• To conduct research purely for the sake of research.

At what phase of the project is it better to perform an interview?

The 8-Step Process to Conduct Effective User Interviews

Step 1: Defining Objectives and Scope

Start by defining the purpose of your research:

• What problem are you solving? For example, is user onboarding too complex, or are certain features underutilized?

• What information do you need? Are you seeking feedback on a feature, or insights into user frustrations and motivations?

• How will the data be used? Decide how the insights will impact product development, prioritization, or design strategies.
  
  For instance, if you’re developing a new feature, your goal might be to understand how users currently solve the problem this feature addresses and what challenges they face. Additionally, defining the context includes understanding the user's environment, their workflows, and any external factors that may influence their interaction with your product. This comprehensive understanding helps in framing the right questions and interpreting the responses effectively.

Pro Tip: A clear research objective ensures the interviews yield actionable and focused insights.

Step 2: Formulating Research Questions

The right questions are the backbone of a successful interview. Follow these guidelines:

• Start with broad questions to understand the user’s overall experience and context. For example, “Can you describe a typical day at work?” or “What tools do you use most frequently?”

• Focus on specific tasks and problems related to your product. Ask questions like, “How do you currently manage your workflow?” or “What challenges do you face when using [specific feature]?”

• Explore pain points. Identify areas where users experience frustration or inefficiency. Questions might include, “What is the most difficult part of your current process?” or “Have you encountered any issues with our product?”

• Uncover user needs and preferences: gain insights into what users value and what features they wish to see. Ask, “What features are most important to you in a tool like ours?” or “What would make your experience better?”

• Understand user behavior and motivation. Learn about the reasons behind user actions. Questions such as “Why do you choose to use our product over others?” or “What motivates you to complete a task in a certain way?” can be revealing.

Avoid yes/no or leading questions, as these can bias the responses.

Step 3. Creating a sample

Selecting the right participants is crucial for obtaining relevant insights. Here’s how to create a representative sample:

Identify your user segments

Consider the different types of users who interact with your product. This might include primary users, secondary users, and any stakeholders who influence the purchasing decision. Understanding these segments helps in creating a diverse sample that reflects the variety of experiences with your product.

Once again the word to Maxym: "Why should you segment your target audience?"

• To make sure you identified it correctly

• To make sure your positioning, product, and messaging correct

• To avoid creation of Frankenstein product (which may have "all cool stuff from the market" without an actual need)

Prepare the sample

• Make sure your sample is big enough (10-40 people, depending on the goals and product's specifics).

• Divide this group into subgroups (depending on the product's specifics).

• Make sure you've included people from different locations (genders, ages, etc, depending on the product specifics and research goals).

• Ensure your sample includes a variety of diversely represented users to get a comprehensive view of different perspectives. This includes considering factors such as job roles, experience levels, industries, and geographic locations. Diversity in your sample helps uncover a wider range of insights and ensures your findings are not biased towards a particular group.

• Create detailed user profiles or personas to guide your recruitment process. These profiles should outline the characteristics of your ideal interviewees, including their demographics, behaviors, needs, and pain points.

Step 4. Preparing a script

A well-prepared script ensures that your interviews are structured and focused. Here’s how to create an effective script:

• Start with a friendly introduction to build rapport. Explain the purpose of the interview, how the information will be used, and assure confidentiality. This helps in making the participant feel comfortable and willing to share openly.

• Begin with some general warm-up questions to ease the participant into the conversation. These can be about their background, role, or daily tasks. Warm-up questions help in setting the context and making the participant feel at ease.

• List your main research questions. These should be open-ended to encourage detailed responses. Organize them logically, moving from broader topics to more specific ones. For example, start with questions about overall workflow and then drill down into specific tasks related to your product.

• Prepare follow-up questions for each core question to probe deeper into the participant’s responses. These can help clarify details and uncover underlying motivations or frustrations.

• Use scenario-based questions to understand how users would react in specific situations. For instance, “What would you do if this feature was not available?” or “How would you solve this problem without our product?”

• Behavioral questions: ask about past behaviors to predict future actions. Questions like “Can you describe a time when you faced this issue?” or “What did you do to overcome this challenge?” provide insights into user behavior.

• End with some closing questions to wrap up the interview. These could include asking for any additional thoughts or feedback, and thanking the participant for their time.

• Keep your script flexible. Be ready to deviate from it if the conversation leads to unexpected but valuable insights. Flexibility allows for a more natural and engaging interview process.

A well-structured script not only ensures that you cover all necessary topics but also makes the interview process smoother and more productive.

Step 5. Scouting and recruiting participants

Finding the right participants can be challenging. Here are some strategies to scout and recruit:

• Start with your current user base. Reach out to them through email campaigns, in-app messages, or user community forums. Existing users are often more willing to participate as they are already engaged with your product.

• User panels: use user research platforms like UserTesting, Respondent, or UserInterviews. These platforms have large pools of potential participants and can help you find users who match your criteria.

• Leverage LinkedIn and other professional networks to find participants. Join relevant groups and forums where your target users are likely to be active.

• Attend industry conferences, webinars, and events. These are great places to network and recruit participants who are knowledgeable about your industry and product.

• Use social media platforms like X, Facebook, and Reddit to post recruitment messages. Target groups and communities related to your product’s domain.

• Offer incentives to encourage participation. These could be monetary rewards, gift cards, discounts on your product, or donations to a charity of their choice. Ensure the incentives are significant enough to attract participants without introducing bias.

• Implement a screening survey to filter potential participants. This survey can include questions about their role, experience, and familiarity with your product. Screening ensures that you select participants who are most relevant to your research goals.

• Clearly communicate the purpose of the interview, the time commitment required, and how the information will be used. Transparency builds trust and encourages participation.

Step 6. Conducting the Interview

During the interview, create a comfortable environment to encourage open and honest feedback. Here are some best practices:

• Build rapport. Start with some casual conversation to make the participant feel at ease. Building rapport helps in creating a relaxed atmosphere where the participant feels comfortable sharing their thoughts.

• Active listening. Pay close attention to the participant’s responses. Show that you are listening by nodding, maintaining eye contact, and providing verbal affirmations. Active listening encourages participants to share more and feel valued.

• Stay neutral. Avoid leading questions or expressing your own opinions. Staying neutral ensures that the participant’s responses are unbiased and authentic.

• Use open-ended questions. Ask open-ended questions to encourage detailed responses. For example, “Can you describe how you use this feature?” or “What challenges have you faced with our product?”

• Probe for details. Use follow-up questions to dig deeper into the participant’s responses. Ask for examples, reasons, and explanations to get a comprehensive understanding.

• Take notes. While recording the interview (with permission) is useful, taking notes can help highlight key points and follow-up questions. Notes also serve as a backup in case of recording issues.

• Manage time. Keep the interview within the agreed duration, but allow for some flexibility if the participant is sharing valuable insights.

• At the end of the interview, thank the participant for their time and insights. Let them know how their feedback will contribute to improving the product.

Some tips to keep in mind:

Before the interview

• The interview should include not more than 3 people (including the person who is being interviewed)

• Make sure you don't have too many interviews at once (it is better to have no more than 2-3 per day)

• Make sure you book a time for the interview (and prepared some "presents" if they are any for the respondents)

• Make sure your recording is working (audio/video)

At the beginning

• Explain who you are and why are doing this interview (without explaining what is the goal)

• One person performs the interview, another one makes notes and helps to stick to the script

During the interview

• Ask one question at a time (no multiple questions)

• Use your responder language (words that they used)

• Use "why" (as a main question to understand the reason for motivations, problems etc of the responder)

• Do not talk about the future (to avoid definitions)

• Do not push your opinions (not "Why don't you like ...?", but "How is your opinion about ...?")

• Do not help or ask "closed" questions that could be answered as "yes/no" (not "Do you do that to...?, but "Why do you do that?)

• Do not shape experience (not "In case we do that, would you spend more time on the platform?", but "Describe your ideal platform")

• Do not use professional language (in case it is not a part of the product)

7. Analyzing the data

How to analyze interview data after conducting it? Here are the tips:

• Transcribe the interviews to have a written record of the conversations. Transcriptions make it easier to review and analyze the data in detail.

• Identify common themes and patterns in the responses. Group similar responses together to find recurring ideas and insights. This process helps in organizing the data and identifying key trends.

• Use affinity diagrams to organize and visualize the data by grouping related insights together. Affinity mapping helps in identifying relationships between different themes and insights.

• Look for key insights that address your research questions and uncover new opportunities for product improvement. These insights should be actionable and directly relevant to your product development goals.

• Where possible, quantify the qualitative data to provide a sense of scale and impact. For example, if several participants mention a specific pain point, note the frequency to highlight its significance.

Thorough analysis ensures that you derive meaningful and actionable insights from your user interviews.

Tips from Maxym:

• Discuss the interview with your partner (if any) to avoid misunderstanding or bias

• Reread/Relisten interview and highlight the main points

• Share and discuss all findings with colleagues

• Clasterize insights (same experience, patterns, answers)

💡 Note: Analysis is not a search for solutions, it is about the search for answers on research questions

8. Creating artifacts and sharing with the team

The final step is to create artifacts that effectively communicate your findings to the team. These might include:

• User personas. Detailed profiles representing different user types based on the insights gathered from the interviews. Personas help the team understand the diverse needs and behaviors of your user base.

• Journey maps. Visual representations of the user’s experience with your product, highlighting key touchpoints, pain points, and opportunities for improvement. Journey maps provide a holistic view of the user experience.

• Insight reports. Summarized findings with actionable recommendations. These reports should be concise, focused, and easy to understand, providing clear guidance for the product development team.

• Presentations. Create presentations to share the insights with stakeholders. Use visuals like charts, graphs, and quotes to make the data engaging and easy to comprehend.

• Workshops. Conduct workshops with your team to collaboratively review the findings and brainstorm solutions. Workshops foster collaboration and ensure everyone is aligned on the insights and next steps.

• Documentation. Maintain detailed documentation of the interview process, findings, and recommendations. Documentation serves as a reference for future research and ensures that insights are preserved and accessible.

Share these artifacts with your team through presentations, reports, or collaborative tools to ensure everyone is aligned and can leverage the insights in their work. Effective communication of your findings ensures that the valuable insights gathered from user interviews are utilized to drive product improvements and create a better user experience.

Applying Insights to UI/UX Design

• Prioritizing features and improvements. Use the insights from user interviews to prioritize features and improvements. Focus on addressing the most critical pain points first. Create a roadmap that outlines the planned changes and their expected impact on the user experience.

• Designing with empathy. Empathy-driven design involves putting yourself in the user's shoes. Use the personas and insights to guide your design choices. Ensure that the interface is intuitive, the workflows are seamless, and the features align with the user's needs and preferences.

• Iterative testing and feedback. User interviews should be part of an iterative design process. After implementing changes, conduct usability tests to gather feedback on the new designs. Use this feedback to make further refinements, ensuring that the product continuously evolves to meet user needs.

HealthStream Case

HealthStream is an app catering to healthcare enterprises. It creates reports about the employees. When they came to Eleken, they needed some redesign. The users' workflow was suboptimal: a single report didn't contain all the necessary information, so users had to generate a couple of different reports and then manually copy-paste data from one to another. To solve this issue, Healthstream team assumed that fully customized reports are what their users need. 

Turns out, they were wrong.

User interviews Eleken conducted allowed to conclude that customers don't need such highly customized reports. All they wanted was a standard report with just a little customization. That was a starting point for the redesign that was actually successful. 

Measuring the Impact

• User feedback and satisfaction. After implementing the changes, the company conducted follow-up interviews and surveys to gather user feedback. The results showed a significant increase in user satisfaction, with many users highlighting the improved usability and customization options.

• Metrics and KPIs. Key performance indicators (KPIs) such as user retention, task completion time, and feature adoption rates were monitored. The metrics indicated a positive impact, with increased user engagement and efficiency.

Best Practices for Conducting User Interviews

• Preparation is key. Thorough preparation ensures that you cover all relevant topics and make the most of each interview. Plan your questions, select your participants carefully, and create a comfortable environment for the interview.

• Be an active listener. Active listening involves not just hearing but understanding the user’s perspective. Show empathy, ask follow-up questions, and pay attention to non-verbal cues.

• Stay neutral. Avoid leading questions or expressing opinions that might influence the participant’s responses. Your goal is to understand their perspective, not to validate your assumptions.

• Document everything. Accurate documentation is crucial for analyzing the insights. Record the interviews, take detailed notes, and organize the data systematically.

• Iterate and refine. User interviews are not a one-time activity. Incorporate them into an iterative design process, continually gathering feedback and making improvements.

Limitations of User Interviews

While user interviews are invaluable for gathering insights, NNG points out that they come with certain limitations. One significant issue is poor or faulty recollection; users might struggle to remember specific details about their experiences, leading to incomplete or inaccurate data. Additionally, crucial details may be missed, either because users do not consider them important or simply forget to mention them. Social-desirability bias also poses a challenge, as participants may alter their responses to align with what they perceive as socially acceptable or favorable, rather than providing their true opinions. The skills of the interviewer play a critical role as well; an inexperienced or unskilled interviewer might fail to ask the right questions, misinterpret responses, or inadvertently lead the participant, all of which can skew the results. These limitations highlight the importance of using a combination of research methods to obtain a comprehensive understanding of user needs and behaviors.

Final Thoughts

When done correctly, user interviews can give you invaluable user insights that may help you shape the product in a way that ensures its features are exactly what users need. 

Your product discovery process is a mess, and your information architecture (IA) is to blame. There, I said it. The harsh truth is that almost 8 in 10 software projects (or 78%) grow much bigger than planned, often leading to failure. This happens due to poor initial planning, lack of clear communication between teams, and misalignment between stakeholder expectations and user needs.

But before you panic, take a deep breath. This article isn't just about pointing out the problem — it's about arming you with the tools to fix it. Drawing from our UI/UX design team's years of experience, I'll guide you through the world of information architecture. By the end, you'll know exactly how to design a clear IA UI in four practical steps, with real-life examples to ground your understanding.

What is information architecture

Information architecture (IA) definition refers to how information (content and functionality) is organized, structured, and presented in a product or application. When done right, it's like having a master blueprint for your digital space. IA helps you:

• Plan your work on product’s design or on integrating new features seamlessly.

IA helps you visualize the entire product structure before diving into designing screens themselves. This foresight allows you to spot potential conflicts or redundancies early, understand which design elements would fit better in this or that situation, and roughly estimate how much time will be needed for your work. It all saves time and resources during development.

• Gain a clear understanding of your existing product structure.

Having a high overview of the entire product acts as a diagnostic tool. It reveals hidden complexities, redundant features, or underutilized sections that might be dragging down user experience.

• Decide how best to organize content and create navigation.

IA forces you to think from the user's perspective, helping you group related information logically. This results in intuitive navigation that guides users naturally through your product, reducing friction and improving overall experience.

• Ensure all team members and stakeholders are aligned and moving in the same direction.

A well-defined IA serves as a shared vision for the product. It helps prevent miscommunication between designers, developers, and stakeholders, ensuring everyone understands the product's structure and goals. With a clear plan on hands, it becomes much easier to explain some new ideas for different departments. 

• Schematically displays the difference between various elements of the application.

IA visually represents the relationships between different parts of your product. This clear differentiation helps in prioritizing features and understanding how changes in one area might impact others.

The problem with designing an effective information architecture is that many resources on the internet are either too theoretical without practical guidance, or too basic, only showing sitemaps UX without explaining their real-world use. The approach I’m going to present to you will combine both theoretically easy-to-understand information and practical application of it. 

So, now that you understand the information architecture meaning, what should be your starting point for building it?

Step 1: OOUX

Information architecture is based on the principles of Object-Oriented UX (OOUX). It's a method of designing digital products by focusing on the core objects or "things" that users interact with, rather than just the actions they perform.

What does this mean? Let's take a project management app as an example.

Theoretical info

• If you were thinking out the structure of your future app using the traditional approach, you might start by listing actions like "track time," "send invoice", "manage clients", and so on. This can lead to a fragmented user experience with separate sections for each action.

• With the OOUX approach, you'd start by identifying core objects: Projects, Clients, Tasks, Invoices, and only then think what properties these objects have and what actions they can perform. 

Focusing on objects first in OOUX brings more benefits because:

1. It mirrors how users naturally think about and interact with the world. Freelancers think, "I'm working on a project for a client," not "I'm performing a series of administrative actions."

2. It creates a more stable foundation for your product that can easily adapt to new features or changes. If you later want to add "expense tracking" or "contract management," these fit naturally under the "Project" or "Client" objects without major restructuring.

3. It helps prevent feature bloat by keeping the focus on core elements. All project-related information (tasks, time tracked, invoices, etc.) stays together, creating a more intuitive and integrated user journey.

Planning your app using the OOUX approach may take different forms, like a table made in a spreadsheet, or a bunch of sticky notes.

No matter how it looks, with OOUX you divide your entire interface into

• Objects – the main "things" users interact with in your digital product. Think of them as nouns. For a project management app, these gonna be projects, tasks, clients, and so on.

• Attributes – characteristics or properties that describe an object. For a project object, attributes might include name, client, description, and status.

• Actions, sometimes also referred to as call to action (CTA) – define what users can do with the objects. They're like verbs - for a project object, actions could include "create," "delete," "view", and “edit”.

Object-oriented design can get complex, especially when defining actions for different roles in an app. For example, in an app like Uber, you'd need to figure out actions for passengers, drivers, support staff, the system itself, and admins.

However, when designing information architecture, you don't need to be that detailed. Instead, you can focus on the admin role, as admins usually have access to all actions. This approach helps you form the overall structure of your application more easily.

Practical use

To begin the IA design process, at this step, you should do three things:

1. Define main objects and their relationships (establish how these objects connect to each other),

2. Determine object attributes (list the essential characteristics for each object)

3. Outline user actions (specify what users can do with each object).

So, we get back to our project management app for freelancers. To identify key elements, ask yourself “What does a freelancer need to work with?” Typically, a freelancer needs:

• Clients

• Projects

• Tasks

• Invoices

• Proposals

• Contracts

These form the core elements of our app's structure, which often become the main pages or sections of our product. Let’s write them down (I used Figjam for this purpose, but you can use any other convenient tool, such as Figma, Lucidchart, or Miro).

Next, consider each object's attributes (properties). For example, a Project object might have:

• Name

• Status (In Progress, Completed, On Hold)

• Description

• Client ID

• Budget

• Start Date

• Due Date

• Invoice ID

While objects typically become main pages, attributes represent the information displayed on each page.

Finally, list the actions a freelancer can perform on a Project. To make sure you cover everything, it’s helpful to organize them into three groups:

• CRUD (Create, Read, Update, Delete/Archive).

These are the basic things you can do with most stuff in the app. Like making a new project, looking at project details, changing project info, or getting rid of a project. For important data, such as financial apps, we often put archive instead of delete.

• List Actions (view all, sort, filter).

These are for when you have lots of one thing, like many projects or clients. This includes seeing all items, filtering them, or putting them in order. For example, looking at all your clients or sorting tasks by when they're due.

• Other cool stuff.

These are special actions that don't fit in the other groups Some examples are share and export.

By the end of this step, you'll have three lists:

1. Key objects

2. Attributes for each object

3. Actions users can perform on objects

For your convenience, differentiate these three groups with colors.

Step 2: user stories

In this step, we'll connect our objects, attributes, and actions together to build the app's logical structure. To do this, we'll need to form user stories.

Theoretical info

If objects, attributes, and actions are building blocks than user stories is what we build from them. And here's a more formal way to explain the term:

User stories are short, simple descriptions of a feature told from the perspective of the person who wants the new capability, usually a user or customer of the system. They typically follow a simple template:

As a [type of user], I want [an action] so that [a benefit/a value].

For example, a user story like "As a freelancer, I want to quickly access my current projects so that I can update their status" might inform the decision to place a “Current Projects” section prominently in the IA.

This way, by creating user stories, we will be able to 

• Keep the focus on user needs and goals, ensuring the IA serves actual user requirements.

• Prioritize features and content, which informs the hierarchy and structure of our IA. 

• Ensure clear, concise descriptions of functionality, which can guide how information is organized and presented.

Now, let’s see how creating user stories works in practice.

Practical use

In the first step, we made a list of the main components of our app's structure. In the second step, it's time to combine them together and start building the IA scheme.

To keep it simple, think of writing user stories as defining the main functions for the admin role, who has access to all actions.

So, if we get back to our example of a user story "As a freelancer, I want to quickly access my projects so that I can update their status", we can single out

• Object “Projects”

• Action “Update”

• Attribute “Status”

Linking them together would result in something like this:

Here are several more examples of user stories you could come up with for a project management app.

• As a freelancer, I want to create a new project so that I can organize my work for a client.

• As a freelancer, I want to set a project deadline so that I can manage my time effectively.

• As a freelancer, I want to add tasks so that I can break down my work into manageable steps.

• As a freelancer, I want to generate an invoice from a project so that I can bill my clients easily.

• As a freelancer, I want to attach files to a project so that I can keep all related documents in one place.

Still, writing user stories for every case can be time-consuming. Instead, try this simpler approach:

1. Line up key objects and think of them as the main pages your future app will have.

2. Based on actions, think out main app functions and match them to each object 

Start by looking at each object, like Projects, Clients, or Tasks. For each one, think about what users can do with it. Remember the three types of actions we talked about earlier: basic stuff like creating and deleting, list actions like viewing all and sorting, and special features like sharing data.

For example, since we'll have multiple projects, apart from the obvious function “Create new project”, we should apply List actions to the Project object:

• View all projects

• Sort projects

• Filter projects

Going through this process for each object helps you see clearly what every part of your app needs to do. It's a simple way to make sure you're not missing any important functions. 

3. Create user stories for the admin role and group objects, attributes, and actions.

With your objects and actions laid out, creating user stories and building the Information Architecture becomes easier. Present each user story schematically by arranging objects, actions, and attributes in a logical order and establishing appropriate connections between them.

But before I illustrate the complete IA map now, let's move to Step 3. This step is also part of building user stories but requires detailed discussion, so I wanted to address it separately.

Step 3: modals

Consider this user story:

“As a freelancer, I want to quickly view and edit information about a specific project, so that I can manage all aspects of a project in a focused, detailed environment."

To provide a positive user experience for this scenario, our project management app should have a separate window or page for each specific project. This needs to be represented in our Information Architecture UX.

This is where modals become useful.

Theoretical info

When we talk about IA in UI/UX design, a modal refers to a specific type of user interface element that temporarily disables the main content, forcing the user to interact with the modal or close it. 

In IA, modals can take the form of:

• A new page

• A separate flow screen

• A modal window (pop-up or dialog box)

Using modals in IA allows designers to:

1. Focus on the solution without getting attached to specific concepts or structures

2. Present information or interactions that don't fit naturally within the main navigation

3. Keep the main IA clean while allowing for necessary additional interactions

This approach helps maintain focus on the overall structure. Still, as I already mentioned, incorporating modals into our IA is a part of our previous step – user stories. Together with objects, attributes, and actions, modals serve as building blocks for user flow.

Practical use

So, let’s get back to where we stopped at the previous step. We have clearly defined key objects and main functionality of the app.

Modals are typically based on actions. Let's examine each action to determine if it requires a modal:

• "View all projects": Requires a separate modal for each specific project.

• "Sort" and "Filter" projects: Don't require new pages or pop-up windows.

• "Create a project": Needs a new page or a separate window (depending on the amount of information) for users to enter all necessary information.

This analysis allows us to enhance our IA map with appropriate modals.

Each modal will have its own set of actions. Referring back to user stories, here are the actions that can be available on a Project page:

• View project details

• Edit project

• Delete/Archive project

• Mark project as done

• Export project

We now link the attributes defined in the OOUX step to modals and their relevant actions. They will represent the content on the modals “Project page” and “Create new project”.

For example:

• Users can view and edit attributes like "Project status," "Project description," "Client name," and "Invoice ID."

• Actions such as Delete/Archive or Mark as Completed apply to the entire project, not individual attributes.

The last thing you have to do at this point is to visually differentiate objects, attributes, actions, and modals in a scheme with different colors.

Step 4: Relationships

Along this text, we mainly focused on the Projects object, detailing its actions, attributes, and modals and formed the structure of this specific flow. However, beyond the connections within each object, we also need to consider how different objects interact with each other. Defining these relationships is crucial for creating smooth app navigation.

Practical use

Our IA map shows that a Project page contains information like Invoice ID, Client ID, and Task ID. This indicates that users can view project-specific tasks, associated clients, and related invoices from a single project page

‍When we look at the IA map we have so far, we can see that Project page contains information like Invoice ID, Client ID, and Task ID. This indicates that on this page, users can view project-specific tasks, associated clients, and related invoices.

We can define key relationships such as:

• “Creating a Project leads to Adding Tasks, which leads to Generating an Invoice”

• “Clients are linked to Projects, but can exist independently”.

To visualize these relationships, you can use lines or arrows to connect related objects in your IA diagram.

This way, we illustrate how app navigation works. Users can find the Client ID by viewing project details or by going to the Clients page and selecting a specific client. This information is accessible from different pages and is interconnected.

This step completes your IA map, giving a comprehensive view of your app's structure, functionality, and object relationships. It also allows for non-linear navigation, ensuring your product’s UX adheres to one of the 10 usability heuristics: User Control and Freedom.

Summing up: a quick action plan

Congratulations! We've come a long way in creating our IA map covering both theoretical concepts and practical applications. Now, to ensure you clearly understand what you need to do, here's a concise step-by-step plan to guide you through the process.

1. Identify Core Objects with OOUX

• Define main objects: Determine the core elements users will interact with. They are likely to be the main pages of your future app.

• Determine bbject attributes: List key characteristics for each object. For example, a Project might have attributes like Name, Status, Description, Client ID, Budget, Start Date, Due Date, and Invoice ID.

• Outline user actions: Identify actions users can perform on each object. For example, actions for a Project could include Create, Read, Update, Delete/Archive, View all, Sort, Filter, Share, and Export.

2. Develop User Stories

• Write user stories: Create short, simple descriptions of features from the user's perspective. Use the format: "As a [type of user], I want [an action] so that [a benefit/a value]."

• Connect each user story to the relevant object, action, and attribute.

3. Incorporate Modals

• Identify actions requiring modals: Determine which actions need a separate modal or page.

• Create modals for complex actions: Define the actions available within each modal.

• Ensure you use different colors for objects, actions, modals, and attributes.

4. Define Relationships and Complete IA Map

• Map object relationships: Identify how different objects interact and link together. 

• Visualize connections: Use lines or arrows in your IA diagram to show how objects are interconnected.

By building a clear IA at your product discovery stage, you'll be able to transform the uncertain question of “What are we building?” into the confident assertion “This is exactly what our users need.”

Remember, a well-planned IA isn't just a blueprint — it's the backbone of your entire user experience. It can mean the difference between a product that merely functions and one that truly excels in the market.

If there’s one thing I’ve learned as a Product Manager, it’s that frameworks are indispensable. They guide our decisions, keep our teams on track, and ensure we’re focusing on the right things at the right time.

As you grow in your career, you’ll start collecting these frameworks like trading cards. They’re invaluable weapons in your arsenal, helping you tackle prioritization, pricing strategies, customer data analysis, and more.

But here’s the thing – the number of frameworks out there is staggering. Some overlap, others do the same thing in slightly different ways, and if you try to keep track of them all, it can feel overwhelming.

If you’ve been juggling a million frameworks and your brain feels like it’s running out of storage, you’re in good company. I’ve been there too.

This list isn’t about overloading you with more. It’s about cutting through the noise and focusing on the 16 most essential Product Management frameworks that I personally use and trust.

Each of these frameworks has earned its place in my toolkit – and if you’re just building yours, this is a great place to start.

Using an Opportunity Solution Tree encourages a systematic approach to product discovery. Instead of jumping straight to solutions, teams spend time actually exploring the problem space, ensuring they address real user needs. Breaking the process into steps reduces wasted effort on misaligned initiatives. Everything is focused on outcomes, not outputs, and every solution is tied to a validated opportunity.

The Ultimate List of Product Management Frameworks

Let’s jump straight in. This is a list of 16 essential Product Management frameworks that I believe every PM should know. This isn’t an exhaustive list – that would take forever. If you know a framework that’s working wonders for you and it’s not here, please share it! I’d love to know.

To keep things organized, I’ve broken the frameworks down by category. You can skip to the ones that fit what you need right now:

• Prioritization Frameworks

• Product Discovery Frameworks

• Product Development Frameworks

• Team Management Frameworks

• Customer Experience Frameworks

Product Management Frameworks for Prioritization

When it comes to Product Management, prioritization is key. Most frameworks revolve around prioritizing tasks, features, or ideas because deciding what to work on next is half the battle.

Here are the core prioritization frameworks that I believe are essential for any PM’s toolkit:

1. RICE Scoring

Not all features are created equal. Some drive impact, while others drain resources. RICE scoring is a simple but powerful way to objectively prioritize initiatives.

How It Works:

You score each feature (or idea) across four dimensions:

• Reach – How many users will this affect?

• Impact – How significantly will it improve their experience?

• Confidence – How sure are we about the estimates above?

• Effort – How much work is required to implement this?

 Oh, would you look at that, the first letters of each word spell R.I.C.E, who would have thought? From here, you can then work out your RICE score by plugging it into the pretty straightforward formula: 

This score makes it easy to compare ideas and see which ones move the needle without excessive effort.

2. Weighted Impact Scoring

Weighted impact scoring is similar to RICE but allows for more flexibility. The key difference? You can assign different weights to each factor based on what’s most important to your business.

How to Apply Weighted Scoring:

1. Identify Criteria – Define the key factors influencing success (e.g., market demand, cost, technical feasibility, customer impact).

2. Assign Weights – Distribute weight based on importance (total = 100%) For instance, market demand might carry 40% weight, while cost might have 20%..

3. Score Ideas – Rate each idea from 1 to 10. A higher score indicates a better alignment with the criteria you’ve created.

4. Calculate Total – Multiply each idea’s score by its corresponding weight, then add the results to generate a total weighted score.

5. Rank ideas: Use the total scores to rank options. The highest-scoring ideas are prioritized for implementation while low-scoring ones can be deprioritized or excluded.

Weighted scoring makes prioritization reflect business goals by emphasizing what matters most to your team. By following these steps, you’ll get something like this: 

In this example, it’s clear that Product Idea 2 is the best to work on first and will provide the biggest impact

3. Kano Model

Sometimes, user satisfaction drives success more than effort or reach. The Kano Model uses customer feedback to prioritize features based on their potential to delight users.

How It Works:

• Survey Questions:

  1. How would you feel if we added this feature?

  2. How would you feel if it was missing?

• Users can respond by ticking one of five options that range from “I like it” to “I dislike it”. From these answers, you can then categorize your ideas or existing features based on what users like and dislike, helping you know what to drop and what to focus your efforts on in the future. Through this survey, you’ll be able to categorize your features or ideas into 5 sections: 

  1. Basic: Must-haves that users expect.

  2. Performance: Features that increase satisfaction the more they’re improved.

  3. Delighters: Unexpected features that delight users.

  4. Indifferent: Features users don’t care about.

  5. Dissatisfiers: Features that frustrate users if present or missing.

4. MoSCoW Prioritization

If you’re struggling to work out which features you should have in your product or need to know which ideas on your roadmap or backlog are worth sticking with, the MoSCoW Prioritization framework can help you.

When using this framework, you rank your ideas based on them being a… 

• M – Must Have: Non-negotiable essentials for project success.

• S – Should Have: Important but not critical; can be postponed if necessary.

• C – Could Have: Nice-to-have features that add value but are not priorities.

• W – Won’t Have: Explicitly excluded from the current scope but may be revisited later.

MoSCoW works well for roadmap planning and aligning stakeholders.

Product Management Frameworks for Product Discovery

Discovery is a core part of the Product Management lifecycle. PMs need to stay curious, constantly learning about their audience, product, and market.

Here are my favorite frameworks for structured discovery:

5. Double Diamond

The Double Diamond framework takes teams from rough ideas to fully developed solutions. It’s visual, easy to follow, and ensures you define the problem before jumping into solutions.

It visually represents the process with two diamonds: the first focuses on defining the problem, while the second centers on designing the solution.

The framework has four key stages: 

• Discover – involves exploring the problem space through research and gathering insights. Teams cast a wide net to uncover user needs and pain points.

• Define – the insights are analyzed to pinpoint the core problem, narrowing the focus to define a clear, actionable problem statement.

• Develop – ideate and prototype potential solutions. This is a collaborative process, encouraging creativity and exploration of multiple ideas.

• Deliver – Finalize and launch.

6. ICE Scoring

Need something quick and easy? ICE scoring evaluates ideas based on:

• Impact – Value the solution adds.

• Confidence – How certain you are.

• Ease – How easy it is to implement

To work out your ICE score, you first score each factor between 1-10, and you then multiply them together to get your final ICE score. The higher, the better.

The simplicity of ICE Scoring makes it an ideal framework for quickly comparing a wide range of ideas. It encourages objective decision-making by breaking down initiatives into measurable components, reducing biases that may crop up from gut feelings or organizational politics. 

7. Opportunity Solution Tree

Developed by Teresa Torres, this framework maps out:

• Outcome – The overarching goal or desired result. For example, “Increase user retention by 20%.”

• Opportunities – User needs, pain points, or problems that could help achieve the outcome. These are identified through user research.

• Solutions – Potential ways to address the opportunities. Teams brainstorm and validate ideas here.

It ensures teams focus on outcomes over outputs.

Using an Opportunity Solution Tree encourages a systematic approach to product discovery. Instead of jumping straight to solutions, teams spend time actually exploring the problem space, ensuring they address real user needs. Breaking the process into steps reduces wasted effort on misaligned initiatives. Everything is focused on outcomes, not outputs, and every solution is tied to a validated opportunity.

Product Management Frameworks for Product Development

Sometimes, the hardest part of Product Management is the actual execution – taking plans and turning them into reality. Building and implementing a product can feel overwhelming, especially when the stakes are high.

The good news? There are frameworks designed to streamline this process, ensuring your team stays on track and your product gets delivered efficiently.

Here are some of the best frameworks for Product Development that I’ve personally found invaluable:

8. Kanban Framework

Kanban is a visual workflow management framework that enables teams to manage work in progress and optimize flow. It’s like having a shared digital planner that keeps everyone aligned.

At its core, Kanban revolves around tracking tasks on a Kanban Board. The board typically consists of three columns representing different stages of the workflow:

• To Do

• In Progress

• Done

Tasks are represented as cards that move from one column to the next as they progress. This approach brings transparency to the process, allowing everyone to see what’s being worked on, who is responsible, and where potential bottlenecks may arise.

Why Kanban Works:

• Limits Work in Progress (WIP): By capping the number of tasks in each stage, teams avoid taking on too much at once.

• Continuous Improvement: Teams regularly review the board and adjust to optimize flow and reduce inefficiencies.

• Flexibility: Kanban doesn’t require overhauling existing processes. It layers over current workflows and enhances them.

For teams looking to improve delivery times and reduce waste, Kanban is a cornerstone of Agile practices.

9. GIST Planning

Created by Itamar Gilad, GIST Planning simplifies long-term strategic planning for Agile teams. It's perfect for balancing high-level vision with short-term execution.

GIST stands for:

• Goals – The high-level objectives your team is working toward (e.g., improve user retention).

• Ideas – Potential projects or initiatives that might help achieve these goals.

• Step-Projects – Small, actionable projects derived from the prioritized ideas.

• Tasks – Specific actions needed to complete each step-project.

Why GIST Works:

GIST breaks large goals into smaller, more manageable pieces – think of it as cutting a chocolate bar into bite-sized squares instead of eating it whole.

• Avoids Overcommitment: By focusing on smaller, iterative projects, teams stay flexible and adaptable.

• Encourages Progress: Teams consistently move forward by tackling tasks incrementally.

• Alignment with Business Objectives: Every task is linked directly to a higher-level goal.

GIST is ideal for fast-moving teams that need clarity without the rigidity of traditional planning methods.

10. V2MOM

Originally developed by Salesforce, the V2MOM Framework is a planning and alignment tool that ensures everyone in the organization is working toward the same overarching goals.

V2MOM stands for:

• Vision – The ultimate goal or direction.

• Values – The principles guiding decision-making and defining success.

• Methods – The strategies and actions necessary to achieve the vision.

• Obstacles – Challenges that may arise and need to be addressed.

• Measures – The metrics used to track progress and success.

Why V2MOM Works:

• Clarity and Alignment: Everyone knows what the team is working on and why it matters.

• Cross-Team Focus: Prevents misalignment across departments and reinforces shared goals.

• Transparency: V2MOM documents are often shared organization-wide, ensuring all teams stay aligned.

In large organizations, V2MOM plays a crucial role in fostering collaboration and maintaining strategic focus.

Product Management Frameworks for Team Management

A Product Manager’s success often hinges on how well they manage cross-functional teams. Without the right structure, teams can quickly descend into chaos, causing blockers, miscommunication, and inefficiencies.

These frameworks help clarify roles and ensure smooth collaboration:

11. DACI Framework

DACI is a decision-making and accountability framework that defines who is responsible for what. It’s especially useful for cross-functional teams working on product development, strategy, or large initiatives.

DACI outlines four roles:

• Driver – Leads the decision-making process and coordinates discussions.

• Approver – Has the final say and ensures alignment with broader goals.

• Contributors – Provide input and recommendations but don’t make the final decision.

• Informed – Need to stay updated but don’t influence the decision directly.

Why DACI Works:

• Clear Accountability: Everyone knows their role in the decision-making process.

• Avoids Overlaps: Prevents multiple people from taking charge or stepping on each other’s toes.

• Streamlines Processes: Ensures that decisions are made quickly and efficiently.

DACI is particularly beneficial for breaking down silos and empowering teams to make decisions confidently.

12. RACI Matrix

While DACI focuses on decisions, RACI focuses on execution. The RACI Matrix is designed to ensure that all tasks are completed efficiently, with clearly defined responsibilities.

RACI stands for:

• Responsible – The person doing the actual work.

• Accountable – The individual who ensures the work gets done and approves the final outcome.

• Consulted – Subject-matter experts who provide input or guidance.

• Informed – Those who need to stay in the loop but don’t directly contribute.

Why RACI Works:

• Eliminates Ambiguity: Everyone knows their role in executing a task.

• Prevents Bottlenecks: Avoids situations where work stalls because responsibility is unclear.

• Improves Communication: Ensures the right people are kept informed at every stage.

Quick Tip: While DACI handles big-picture decisions, RACI is your go-to for daily task management.

13. Product Trios

The Product Trio model brings together three core roles during product development:

• Product Manager – Focuses on product strategy and market fit.

• Engineer – Provides technical expertise and ensures feasibility.

• Designer – Focuses on user experience and design.

By collaborating from the start, Product Trios ensure products are viable, feasible, and desirable – the holy grail of product development.

By creating a Product Trio, teams break away from the silos that traditionally isolate these roles, ensuring that everyone involved has visibility into the product development process at all stages. This integrated approach leads to better alignment, faster decision-making, and a more efficient product development cycle.

Product Management Frameworks for Customer Experience

At the end of the day, every product update, feature rollout, and enhancement aims to improve the customer experience (CX). Satisfied users become loyal advocates, and frameworks that help Product Managers focus on user needs are crucial to building products that stand out.

Here are frameworks designed to enhance customer experience and craft a strong value proposition:

14. Value Proposition Canvas

The Value Proposition Canvas is a powerful tool for aligning product offerings with customer needs. Developed by Strategyzer, it’s a visual framework that helps teams deeply understand their customers and design products that solve the right problems.

The Canvas Consists of Two Key Sections:

1. Customer Profile:

   • Jobs – Tasks the customer is trying to complete (functional, social, emotional).

   • Pains – Challenges, risks, or frustrations the customer faces.

   • Gains – Desired outcomes or benefits the customer hopes to achieve.

2. Value Map:

   • Products and Services – How the product helps the customer get their job done.

   • Pain Relievers – Ways the product eases specific frustrations.

   • Gain Creators – Features or aspects of the product that deliver positive outcomes.

Why It Works:

The Value Proposition Canvas ensures that everything your product offers directly addresses the customer’s needs, pains, and desires. It also highlights areas where value may be missing, allowing teams to refine features and enhance the user experience.

15. AARRR (Pirate Metrics)

AARRR, also known as Pirate Metrics, breaks down the customer journey into five critical stages. This framework, developed by Dave McClure, focuses on tracking user behavior from the moment they discover your product to becoming loyal, paying customers.

The Five Stages of AARRR:

1. Acquisition – How users find and discover your product.

2. Activation – The user’s first meaningful experience (the “aha!” moment).

3. Retention – How many users return and continue to use your product.

4. Referral – How many users recommend your product to others.

5. Revenue – How effectively your product generates income.

Why It Works:

• AARRR tracks key metrics across the entire lifecycle of a user, enabling teams to identify gaps and optimize the funnel.

• Pinpoints Weaknesses: If acquisition is high but retention is low, it signals issues with the product’s value or onboarding process.

Pro Tip: Focus on retention and activation. Even the best marketing efforts won’t matter if users don’t stick around.

16. User Story Mapping

User Story Mapping is a visual technique that puts the user at the center of product development. Popularized by Jeff Patton, this framework organizes user stories (features or tasks) into a structure that reflects the customer journey.

How It Works:

• Start with Activities: Outline high-level activities that users perform (e.g., sign-up, purchase, etc.).

• Break It Down: Beneath each activity, break it into smaller user stories representing steps or interactions.

• Prioritize: Arrange stories vertically based on importance. The most critical tasks go at the top.

This map provides a holistic view of the user experience and ensures that core features are built first, followed by less critical enhancements.

Why It Works:

• Aligns Development with Real User Needs: Helps teams avoid building unnecessary features.

• Visualizes Gaps in the User Journey: By mapping each step, teams can identify missing features or pain points.

• Prioritization is Easy: Teams can instantly see what matters most to users and focus efforts there.

Setting the Foundations

And that’s a wrap – 16 of the most valuable and trusted Product Management frameworks.

These frameworks aren’t just theories; they’re practical tools that I (and many PMs) have used to prioritize better, discover user needs, develop efficiently, manage teams, and enhance customer experience.

If you’re just starting out, focus on mastering a handful of these frameworks – RICE, Kanban, and User Story Mapping are great starting points. As you grow, you’ll naturally expand your toolkit and tailor frameworks to fit your team’s needs.

Final Thought:

Curiosity is one of the greatest assets of a Product Manager.
Keep exploring new frameworks, stay open to adapting them, and continuously refine your process. Product Management is never static – the best PMs evolve with the needs of their teams and users.

If you have a favorite framework I didn’t cover, I’d love to hear about it. Reach out, and let’s chat!

Instagram, the photo-sharing app that transformed how we connect, has become a cornerstone of the digital age. What started as a simple app in 2010 has grown into one of the world’s most influential social media platforms. But Instagram’s rise hasn’t been without its hurdles. This blog takes you through Instagram’s journey – the early challenges, market expansions, fierce competition, and continuous innovation.

From dealing with scalability issues to introducing groundbreaking features like Stories and Reels, Instagram’s playbook offers a masterclass in product evolution. Let’s dive into the key moments that shaped this tech giant.

The Early Days – Launching in a Crowded Market (2010-2012)

A Simple Yet Powerful Idea
In October 2010, Instagram was born out of the creative minds of Kevin Systrom and Mike Krieger. They envisioned a platform that simplified photo-sharing and allowed users to capture life’s moments with ease. Unlike other social platforms, Instagram focused heavily on mobile-first design and seamless user experience.

Challenge: User Adoption and Retention
The digital world was already buzzing with platforms like Facebook and Twitter. Breaking through the noise wasn’t easy. Instagram needed something that would set it apart.

Solution: Minimalism and Filters
Instead of overwhelming users with complex features, Instagram honed in on simplicity. Photo filters and easy editing tools turned ordinary snapshots into art. The minimalistic design struck a chord, leading to 1 million downloads within just two months of launch.

Scaling for the Future
By 2011, Instagram’s growth skyrocketed – but that brought new problems. The infrastructure struggled to keep up with rising traffic.

Answering the Call: Cloud Services and Optimization
Instagram transitioned to cloud services and optimized its backend systems to ensure the platform could handle increasing demand. This laid the foundation for continued growth.

The Game-Changer – Facebook Acquisition (2012)

In April 2012, Facebook announced its $1 billion acquisition of Instagram – a deal that raised eyebrows across the tech world.

Why Did Facebook Buy Instagram?
Facebook saw the future in mobile apps, and Instagram’s potential in photo-sharing fit perfectly into its expansion strategy. The acquisition provided Instagram with the resources to scale faster while maintaining its independence.

The Aftermath:

• Instagram kept its brand identity but benefited from Facebook’s vast infrastructure.

• By September 2012, Instagram had grown from 30 million users to over 100 million.

Monetization and Expansion (2013-2015)

With Facebook’s backing, Instagram’s next focus was monetization. But how do you introduce ads without alienating users?

Enter Sponsored Posts
In 2013, Instagram introduced its first sponsored post – an elegant, native ad format that blended seamlessly with regular content. Brands flocked to the platform, seeing the potential for engagement.

Diversifying Content – Beyond Photos
Instagram wasn’t content with just photo sharing. To keep users engaged, video uploads were introduced in 2013. This opened doors for creative content and increased user retention by 40%.

Facing the Snapchat Threat (2016-2018)

In 2016, Instagram faced one of its biggest competitors – Snapchat. The younger audience gravitated towards ephemeral content that disappeared after 24 hours. Snapchat Stories was quickly becoming a dominant force.

Instagram’s Response: Stories
Instagram didn’t just respond – it borrowed the idea and perfected it. In August 2016, Instagram Stories launched, allowing users to post disappearing content. Within a year, Stories surpassed Snapchat in daily users, hitting 250 million.

Algorithm Shift – A Controversial Move
2016 also saw the introduction of Instagram’s algorithmic feed, replacing the chronological timeline. Content that users were more likely to engage with appeared first. Though met with initial backlash, this change boosted engagement by keeping users on the app longer.

Innovation and E-Commerce Boom (2019-2021)

By 2019, influencer marketing had become the lifeblood of Instagram. The platform needed to cater to brands, creators, and consumers alike.

Shopping on Instagram
Instagram leaned into e-commerce with Shopping Tags, allowing businesses to link products directly in posts and stories. A few taps took users from browsing to checkout – all without leaving the app.

Reels: Fighting TikTok
In August 2020, TikTok’s meteoric rise prompted Instagram to launch Reels, a short-form video feature. Reels not only retained users but also attracted new creators. Engagement on Reels skyrocketed, making it a key focus for Instagram’s growth strategy.

Evolving with Technology – AI, AR, and Video (2022-Present)

Instagram’s next frontier lies in artificial intelligence (AI) and augmented reality (AR). In 2024, the platform announced AI-powered video editing tools, powered by Meta’s Movie Gen AI model.

Coming in 2025:

• Users will soon be able to edit video backgrounds and features with just text prompts.

• AR filters continue to evolve, making content more interactive and immersive.

Carousel Posts Expand
In August 2024, Instagram expanded carousel post limits to 20 slides, giving users more room for storytelling.

Prioritizing Mental Health and Safety (2024-Present)

As social media’s impact on mental health came under scrutiny, Instagram took action to create a safer environment.

Teen Accounts (2024):
Instagram introduced teen-specific accounts that limit exposure to sensitive content and default to private settings.

Hiding Like Counts
To reduce social pressure, Instagram experimented with hiding like counts in certain regions, focusing on user well-being over engagement.

The Road Ahead

Instagram’s evolution is far from over. With each year, new trends, competitors, and technologies emerge. Yet, through every challenge, Instagram adapts – ensuring it remains at the forefront of social media.

From humble beginnings to billion-user milestones, Instagram’s journey offers valuable lessons in innovation, resilience, and the power of putting users first.

Stay tuned – because Instagram’s next chapter is just around the corner.

About the Author

I’m Aditya, a Mumbai-based design-centric Product Manager with a passion for all things bikes, airplanes, and dogs! With over 6 years of experience in the ever-evolving world of digital products, I’ve become the ultimate driving machine for crafting pixel-perfect experiences that’ll rev your engines. When I’m not obsessing over pixels, you can find me travelling. I thrive on collaborative projects and delight in finding innovative solutions that not only wow users but also drive tangible results. I take my work seriously, but I also believe in adding a sprinkle of humor and quirkiness to keep things exciting. Aditya ChaudhariProduct Manager

Aditya Chaudhari

Product Manager

From wireframes to launchpads, Aditya engineers AI-powered experiences with the precision of a pilot and the soul of a designer.

Blog Portfolio About Connect

Also read...

Understanding Root Cause Analysis

Root Cause Analysis is the process of uncovering the fundamental reasons behind a problem or issue. It goes beyond addressing surface-level symptoms and focuses on identifying the core causes. By employing RCA techniques, product managers can gain a deeper understanding of the problem and develop targeted solutions that address the root issues.

Why RCA Questions in Product Management Interviews?

RCA questions serve multiple purposes in product management interviews. They allow interviewers to assess a candidate's skills in various areas:

1. Product Sense: RCA questions help evaluate a candidate's ability to analyze a product comprehensively, considering different levels of depth and impact.

2. Problem-Solving: RCA questions test a candidate's problem-solving skills, specifically their ability to identify and address the underlying causes of a problem rather than just treating the symptoms.

3. Structural Thinking & Communication: These questions assess a candidate's ability to structure their thoughts, prioritize information, and effectively communicate their analysis to others.

4. Domain Knowledge: Through RCA questions, interviewers gauge a candidate's understanding of the product's domain and its key metrics, allowing them to evaluate the candidate's domain expertise.

Approach to Solving RCA Questions

To excel at RCA questions, it is crucial to follow a structured and methodical approach. Here's a step-by-step framework to guide you:

1. Validate the Problem: Begin by validating the problem itself. Seek clarification on the problem statement and ensure you have a clear understanding of what needs to be addressed.

2. Ask Clarification Questions: Ask detailed questions to gain deeper insights into the problem. Break down the problem statement into keywords and inquire about their meanings. Seek information about relevant metrics, time frames, segmentation, and any significant changes or patterns.

3. Identify Internal Factors: Explore potential internal factors that could contribute to the problem. Consider aspects such as user journey, changes in policy, UI/UX updates, or technical glitches. Analyze any recent changes that might be relevant to the problem at hand.

4. Consider External Factors: Examine external factors that could influence the problem. Look into governmental regulations, competitor activities, social media trends, or specific events that may impact the product's performance.

5. Assess User Intent: Consider the user's intent and potential shifts in behavior that could affect the problem. External factors such as cultural or environmental changes, economic shifts, or societal events might alter user preferences or habits.

6. Summarize and Communicate: Take a moment to summarize your thoughts and conclusions. Clearly communicate your findings and thought process to the interviewer, showcasing your structured thinking and effective communication skills.

Step 1- Clarify

A data scientist spends most of the time cleaning and preparing data (approx 70%). This step is essential because, in most situations, data provided by the customer has bad quality or just cannot be directly fed to some ML model. Consider this step to be analogous to the data-preprocessing step in data science. You will have to define the scope correctly, narrow down the situation, and clarify terms.

Moving vertically and horizontally through the problem statement: Let’s try to understand this with an infographic.

Moving horizontally to clarify terms used in question and moving vertically w.r.t to “what” and “where” to narrow down the scope. This will help us in limiting our observation to a narrow space of limited variables.

A good question before moving to step 1 could be “have we made any changes to the definition of cancellation, or did we change the tool which used to measure this cancellation rate.”

Step 2- Check for external factors

Make this a habit; sometimes, it’s just an earthquake causing some problem (not joking). You already have some context about the situation after step-0. Use this information to think of major external factors that could have influenced the product in any way.

An excellent way to test the involvement of external factors in a problem is to ask — “Is this an industry-specific problem or company-specific?”

Industry-specific problems can have root causes in factors beyond their line of work. (For example, a roadside vegetable vendor has a bad season because people have started buying packaged food post-COVID-19).

Let’s try to list down some common external factors to check for-

1) Any recent natural calamity/Power Shutdown (can be asked when the trend is not gradual or a single point decline in the graph.)

2) New government regulation/policy change?

3) New product entry in the market/product substitute.

4) Sentiments on social media? (E.g. Controversial tweet by the company, fake news around the company, etc.)

After touching on possible external factors we can move to our next step- Making a user journey.

Step 3- User Journey

Try to make an end-to-end user journey for the product so that you can cover every tiny point of failure where a problem can reside. Let’s try to make a User Journey for our case. We will try to do this in parts-

A. Channels: Different ways a user lands on the product web page/app.

1. Google search ads.

2. Ads on blogs/websites.

3. Organic search.

4. Emails.

5. Shareable link (from friends, any third party.)

6. Push notifications.

7. Organic app open.

You can club these under promotional and organic, paid and unpaid, or any suitable classification of your choice. Ask relevant questions about each channel. E.g., how’s the trend of cancellation been in these channels?, Are we getting cancellations on orders bought from any specific medium, or is it even for all channels?

B. Key Action in app/web page- Divide the web app segments with which a user interacts during product discovery.

Search Bar- Relevant Question (R.Q.)- Are we facing cancellations on orders discovered through the search bar?

Recommendation section- (R.Q.) — Did we make any changes in the recommendation algorithm?

Product category tab- (R.Q.) — Are we facing order cancellations for a specific product category? Have we made any changes to how we define types? Any new addition to product categories?

C. Selection — (R.Q.) — Any changes made to the product listing page/product description page? Any changes in how users add items to the cart/add details/add address (is it accurate enough)?

D. Payments — Always check for the mode of payment by which the order was bought. (R.Q.)- Are we facing cancellations for a specific payment mode (C.O.D., card payment, credit payment, etc.), Is there a payment failure for canceled orders?

E. Confirmation and Tracking: (R.Q.) — At what point after confirmation, orders are getting canceled? Any specific source pin codes where orders are getting canceled? Any specific mode (Airway, Roadway, Type of warehouse) for which cancellations are up?

A structured narrowing approach with good coverage of crucial considerations regarding the product will be enough to crack this round!

So we are almost done with the R.C.A. post; before I end this post, I have some bullet points and a cheat sheet for those who have skipped directly to the end part ( for claps, maybe :P)

1. Remember- Simple Problems Are Often the Hardest to Solve. Pay attention to the tiniest of details and never assume anything.

2. Speak out your thought process at every stage of the interview process so that your hidden assumptions(in case you have made any) are visible to the interviewer.

3. If you think your structure is lost, summarize your approach and utilize that time to think ahead or change tactics.

Tips for RCA Interviews

Here are some additional tips to excel in RCA interviews:

1. Ask Clarification Questions: Seek clarification on any ambiguous aspects of the problem statement. This demonstrates your attention to detail and your ability to extract critical information.

2. Request Data and Insights: Ask for relevant data and insights to support your analysis. This showcases your ability to make data-driven decisions.

3. Be Conversational: Make the interview more conversational rather than relying solely on a question-answer format. Engage with the interviewer and adapt your approach based on their cues.

4. Focus on Thought Process: Emphasize your thinking process and how you arrive at conclusions. Interviewers are interested in understanding your problem-solving approach and your ability to think critically.

5. Remain Flexible: Be open to changing your line of inquiry or adjusting your assumptions based on new information or cues from the interviewer. Adaptability is a key quality in product management.

Conclusion

Cracking RCA questions in product management interviews requires a combination of structured thinking, problem-solving skills, and effective communication. By following a systematic approach, asking relevant questions, and considering internal and external factors, you can demonstrate your ability to identify root causes and provide valuable insights. With practice and a thoughtful approach, you can master the art of Root Cause Analysis and excel in product management interviews.