Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions OKR.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# Nodejs.dev Objectives and Key Results

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.

## Key Concepts
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call including a OKR brief.


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.

### External References

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

- [Guide: Set goals with OKRs](https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/introduction/)
- [What is OKR?](https://felipecastro.com/en/okr/what-is-okr/)
- [What Are OKRs? How to Use OKRs for Planning (and Achieving) Your Goals](https://plan.io/blog/what-are-okrs/)

## OKRs (2020 Set 1):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, I'm +1 for the OKRs listed here. Great capture of what we had discussed!

I would recommend framing the KRs as results rather than actions.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for results


- **Objective:** Continuity of process

- **Key Result:** Staging and CI have 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?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I seem to misunderstand the discussion. Is this about using PRs to propose changes instead of Issues? If so, what friction are we looking to solve?