Introduction
Many organizations struggle with a simple but important question: where should OKRs be drafted, and when should they be published? Should teams enter OKRs directly into software, or first refine them in a draft format?
Based on two decades of coaching organizations implementing OKRs, one pattern consistently leads to better alignment, clarity, and execution: separating draft OKRs from final OKRs using a structured OKR tracker.
This article explains why drafting first improves OKR quality, how an OKR tracker works, and when organizations should consider dedicated OKR software.
What Is an OKR Tracker
An OKR tracker is a single, shared location where all finalized OKRs are documented and visible across the organization.
It serves as:
- The source of truth for objectives and key results
- A transparency and alignment tool
- A way to track progress consistently at each of the 3 steps of the OKRs Cycle
- A foundation before adopting OKR software
While tools vary, the purpose remains the same: create a clear and consistent place where final OKRs live.
Why Teams Should Draft OKRs Before Publishing
When I first began coaching OKRs, every team drafted OKRs in a separate document marked clearly with the word “DRAFT.” Only after refinement and review were OKRs published into a shared tracker.
This practice remains common today for good reason.
Drafting Improves Clarity
Writing strong OKRs requires iteration. Early drafts often resemble a list of activities rather than measurable outcomes. Separating draft from final allows teams to refine wording and sharpen focus.
Drafting Reduces Risk
Many teams are uncomfortable publishing unfinished OKRs in a fully transparent system. Drafting first prevents confusion about which OKRs are final and which are still evolving.
Drafting Improves Alignment
Reviewing draft OKRs before publication allows leadership and teams to ensure objectives are aligned before they become visible across the organization.
Where Teams Draft OKRs Today
Organizations typically draft OKRs in tools they already know, including:
- Microsoft Word or Google Docs
- Excel/Google Sheets
- Notion, Airtable, or Smartsheet
- Whiteboards during workshops
The drafting environment matters less than the process. Flexibility during drafting helps teams focus on quality rather than tooling.
Why Final OKRs Should Live in One Place
Regardless of where OKRs are drafted, final OKRs should always be documented in a single shared location.
This improves:
- Visibility
- Accountability
- Alignment across teams
- Consistency in tracking progress
We refer to this shared location as the OKR tracker.
Should You Buy OKR Software First
Many organizations purchase OKR software before establishing a working OKR process. This often leads to frustration.
Software can automate a process, but it cannot create one.
Before adopting dedicated OKR tools, organizations should:
- Complete at least one OKR cycle
- Pilot with a few teams
- Establish a clear drafting and publishing process
- Build discipline around tracking progress
Once the process works, software can help scale it.
The Role of an OKR Tracker in Early Implementation
An OKR tracker provides structure without unnecessary complexity.
It allows organizations to:
- Start simple
- Maintain clarity
- Build execution discipline
- Learn before scaling
In many successful OKR implementations, the tracker precedes the software.
Practical Coaching Takeaways
If you are implementing OKRs, consider these practices:
- Start with a standard OKR drafting template
- Allow teams flexibility in how they draft OKRs
- Publish all finalized OKRs in a single shared tracker
- Complete at least one full OKR cycle before evaluating software
These simple steps improve clarity, alignment, and execution.
Want a Proven OKR Tracker Template
If you would like to see the exact OKR tracker used with real organizations, you can request a sample. Email Ben@OKRs.com with the subject line OKR TRACKER and receive a template to help you start building your OKR system.
Final Thought
The quality of OKRs depends less on the tool and more on the process.
Separating draft OKRs from final OKRs allows teams to refine, align, and clarify before publishing. A structured OKR tracker then provides the visibility and discipline required for execution.
Start simple, build the process, and scale with confidence.







Recent Comments