Give the team a shared purpose.
Define the objective and measurable key results. Make the owner, baseline, target, and planning period clear.
Objectives & key results
Connect what you want to change with measurable results, delivery forecasts, and the evidence that challenges the plan.
OKRs in ScrumDo Business preview.
Illustrative example · Fictional data
ObjectiveMore completed orders. Fewer customers starting over after a failed payment.
Current completion rate · Target marker at 90%
Completion is up 14 percentage points from baseline. The team still needs to understand who is struggling and whether the improvement holds.
From forecasts to service expectations to OKRs
In Forecast, set a service-level expectation (SLE): the percentage of matching work expected to finish within a time window. Link that expectation to a compliance key result.
Delivery risk and customer impact answer different questions. Keep outcome measures and customer evidence alongside the service expectation.
A delivery key result supporting the objective
Matching work, from start to finish.
39 of 50 assessed work episodes met the expectation.
Below expectation · Review delivery risk
Forecast warnings guide where to investigate. The owner’s health assessment stays separate.
An objective is a direction. A key result is a measure.
An objective describes the change you want. Key results define observable measures of success. Delivery work supports the outcome; completing tasks alone does not prove it.
Define the objective and measurable key results. Make the owner, baseline, target, and planning period clear.
Link objectives to portfolio epics and the teams involved. Keep the intended outcome visible when reviewing priorities.
Use check-ins, lifecycle health, and source evidence to discuss progress. Revisit assumptions when the measure and people’s experiences tell different stories.
Crowdsourced insight. Shared direction.
Bring team contributions and customer stories into the objective conversation. ScrumDo connects the OKR catalogue with Strategy Feedback and evidence review, so a target can be questioned as well as tracked.
Use the numbers to see movement. Use the stories to understand the experience behind them.
For the framework fundamentals, see Google re:Work’s introduction to OKRs.
A linked service-compliance key result receives measurements from the work covered by its SLE. Other key results still need their own measurement sources and check-ins. Forecast warnings inform a review; they do not replace the owner’s assessment or prove the broader objective was achieved.
Yes. Portfolio epics and OKRs can have multiple links. Use those links to make the intended contribution explicit; a link by itself does not demonstrate impact.
A task describes an action. A key result gives you a measure against which to assess the objective. Shipping payment recovery is work; a sustained improvement in checkout completion is an outcome to test.
Use a Wardley Map to examine strategic options and dependencies. Use an objective and key results to describe and assess the change you choose to pursue.