top of page
Writer's pictureSwarna Hebbar

Your Product Requirements should be a Workflow, not a document

Alan sat to write his product requirements document. After spending 2 weeks on it & making sure that he has covered all his user scenarios along with his designer, he added his developers to the document.

Brenda, the engineering manager & Alan got on 4–5 calls over the next 2 weeks. After a high level thumbs up, Alan got the green signal to start handing this off to his tech team.

Alan would now spend a couple of days copy pasting these features to Jira tickets, grooming his backlog, setting priorities etc. All this prep before the next sprint cycle.


For the next sprint cycle, Alan spent 3 hours with his tech team, individually assigning tickets to each member.

2 days after sprint planning:

Hey Alan! Jamie here. Just wanted to call out that the sorting of values cannot be done without backend effort.

Hey Jamie! That’s a bummer. Can we just have a default sorting in that case?

Sure!

Cool, thanks Jamie.

Scroll, scroll, click, close, scroll, scroll.. After 10 minutes of scrolling, Alan finally finds the Jira ticket assigned to Jamie and makes changes to it.

Done!



3 weeks go by:

Hey Maurice, why hasn’t the dashboard feature been pushed to the test website yet?

Hey Alan, there are a couple of failure points when I test. Sorting isn’t working as it should.

We decided to scrap sorting, don’t need that feature!

Oh really? your PRD still states that feature with a high priority mention though!

Alan’s pulse rose quickly. 2 weeks of feature delay because he missed updating his PRD.

Product Managers own many many many things. They own requirements, handoff process, team collaboration, negotiation, customer success, customer feedback, business bottomline considerations. You name it.


Adding to the juggle, is the stress of managing these across multiple platforms, and worse still, highly customisable platforms that require PMs to do the added work of personalising them to their workflow.

Everything starts with Product Requirements. But with Google docs / Microsoft Docs, this is the first & most disconnected step in the workflow.


At Boggl.ai, we aim to make the life of PMs a little easier by upgrading Product Requirements from a mere document to a Microapp that can be integrated into any workflow.


Because, whether it be personas, project management, metrics, customer success, roadmap planning, feature launch planning, everything starts with product requirements.



10 views0 comments

Yorumlar


bottom of page