Suggestions
Aipmm Gabriel Pendleton
Product Manager, Creator Experience at Twitch
Gabriel Pendleton is a seasoned product leader with over 10 years of experience in the tech industry, specializing in creator platforms and live-streaming products. He is currently the Vice President of Product at Sizzl, where he leads initiatives to enhance live-streaming experiences for the culinary community. Previously, he served as a Product Manager for the Creator Experience team at Twitch, where he focused on improving tools and features for millions of creators globally.
Pendleton's expertise includes product strategy, user engagement, Agile/Scrum development, and business roadmapping. His career also spans roles such as co-founder of AudioStaq, a podcast content and revenue platform, and various technical positions in software engineering and quality assurance. He holds certifications such as Certified Scrum Product Owner (CSPO) and Certified Product Manager (CPM) and has completed advanced product management courses at Stanford Continuing Studies and Product Faculty.
In addition to his professional accomplishments, Pendleton is recognized for his contributions to the creator economy and his ability to align product strategies with user needs and business objectives.
Highlights
Creating a genuine customer problem statement is a game-changer in product development. Many times, what we see labeled as "customer problems" are just dressed-up solutions that someone in the company has already decided on.
These can come from business stakeholders or designers who are set on a particular idea. Even if you're starting with a predetermined solution, it's crucial to backtrack and ensure there's a real customer problem being addressed.
Why is defining a real customer problem important?
You might have heard the quote, often misattributed to Einstein: "If I had only one hour to save the world, I would spend fifty-five minutes defining the problem and only five minutes finding the solution." The essence of this quote is spot on. Understanding the detailed experience you aim to change with your product is essential. If you skip this step, you risk addressing the wrong issue entirely.
Doing customer research to discover and validate problems is a no-brainer. This post isn’t about finding problems but about articulating them correctly, ensuring clarity for your team and paving the way for effective solutions.
A quick rule of thumb:
If your customer problem statement mentions your product, service, or solution, it's likely not a true customer problem. Your solution should not be part of the problem; the issue exists independently of what you're offering.
Example of a poorly written customer problem statement: "Customers want to be able to pay bills using their smartphone camera."
This statement is essentially a solution masquerading as a problem. It doesn’t highlight any specific issue with the current way customers pay bills. It presupposes a solution without identifying the actual problem customers face.
Example of a well-written customer problem statement: "Customers find paying bills tedious and the process of entering details for each bill cumbersome and time-consuming."
This version is better because it:
- Doesn't presuppose a solution.
- Targets a specific group of customers with whom you can empathize.
- Reflects the actual user experience.
- Guides the project to address the underlying issues.
- Sets measurable obstacles to overcome, which helps in evaluating the success of your solutions.
Understanding the problem is the key to solving it. Don’t rush this step. Take the time to get it right, and your solutions will be far more effective.
