<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Leslie L. Grandy on Medium]]></title>
        <description><![CDATA[Stories by Leslie L. Grandy on Medium]]></description>
        <link>https://medium.com/@lesliegrandy_86311?source=rss-a769b5b95b0c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CeJr5tQXOoZ4AYQze-mjTQ.jpeg</url>
            <title>Stories by Leslie L. Grandy on Medium</title>
            <link>https://medium.com/@lesliegrandy_86311?source=rss-a769b5b95b0c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:35:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lesliegrandy_86311/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Role of Problem Definition in Driving Innovation]]></title>
            <link>https://medium.com/@lesliegrandy_86311/the-role-of-problem-definition-in-driving-innovation-3dd8303a02f2?source=rss-a769b5b95b0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dd8303a02f2</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-management-skills]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Leslie L. Grandy]]></dc:creator>
            <pubDate>Mon, 22 Jan 2024 00:17:59 GMT</pubDate>
            <atom:updated>2024-01-22T08:45:03.951Z</atom:updated>
            <content:encoded><![CDATA[<p>Knowing how to craft effective problem statements is a critical skill for product teams, as it ensures that the team is solving the right problem and that the problem is worth solving. Effective problem statements keep product teams focused on the customer’s needs throughout the development process. A well-crafted problem statement clearly defines the issue to be addressed, ensuring that everyone on the team understands the core challenge. A well-written problem statement helps teams understand both the as-is condition and the desired to-be state. This clarity ensures the best outcome for the customer and the business.</p><p>Moreover, a well-defined problem statement stimulates creativity and innovation. Team members can generate more targeted and inventive solutions by precisely outlining the issue. This focus on a specific problem fosters an environment where creative problem-solving thrives, leading to more effective and innovative products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-q-0mnmt4h6XBPioIPmGhQ.png" /><figcaption>Image by pch.vector on Freepik</figcaption></figure><h3><strong>Risks of Poorly Constructed Problem Statements</strong></h3><p>Poorly constructed problem statements can lead to a variety of issues for product teams. First, a vague or overly broad problem statement can lead to misalignment within the team. Additionally, a poorly defined problem can result in solutions that are misaligned with user needs. If the problem statement does not accurately reflect the user’s pain points, the resulting product may fail to address the actual needs of the target audience, leading to low adoption and customer dissatisfaction. One of the reasons this can happen is that problem statements may target symptoms of a bigger problem because the team doesn’t invest in understanding the root cause of the customer experience that needs to be addressed.</p><p>A problem statement that is poorly crafted can hinder innovation because when the problem is not clearly defined, it becomes difficult for team members to focus their creative energies effectively. This lack of focus can result in uncompetitive or uninspired solutions that do not significantly advance the product or offer novel solutions to the user.</p><p>Poorly drafted problem statements can also mistakenly include elements of a solution the team already has in mind. When a team begins with a problem statement that subtly suggests a specific solution, it unintentionally biases the development process toward that predetermined approach. This restricts the exploration of alternative solutions and stifles innovation. For instance, if a problem statement implies that a digital tool is the answer, it may overlook non-digital or hybrid solutions that could be more effective. Instead of openly considering a range of possibilities, the team might demonstrate confirmation bias by favoring information or approaches that align with pre-existing beliefs or ideas, often in the name of speed to market.</p><p>Another risk is the squandering of resources. A team working with a poorly defined problem might spend time and money developing features or aspects of a product that are not critical to solving the core issue and which ultimately don’t get used. This misallocation of resources can lead to a situation where critical aspects of the product aren’t given enough attention, eventually leading to a suboptimal solution. It wastes time and money, can frustrate customers, and delays the delivery of the final product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jD2c7seYGBBSDfBdcOhHnw.png" /><figcaption>Image by pch.vector on Freepik</figcaption></figure><h3><strong>Best Practices for Developing Effective Problem Statements</strong></h3><p><em>Do you understand the problem you are trying to solve well?</em></p><p>A good problem statement does not offer commentary on a proposed solution. It considers the facts and describes the problem without diagnosing it or pointing fingers. It is objective, descriptive, and factual. A great problem statement goes even further because it also indicates the scope and impact of the problem. There can be a temptation to ensure understanding of the problem space by adding more conditions and descriptors to aid in clarifying the issues. However, it’s crucial not to over-explain because an effective problem statement should be concise and specific. Avoid vague descriptions, and use language understandable to all team members, regardless of their technical expertise.</p><p>Problem statements should not describe a business problem. You must center the problem statement around the customer. Understand how they experience the issue, clarifying what frustrations it causes or prevents the customer from achieving the desired outcome. It’s essential to dig deep and be sure you aren’t focused on the problem’s symptoms instead of the problem itself. Techniques like the “Five Whys” can effectively peel back an issue’s layers to reveal its core.</p><p><em>How do you know this is a problem worth solving?</em></p><p>As a business, it’s natural to want to solve every problem your customers experience. However, you need to be mindful of your limited resources and time. Prioritizing and focusing your team’s efforts on the problems worth solving is essential. To do that, you must first evaluate whether the problem statement is relevant to your organization’s mission and goals. This assures other parts of the organization will be more likely to understand your strategy and rationale. Gaining alignment with team members and stakeholders on the problem statement you are solving is essential for customer success. This means identifying issues that align with your business objectives and can be addressed with your available resources. By doing so, you can ensure that your team is working on the most impactful problems and maximizing the impact of your efforts.</p><p><em>How will you know you were successful once you deliver a solution?</em></p><p>Any problem worth solving needs to be defined in a way that makes it possible to measure success. This measurability aids in prioritizing your time and resources, assuring an ROI, and validating “the juice is worth the squeeze.” Measures of success should include the solution’s effectiveness against an established metric (e.g., NPS, conversion, etc.) and the cost to deliver the experience versus the value created from the experience (i.e., ROI). In addition, tracking the cost to service and support customers using the solution - and whether the effort and expense increase or decrease after launch - is essential.</p><p>The development of effective problem statements is a critical task for product teams. It requires clarity, a focus on the user, understanding the root cause, measurability, relevance, and impact. Teams should consider using the <a href="https://en.wikipedia.org/wiki/Five_whys">Five Why</a> technique to ensure they address the root cause of their customers’ issues and solve the most critical problem, not just a symptom. The risks associated with poorly constructed problem statements — such as persisting the problem due to misalignment within the team, development of irrelevant solutions, resource wastage, and stifled innovation — underscore the importance of developing this skill. By adhering to best practices in crafting problem statements, product teams can set a solid foundation for successful and innovative product development.</p><p>For more tips on the art of framing effective problem statements, please join my Maven Course using this special offer for Medium readers, <a href="https://maven.com/the-product-guild/customer-centric-innovation?promoCode=Medium">“Master Customer-Centric Innovation to Unlock Disruptive Ideas.”</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dd8303a02f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Gift is Thoughtful Service Design]]></title>
            <link>https://medium.com/@lesliegrandy_86311/the-best-gift-is-thoughtful-service-design-88f225fa23ee?source=rss-a769b5b95b0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/88f225fa23ee</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Leslie L. Grandy]]></dc:creator>
            <pubDate>Thu, 21 Dec 2023 05:28:08 GMT</pubDate>
            <atom:updated>2023-12-21T05:45:51.288Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s the one that arrives precisely as expected and delights the gift recipient immediately upon unboxing.</h4><p>I bet you have had a poor customer service experience in this post-pandemic era of labor shortages and supply chain hiccups. You are not alone. According to a survey conducted by <a href="https://www.nbcboston.com/investigations/consumer/nbc-boston-responds/the-results-are-in-for-our-survey-of-customer-service-during-covid/2233378/">NBC</a>, 75% of consumers say customer service worsened during the pandemic, and 78% of consumers have contacted a company multiple times to address a single concern. I agree — service is not what it used to be. And to make things worse, you’ve probably also been met with a series of reasons why the service you expected is not what you received.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*K3-aYJvsF2DkcyWPMueeLA.jpeg" /><figcaption>Image by brgfx on Freepik</figcaption></figure><p>Recently, I placed an order for some wine, and even allowing for the 1–3 days of handling before shipping, there was still plenty of time for it to arrive by Christmas. After two days, I called the winery to confirm that the product would be shipped that day or the next business day, which was a Monday. I was assured the package had been dropped off at their mailroom and would ship on Monday. I was further informed that the tasting room was closed on Monday and Tuesday, so if I didn’t receive the shipping confirmation, I should email the winery, as emails would be checked when the phone wasn’t answered. Nothing landed in my inbox on Monday, so I emailed and cc’d the winery manager to let them know. Another two days went by with no reply. Finally, the next day, a week after I placed the order, I received a call from the manager, informing me she was on vacation, that they used a third party to ship, and that the mailroom had cold storage so my wine would have been safe over the weekend. However, she didn’t communicate if the product had shipped. when it had been shipped, or the tracking info. [This information is essential since shipped wine requires an adult signature when receiving it.] Instead, she sought my empathy that she was responding while on vacation, and she spent the call describing their use of a third party called “The Mailroom” as if that somehow addressed my inquiry. She ultimately provided no order status insights, only a detailed description of a process that, as far as I knew at that point, had failed me.</p><p>Customers don’t care whether an employee or a partner wraps and ships the package. They expect that the process will work. If you make a point to say you returned the call from them while on your vacation, customers learn that nobody is minding the store when you are out of the office. If you feel it is more critical to lecture the customer on how things work rather than serve them, don’t be surprised if they don’t return.</p><p>It’s not the customer’s job to understand your labor issues or poor partner choices. It’s not the customer’s job to track down whether you fulfilled their expectations with multiple calls to customer service. <strong>When you charge the customer’s credit card, you take responsibility for their entire experience through all of the stages of their engagement with you</strong>. Do the various methods to contact you clarify how fast your response time might be? Do you have a way for customers to track the order online so that if your emails get caught by a spam filter, the customer can still access the necessary information? Do you make customers feel good when things go off the rails? Or do you tell them a sob story about your labor issues?</p><p>You’ll note that I don’t mention the winery by name because that is beside the point. Great wine is accessible, and there are many consumer choices. When you buy directly from a brand and not a distributor, you create a relationship with that brand. In other words, you are one of their best customers because they have all your information. When buying directly, it’s fair to anticipate that the experience from that brand will reflect its quality and values. Great wine should be accompanied by excellent customer service (and a great meal!) When a customer’s expectations aren’t met, trust dissipates, tarnishing the greatness.</p><p><strong>Great service design is the seamless combination of people, processes, products, and partners. </strong>Ineffective processes, unreliable partners, and rude employees can significantly diminish the quality of a product, particularly when there are other options available that meet the same quality bar. Simply having a well-designed product is not enough to attract and retain customers; a dependable and delightful customer experience is essential to earning their continued loyalty and endorsement (who doesn’t want more 5-star reviews?)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88f225fa23ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Still Doing More With Less]]></title>
            <link>https://medium.com/@lesliegrandy_86311/still-doing-more-with-less-1f4babae0618?source=rss-a769b5b95b0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f4babae0618</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Leslie L. Grandy]]></dc:creator>
            <pubDate>Mon, 18 Dec 2023 04:27:25 GMT</pubDate>
            <atom:updated>2023-12-18T04:45:27.801Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="image of money by KStudio on FreePik" src="https://cdn-images-1.medium.com/max/1024/1*9LdXhmQAxu3WwvRTfi1H7g.jpeg" /></figure><p>I recently rediscovered<a href="https://tpgblog.com/2010/09/28/leslie-grandy-more-less/"> this guest post</a> I wrote back on September 28, 2010 which appeared on The Product Guy blog. I am amazed as I revisit it that it’s no less relevant thirteen years later.</p><blockquote>In a world of economic‐downsizing, we are seeing less of everything — less merchandise on the shelves, less people to service our business, less value from our investments. As a society, we are facing individually and professionally, the need to do more with less. When we are desperate, we often try too many things to fix what is broken, or we think any effort is progress. We are often motivated by our Quixotic belief it will be possible to find that single silver bullet to fix all that has broken. Everyone is, after all, only a lottery ticket away from the Powerball.</blockquote><blockquote>Sadly, the same thing happens in product design and the odds of a winning design that accomplishes everything that every customer wants are not in a product manager’s favor. Smart people are inventing technology faster than other smart people can knit it together into anything useful, valuable or economical. This is causing segments to beget niche sub‐segments, making interaction behaviors even harder to predict.</blockquote><blockquote>Redacting our everyday lives to meet a tighter monthly budget requires we make hard choices as consumers, but reducing is never easy once you have had a taste of more. No one wants to give up premium services or features and pay the same price for less value, but companies big and small are providing us slower response times, less durable products, low quality goods and consistent experiences because they are forced to cut back while we all aren’t spending as much anymore.</blockquote><blockquote>Whether 2010 is a just a low watermark for the economic tide, or it provides a persistent financial basement on which we found our future as consumers, product design teams should heed the underlying message because it holds a simple truth: economizing can be the most innovative thing a new product or service experience offers. The ones that reduce the amount of time it takes to accomplish a familiar task, eliminate redundant tasks that waste time and resources, and enable me to focus on only those tasks that really matter are always going to be at the top of my list of things I want to buy, even in harder fiscal times. How about you?</blockquote><p>I started wondering why this post still feels current beyond describing a similarly challenging economic time and its pressure on consumers and businesses. Leaving aside the impact of the pandemic on consumerism, for the moment, what other reason might explain why this still resonates? And then I realized that the underlying message remains profound:</p><blockquote>“Economizing can be the most innovative thing a new product or service experience offers. <strong>The ones that reduce the amount of time it takes to accomplish a familiar task, eliminate redundant tasks that waste time and resources, and enable me to focus on only those tasks that really matter are always going to be at the top of my list of things I want to buy, even in harder fiscal times.”</strong></blockquote><p>Unlocking the power of AI to economize and streamline tasks is the key to creating truly innovative products and services. By designing customer experiences that eliminate redundancies, prioritize essential activities, and free up capacity, we can empower customers to focus on what truly matters.</p><p>The same benefits of efficiency exist for product teams that build these customer experiences. Maximizing the team’s time to deliver value is a constant pressure. Product teams should recognize the resource constraints can be somewhat mitigated by using AI as a tool to assist in decision-making rather than relying solely on AI-generated outputs. <strong>The most effective product teams will learn to combine the strengths of human judgment and intuition with the efficiency of AI.</strong></p><p>While Generative AI is a valuable tool for automating tasks and generating content, it cannot replace the distinct qualities of human creativity, empathy, and adaptability. Encouraging employees to develop creative literacy ensures that they remain essential in guiding, augmenting, and enhancing AI-generated solutions, as well as addressing the evolving, complex, and unforeseen challenges of the business world. With the rise of computational creativity, boosting product managers’ creative confidence will ensure that generative AI’s large language models and outputs are deployed and interpreted imaginatively and ethically.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f4babae0618" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>