-
Notifications
You must be signed in to change notification settings - Fork 10
feat(os): OKR process updates #51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
angelaliu22
wants to merge
2
commits into
flexpa:master
Choose a base branch
from
angelaliu22:update-okr-page
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -1,25 +1,64 @@ | ||||||
# 🚦 OKRs | ||||||
|
||||||
At Flexpa, our mission is to refactor healthcare by connecting applications to identified claims data. | ||||||
At Flexpa, our mission is to refactor healthcare by connecting applications to identified claims data. We recognize the significance of setting clear goals and tracking progress to achieve remarkable results. | ||||||
|
||||||
We recognize the significance of setting clear goals and tracking progress to achieve remarkable results. | ||||||
We rely on OKRs, or Objectives and Key Results, as a simple yet powerful tool for goal-setting, alignment, and performance tracking within our organization. While we acknowledge many companies have instituted OKRs, we at Flexpa have set up a particular process that works for our team at our size. | ||||||
|
||||||
We rely on OKRs, or Objectives and Key Results, as a simple yet powerful tool for goal-setting, alignment, and performance tracking within our organization. | ||||||
## Why have OKRs? | ||||||
We adopted OKRs early on, recognizing the importance of everyone understanding our top priorities and how to measure our impact. We set OKRs at the company and team levels, consistently reviewing our progress and learning from challenges. OKRs serve as a catalyst for meaningful conversations, valuable feedback, and recognition within our teams, enhancing both performance and our company culture. We firmly believe that OKRs, along with regular progress tracking and check-ins, are key factors in our success, and we constantly strive to leverage them even better. | ||||||
|
||||||
While we acknowledge many companies have instituted OKRs, we at Flexpa have set up a particular process that works for our team at our size. | ||||||
By utilizing OKRs, we effectively communicate our vision and strategy, focus on our customers' needs, and establish a culture of transparency and accountability. OKRs motivate us to exceed our own expectations and achieve outstanding outcomes. | ||||||
|
||||||
OKRs help us prioritize what matters most, foster collaboration, stretch our capabilities, and continuously learn and improve. They consist of a few ambitious objectives and measurable key results that indicate progress and success. By utilizing OKRs, we effectively communicate our vision and strategy, focus on our customers' needs, and establish a culture of transparency and accountability. OKRs motivate us to exceed our own expectations and achieve outstanding outcomes. | ||||||
## OKRs at Flexpa | ||||||
At Flexpa, we believe that OKRs are not used as a tool to track individual performance but rather as a means to align collective efforts, foster cross-functional collaboration, and drive organizational success. OKRs are the sole mechanism used to plan work for the quarter at Flexpa. They are collaboratively defined with avenues to contribute towards a goal from every Flexpa team member. Our Product Roadmap serves as a reflection of the quarter’s work towards OKRs as well as a projection of potential future priorities. | ||||||
|
||||||
Objectives represent the outcomes we strive to achieve, embodying the "Whats" of our journey. Key Results outline the measurable steps that pave the way, serving as the tangible "Hows" toward realizing those objectives. Objectives are qualitative and aligned with our mission of refactoring healthcare, while key results are quantitative, specific, and time-bound. We limit top-level objectives to five per quarter to maintain focus and clarity and have no more than five key results per objective. At Flexpa, we believe that OKRs are not used as a tool to track individual performance but rather as a means to align collective efforts, foster cross-functional collaboration, and drive organizational success. | ||||||
Objectives represent the outcomes we strive to achieve, embodying the "Whats" of our journey. Key Results outline the measurable steps that pave the way, serving as the tangible "Hows" toward realizing those objectives. Objectives are qualitative and aligned with our mission of refactoring healthcare, while key results are quantitative, specific, and time-bound. We have a single top-level (Level 1) objective to maintain goal alignment, and no more than five key results (Level 2 Objectives) to maintain focus. | ||||||
|
||||||
At Flexpa, OKRs are scored using [bankers rounding](https://wiki.c2.com/?BankersRounding) to round quantities to integers. The scoring framework ranges from 0.0 to 1.0, where "0" represents failure and "1.0" indicates complete achievement of the objective. Each key result is graded within this framework, and the average score is used to determine the objective's overall score. The scoring system at Flexpa follows these guidelines: | ||||||
## Owning OKRs | ||||||
Each L1 Objective and its corresponding L2 Objectives are assigned a dedicated Flexpal as an Owner. The overall OKR process each quarter is supervised by the owner of the company level Objective. The Owner is not solely responsible for the success of the Objective or Key Result. At Flexpa, we embrace a collaborative approach, and any Flexpal, regardless of their title or role, has the opportunity to be an Owner and contribute to the achievement of the OKRs. | ||||||
|
||||||
### L1 owners are responsible for: | ||||||
* **Process ownership:** The L1 O owner closely monitors OKR progress through the L2 O owners’ weekly updates. The L1 O owner conducts bi-weekly check-ins with Flexpa’s OKR coach to provide teams and individuals with valuable feedback on progress and refine our approach to the process. | ||||||
* **Product leadership:** The L1 O owner needs to maintain understanding of each L2’s surface area. They need to lead L2 Owners towards making changes but need to be empowered to affect change directly as necessary. | ||||||
|
||||||
### L2 owners are responsible for: | ||||||
* **Driving progress and results:** Owners should be planning out milestones and issues in Linear that map out the quarter’s tasks with as much fidelity as is reasonable at any given time. The teammates they rely on should be aware of their dependencies to prioritize individual work accordingly. | ||||||
* **Reassessing goals:** Based on progress through the quarter, owners should be constantly reassessing whether we are pointed at the right target. | ||||||
|
||||||
## Setting OKRs | ||||||
When establishing OKRs, we adopt a scientific approach to avoid setting unattainable goals, where achieving a perfect score seems impossible or unrealistic. OKRs are not static mandates. We evaluate our OKRs to ensure they align with the most important work at Flexpa and adjust them throughout the quarter if necessary. OKRs are scored, and new ones are agreed upon at our quarterly in-person retreat, fostering reflection, alignment, and goal setting. | ||||||
|
||||||
* **0.0 to 0.3**: Red - Indicates that real progress was not made. | ||||||
* **0.4 to 0.6**: Yellow - Represents progress made but falling short of completion. | ||||||
* **0.7 to 1.0**: Green - Signifies successful delivery and achievement of the objective. | ||||||
In writing Objectives and Key Results, we keep these heuristics in mind: | ||||||
* Objectives: | ||||||
* Must articulate a single high leve goal. | ||||||
* May not necessarily be measureable themselves, but can only be successful based on its KRs | ||||||
* Key Results: | ||||||
* Should be guided by the SMART framework: | ||||||
* Specific - Target a well-defined area | ||||||
* Measurable - Have a quantifiable element to serve as an indicator of success | ||||||
* Achievable - Be ambitious but attainable with allocated resources | ||||||
* Realistic - Must be feasible within the contraints of the team's capabilities, time, and other priorities | ||||||
* Time-bound - Have an established deadline for measurement | ||||||
* That track 0-1 workflows or products should consider drafting key results that the team can have the "right to unlock" when progress on preceeding KRs have been achieved. This prevents tracking 0 progress against KRs that we do not have enough information to determine realisticness at the start of the quarter yet. | ||||||
* Should not be "task" oriented without clear articulation a desired outcome to those tasks. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
## Tracking OKRs | ||||||
Within the first two weeks of a quarter, all L2 O owners should draft a written report outlining the tasks they plan to accomplish and accompanying target completion dates for each task. This document provides the company level Objective owner with context into the quarter’s plan and allows them to rapidly triage or ask follow up questions where necessary. | ||||||
|
||||||
L2 owners will report weekly on OKR progress via a written update on Linear, and Loom recordings that are sent to our dedicated Slack channel. We use a color coded system to indicate progress and capacity during these check-ins (see below for details). | ||||||
|
||||||
## Scoring OKRs | ||||||
At Flexpa, OKRs are scored using [bankers rounding](https://wiki.c2.com/?BankersRounding) to round quantities to integers. The scoring framework ranges from 0.0 to 1.0, where "0" represents failure and "1.0" indicates complete achievement of the objective. Each key result is graded within this framework, and the average score is used to determine the objective's overall score. The scoring system at Flexpa follows these guidelines: | ||||||
|
||||||
When establishing OKRs, we adopt a scientific approach to avoid setting unattainable goals, where achieving a perfect score of 1.0 seems impossible or unrealistic. Each Objective and its corresponding Key Results are assigned a dedicated Flexpal as an Owner. The Owner is not solely responsible for the success of the Objective or Key Result. At Flexpa, we embrace a collaborative approach, and any Flexpal, regardless of their title or role, has the opportunity to be an Owner and contribute to the achievement of the OKRs. | ||||||
* **🔴 0.0 to 0.3:** Red | ||||||
* At weekly reporting, this indicates the KR is at risk. We may need significant changes to the goal or resourcing, or we may need to rewrite it altogether. | ||||||
* At the end of the quarter, this indicates that real progress was not made. | ||||||
* **🟡 0.4 to 0.6:** Yellow | ||||||
* At weekly reporting, this indicates the KR needs attention. We may need to look at different tactics to accomplish this, reduce the goal, or get more resources. | ||||||
* At the end of the quarter, this represents progress made but falling short of completion. | ||||||
* **🟢 0.7 to 1.0:** Green | ||||||
* At weekly reporting, this indicates the KR is on track. With current progress, we anticipate to reach a green at the end of this quarter. | ||||||
* At the end of the quarter, this signifies successful delivery and achievement of the objective. | ||||||
|
||||||
We closely monitor OKR progress through weekly updates in our dedicated Slack channel and bi-weekly check-ins to provide teams and individuals with valuable feedback and refine our approach. We use a color code to indicate progress and capacity during these check-ins: green signifies being on track (0.7 to 1.0), yellow represents areas that need attention (0.4 to 0.6), and red indicates being at risk (0 to 0.3). OKRs are not static mandates. We evaluate our OKRs to ensure they align with the most important work at Flexpa and adjust them if necessary. OKRs are scored, and new ones are agreed upon at our quarterly in-person retreat [link], fostering reflection, alignment, and goal setting. | ||||||
We pair the quarterly OKR scores with qualitative learnings as well. These consist of the owner’s takeaways on anything from OKR construction, to reflections on size of the task, to learnings from the work completed. | ||||||
|
||||||
We have embraced OKRs to drive our mission of refactoring healthcare. We adopted OKRs early on, recognizing the importance of everyone understanding our top priorities and how to measure our impact. We set OKRs at the company and team levels, consistently reviewing our progress and learning from challenges. OKRs serve as a catalyst for meaningful conversations, valuable feedback, and recognition within our teams, enhancing both performance and our company culture. We firmly believe that OKRs, along with regular progress tracking and check-ins, are key factors in our success, and we constantly strive to leverage them even better. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.