📄️ Intro
One of the most common startup mistakes is prioritizing software development over effective product management. Should your investment go into building code that can be clicked, or should it be directed towards defining a product strategy that will connect with an audience?
📄️ The Product Vision
📄️ Prioritisation features
From my experience, this is the most important section of this handbook. What is being worked on now HAS to be the thing that is more likely to turn the product into something people want. There should be no other feature that people are more keen to see.
📄️ User Experience in practice for softare engineers
![Image](https://media.licdn.com/dms/image/v2/D4E22AQGlPeFZUlL2w/feedshare-shrink800/feedshare-shrink800/0/1697180706305?e=1730332800&v=beta&t=zhKXqyHCKkIBQpb2QBqlwUvlODlNo6B7CK
📄️ Define user flows
Decide how the prototypical user flows to a particular feature and the interactions they do to complete that.
📄️ Wireframes
Learn basic figma or pen + paper
📄️ User Stories
Just enough detail to get the job done.
📄️ The "Jobs to be Done" (JTBD) Framework
In product management, the concept of "Jobs to be Done" (JTBD) refers to a framework that helps teams understand the underlying needs and motivations of customers when they seek a product or service. It shifts the focus from demographic information or product features to the specific "job" the customer is trying to accomplish.
📄️ How do we know a ticket is done?
- It fulfills the acceptance criteria.