3/15/2024 0 Comments The pathless androidTo accomplish this, I believe the best specs provide critical context across these 5 sections:ġ️⃣ The Opportunity - This section should explain not just what the problem you’re solving with this feature is, but also why you are prioritizing building it in the first place.Ģ️⃣ Target Audience - This section should detail who exactly you are building this feature for. This is where we need to invest more in our product specs, giving the team the context they need to empower them to make well-informed decisions. But to truly enable your designers & engineers to make these decisions, they need to have the appropriate product context to make informed calls. The best product specs empower designers & engineers to make a ton of micro-decisions about the product themselves, leaving PMs to focus on the most critical decisions. Light specs do save PMs time up-front, but ultimately result in PMs spending significantly more of their time going back and forth with design & engineering in messages, meetings, and tickets, leaving PMs feeling even more overwhelmed. While I certainly don't want to go back to my Microsoft days, I honestly think we've swung too far in the direction of light specs. During my career, I've seen a huge shift in product specs from being long 30+ page documents I regularly wrote in my Microsoft days to specs now containing little more than annotated screens.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |