Build Your Product Vision with Jira Cards
A Jira card is a placeholder for a conversation. Product requirements are glorified meeting notes.
I use the term Jira card, but as we know there are a zillion project management tools out there: Trello (which is owned by Jira), Asana, Azure DevOps (prev VSTS), Monday, Notion, Airtable, etc. The tool isn’t what matters, how teams use them to maintain the home base of product requirements, discussion notes, whiteboard takeaways, and new directions is. I’ll refer to them as Jira cards.
A Jira card is a microcosm of a product manager. PM’s are the glue in product development teams–acting as a conduit, communicator, prioritizer (/deprioritizer), and collaborative problem solver. Designers deliver wireframes, mockups and high res designs. Engineers deliver clean, scalable, tested code. You know when deliverables are effective. Product managers deliver…effective teams, processes and applications for users. Product done well can supercharge a team, delight users, hit KPIs, prevent late nights, enable teammates to take PTO and make it possible to commit to customer deadlines months in advance. Product done poorly….doesn’t do any of the above–which is very expensive.
Let’s fist double click on what a product manager does. Knowing no two teams and products are the same, your purpose as a PM is to help your team ship the right…
