The Nodejs.dev project uses Objectives and Key Results to provide direction and guidance to the work we do, enabling our work and the work of our initiatives to have a north star for us to work towards.

OKRs consist of two elements:

• Objectives
  • Objectives are qualitative, ambitious, and memorable definitions of the things we as a committee would like to achieve.
• Key Results
  • Key Results are a set of metrics by which we can measure progress toward their objectives. Like objectives, they should be ambitious and overestimate what we can accomplish.

Here are some external references that may help provide further context on OKRs.

• Guide: Set goals with OKRs
• What is OKR?
• What Are OKRs? How to Use OKRs for Planning (and Achieving) Your Goals

• Objective: Continuity of process

  • Key Result: Staging and CI each have a published technical administration summary and a how-to guide.
  • Key Result: Consider using issue templates to facilitate operations.

• Objective: Identify areas of progress and future goals

  • Key Result: Create a feature roadmap
  • Key Result: Track features & priorities in one place (project?)
  • Key Result: Make available the top two features in nodejs.org:
    1. Docs — https://nodejs.org/en/docs/
    2. Download — https://nodejs.org/en/download/

• Objective: Make explicit the channels of interfacing internally and with larger org

  • Key Result: Write down implicit team norms
  • Key Result: How do we propose and review non-feature changes in PRs?