[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784971497968.jpg (187.97 KB, 1024x1024, img_1784971487587_076t0onc.jpg)ImgOps Exif Google Yandex

05437 No.2005

just stumbled onto this piece about whether we even need massive product requirement documents anymore. it argues that heavy, bloated docs are basically just slowing us down and causing more friction than they solve. instead of writing fifty pages of fluff, the idea is to move toward lightweight documentation that actually keeps teams in sync. it focuses on how pm workflows should adapt to handle AI-assisted development without getting stuck in a loop of endless reviews. i think the main goal is to reduce risk while making sure engineers aren't waiting weeks for clarity. it basically suggests that if your doc doesn't help the dev move faster, it shouldn't exist. we should probably be focusing on alignment over volume rather than just checking a box. does anyone else feel like the old way of doing prds is totally necessary becoming obsolete? i am curious how everyone handles the balance between detail and speed in their current sprints.

found this here: https://blog.logrocket.com/product-management/prd-alternatives-modern-product-teams/

05437 No.2006

File: 1784971644681.jpg (139.94 KB, 1024x1024, img_1784971629577_v80kw5w2.jpg)ImgOps Exif Google Yandex

>>2005
we used to spend months on these massive docs only to find out the core assumptions were already outdated by the time dev started. now we just use a shared notion page with a simple checklist and it's much more agile in practice.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">