But there is 'NO' small change
Deepak Paripati
Head of Customer Success @ Nektar.ai | Scaling Customer Success for Growth | Passionate Builder, Operator & Leader
As a user of many products, I always used to comment and discuss on why is ABC not building this feature!
"Do they have such a dumb product team ?"
"Are they even listening to its customers ?"
"The company seems to be killing its product !"
One such feature, I always wished to have on LinkedIn's mobile app is, a filter to see Applied jobs, jobs Viewed but not Applied, and New jobs i.e. not Seen or Applied. And I have heard about this requirement from many avid users of the app, and commented as above.
Isn't this a small change ?
Definitely a No, when you think like a product manager. Because, Product Manager thinks on the difference a feature can be bring to the user through the product, rather than just the small change.
And may be the technical folks reading this, about the above requirement, might feel it is just about a small piece of code, but product managers have a huge list of questions to ask.
On the same example above, let's start with a few questions as a LinkedIn Product Manager,
- What happens when a job post one had applied has been removed?
- Where to show the status of a job?
- What are the different filters to be used?
- Should the filters to be tabs or check boxes or radio buttons?
- How should the search results be shown? In one page or multiple-pages?
- What is the default order the search results should be displayed? Applied date or Viewed date or Job posted date?
- If there are 0 search results, what should the message be?
and more, more and more...
The bigger picture is the documentation on the feature, the customer support being prepared on the same, handling of previously applied or seen posts etc.
And once we are done with all this, you will have a feature in place and it is about filtering of jobs by status like Applied, Seen and New.
Does this requirement still seem to be small as it seemed to be in the beginning? And that's the exact reason, a product manager understands and thinks so much detail about a product feature before saying a dumb 'YES' and before adding it to the roadmap.
These above mentioned is the way a quality product team takes to build a quality feature that adds value to its product in return to its users.
The above is just an example from my learning and experience of product management. I do not represent LinkedIn product management; while just a user thinking from the shoes of Product Management.?