In any situation, if you understand the chain of thought, the challenges and the solution of your counterpart, you will discuss much more empathetically. That helps the team move forward towards the goal.
Love this article, it's all about good communication, making sure your audience fully understand the "customer" painful points and what needs fixing.
Min basic requirement to become a good PO IMO should be to understand how data travels end to end, and how can we use data to build good product (or vice versa, which data do I need in order to build this product).
Task 1 - E.G. get a Json/XML feed from any type of e-commerce business, then be creative enough to design a basic wireframe/mockup that can be used as reference by your UX team, then once you have the designs complete user testing with user personas (paper prototyping will help to validate all user journeys), after this you should have gathered enough information that allows you to refine/improve upon the first iteration.
Task 2 - E.G. Get a wireframe design, build user journeys around it, then try to understand what data will be needed in order to power the product you want to build.
Other tools:
Customer Surveys, understand from various user personas what are the main painful points, if you get multiple feedback around same topic that is a clear evidence that you need to address this customer painful point.
The end goal should be to deliver a product that fits both your customer and business needs.
Data analysis to understand customer behaviour around key products.
PO can master these skills, it will certainly help to become successful.
Each project is unique has its own challenges, so its a matter to make sure PO is ready to face all the challenges and obstacles on the way.
In any situation, if you understand the chain of thought, the challenges and the solution of your counterpart, you will discuss much more empathetically. That helps the team move forward towards the goal.
Love this article, it's all about good communication, making sure your audience fully understand the "customer" painful points and what needs fixing.
Min basic requirement to become a good PO IMO should be to understand how data travels end to end, and how can we use data to build good product (or vice versa, which data do I need in order to build this product).
Task 1 - E.G. get a Json/XML feed from any type of e-commerce business, then be creative enough to design a basic wireframe/mockup that can be used as reference by your UX team, then once you have the designs complete user testing with user personas (paper prototyping will help to validate all user journeys), after this you should have gathered enough information that allows you to refine/improve upon the first iteration.
Task 2 - E.G. Get a wireframe design, build user journeys around it, then try to understand what data will be needed in order to power the product you want to build.
Other tools:
Customer Surveys, understand from various user personas what are the main painful points, if you get multiple feedback around same topic that is a clear evidence that you need to address this customer painful point.
The end goal should be to deliver a product that fits both your customer and business needs.
Data analysis to understand customer behaviour around key products.
PO can master these skills, it will certainly help to become successful.
Each project is unique has its own challenges, so its a matter to make sure PO is ready to face all the challenges and obstacles on the way.
What is your opinion about my comments ?