Meet Bosch
Bosch is a global engineering and technology company with more than 420,000 employees. The OKR Institute worked with Bosch to strengthen how its product and scrum teams set direction and deliver on it, using Objectives and Key Results. What made this engagement interesting was the starting point. Bosch already ran on agile methods, so the job was not to introduce a brand new way of working. It was to help OKRs and agile support each other rather than compete.
In a company this size, even a small misstep in how the two fit together would multiply across hundreds of teams, so getting the approach right mattered a great deal.
Aligning Goals with Agile Rhythms
The main challenge was alignment. Product teams and scrum teams each had their own goals and their own pace. Bosch wanted those teams to pull in the same direction around shared objectives. At the same time, the OKR approach had to respect the agile practices that teams already relied on, like scrum. If OKRs got in the way of a sprint or added a layer of paperwork, they would have done more harm than good.
There was also a mindset to manage. Agile teams value short cycles and quick feedback, while OKRs ask people to hold a clear quarterly outcome in view. Bringing those two time horizons together, without either one swallowing the other, was the real test of the work.
Training the People Who Set the Tone
The OKR Institute built a focused education program for the people who shape how teams work day to day. Rather than train everyone at once, we started with the team leads who set the tone.
- OKR Practitioner courses: These were made for Agile Coaches and Product Managers. The sessions taught how to draft OKRs that carry real weight and how to weave them into existing agile practices like scrum.
- Hands-on practice: The training gave team leads the tools to write OKRs that were clear, measurable, and ambitious, then connect those goals to the work already moving through their sprints.
- Agile-first framing: Throughout, we kept the message simple. OKRs are there to give agile work a sense of direction, not to replace the way teams plan and deliver.
By starting with team leads, the approach gave the framework natural champions. Once those leads could see how OKRs fit their sprints, they carried that understanding into their teams without it feeling like a top-down mandate.
What Made it Work
- Start with team leads: Training the people who shape daily habits first gave OKRs natural champions who spread the framework organically.
- Respect the existing rhythm: OKRs were designed to complement agile and scrum, not replace them, so teams adopted them willingly.
- Bridge two time horizons: The approach connected short sprint cycles to quarterly OKR outcomes, giving agile work a clear strategic direction.
- Practical, not theoretical: Hands-on drafting and real-team application ensured the training stuck beyond the classroom.
What Changed at Bosch
Stronger OKR drafting
Team leads got good at writing OKRs that were clear and measurable, with enough ambition to stretch the team and sharpen quarterly focus.
Better fit with agile
Participants learned to line their OKRs up with scrum and other agile methods, so the goals lifted the work rather than slowing it.
More cohesion across teams
With shared objectives in place, product and scrum teams found it easier to coordinate and move together toward the same outcomes.
Clearer cross-functional priorities
When product managers and scrum masters shared the same objective, the usual friction between roadmap and sprint planning eased.
What This Shows
Bosch is proof that OKRs and agile are not rivals. When you train the right people first, the team leads who shape daily habits, the framework spreads naturally from there. The lesson is to start small and start with the people who set the rhythm. Once they can draft sharp OKRs and tie them to the work already in motion, alignment follows without a heavy rollout. For a company building complex products at scale, that quiet, practical fit is worth a great deal, because it lets the organization gain focus without giving up the speed that agile provides.
