Want to level up your PRDs? Skip the 50-page spec that spells out every detail of every use case you can imagine.
Instead, give your team space for creativity. When you kick off a project with a PRD, provide plenty of context about the problem, the goal, and the scope, but leave the requirements open-ended enough for the team to explore solutions. That’s how innovation happens.
But where do you put the solution details, you ask? Don’t worry, you can specify the “how” in the UI/UX spec, the technical design doc, and your Jira tickets, after you’ve figured out the right solution to build.
Get my PRD template to write product specs like a pro. www.academyofpm.com/templates?utm_source=youtube&u…
About Sondra:
Sondra has over a decade of product management experience as former Product Lead at Google and Looker, former growth product manager at Upwork, and the first product manager at multiple startups. Here at Academy of Product Management, she shares the lessons she wished for when she started her career in product management. Past companies include Google, Looker, Upwork, CNET, AOL, and lots of startups. Sondra has a Bachelor's degree in Management Science from MIT. She is currently a startup consultant and CEO, founder, and lead instructor here at Academy of Product Management.
Where to find Academy of Product Management:
• Website: www.academyofpm.com/
• Youtube: youtube.com/@academyofpm
• Blog on Substack: blog.academyofpm.com/
• LinkedIn: www.linkedin.com/company/academyofpm
• Instagram: www.instagram.com/academyofpm
• TikTok: www.tiktok.com/@academyofpm
コメント