The method is what it is because these rollouts taught us.
Three anonymised implementations that changed how we work. These are not client wins. Their value is exactly their honesty: hard rollouts, named failure modes, and what each one changed in the method.
Metric immaturity and strategic disconnection
The organisation attempted OKRs across around 1,500 people without strategic guardrails or metric fundamentals. Revenue metrics were clear at the top, but teams could not connect their work to value. Operations wrote activity-based OKRs such as “launch three new support channels” with no link to impact; product wrote technically sound but strategically misaligned objectives from unclear priorities. Teams reported activity completed, not value delivered.
Strategic narratives and guardrails come first; metric models and KPI trees are now a prerequisite to OKR creation, because metrics often need developing before they can anchor a Key Result. Discovery runs as its own track, never inside OKRs, and we help operational teams connect their work to strategic value.
Team formation and resource management
The company ran fifteen strategic OKRs at once, each needing cross-functional collaboration. New team leads, chosen for technical expertise, were given cross-functional teams with no support; members who had never worked together struggled with trust and basic collaboration. Analysis found key people spread across three to four OKR teams, causing context-switching and burnout, and promising initiatives stalled.
Dedicated time for key people on wildly important OKRs (80%+ commitment); structured team-formation processes; real support for new OKR leads; and deliberate social-equity building in new teams. This is the origin of our team-formation playbook and resource-allocation guidelines.
Fear culture and top-down implementation
A modernisation driven through OKRs stalled on culture. Leadership tied OKR achievement to reviews and bonuses, creating fear; teams received objectives from above with no context, so they sandbagged to protect their ratings. Concerns about feasibility were dismissed as “not ambitious enough,” which damaged safety. Several teams hit their OKRs but delivered no business impact, which is what finally exposed the flaw.
Separate OKRs from performance management; build psychological safety into goal setting; require bottom-up input; and celebrate learning from partial achievement rather than punishing the miss.
The common threads
Cross-team collaboration failed three ways: unclear value chains (SaaS), too many simultaneous collaborations (fintech), and forced collaboration without buy-in (retail).
Resource management broke down when priorities were unclear (SaaS), when key people were over-allocated (fintech), and when OKRs were treated as extra work on top of the day job (retail).
Leadership engagement was the deciding variable: leaders who could not articulate direction (SaaS), who failed to protect team time (fintech), or who created fear through the wrong incentives (retail). These patterns shaped our pattern-based implementation methodology, the team-formation playbook, the emphasis on psychological safety, and the focus on metric-model development.
We have already made these mistakes so you do not have to. That is what a maintained methodology buys you.