Skip to content

OKR Implementation and Goal Management

This one-day training covers implementing Objectives & Key Results (OKR) across an organization — rollout, quarterly cadence, connecting team goals to company goals, and the most common implementation anti-patterns, using a framework adopted by Google, Intel, LinkedIn, and Spotify, among others.

A Silicon Valley framework, increasingly adopted in Poland

OKR (Objectives & Key Results) is a goal-management system popularized by Google (adopted from Intel) and now used by companies including LinkedIn and Spotify. More and more Polish technology companies are turning to this framework, but rollouts often stall on paper — with empty OKR spreadsheets that nobody updates after the first quarter. The problem rarely lies in the idea itself, but in the lack of an implementation rhythm and confusing OKRs with a task list.

Cascading without bureaucracy

The biggest implementation challenge is finding the balance between goal alignment across the organization and team autonomy. The training shows a concrete cascading model: company goals translate into team goals, but teams retain room to choose their own Key Results supporting the parent goal — instead of rigidly mapping an identical structure onto every organizational level.

One day, a ready first-quarter plan

The training ends with a workshop where each participant designs the first quarter of OKR implementation for their own team — with concrete Objectives, Key Results, and a schedule of weekly check-ins. It’s a practical starting point, not just framework theory.

Benefits

  • Distinguish OKR from traditional MBO and KPIs — understand why ambitious (moonshot) goals are integral to the framework
  • Design goal cascading from the company level to the team level without rigid, bureaucratic top-down mapping
  • Establish the quarterly OKR cadence — planning, weekly check-ins, scoring, and retrospectives
  • Recognize the most common implementation anti-patterns and design a rollout that avoids them

Who is this training for?

Managers and team leads implementing OKR for the first time in their organization
Operations and strategy directors responsible for connecting company goals to team work
Product Managers and Product Owners wanting to link the product roadmap to business goals
HR Business Partners supporting the rollout of a new goal-management system

Prerequisites

  • Experience leading a team or participating in an organizational goal-planning process
  • No prior OKR knowledge required

Training program

01

OKR fundamentals — how it differs from KPIs and MBO

  • OKR structure: Objective (a qualitative, inspiring goal) + Key Results (2-4 measurable results)
  • The difference between OKR and KPIs — ambitious (moonshot) goals versus operational targets, and the role of 0.7 as a 'good score'
  • Why OKRs shouldn't be directly tied to bonuses — the sandbagging trap
  • A brief history: from Intel through Google to Spotify and LinkedIn — lessons from these rollouts
02

Cascading goals without bureaucracy

  • The cascading model: company goals → team goals, with room for team autonomy in choosing Key Results
  • When to cascade rigidly and when to give teams room for their own OKRs supporting the parent goal
  • Avoiding the 'domino' effect — how to avoid mapping every organizational level with an identical structure
  • Workshop: connecting a sample company goal to team-level OKRs
03

Quarterly cadence — the rhythm that keeps OKR alive

  • Quarterly planning — what a goal-setting session looks like at the start of the quarter
  • Weekly check-ins — a short ritual for tracking progress without creating additional bureaucracy
  • End-of-quarter scoring and retrospective — what worked, what to improve in the next cycle
  • Tools supporting the OKR cadence — from spreadsheets to dedicated platforms
04

Implementation anti-patterns and rollout plan

  • Common mistakes: too many OKRs at once, confusing tasks with Key Results, no mid-quarter review
  • OKR as a control tool instead of a focus tool — how to recognize and reverse this drift
  • Pilot plan: rolling out OKR in one team before scaling to the whole organization
  • Workshop: participants design the first quarter of OKR implementation for their own team

Delivery Methods

Online

  • Convenience of participating from anywhere
  • Interactive live sessions with trainer
  • Materials available for 30 days
  • No travel costs

On-site

  • Direct contact with trainer and group
  • Intensive hands-on workshops
  • Networking with other participants
  • Full focus on learning

Frequently asked questions

How does OKR differ from the traditional KPIs we already have?

KPIs measure the current state of the business (e.g., revenue, retention) and are typically realistic targets aiming close to 100% completion. OKR is a framework of ambitious, qualitative goals (Objectives) with 2-4 measurable results (Key Results), where a score of around 0.7 (70%) is considered good — because the goal was deliberately ambitious (a moonshot). OKRs and KPIs can coexist: KPIs monitor business health, while OKRs drive focus and ambitious initiatives for a given quarter.

Should OKRs be tied to the bonus system?

The recommendation from Google's and Intel's practice: not directly. If OKRs are tied to bonuses, teams start lowering the ambition of their goals to guarantee achievement (sandbagging), which undermines the purpose of the framework. The training shows how to separate employee performance evaluation (for bonus purposes) from OKR achievement assessment (for development and team focus purposes).

How long does a full OKR rollout take across an organization?

We recommend piloting in one team for one quarter before scaling — this lets you learn at a smaller scale before rollout mistakes spread across the whole organization. A full rollout in a mid-sized organization (dozens to a few hundred people) typically takes 2-3 quarters, from pilot to a stable rhythm company-wide.

What if a team doesn't hit its Key Results for the quarter?

That's normal and expected — with well-calibrated, ambitious OKRs, a 60-70% completion rate is a success, not a failure. The key is the end-of-quarter retrospective: why a given Key Result wasn't achieved (bad assumptions, shifting priorities, too ambitious a target) and what to learn for the next cycle. The training shows the structure of such a retrospective.

Jakub Malarczyk
Jakub Malarczyk Opiekun szkolenia

Request a quote

Funding Options

Check funding options for your company

Up to 80%

Development Services Database

Up to 80% funding for SMEs from EU funds

Check availability
Up to 100%

National Training Fund

Up to 100% funding for employers

Learn more

Trusted by

We train teams at Poland's largest companies

ING Bank - EITT client
mBank - EITT client
PKO Bank Polski - EITT client
PZU - EITT client
Allianz - EITT client
T-Mobile - EITT client
KGHM - EITT client
PGE - EITT client
IKEA - EITT client
InPost - EITT client
Leroy Merlin - EITT client
ZUS - EITT client

Interested in this training?

Contact us - we'll prepare an offer tailored to your organization's needs.

500+ experts
2500+ trainings available
ISO 9001 quality certified
Request Training
Call us +48 22 487 84 90