Discover Tability AI: the AI platform that helps you drive OKRs, strategies and metrics

3 OKR examples for Monolith

What are Monolith OKRs?

The Objective and Key Results (OKR) framework is a simple goal-setting methodology that was introduced at Intel by Andy Grove in the 70s. It became popular after John Doerr introduced it to Google in the 90s, and it's now used by teams of all sizes to set and track ambitious goals at scale.

Creating impactful OKRs can be a daunting task, especially for newcomers. Shifting your focus from projects to outcomes is key to successful planning.

We have curated a selection of OKR examples specifically for Monolith to assist you. Feel free to explore the templates below for inspiration in setting your own goals.

If you want to learn more about the framework, you can read our OKR guide online.

Building your own Monolith OKRs with AI

Using Tability AI to draft complete strategies in seconds

While we have some examples available, it's likely that you'll have specific scenarios that aren't covered here.

You can use Tability's AI generator to create tailored OKRs based on your specific context. Tability can turn your objective description into a fully editable OKR template -- including tips to help you refine your goals.

See it in action in the video below 👇

Using the AI generator, you can:

  • Chat with an AI to draft your goals
  • Ask questions or provide feedback to refine the OKRs
  • Import the suggestion in an editor designed for goal setting
  • Switch back to a goal-tracking view in 1-click

Try Tability AI

Using the free OKR generator to get a quick template

If you're just looking for some quick inspiration, you can also use our free OKR generator to get a template.

Unlike with Tability, you won't be able to iterate on the templates, but this is still a great way to get started.

Our Monolith OKRs examples

You'll find below a list of Objectives and Key Results templates for Monolith. We also included strategic projects for each template to make it easier to understand the difference between key results and projects.

Hope you'll find this helpful!

1OKRs to successfully transition from monolith to microservices architecture

  • ObjectiveSuccessfully transition from monolith to microservices architecture
  • KRImplement the new architecture in a test environment and ensure 98% uptime
  • TaskRecord and resolve any occurring downtime issues
  • TaskMonitor and maintain a 98% uptime
  • TaskSet up new architecture in a test environment
  • KRDevelop and document a detailed migration plan by week 4
  • TaskBegin drafting migration plan documentations
  • TaskDetermine the timeline and needed resources
  • TaskIdentify applications, services and data for migration
  • KRSuccessfully migrate 75% of application modules to microservices architecture
  • TaskPrioritize modules based on dependencies and business needs for migration
  • TaskBegin progressive implementation of migration, monitoring progress continuously
  • TaskDevelop a comprehensive microservices migration strategy and blueprint
Tability

2OKRs to execute effective decoupling of legacy monolith system

  • ObjectiveExecute effective decoupling of legacy monolith system
  • KRReduce number of monolithic components by 30% using microservices architecture
  • TaskIdentify monolithic components viable for redesign into microservices
  • TaskImplement and test newly created microservices
  • TaskDevelop microservices replacing identified monolithic components
  • KRAchieve 90% functionality in new services, ensuring business continuity without interruptions
  • TaskImplement regular maintenance and updates schedule
  • TaskDevelop comprehensive testing procedures for new services
  • TaskInitiate contingency planning for potential disruptions
  • KRTrain 75% of the software team in modular programming languages for maintenance
  • TaskSchedule and implement comprehensive training sessions
  • TaskEvaluate and measure progress after training
  • TaskIdentify team members lacking modular programming skills

3OKRs to externalize authorization models from monolith

  • ObjectiveExternalize authorization models from monolith
  • KRIdentify and list all authorization models by Week 2
  • TaskFinalize and submit the list by Week 2
  • TaskResearch various types of authorization models
  • TaskCatalogue each identified authorization model in a list
  • KRSuccessfully migrate at least 90% of authorization models to the external component by Week 10
  • TaskMap current authorization models to the external component
  • TaskDevelop a detailed migration plan
  • TaskExecute migration and verify success rate
  • KRDesign and develop a separate external component for authorization models by Week 6
  • TaskIdentify necessary features for authorization component
  • TaskDesign a prototype of the authorization component
  • TaskDevelop and test the authorization component

Monolith OKR best practices

Generally speaking, your objectives should be ambitious yet achievable, and your key results should be measurable and time-bound (using the SMART framework can be helpful). It is also recommended to list strategic initiatives under your key results, as it'll help you avoid the common mistake of listing projects in your KRs.

Here are a couple of best practices extracted from our OKR implementation guide 👇

Tip #1: Limit the number of key results

Focus can only be achieve by limiting the number of competing priorities. It is crucial that you take the time to identify where you need to move the needle, and avoid adding business-as-usual activities to your OKRs.

We recommend having 3-4 objectives, and 3-4 key results per objective. A platform like Tability can run audits on your data to help you identify the plans that have too many goals.

Tip #2: Commit to weekly OKR check-ins

Having good goals is only half the effort. You'll get significant more value from your OKRs if you commit to a weekly check-in process.

Being able to see trends for your key results will also keep yourself honest.

Tip #3: No more than 2 yellow statuses in a row

Yes, this is another tip for goal-tracking instead of goal-setting (but you'll get plenty of OKR examples above). But, once you have your goals defined, it will be your ability to keep the right sense of urgency that will make the difference.

As a rule of thumb, it's best to avoid having more than 2 yellow/at risk statuses in a row.

Make a call on the 3rd update. You should be either back on track, or off track. This sounds harsh but it's the best way to signal risks early enough to fix things.

How to track your Monolith OKRs

Your quarterly OKRs should be tracked weekly in order to get all the benefits of the OKRs framework. Reviewing progress periodically has several advantages:

  • It brings the goals back to the top of the mind
  • It will highlight poorly set OKRs
  • It will surface execution risks
  • It improves transparency and accountability

We recommend using a spreadsheet for your first OKRs cycle. You'll need to get familiar with the scoring and tracking first. Then, you can scale your OKRs process by using a proper OKR-tracking tool for it.

A strategy map in TabilityTability's Strategy Map makes it easy to see all your org's OKRs

If you're not yet set on a tool, you can check out the 5 best OKR tracking templates guide to find the best way to monitor progress during the quarter.

More Monolith OKR templates

We have more templates to help you draft your team goals and OKRs.