The document discusses key philosophies of product management, emphasizing a customer-centric approach and the importance of assessing the impact of features. It advocates for breaking down large requests into manageable phases and maximizing output based on customer usage rather than internal processes. Additionally, it highlights the importance of owning features and ensuring proper documentation and user interface design.

1. What Product Management Is Not

2. A few thoughts around the product management perspective. Key philosophies if you will. Amarpreet Kalkat Co-founder & Chief Technologist @ Ciafo

3. Thinking from customer's point of view

4. Thinking from customer's point of view Pool all customer problems as if they were your own and you were the only customer. And then say which one is how important to you.

5. Thinking in terms of impact, not effort.

6. Thinking in terms of impact, not effort. Put a value on every feature request and be ready to trade off one with another. Then put a timeline on the value, and maximize the multiple.

7. Thinking in terms of output, not input. Imagine how your product would be used by customers, not how you would build it. Don’t forget the implications for other teams and stakeholders.

8. Phase the big feature requests.

9. Phase the big feature requests. Tell your PM to break down the problem into smaller sub-problems and phase them in. Apply the learnings from one effort to the next one, its easy to forget good things. Incidentally, that is what agile was supposed to be about.

10. Put a good face to a good solution. For consumer products, it’s the UI. For developer focused products, documentation and rich collaterals is the UI.

11. It is your feature. Own it.

12. It is your feature. Own it. Play the Product Manager for your feature, or your module. Ask the right questions, some of them listed in this slide deck. Do you really do it?

13. In the end…

14. Thanks for dropping by.