Customer Pain Point Identification

In a recent conversation with a CEO about “the next leg” of their AI transformation, the CIO proudly walked me through their annual customer requirements survey, the long list of requested features, and the research budget devoted to capturing what customers say they want. It immediately reminded me of the line famously attributed to Henry Ford: “𝙄𝙛 𝙄 𝙝𝙖𝙙 𝙖𝙨𝙠𝙚𝙙 𝙥𝙚𝙤𝙥𝙡𝙚 𝙬𝙝𝙖𝙩 𝙩𝙝𝙚𝙮 𝙬𝙖𝙣𝙩𝙚𝙙, 𝙩𝙝𝙚𝙮 𝙬𝙤𝙪𝙡𝙙 𝙝𝙖𝙫𝙚 𝙨𝙖𝙞𝙙 𝙖 𝙛𝙖𝙨𝙩𝙚𝙧 𝙝𝙤𝙧𝙨𝙚.” Customers often describe the solution they can imagine, not the breakthrough they truly need. This is exactly the trap many organisations are falling into with AI. They are using AI to optimise what is already known: faster responses, incremental efficiency, a bit more automation around existing processes and stated requirements. That is useful, but it is not transformative. The real power of AI lies in helping us see and solve for the unknown – the unarticulated needs, the patterns humans cannot easily spot, the new ways to get customers from point A to point B that no one has words for yet. Jeff Bezos framed this beautifully when he said that Amazon’s strategy is built not on guessing what will change, but on what will not change: 𝙘𝙪𝙨𝙩𝙤𝙢𝙚𝙧𝙨 𝙬𝙞𝙡𝙡 𝙖𝙡𝙬𝙖𝙮𝙨 𝙬𝙖𝙣𝙩 𝙡𝙤𝙬𝙚𝙧 𝙥𝙧𝙞𝙘𝙚𝙨, 𝙛𝙖𝙨𝙩𝙚𝙧 𝙙𝙚𝙡𝙞𝙫𝙚𝙧𝙮, 𝙖𝙣𝙙 𝙢𝙤𝙧𝙚 𝙘𝙝𝙤𝙞𝙘𝙚. Those are needs, not feature requests. In the same way, AI strategy should start from enduring customer needs and then ask: what could become possible now that was impossible before, if we stopped listening only to “faster horse” feature lists? So for all the leaders racing to “train everyone on AI” and pack roadmaps with AI features, perhaps the first mindset shift is this: move from customer requirements to customer needs – especially the unspoken and unmet ones. Use AI not just to speed up the old system, but to re‑imagine the journey itself. Are you using AI mostly being used to build “faster horses” for existing requirements, or to reveal and serve the deeper customer needs that nobody has quite been able to articulate yet? #transformation #leadership

🔹 𝐒𝐭𝐞𝐩-𝐛𝐲-𝐒𝐭𝐞𝐩 𝐆𝐮𝐢𝐝𝐞: 𝐓𝐫𝐚𝐧𝐬𝐥𝐚𝐭𝐢𝐧𝐠 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬 𝐢𝐧𝐭𝐨 𝐔𝐬𝐞𝐫 𝐒𝐭𝐨𝐫𝐢𝐞𝐬 🔹 1️⃣ Understand the Business Requirements Gather and analyze the business needs through stakeholder discussions, workshops, and existing documentation. Identify key functionalities, constraints, and dependencies. 2️⃣ Break Down the Requirements Decompose high-level requirements into smaller, manageable pieces. Ensure each piece delivers value independently. 3️⃣ Use the User Story Format Follow the standard “As a [user], I want [goal], so that [benefit]” format. Example: "As a customer, I want to receive order confirmation via email, so that I can track my purchase." 4️⃣ Define Acceptance Criteria Clearly outline what must be met for the story to be considered “done.” Example for the above story: ✅ Email is sent within 5 minutes of order placement. ✅ Email contains order details, expected delivery date, and customer support contact. 5️⃣ Prioritize and Refine with Stakeholders Work with Product Owners and Development teams to ensure the stories are clear, feasible, and prioritized correctly. Use INVEST criteria: Independent Negotiable Valuable Estimable Small Testable 6️⃣ Link Back to Business Goals Ensure every story aligns with the overall business objectives and adds value to the end user. 7️⃣ Continuously Improve Conduct backlog grooming sessions to refine and update user stories based on feedback. 💡 Pro Tip: If a requirement feels too big for a single user story, break it down into epics and further decompose them into smaller user stories. Mastering this process ensures that business needs are translated into actionable, developer-friendly work items that drive real value! 🚀 BA Helpline

The Problem: No Shared Definition of Customer “Need” Most organizations assume they are customer-centric, but in practice, sales, marketing, and development teams all define customer “needs” differently: • Sales teams see needs as features, benefits, or exciters that help close deals. • Marketing teams describe needs as value drivers, use cases, or personas that segment the market. • Development teams think about needs as requirements, specs, or technical solutions that guide design. Each discipline is correct in its own context, but because their definitions differ, the organization ends up misaligned on what customers truly want. This lack of agreement leads to: • Wasted investment: teams build features or campaigns customers don’t care about. • Misaligned priorities: marketing highlights one “need,” while development is solving for another. • Unreliable growth: innovation success rates remain low because there’s no common, customer-driven truth guiding decisions. The Outcome-Driven Innovation process is the solution. ODI resolves this by defining needs as customer outcomes—the metrics customers use to measure success when getting a job done. • Outcomes are solution-independent: not features or benefits, but timeless measures of what getting the job done “better” means. • Outcomes are precise and measurable: e.g., “Minimize the time it takes to gain visual access to the target structure” rather than “faster setup.” • Outcomes create a common language: aligning sales, marketing, and development around the same customer truth. With ODI, everyone agrees on what a “need” is, because it’s framed as a customer-defined metric of success — not each team member’s conflicting interpretation. Outcome statements are unambiguous, precise, knowable and discoverable, stable over time (as is the job-to-be-done), measurable and controllable, and they follow a set of time-tested rules. Companies like Bosch, Cox Automotive, and The Medicines Company aligned their teams around customer outcomes before development began, resulting in products that were not only successful, but sustained market leadership.

Most teams skip the hardest part of creating OKRs: translating validated customer problems into meaningful metrics. You've done the discovery work. Your interviews revealed that drivers on your ridesharing platform struggle with shift planning—they can't predict which areas will be busy, leading to wasted time and lower earnings. But instead of jumping straight to "build demand forecasting," you need one more step: defining what behavior change would tell you the problem is actually solved. 𝗧𝗵𝗲 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝗯𝗹𝗲𝗺 I see teams make this leap constantly: Customer problem → Solution idea → Cross fingers and hope. What's missing is asking: 𝗪𝗵𝗮𝘁 𝘄𝗼𝘂𝗹𝗱 𝘂𝘀𝗲𝗿𝘀 𝗱𝗼 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁𝗹𝘆 𝗶𝗳 𝘄𝗲 𝘀𝗼𝗹𝘃𝗲𝗱 𝘁𝗵𝗶𝘀 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝘄𝗲𝗹𝗹? An outcome describes a change in human behavior, not a company aspiration. "Increase driver satisfaction" is what the business wants. "Drivers spend less time in low-demand areas" describes how humans would behave differently. 𝗔 𝗦𝗶𝗺𝗽𝗹𝗲 𝗦𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗧𝗵𝗮𝘁 𝗪𝗼𝗿𝗸𝘀 When you've validated a customer problem worth solving, structure your outcome similarly to what Joshua Seiden and Jeff Gothelf suggest in their book "𝗪𝗵𝗼 𝗗𝗼𝗲𝘀 𝗪𝗵𝗮𝘁 𝗕𝘆 𝗛𝗼𝘄 𝗠𝘂𝗰𝗵?" [𝗦𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗔𝘂𝗱𝗶𝗲𝗻𝗰𝗲] + [𝗕𝗲𝗵𝗮𝘃𝗶𝗼𝗿 𝗖𝗵𝗮𝗻𝗴𝗲] + [𝗛𝗼𝘄 𝗬𝗼𝘂'𝗹𝗹 𝗠𝗲𝗮𝘀𝘂𝗿𝗲 𝗜𝘁] Compare these examples: 𝗩𝗮𝗴𝘂𝗲: "Improve user engagement by 20%" 𝘞𝘩𝘰 𝘦𝘹𝘢𝘤𝘵𝘭𝘺? 𝘋𝘰𝘪𝘯𝘨 𝘸𝘩𝘢𝘵 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵𝘭𝘺? 𝘞𝘩𝘺 𝘥𝘰𝘦𝘴 20% 𝘮𝘢𝘵𝘵𝘦𝘳? 𝗖𝗹𝗲𝗮𝗿: "Part-time drivers in suburban markets reduce unpaid waiting time from 30+ minutes per shift to under 10 minutes." 𝘚𝘱𝘦𝘤𝘪𝘧𝘪𝘤 𝘴𝘦𝘨𝘮𝘦𝘯𝘵, 𝘤𝘭𝘦𝘢𝘳 𝘣𝘦𝘩𝘢𝘷𝘪𝘰𝘳 𝘤𝘩𝘢𝘯𝘨𝘦, 𝘮𝘦𝘢𝘯𝘪𝘯𝘨𝘧𝘶𝘭 𝘮𝘦𝘢𝘴𝘶𝘳𝘦𝘮𝘦𝘯𝘵 Before settling on any Key Result, ask yourself: "𝗪𝗵𝗮𝘁 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗺𝗲𝘁𝗿𝗶𝗰 𝘄𝗼𝘂𝗹𝗱 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘁𝗲𝗹𝗹 𝘂𝘀 𝘄𝗲'𝘃𝗲 𝗮𝗰𝗵𝗶𝗲𝘃𝗲𝗱 𝘁𝗵𝗶𝘀 𝗯𝗲𝗵𝗮𝘃𝗶𝗼𝗿 𝗰𝗵𝗮𝗻𝗴𝗲?"

"Center the customer in everything you do." This kind of advice is tossed around a lot in customer success. At the surface, it's great! *Of course* we should center the customer!! Buuuutttt.... How, exactly? I like to use the ACT Framework to make this general concept more actionable. "ACT" - Advocate, Connect, Translate. This framework helps anyone in a customer-facing role (but especially CSMs) earn customer trust, drive value, and influence internal priorities, by keeping the customer at the core. 🙋♀️ ADVOCATE: Be the voice of the customer – internally and externally. Build credibility and trust by relentlessly championing the customer’s success – internally with teams, and externally with the customer. - Build trust by showing customers you understand their goals, frustrations, and business context - Internally, consistently represent customers’ needs in product discussions, roadmap planning, and enablement - Example scenarios: ▶️ External: Your customer is struggling with onboarding delays. Instead of saying “that’s handled by another team,” you say, “let’s walk through the blockers together – I’ll escalate and stay with this until it’s resolved.” ▶️ Internal: During a roadmap or release review, you say, “This request has come up from 3 of my strategic accounts – it’s tied to their quarterly KPIs. Can we scope it for Q4?” 🤝 CONNECT: Tie everything back to your customer’s business outcomes. Drive value by aligning product usage to what matters most to them – revenue growth, patient care, efficiency, etc. - Go beyond product usage – understand how your solution fits into customers' broader goals and challenges - Use this context to personalize recommendations and measure success - Example scenarios: ▶️ “You mentioned one of your focus areas is reducing time spent on administrative tasks like charting after patient appointments – let’s look at how your team’s adoption of [Feature X] is trending and what we can do to increase ROI.” ▶️ “This workflow would reduce manual reporting by 20+ hours/month – that's a win you can share with leadership.” 📣 TRANSLATE: Turn insights into action for both sides. Bridge the gap between customer language and product/engineering language – and vice versa.  - Translate customer feedback into clear, actionable insights for your internal teams - Translate product updates and capabilities into value-based messaging for your customer - Example scenarios: ▶️ External: “This new release includes [Feature Y] – which should save your team at least 3 hours/week based on the process we mapped out last month.” ▶️ Internal: “Here’s what customers actually mean when they say the platform doesn’t work for their workflow – it’s not the functionality, it’s the lack of integration templates.” How do you "center the customer" in a practical way??

Most feature requests need translation before you can act on them. Here's how to break down vague requests into work you can act on: → Ask what job they're trying to do. "Reporting" is a solution. The job might be "prove ROI to my boss" or "track trends over time." → Get specific use cases. Ask them to walk through exactly how they'd use the feature. What would they do first? Then what? → Explore visualization preferences. Some people want raw data exports. Others want pretty charts. These are different builds. → Identify the trigger. What moment makes them think "I need this"? That context shapes the solution. → Separate related but distinct ideas. "Reporting" might break into five smaller features. Track evidence for each one separately. → Collect supporting evidence over time. One request is an anecdote. Ten requests with similar use cases is a pattern. → Define scope before estimating effort. You cannot estimate "build reporting." You can estimate "create a dashboard showing X metric with Y filter." → Validate your interpretation. Before building, describe what you understood back to the customer. Make sure you got it right. Vague requests are not bad requests. They're starting points for better conversations. Your job is to dig deeper until you have clarity on what to build and why.

Designing projects around real customer needs When projects are built on incorrect assumptions about the customer needs, it results in unsatisfactory results. Every assignment has to be viewed from the customer’s perspective - not just what we think they need, but what they actually require. The project execution has to be fine-tuned to reflect the customer’s realities. Never define a project based on internal assumptions. The process should begin with discussions involving all stakeholders to identify real pain points. Collective brainstorming will uncover ground-level insights and ensure that the project has a strong foundation. This will align the team with the core requirements of the customer. The best projects don't just follow a plan; they solve customers’ problems. If we focus on what customers actually need, we're much more likely to build something meaningful. So, talk to your customers, observe their actual issues, and listen actively.

Customers don't buy features; they buy solved problems. Yet, product teams often struggle to communicate clear, differentiated value propositions that focus on solving the customer’s business pain. One major challenge I’ve seen companies do over and over again before a product launch is translating features into customer-centric benefits. They tend to default to talking about features because it's easy and familiar. After all, features are tangible, making them easier to demo, show on the website, and promote. However, when buyers ask for evidence of business benefits, the technical sale breaks down. Despite extensive market research and product design efforts, messaging is often neglected. Instead of creating compelling value propositions, companies end up with messages filled with incomprehensible tech-speak and jargon. The goal should be to differentiate themselves clearly but most just position themselves as just yet another option. Product professionals, often from technical backgrounds, may lack the training to communicate in customer-centric language. They also tend to assume that their perspective reflects everyone’s, a mistake when users and buyers often have distinct motivations. Many value propositions fail because they aren't tailored to the right audience. Developing effective value propositions requires a structured approach. The Value Propositions Methodology Successful value propositions explain how specific products solve customer problems. This involves addressing four key areas: 1. The Broad Context: Customers don’t buy technology for its own sake. They want to solve an underlying business problem, with things such as ‘efficiency gains’ often just being a means to that end. Understanding the broader context—industry trends, regulatory requirements, external disruptions—is crucial for addressing the customer's true business pain. 2. The Buyer Persona: Users and buyers are often different people with different motivations. Understanding who the actual decision-makers are, their requirements, and potential objections from other stakeholders is key to crafting persuasive value propositions. 3. Business Benefits: Once you understand the customer’s pain, it’s time to translate product features into tangible business benefits. This means explaining how a product addresses the business problem, whether by increasing revenue, reducing costs, mitigating risks, etc. Quantifying this, with real-world data, goes a long way in building credibility here. 4. Competitive Differentiation: If a product is similar to the competition, it risks competing on price alone. Differentiating the value proposition may require emphasizing non-product aspects, such as customer service, industry expertise, or brand reputation. You’ll want to define three unique elements to create a strong, differentiated value proposition that sets you apart from competitors. Putting the Methodology Into Action [continued in comments]