OKRs
  • About OKRs
  • The market
  • Why build ourselves?
  • Product philosophy
  • Product Decision Record
  • Key milestones
  • Features
    • OKR Unit
    • OKR Views
    • Default Sorting in views and Filters
    • OKR details page
    • Filters
    • Notifications
    • Move and Paste feature
    • Personal Starring ⭐️
    • Due date as an attribute
    • Cloning OKRs to a new quarter
    • Help Section
    • OKR dependency resolution
    • Drag and Drop (Upcoming)
    • Visibility control 🔒
    • Admin Page (Upcoming)
    • Search
    • Sort feature
    • Slack Integration
  • Key Documents
  • Data Strategy
    • Success Metrics
    • Reporting/Metrics Dashboard
  • Program Management
    • Team
    • Working Principles
    • Toolkit
    • Meetings Schedule
    • Product Roadmap
    • Release notes
  • Major links
    • Project Board
    • Design Mockups
    • Feature Discussions Document
    • xto10x Google Drive
    • xto10x Wiki
    • xto10x Slack
    • Staging (OKR tool)
  • Templates
    • Document Template
    • Voice and Tone
Powered by GitBook
On this page
  • Product feature prioritisation
  • Feedback management

Was this helpful?

  1. Program Management

Product Roadmap

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

PreviousMeetings ScheduleNextRelease notes

Last updated 5 years ago

Was this helpful?

Product feature prioritisation

Prioritisation framework is as follows:

Questions to ask while evaluating business value

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

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

Drive alignment basis above