Ask yourself: What are their problems, needs, and desires? What's truly important to them? What jobs do they want to perform? By which outcomes will they evaluate your product's value?
A common mistake is to focus too much on a particular solution. Theodore Levitt famously said, "Customers don't want a drill, they want a hole in the wall."
A great approach is to segment customers by their underserved needs and work backward to identify their common characteristics (age, gender, education, etc.).
Tip: The User and Buyer may be two different people. In that case, they will care about different outcomes.
2. Know your market and industry
Understand your product's domain. What are the technological trends? What are the dynamics of your market and industry? Are there any regulations that constrain what's viable for the business?
Try to understand the vision and strategy of your key competitors. I usually advise using their products regularly. This allows you to understand their weak points and what they are good at and to better position relative to them.
At the same time, do not take it too far. According to the first @amazon leadership principle "(...) Although leaders pay attention to competitors, they obsess over customers."
According to Michael Porter, It's not about being the best. It's about competing to be unique.
4. Know your business
Your product vision and product strategy must be aligned with the brother company's vision and business strategy.
It's also essential to understand the organizational structure, dependencies between departments, and the distribution of power and interests.
Ask yourself: What are the other products in your company's ecosystem? Are there any constraints (e.g., financial, sales, marketing) you should consider?
Tip: A few weeks ago, I wrote a LinkedIn post about working with stakeholders:
Sometimes there might be some UI guy who takes care of selecting stock photos or modifying the CSS styles. But in reality, the usability of the product is not taken seriously by anyone.
So the usability sucks.
2. The Designer is engaged too late.
The Designer is asked for help when low-fidelity prototypes are ready, or worse, once the application is built. Their only job is to "make it prettier."
No matter how much they try, it's like lipsticking a pig.
• The number one book for all Product Managers.
• Most of your ideas are not going to work.
• Principles of product discovery, which results in a validated product backlog.
• You need to be very specific when identifying the most important business problems.
• Your role as a leader is to help everyone on the team achieve the competence necessary to solve those problems.
The biggest collection of PM learning resources: books, podcasts, videos, internships, free courses, conferences, frameworks, and much more (October 2022): 🧵
With over 200,000 subscribers, it's simply the number one product newsletter on this planet. You will also find a link to the world's best product podcast on the newsletter page: lennysnewsletter.com
A broad range of topics you may know from Inspired, Empowered, or Loved. Product Management, Product Discovery, Leadership, Product Marketing, and much more: svpg.com
It happens when the product manager forgets about the "Why" and becomes a waiter. 🧵
To please everyone, PM collects and waterfalls all the requirements to the team. But no matter how much they implement, it gets only worse. Features shipped in a hurry do not solve anyone's problems and do not drive the expected business results.
The feature factory.
Fortunately, you can prevent or escape that trap. Try this: