Gno OKR 24S1

Guidelines for Setting Your Individual OKRs (Jan-Jun):

1. Review OKRs: Start by understanding the team and key members' current OKRs.
2. Align Your OKRs: Make sure your OKRs match the team's main goals.
3. Choose Your OKR Type: Pick between specific, tough, achievable OKRs (like porting 10 stdlib packages) or broader goals (like improving developer experience). It's better to have measurable OKRs.
4. Bonus Based on Performance: Your bonus depends on how well you meet your OKRs, as judged by your manager. Talk to your manager to make sure you both agree on what the OKRs mean.
5. Review Process: In 6 months, your manager will review your performance. They'll check if you met, exceeded, or didn't meet your OKRs. For broader goals, your manager will see if you put in enough effort.
6. How Your Bonus Works:
   • 2/3 of your bonus is based on your personal OKRs.
   • 1/3 is based on team OKRs, split between team tasks and individual goals.
7. Working on Side Projects: You can spend up to half your time on side projects. These can count for up to 20% of your OKRs if they help the main project and your manager agrees. But, at least 80% of your OKRs should be about the team's goals.
8. Balancing Tasks: Mix big, important tasks with regular ones (chores) to share work fairly.
9. Deadlines and Help: Remember the deadlines and ask Mig if you need help.
10. Forced OKRs: All engineers (core team, DevRel, and Tokenomics) must include the 'O5: Core Team Alignment Tasks' as mandatory individual objectives in their respective OKR documents.
11. Note for European Core Team: Management Change: Milos will start leading most of the European team in January. Milos and I will first check your OKRs in two weeks. After that, Milos will be in charge of your 6-month review.

Deadlines:

• November 24: Distribution of current team and managers' OKRs along with instructions.
• December 1: Submit your proposed OKRs to your manager for initial discussion and refinement.
• December 8: Managers to finalize, approve, and submit OKRs to HR.

Resources:

Draft: https://miro.com/app/board/uXjVMyjw-pI=/

Gno Core International (top-level OKRs)

• O1: Launch Preparation

  • KR1: Complete all critical launch tasks to launch in Q2.
  • KR2: Execute testnets (Gnolang, TM2/Multinode, launch RC) and resolve issues promptly.

• O2: Ensure Stability and Security

  • KR1: Achieve zero critical vulnerabilities and pass security audits.
  • KR2: Attain 90% code coverage for critical components, and 70% overall.
  • KR3: Enhance testing (CI/CD), with less than 10% new code bugs and a 2-week SLA for critical bug fixes.

• O3: Streamline Development and Documentation

  • KR1: Simplify development processes for Gophers to publish first contracts in hours.
  • KR2: Boost compatibility with the Go language and support for clients and tools.
  • KR3: Develop comprehensive developer documentation, examples, and tooling.
  • KR4: Enhance the report and documentation regarding ongoing complex subjects such as Tokenomics, WorxDAO, and PoC.

• O4: Boost Growth and Awareness

  • KR1: Develop and release a Gnolang interpreter for the terminal without using blockchain technology. Aim to attract and engage the Gopher community. (Q1)
  • KR2: Implement and optimize on-chain project management for essential processes.
  • KR3: Implement Evaluation DAO, Application Process for GoR.
  • KR4: Publish at least one technical blog post monthly.
  • KR5: Promote internal use of smart contracts and enhance community engagement.

• Ox: Core Team Alignment Tasks (forced individually)
  • KR1: Each team member to deploy one examples/ contract per semester.
  • KR2: Each member contributes to or writes a technical blog post per semester.
  • KR3: Participate in PR/issue reviews and maintain project awareness.
  • KR4: Organize one workshop per semester on their area of expertise.

Manfred (Transversal Engineering)

• O1: Foster Education and Strategic Thinking

  • KR1: Develop comprehensive educational materials for project standards and philosophy.
  • KR2: Host strategy workshops to align team efforts with long-term objectives.
  • KR3: Delegate management tasks to empower teams and scale operations.
  • KR4: Create a mentorship program to nurture strategic thinking skills.

• O2: Architectural Planning and Team Enablement

  • KR1: Design a scalable architecture for the GovDAO and associated DAOs.
  • KR2: Establish self-sufficient teams for each DAO with clear strategic plans.
  • KR3: Implement systems to enhance team autonomy and inter-DAO collaboration.
  • KR4: Foster a culture of continuous learning and improvement within teams.

• O3: Simplify and Communicate Complex Concepts

  • KR1: Regularly update architectural frameworks with a focus on simplicity.
  • KR2: Maintain a living library of easily understandable technical documentation.
  • KR3: Organize knowledge-sharing sessions to demystify complex development topics.
  • KR4: Curate a repository of explanations for complex topics to support ongoing education.

• O4: Strategic Execution and Process Optimization

  • KR1: Collaborate with teams to refine strategies and streamline processes.
  • KR2: Align daily operations with strategic objectives and delegate effectively.
  • KR3: Develop tools and frameworks to support strategic decision-making.

• O5: Visionary Coding and Project Roadmapping

  • KR1: Code key components that translate vision into reality.
  • KR2: Document and communicate a clear, actionable project roadmap.
  • KR3: Gather and integrate community feedback to ensure the roadmap's relevance.
  • KR4: Lead by example in coding practices, setting a benchmark for quality and innovation.

Milos (European Manager)

• O1: Ensure alignment between the EU engineering team and top stakeholders
  • KR1: Implement a process that ensures transparent and efficient performance reporting of team efforts, which fosters alignment on a per-quarter basis with the vision and community.
  • KR2: Categorize and gather all engineering pain points (project-level), and develop action plans for tackling each within the span of a month.
  • KR3: By end of January develop a personalized support system that includes regular team member check-ins bi-weekly and allocates 20 hours a month from my schedule to assist team members in achieving their individual OKR goals. Target 80% completion rate of personal OKRs across the team for the current measurable period (January - June).
  • KR4: Foster and organically nurture a growing team culture, by hosting meetups and joint activities / efforts.
• O2: Ease main-net development efforts
  • KR1: Implement a live node sync protocol, along with a better way to backup blockchain data locally.
  • KR2: Implement a robust debugging framework for the Gno node (includes logger rework, data extractors, new endpoints…).
  • KR3: Develop a framework for measuring code performance progress over time, including benchmarking, tool development, and implementing tracers and metrics systems to track and enhance code performance.
• O3: Improve the TM2 experience
  • KR1: Implement a feature-rich data indexer that can be used by users and development teams for local or remote chains.
  • KR2: Lead comprehensive refactoring and optimization efforts on critical code segments such as the Tendermint 2 consensus engine and protocol to improve performance and efficiency.
  • KR3: Refactor and redesign the RPC API for the TM2 node, in regards to making client implementations cleaner.

Ray (US Team)

• O1: Main luanch, align with Core Team O1 and O2

  • KR1: Successfully launch the main testnet, including the chain rollback and upgrade process.
  • KR2: Complete one end-to-end contract application that demonstrates the top three core features of Gno.land.
  • KR3: Establish a baseline and identify the bottlenecks in the performance of main testnet, including the Gno VM and Tm2.
  • KR4: Establish a baseline and fine-tune the gas assumption model on the main testnet.

• O2: Attraction and growth, align with Core Team O3 and O4

  • KR1: Establish a funnel and define metrics to measure the attraction to Gno and gno.land.
  • KR2: Increase the contributor engagement.
  • KR2: Increase awareness of Gno among Go developers and those interested in developing smart contracts.

Upcoming TPM (International Project Manager)

• O1: Project Management Excellence

  • KR1: Audit the existing things, and build a clear plan.
  • KR2: Process the project inboxes (issues, PRs, etc) and keep the plan up to date.
  • KR3: Develop and manage project timelines for on-time delivery.

• O2: Cross-Team Collaboration & Reporting

  • KR1: Facilitate collaboration between DevRel, Marketing, and Engineering teams.
  • KR2: Work with managers to ensure allocation and monitoring of project resources effectively.
  • KR3: Maintain clear communication and provide regular project updates to team members.
  • KR4: Create a high-level project management plan for the ecosystem, considering the existing partners.
  • KR5: Simplify the backlog and changelog to enhance community comprehension.

• O3: Risk Mitigation and Project Success

  • KR1: Identify and address project risks to ensure successful outcomes.
  • KR2: Monitor project progress and proactively mitigate potential delays.
  • KR3: Maintain high-quality project deliverables and address performance issues promptly.

• O4: Process Improvement

  • KR1: Contribute to improving project management processes and workflows.
  • KR2: Streamline project management practices to enhance efficiency.
  • KR3: Foster a culture of continuous improvement and knowledge sharing.