Finest-5 Product reads #32
Finest-5 Product reads #32
Roadmaps, feature success and other reads..
Hey,
I was going over some tools yesterday and realised: To make life a little easy every time; I have learned so many of them. An added advantage of working as a product manager, I can flaunt some tools.
Every week, I summarise the best reads from 100+ articles with the sole purpose of helping you become better at product with minimal effort. Subscribe!!
5 Ways to Convince Your Boss Product Roadmaps Don’t Need Deadlines
Having strong roadmaps provides a sense of safety to management, but does it do more harm than good? Is a good argument to be made depending on the team.
Key Takeaways:
Either the team will not do stuff on time, or they’re adding so much buffer that the entire team is operating less effectively than it could.
Team could rush through builds to meet a deadline, delivering a poorer quality product
You’re spending tons of time doing project management work
How to Design Scannable App Screenshots
App Screenshots on stores are sometimes the key value for decision making when a person decides whether to install an application.
Key Takeaways
It takes an average of 7 seconds for a user on the App Store to decide whether they want to download your app or not.
We consistently observed that fewer than 4% of users looking for an app enlarge portrait screenshots, and only 2% enlarged landscape screenshots
Only 9% of users scroll past the first two screenshots. Explain the most important user story of your app in the first two screenshots.
7 Steps to Measuring the Success of a Feature
Measuring the success of a feature is not just a simple metric tracking. There are a lot of other metrics to be tracked systematically to do final analysis.
Key Takeaways
Understand what users are doing right before using the feature
Build a behavioural cohort of people who used the feature to analyse how they compare to your overall user population
Analyse the impact of the new feature on retention, funnel and engagement
The ‘Jobs-to-be-Done’ (JTBD) Framework
At the place of building for features, if the team builds for the buyer, the added value will be very high. JTBD framework helps to use a mechanism to align the team to the user outcome of the product.
Key Takeaways
With JTBD, the idea is to understand what a customer actually wants to get done with the product they are buying.
Here’s a way to construct JTBD statements. The ‘equation’ is: When need(s) [situation], +I/he/she/they want(s) to [motivation], +so that [desired outcome]
People hire your products instead of purchasing them.
Growth Isn’t Happening: What Now?
Growth is not simple marketing, but a factor of so many factors and if it is not happening, one needs to take a step back and look at everything again.
Key Takeaways
The optimizations you were trying to do were just band-aids and won’t solve the root cause of it all.
To not see a lack of growth as a marketing problem (that is one of the main reasons I strongly claim Growth isn’t Marketing).
Often the problems that arise result from not doing enough initial research to truly understand your customer and figure out these matches
Product of the week: Gather
Gather makes spending time with your communities just as easy as real life