Navigating Milestones in the OKR Journey: Insights from Engineering Leadership

PS: Crafted for Engineering Directors and senior role enthusiasts, this article, with a reading span of just over 8 minutes, aims to… -

Navigating Milestones in the OKR Journey: Insights from Engineering Leadership

PS: Crafted for Engineering Directors and senior role enthusiasts, this article, with a reading span of just over 8 minutes, aims to unravel the essence of Milestones in the OKR landscape. Your feedback is a treasure trove, and if you’re on the verge of stepping into such pivotal roles, your quest for knowledge is admirable. Dive in, and discover insights that could be the bedrock of your success.

Embarking on this narrative, I am thrilled to unfold my voyage with the OKR methodology, morphing from an adopter to an advisor.

The OKR Voyage:

My expedition through the OKR framework has been a riveting one. Nestled in the company (hint: [WorkBoard](https://www.workboard.com/)) that commences its day with the strategy for breakfast, feasts on OKRs for lunch, and toasts to outcomes over dessert, has been nothing short of enlightening. I’ve successfully melded the outcome methodology with the OKR framework — a practice initiated by Intel, embraced by Google, and now utilized by many enterprises through our product, platform and services to align and achieve their strategic goals.

Hurdles on the Trail: The brilliance of the OKR methodology, although undeniable, unveils hurdles when it comes to adoption. The triad of challenges unfolds as follows:

1. Change Management Prerequisite: A sturdy change management process is non-negotiable. A miss here spells adoption doom. 2. Organizational Cohesion and Alignment: The methodology calls for a unified framework adoption across the organization. It needs to be secured by the endorsement of senior executives, and a chorus singing the hymn of its merits. 3. Team Endeavor: OKRs flourish on the bedrock of teamwork; the lone wolf narrative finds no script here.

Post-Adoption Conundrum: The post-adoption phase unveils a towering block named ‘implementation.’ Reflecting upon the intricacies faced by engineering leaders, I’ve crystallized the crux of challenges into nuggets of insight:

1. Sustained Effort for Outcomes: Outcomes are the result of sustained efforts, not isolated transactions — it requires multiple owners with the singular driver, and failed to identify it, will lead to failure in realizing the value of the outcomes; here is the DACI matrix for outcome owners- - Driver: The custodian of the outcome or key results. - Approver: The sentinel of upstream alignment — a paramount role! - Contributors: The team in the trenches. - Informed: The guardians of lateral alignment — of equal importance!

2\. Management Investment: The path to successful adoption embodies a non-negotiable commitment to thoughtful management.

3\. Platform Deficit: An absence of apt platform/tools to navigate the outcome landscape is a pitfall. For instance, shackling OKRs to the confines of Excel/Powerpoint is a practice best avoided.

4\. Chasing the Key Results: A common challenge I’ve noticed is the inclination to chase the chain of Key Results for your outcomes. Key Results often link to specific tasks, projects, or actions, and becoming overly fixated on these tasks can cause disillusionment with the OKR framework. This issue manifests in several ways:

i. Output vs. Outcome: This is a prevalent pitfall. Getting caught up in the chain of Key Results can shift the focus excessively towards outputs, overshadowing the actual outcomes. This misalignment often leads to a ‘fake it till you make it’ scenario, which is counterproductive.

ii. Delegation Dilemma: Key Results are typically intertwined with your team(s)’ execution, which can undermine the essence of delegation. It’s crucial to adhere to the DACI framework to ensure proper delegation and accountability

iii. Systemic Dissonance: Execution progress/data might be housed in different systems or sometimes even within the same platform but lacks proper linkage. This disconnection can shift the value focus from the OKR Framework to the Execution Framework, causing a divergence from the intended strategic objectives.

This brings us to a gap in the OKR framework — a lack of explicit construct delineating the pathway to drive outcomes, marked by significant progress points and forward strides. What could serve as the beacons illuminating this pathway?

Milestones, precisely! This missing link in the framework is fundamental. This realization often emerges after the segmentation of work following the delineation of key results. The amalgamation of milestones with the OKR framework can be the salve for the aforementioned ailments.

Let’s dissect the remedy by integrating milestones in the OKR framework:

1. Promoting a Culture of Outcome Over Output: The essence of integrating milestones is to keep the focus on outcomes over outputs. Celebrating the achievement of milestones, which are significant progress points towards the key result, reinforces the culture of valuing outcomes. This cultural shift is vital for the long-term success and adoption of the OKR methodology. 2. Avoiding the Chain Chase: Engage with your teams in dialogues revolving around milestones (the ‘Why’), steering clear of the ‘What’, and certainly the ‘How’. This paradigm shift will refocus discussions on significant progress towards the key result, embracing the fundamental principle that as an engineering leader, your mandate is to sponsor and empower your teams — Celebrating the execution phase means celebrating the outputs, not the outcomes! 3. Enhanced Management Investment: Management overhead is inevitable, but with well-defined milestones, the overhead becomes more about steering the ship in the right direction rather than getting entangled in daily firefighting. Milestones provide a higher-level view of progress, enabling leaders to identify bottlenecks or issues early on and address them before they escalate. 4. Streamlining Execution Across Systems: When milestones are integrated within the OKR framework, it becomes easier to track progress, even if execution data resides in different systems. By having a centralized view of milestones and their status, the need for constant back-and-forths between different systems reduces. This streamlined view can be a game-changer in ensuring everyone is on the same page, regardless of the platform they use for execution — the conversations stay focused in one platform with one framework. 5. Improving Delegation: With clear milestones, delegating becomes more straightforward. Each milestone can have a designated owner, fostering accountability and clarity in roles. This way, as an engineering leader, you can delegate tasks with confidence, knowing that each milestone achieved is a step closer to the key result. 6. One Platform with ONE framework: When milestones are a part of the OKR framework, the need for effective platform becomes apparent. Platforms like [WorkBoard](https://www.linkedin.com/company/workboard-inc/mycompany/verification/) that can seamlessly integrate milestones, OKRs, and execution data while providing a clear, real-time view of progress are invaluable. You focus on reviewing the progress of execution systems, rather keep the focus and conversation on milestones’ status that is the part of OKR framework (THANK!) and in the same platform.

Let’s take a plunge into an OKR example to elucidate the narrative

Objective: Ascend to Industry-leading Site Reliability and Achieve Unmatched Operational Efficiency

Key Results

1. Achieve a system uptime of 99.99% over the next quarter. 2. Decrease the average incident resolution time by 25% within the next six months. 3. Automate 80% of routine system maintenance tasks to free up engineering time by the end of the year. 4. Establish and adhere to error budgets for all critical services, with no budget overruns for the next two quarters.

Let’s delve into the milestones for one of the outlined key results — Achieving a system uptime of 99.99% over the next quarter. \[ progress: 0–100%\]

Milestones i. Establish a Solid Foundation — Complete a comprehensive system audit to establish the current uptime percentage and identify areas for improvement. \[contribution toward the progress — 20%\]

ii. Monitor, Analyze, and Optimize— Deploy necessary system upgrades and optimizations to address identified areas of improvement. \[contribution toward the progress 60%\]

iii. Refine and Validate — Confirm and document that a system uptime of 99.99% has been achieved and maintained over the quarter. \[contribution toward the progress— 20%\]

In summary, the incorporation of milestones within the OKR framework equips engineering leaders with a more nuanced, structured, and focused approach towards realizing the coveted outcomes. Milestones serve as vital navigational beacons, guiding us through the intricacies and exigencies of our strategic voyage towards those formidable, for e.g. our ‘four nines’ outcomes. It allows us to remain within the ambit of our strategic framework and the designated platform, ensuring that all crucial conversations and evaluations occur where they should. This minimizes the need to oscillate between the strategic and execution frameworks, thereby promoting a more streamlined, focused, and effective leadership approach. -

The Expedition Analogy

Much like embarking on a well-planned journey, this approach cultivates a structured yet exhilarating expedition towards our organizational goals. My love for travel, shared ardently with my wife, often parallels the voyage of steering an organization’s strategy. The joy of choosing a captivating destination, meticulously planning the route to traverse, relishing the landmarks along the way, and the daily explorations that enrich the entire adventure — all these facets of travel resonate with the orchestrated, yet dynamic realm of organizational strategy. Here’s a glimpse into this analogy:

1. Organizational Vision & Mission (The Destination): Every memorable journey starts with an inspiring destination in mind, much like how an organization’s Vision & Mission sets a compelling direction for its future. 2. Organizational Strategy (The Trip Itinerary): A fulfilling travel experience requires a well-thought-out itinerary. Similarly, an Organizational Strategy charts the course, providing a roadmap to reach the desired vision. 3. Strategic Outcomes (The Major Landmarks): Just as major landmarks signify the highlights of our journey, Strategic Outcomes are the pivotal progress points that bring us closer to our organizational goals. 4. OKRs (The Travel Plan): A structured travel plan ensures you hit each landmark smoothly. In an organizational setting, OKRs are the structured plans that guide us towards Strategic Outcomes. The milestones within them act as our markers of progress, ensuring our journey remains on track. 5. Execution/Unit of Work (The Daily Excursions): The daily explorations and activities bring depth to any travel experience. Similarly, the Execution and Units of Work are the tangible tasks that drive an organization closer to achieving its OKRs and experiencing its strategic landmarks.

In essence, just as every traveler cherishes the journey as much as the destination, in the world of OKRs and strategic planning, the process is as enriching as the outcome. Embrace the journey, enjoy the landmarks, and make the most of every excursion. Safe travels on your strategic journey!


dall.e-2 (Safe travels on your strategic!) -

Feel free to share your thoughts, ask questions, or delve deeper into any segment that piqued your interest. Your engagement fuels the dialogue and enriches the OKR community. Reach out, and let’s continue this enlightening discourse.

Sincerely,

— Imagination mine, expressions powered by GenAI. Cheers!