◆ OKRs are designed to articulate a desired future and drive commitment to ambitious goals. Yet in practice, many OKRs become hollow—reduced to numerical targets or lists of tasks.

Why do OKRs fail?

◆ In many cases, it is because the means of change required to achieve those goals is missing. Ambitious goals cannot be reached with the same old ways of working. OKRs are meant to drive change and learning—but without a way to realize that change, they fall short.

This is where DevOps comes in.

◆ As a practice of change, DevOps enables teams to continuously evolve through flow, feedback, and learning. It provides the mechanisms for teams to inspect their processes, experiment, and improve.

◆ The key is not to treat DevOps as a set of tools or practices in isolation. Rather, OKRs define the direction of change, and DevOps enables that change to happen.

◆ In this session, we will reframe OKR and DevOps not as separate concepts, but as a reinforcing loop—where goals drive change, and DevOps turns that change into reality.

◆ In a world of constant change, how do we ask the right questions, translate them into meaningful goals, and turn them into action? This talk explores why OKRs fail and how DevOps can make them truly work in practice.

Audience gain：

Through this session, participants will gain the following key insights:

• Understanding the fundamental reason why OKRs often fail: the lack of the "Practice of Change" required to achieve ambitious goals.
• Reframing DevOps as a "Practice" that enables continuous improvement through flow, feedback, and learning.
• Gaining the perspective needed to build a reinforcing loop where goal setting (OKR) and the execution process (DevOps) mutually strengthen each other.