Hi everyone, kicking off this thread to create an index of each teams OKRs and their prep location + create a lever to help everyone define their best OKRs yet.
OKRs Index
- OKR Final Locations
- OKR WIP Locations
Understand what we are optimizing for
One of the things that is crucial for continuous healthy growth of the project and nailing the right OKRs is actually understanding what needs to be achieve to fulfill use-cases and user needs.
We've done some work in the past to document a share understanding of what these needs and users are (applications of IPFS & Design IPFS Roadmap by use case & IPFS User Registry). However, most of the actual needs continuous to be tribal knowledge, only know by a few of the WG Captains or the more active and public facing contributors of IPFS. We need to change that.
Me and @steverichmond are working on a rubric to help WG Captains and Participants document it in a standard way. Meanwhile, there are already a set of questions you can answer and share with the rest of your team. These are:
- What are your top users/applications on top of the part of the project you contribute and/or lead?
- What are their next goals? How can your project help them be successful?
- What are the main blockers for adoption of your project?
- What are the main blockers for contribution to your project?
- Name the most important thing you and your team need to achieve? What is the timeline for that? What could be done to achieve that in less than three months (Hiring, Partnerships, Drop other tasks, etc)?
In the past, this information was propagated because we had the chance to write the OKRs together in the same location. Now that we do the planning Async and Distrbuted, it is up to the teams to gather this information proactively.
Leverage growth - Communicate to each team what are your needs
In the same way, there are now dependencies between IPFS/libp2p/IPLD teams. Examples are: js-ipfs needs js-libp2p and js-ipld; DDC needs GraphSync from IPLD; Web Browsers have needs from js-ipfs.
Consider the dependents as consumers/users of your project and gather their needs as well. You shouldn't be planning something that requires something that is impossible to achieve this quarter by another team.
Hi everyone, kicking off this thread to create an index of each teams OKRs and their prep location + create a lever to help everyone define their best OKRs yet.
OKRs Index
Understand what we are optimizing for
One of the things that is crucial for continuous healthy growth of the project and nailing the right OKRs is actually understanding what needs to be achieve to fulfill use-cases and user needs.
We've done some work in the past to document a share understanding of what these needs and users are (applications of IPFS & Design IPFS Roadmap by use case & IPFS User Registry). However, most of the actual needs continuous to be tribal knowledge, only know by a few of the WG Captains or the more active and public facing contributors of IPFS. We need to change that.
Me and @steverichmond are working on a rubric to help WG Captains and Participants document it in a standard way. Meanwhile, there are already a set of questions you can answer and share with the rest of your team. These are:
In the past, this information was propagated because we had the chance to write the OKRs together in the same location. Now that we do the planning Async and Distrbuted, it is up to the teams to gather this information proactively.
Leverage growth - Communicate to each team what are your needs
In the same way, there are now dependencies between IPFS/libp2p/IPLD teams. Examples are: js-ipfs needs js-libp2p and js-ipld; DDC needs GraphSync from IPLD; Web Browsers have needs from js-ipfs.
Consider the dependents as consumers/users of your project and gather their needs as well. You shouldn't be planning something that requires something that is impossible to achieve this quarter by another team.