Qualitative research in project management doesn’t require complex methodologies or large budgets. At its core, it’s simple: talking to people who will use your product. It’s about observing their daily reality, listening to their frustrations, and understanding the context in which they operate.<\/p>\n\n\n\n
Industry data reinforces this point. According to the Standish Group, as reported in the CHAOS Manifesto<\/a>, up to 45% of features in typical software products are never used. <\/p>\n\n\n\n More recent insights confirm the pattern. The Future of Product Adoption Report by Pendo found that just 11% of features drive 80% of product usage. This isn’t a development problem. It’s a design problem \u2013 building based on assumptions rather than real needs.<\/strong><\/p>\n\n\n\n As a Project Manager, you don’t need to become a professional researcher. You just need to stay curious. Instead of asking: “Do you need this feature?” Ask: “How do you solve this today?” Instead of asking: “Is this intuitive?” Say: “Show me how you do it.”<\/p>\n\n\n\n Skipping these conversations has real consequences: more changes during development, more fixes after release, and a higher risk that users won’t adopt your product.<\/p>\n\n\n\n Lack of direct contact with users creates a cascade of costs: endless change requests, rework sprints, and rushed fixes after launch. You can avoid this with a simple, phased approach:<\/p>\n\n\n\n Schedule 1:1 sessions with users \u2013 about 45 minutes each. You don’t need a long script. A few well-crafted, open questions are enough:<\/p>\n\n\n\n What does your typical day look like in the context of this problem?<\/p>\n\n\n\n Key rule<\/strong>: At the beginning, resist the urge to show your product. Before discussing solutions, understand the context \u2013 the real-life situation your users operate in. During the conversation, write down exact quotes, not interpretations. Quotes capture not just the problem, but the emotions and mindset behind it.<\/p>\n\n\n\n Conversations are just the starting point; their real value<\/strong> lies in how you use them<\/strong>.<\/p>\n\n\n\n Identify patterns<\/strong>: don’t focus on individual opinions \u2013 look for recurring themes. If several people describe similar frustrations, that’s a signal worth acting on.<\/p>\n\n\n\n Pinpoint friction<\/strong>: pay attention to where users hesitate, stop, or look for workarounds.<\/p>\n\n\n\n Create a “pain map”:<\/strong> organize observations by: What is the user trying to achieve? What blocks them? What do they feel in that moment?<\/p>\n\n\n\n Before you move forward with the project, check:<\/p>\n\n\n\n If most of your answers are “no,” it’s worth pausing.<\/p>\n\n\n\n A few years ago, I was invited to research a parenting platform \u2013 after it had already launched. The budget was spent. Campaigns were live. Everything worked as designed.<\/p>\n\n\n\n The problem? Users weren’t coming back<\/strong>.<\/p>\n\n\n\n On paper, the product was perfect<\/strong>. It offered a well-designed method for supporting child development, built by top experts. The UX was polished, and the architecture was solid. But quantitative analysis missed one critical factor: emotional context.<\/p>\n\n\n\n The product assumed that parents live structured, predictable lives. Notifications were sent regularly, aligned with a learning schedule. But real life with children is anything but structured. Parents described exhaustion and constant interruptions.<\/p>\n\n\n\n Instead of helping, the notifications triggered guilt: “I didn’t have time again.” “I feel like I’m failing.”<\/p>\n\n\n\n A product designed to support users became a source of stress for users. Just a few qualitative interviews at the concept stage would have revealed this.<\/p>\n\n\n\n The term “UX research” often raises concerns regarding cost and delays. So don’t talk about “research.” Talk about:<\/p>\n\n\n\n Offer something concrete: five interviews in two weeks. It’s a small investment compared to rewriting half your product after launch.<\/p>\n\n\n\n And now you have two options:<\/p>\n\n\n\n Good luck! \ud83d\ude42 <\/p>\n\n\nA practical workflow: The “Five conversations” Method<\/strong><\/strong><\/h2>\n\n\n\n
\n
How to start: A mini-plan for Project Managers<\/strong><\/strong><\/h2>\n\n\n\n
\n
What to do with the insights?<\/strong><\/strong><\/h2>\n\n\n\n
Checklist for a Project Manager<\/strong><\/strong><\/h2>\n\n\n\n
\n
A million-dollar lesson: A parenting platform case study<\/strong><\/strong><\/h2>\n\n\n\n
![\"job\"](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2026\/03\/praca-EN-k-3.jpg\")
<\/a><\/figure>\n\n\n\nHow to convince stakeholders<\/strong><\/strong><\/h2>\n\n\n\n
\n
\n