Jira Tickets? Well, no!
Everybody thinks product managers should master writing issues on Jira. But that's actually wrong and I'll prove you why.
The Jira-only product org
Some product organizations make the mistake of skipping one of the most crucial parts of a good PM process - developing a strong product thesis. Instead, they jump straight into implementation without fully understanding the “why”. This is a bad practice. No ticket should be written before the product manager has convinced their team of the importance and relevance of the task at hand - WHY THIS, WHY NOW. Product managers should spend at least 50% of their time solidifying their product thesis. This can be achieved through user interviews, market research, competitor analysis, and data review. The stronger your “why” is, the better your team will work together.
Alignment wins.
Once you have conviction on what’s next for your product, you can start breaking things down. But don’t jump straight into writing tickets just yet. First, develop a clear PRD and create a “Fat Marker Wireframe”.
Only after you have a clear “why,” a well-defined PRD, and an agreed-upon wireframe, should you start talking about tickets.
Now that you have a clear WHY, a clear PRD and a clear and agreed-upon wireframe, only now we can start talking about tickets.