Product Thinking: The Skill Behind Better Products
- What product thinking actually means
- The common mistake people make
- The five habits of product thinking
- How to practice product thinking daily
Product thinking is a concept that transcends job titles and seniority; it’s an essential mindset for anyone involved in creating products. While product managers often lead the charge, the best products emerge from collaborative teams where every member—engineers, designers, marketers, and support staff—embraces a product-oriented mindset. This approach prioritizes user needs and problems over mere solutions, fostering innovation and enhancing user experience.
What Product Thinking Actually Means
At its core, product thinking revolves around understanding user problems first. It encourages teams to ask, “What is the user trying to achieve?” before diving into development. This contrasts sharply with solution thinking, where teams may start with a feature or technology and then justify it without fully grasping the underlying user need.
Consider a fintech company that received a request for a “bulk export of transactions” from a significant customer. The product manager quickly drafted a spec, but the engineering lead wisely questioned the necessity of this feature. Why did the customer need it? The discovery process revealed that the customer’s accounting team was spending six hours a month manually reconciling transactions in a spreadsheet. While a bulk export would provide some relief, the real solution was a direct integration with their accounting software, which was faster to implement and fully addressed the problem. The customer had never asked for this integration because they were unaware of its feasibility. This example illustrates how product thinking can lead to more impactful solutions by focusing on user intent rather than superficial requests.
Marty Cagan's extensive research at the Silicon Valley Product Group shows that successful teams consistently prioritize user problems as their primary focus. The most effective product managers aren’t necessarily the most experienced but are those who cultivate the habit of product thinking throughout their teams.
The Common Mistake People Make
One of the most common pitfalls is treating product thinking as solely the responsibility of the product manager. When engineers code strictly to specifications and designers stick to mockups without questioning the underlying assumptions, the quality of the product suffers. This outsourcing of critical thinking can accelerate delivery but leads to products that may not serve the users effectively.
Another mistake is conflating customer requests with customer needs. Customers often articulate desires for features, but they may not express their underlying needs. For example, the request for bulk export masked a deeper need for faster reconciliation. Product teams must dig deeper to uncover these needs.
Further, teams often leap to solutions without fully defining the problem. Meetings that start with “Let’s discuss how to build X” miss an essential step. A more effective approach begins with “What problem are we solving, and for whom?” This slight shift in framing can save significant time and resources.
Lastly, product thinking is not just a one-time planning activity; it’s a daily habit. It should permeate every aspect of the work, from code reviews to customer interactions. Each team member should consistently ask how their actions enhance the user's experience.
The Five Habits of Product Thinking
To embed product thinking into your daily routine, consider adopting these five core habits:
-
Start with "For Whom and For What." Before meetings or decisions, clearly define the user and their goal. For instance, “We’re discussing a new export feature for the customer’s finance team, aiming to help them reconcile transactions more quickly.” This ensures that the user remains at the forefront of discussions.
-
Ask "Why" Three Times. Dive deeper into requests by asking “why” three times. If a customer wants bulk export, ask why they need it, why that solution matters, and why they prefer this method over existing options. This technique helps reveal the true problem and leads to more effective solutions.
-
Define Success Before Defining Work. Clearly articulate what success looks like before scoping a project. For example, “After this feature ships, the finance team will reduce their monthly reconciliation time from six hours to under one hour.” Establishing success criteria early directs the team’s efforts and priorities.
-
Treat Assumptions as Testable. Identify the biggest assumptions behind product decisions and consider how to test them. Instead of blindly implementing a feature based on assumptions, ask how you might validate these assumptions through small experiments.
-
Cut to Ship the Smallest Useful Thing. Focus on delivering the simplest version that meets the user’s success criteria. Many teams mistakenly build out full-featured versions from the outset. Instead, embrace the concept of a minimum viable product (MVP) to ship something useful, gather feedback, and iterate.
A Practical Example
Let’s say your team is developing a new feature for tracking user engagement. Rather than diving straight into feature development, start by clarifying the user and their goal.
-
“For whom and for what?” Identify your user (a content manager) and their goal (to understand which content drives engagement effectively).
-
“Why?” Ask why they want this feature. Perhaps they need better insights to improve content strategy. Why is that important? To drive user retention. Why does retention matter? It impacts revenue.
-
Define success. What does success look like? You might state that after implementing the feature, the content manager should be able to identify top-performing content in under 30 minutes per week.
-
Test assumptions. You assume users will engage with a dashboard. Test this by creating a simple prototype and gathering feedback before full-scale development.
-
Cut to ship. Launch a basic version of the engagement tracking feature that provides essential metrics instead of a comprehensive dashboard.
By applying these habits, the team remains focused on user needs and continuously improves their products based on real feedback.
Conclusion
Product thinking is a habit that transforms how teams approach product development. By centering discussions on user problems rather than just solutions, teams create products that resonate with their audience. This approach requires discipline and commitment but pays off in the form of better products and happier users.
To hone your product thinking skills, consider making it part of your daily routine. Start small, and soon you’ll see the impact it has on your work.
Want to get better at product thinking without adding more to your plate? Take the Omie Skill Assessment to discover personalized learning opportunities tailored to your needs.