Product Roadmap
This page highlights the way we will build our Product Roadmap once we have launched Beta.
Last updated
Was this helpful?
This page highlights the way we will build our Product Roadmap once we have launched Beta.
Last updated
Was this helpful?
Prioritisation framework is as follows:
What stage of the OKR process does it cater to - Setup, manage and review?
This is helpful because we also want to solve the use-cases of the decision maker/ buyer persona who would be running the OKR process along with the enhancement to the basic functionality.
How many times will it be used? (Used once but by many or used by one but multiple times)
One person using throughout the quarter? COS while running check-ins. (Review of OKRs) Or all regular users using it one or twice a quarter in set-up? (Eg: re-ordering of KR's) Change of quarter - used mostly end of quarter by all
Does it provide a 10x shift in experience or does it 10x my chances of acquiring new customers?
Everything that we do should fall in either of the two above mentioned buckets. If it doesn't, we aren't solving the right problems
Capture/ collate feedback at one place. We will use our current Monday board for collating feedback.
Use above mentioned framework to decide priority of various problems.
Brainstorm to get multiple solutions for the identified problem
Consensus building -> Commit to solution
Design and documentation for the committed solution
Delivery to Engineering before the sprint planning meeting