Get Tability: OKRs that don't suck | Learn more →

1 OKR example for Newly Formed Teams

Turn your spreadsheets into OKR dashboards with Tability

Tability is a cheatcode for goal-driven teams. Set perfect OKRs with AI, stay focused on the work that matters.

What are Newly Formed Teams 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.

OKRs are quickly gaining popularity as a goal-setting framework. But, it's not always easy to know how to write your goals, especially if it's your first time using OKRs.

To aid you in setting your goals, we have compiled a collection of OKR examples customized for Newly Formed Teams. Take a look at the templates below for inspiration and guidance.

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

The best tools for writing perfect Newly Formed Teams OKRs

Here are 2 tools that can help you draft your OKRs in no time.

Tability AI: to generate OKRs based on a prompt

Tability AI allows you to describe your goals in a prompt, and generate a fully editable OKR template in seconds.

Watch the video below to see it in action 👇

Tability Feedback: to improve existing OKRs

You can use Tability's AI feedback to improve your OKRs if you already have existing goals.

AI feedback for OKRs in Tability

Tability will scan your OKRs and offer different suggestions to improve them. This can range from a small rewrite of a statement to make it clearer to a complete rewrite of the entire OKR.

Newly Formed Teams OKRs examples

You'll find below a list of Objectives and Key Results templates for Newly Formed Teams. 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!

OKRs to drive Agile and Scrum adoption across teams

  • ObjectiveDrive Agile and Scrum adoption across teams
  • KRImplement Agile and Scrum in 5 teams with an 80% adherence rate
  • TaskAssign a Scrum Master for each team
  • TaskProvide Agile and Scrum training to all team members
  • TaskMonitor progress and enforce 80% adherence rate
  • KRAchieve 95% satisfaction rate for Agile and Scrum training sessions
  • TaskUpdate and improve training curriculum based on feedback
  • TaskImplement post-training evaluations to gather participant feedback
  • TaskProvide extra support for participants struggling with the material
  • KRTrain 10 teams on Agile methodologies and Scrum framework
  • TaskSchedule follow-ups to assess understanding
  • TaskIdentify the experienced trainers in Agile and Scrum methods
  • TaskAllocate distinct training sessions for each team

Newly Formed Teams 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

The #1 role of OKRs is to help you and your team focus on what really matters. Business-as-usual activities will still be happening, but you do not need to track your entire roadmap in the 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

Don't fall into the set-and-forget trap. It is important to adopt a weekly check-in process to get the full value of your OKRs and make your strategy agile – otherwise this is nothing more than a reporting exercise.

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.

Save hours with automated OKR dashboards

AI feedback for OKRs in Tability

The rules of OKRs are simple. Quarterly OKRs should be tracked weekly, and yearly OKRs should be tracked monthly. Reviewing progress periodically has several advantages:

Spreadsheets are enough to get started. Then, once you need to scale you can use Tability to save time with automated OKR dashboards, data connectors, and actionable insights.

How to get Tability dashboards:

That's it! Tability will instantly get access to 10+ dashboards to monitor progress, visualise trends, and identify risks early.

More Newly Formed Teams OKR templates

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

Table of contents