Key Result Milestones are a simple, flexible way to define clear, time-phased targets for your Key Results (KRs). Key Result Milestones give you an avenue to express your expected trajectory of achieving progress with dated, labeled checkpoints – creating shared clarity on how progress should unfold over time.
Define clear expectations for what should be achieved by when
Quickly view what milestone is expected at this point in time
See expected vs. actual progress when updating
Get a clear RAG signal: on-track vs off-track based on where we need to be
What Are Key Result Milestones?
Key Result Milestones are checkpoints along your KR’s timeline that represent specific target values you plan to achieve by certain dates. For example, if your annual goal is to reach 1M new leads, you might set milestones for 100K by Q1, 300K by Q2, and 500K by Q3, culminating in your year-end target.
Milestones make it easy to:
Phase targets over time (e.g., a “hockey stick” growth pattern)
See the expected vs. actual trajectory
Have RAG ratings (Red / Amber / Green) that reflect a custom trajectory
Provide meaningful context at key points (e.g., “60% = go-to-market achieved”)
Setting Up Key Result Milestones
Quick note about supported key results: You can add milestones to most Key Results with a few exceptions:
Key Results that are measuring progress as Range,Should Not Exceed, Should Not Fall Below, Should Equal to
Workstream KRs, KRs using Multiple Interval Targets and Mirrored KRs
How to Add Milestones
Edit or Create a Key Result: Open a KR Edit or Create side panel
Add Milestones
From the Key Result edit pane, click the “Add Key Result Milestones.”
From here, you can either add individual Milestones, or add multiple at a time using the “+ Weekly” or “+ Monthly” buttons.
Set Milestone Details: Each Milestone must have a date, and a value.
Date: When the KR should the Milestone. It must be within the KR’s start and end dates.
Value: What value the KR should achieve by the Milestone date. It must be between the KR’s start and target values.
Label (optional): Add a description for context (e.g., “Go-to-market achieved”).
Removing Milestones: Click “Remove Key Result Milestones” to delete all milestones for the KR.
Save: Saving will add the Milestones to the Key Result
Viewing and Tracking Milestones
On the Key Result Details Page
Chart View: Milestones appear as an “Expected” series. Hover to see the Milestone expected value, and the relevant Label.
Table View: See all milestone data in a table, including date, expected value, actual value, and milestone label. CLick on "View Key Results Milestones" to see the table
Key Result RAG (Red Amber Green): If you add Milestones to a Key Result, its RAG status will reflect the expected trajectory.
Frequently Asked Questions
Q: Can I auto-generate milestones?
Yes, you can select a cadence (quarterly, monthly, weekly) to auto-populate milestone dates. You can then fill in the values and labels.
Q: Where can I see milestone progress?
On the KR Details Page, in the chart, table view, and data table.
Q: Do Milestones replace Multiple Interval Target (MIT) Key Results?
No, Milestones are designed to provide a simple, flexible solution that is lighter weight than MITs. Milestones address the simple phased target use case. If your use case is more complex – for example, it needs different users to own different quarters – MITs may be a better fit.
Q: Can I use milestones with different KR types?
Yes—that’s one of the goals. Milestones are intended to work across KR types, including integrated KRs.
Q: How many milestones should I add?
Enough to make expectations clear, without overcomplicating:
Quarterly milestones for annual KRs
Monthly milestones for shorter or more execution-heavy KRs
Custom milestones when critical business moments matter
Q: What if we miss a milestone but still think we’ll hit the final target?
That’s exactly the kind of signal milestones are meant to clarify. Missing a checkpoint may indicate the KR is off-track unless there’s a credible plan to catch up. Use comments/context in your update to explain the change in trajectory.