...until I realized that this thought of mine is based on the naive assumption that people carefully study and consider the knowledge and mistakes made by their predecessors.
I couldn't help wondering why we keep seeing same basic mistakes in the field of project management, user experience design, project management... (you name it) that people did 5, 10, 20 years ago →
I'm not sure if it's only me, but I perceive A\B-testing manly as a tool to gain new information rather than basic "which is better". I mean if "B" variation succeeded but you don't know why, that was a worthless test.
Google seems like a pretty simple app. It’s just a text input box with a bunch of web links as an output. Does it really need more than 10 engineers to maintain?
developers: complaining that there is no documentation of the product
pm: started documenting the product
developers: complaining that the documentation is not good enough
↓↓↓
So if you don't allow your product manager to make a final decision either you prevent her from learning and being a product manager or you are hired wrong person.
It is important to have a product manager as the sole person responsible for the product. By this I mean that this person has the final say in any product decision. Though getting consent and buy-in from all the stakeholders is important, it's product person job to decide.↓↓↓
It's important in two ways:
1. That way product person gains product ownership, which is crucial for the motivation
2. Mistakes made are also owned by product person so she can learn from that (which is much more effective that learning on 'others' mistakes)
↓↓↓
6. You have baseline and target values for metric you've chosen
7. You have live and running dashboard for that metric
8. You have some solution hypothesis formulated
9. You have a reasonable deadline to launch
10. You have a launch plan
Routine keeps me sane during all that hell happened to Ukraine, so I just keep writing posts every day to make a habit ❤️🇺🇦.
Some thought on RICE prioritisation framework (possible) flaws:
↓↓↓
1. You have problem statement
2. Problem statement consists of _problem_ but not a solution
3. You have (any) data supporting your problem statement (not just an opinion)
4. You have you problem quantitatively measured
5. You have formulated metric to monitor
↓↓↓