Product Roadmap

This page highlights the way we will build our Product Roadmap once we have launched Beta.

Product feature prioritisation

Prioritisation framework is as follows:

Drive alignment basis above

Questions to ask while evaluating business value

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.

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

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

Feedback management

  1. Capture/ collate feedback at one place. We will use our current Monday board for collating feedback.

  2. Use above mentioned framework to decide priority of various problems.

  3. Brainstorm to get multiple solutions for the identified problem

  4. Consensus building -> Commit to solution

  5. Design and documentation for the committed solution

  6. Delivery to Engineering before the sprint planning meeting

Last updated

Was this helpful?