Objectives and key results
John Doerr · OKRs
Objectives with measurable key results, scored against baseline and target and linked to the work that moves them.
One operating rhythm — from every team’s work to the company’s goals.
“Is every team working on what matters?”
OKR and strategy-execution tools track goals. Work management tools track tasks. In between sits a chief of staff with a spreadsheet, stitching status together every week. Business Operations replaces the stitching. Objectives and key results link to the work that moves them. Every team has a room for its delivery, dependencies, capacity and priorities, and it all rolls up across team, delivery and strategy hierarchies. Status is posted once and seen everywhere. Metrics are read against their targets with the work behind them. And the strategy ceremonies — intake, shaping and steering — each end in a recorded decision, so the operating rhythm leaves a record instead of a slide deck.
Rooms you open
- OKR Hub
- Team Rooms
- Status Board
- Metric Room
- Strategy Ceremonies
- Intent vs Reality
Methods supported
OKRsSAFe
Part of Govern & Deliver · How do we turn choices into governed outcomes?
The pressure
Every week, someone rebuilds the picture by hand.
Goals are set in one tool, work is tracked in another and status is collected by email. The chief of staff spends the week before every review stitching it together. Dependencies surface when they break. Nobody can say whether the work actually serves the goals — and the decisions made in the review are remembered by whoever was in the room.
What it looks like today
- Status rebuilt by hand before every review
- Goals with no link to the work behind them
- Dependencies discovered when they break
- Teams that cannot see how their work rolls up
- Decisions remembered, not recorded
What changes
What changes.
TodayWith Dotwork
Goals in one tool, work in another
Objectives and key results linked to the work that moves them
Status collected by email
Status posted once and rolled up across every hierarchy
Each team in its own tool
Team rooms for delivery, dependencies, capacity and priorities
Alignment asserted in slides
Intent versus reality computed from the work itself
Reviews that leave a deck
Ceremonies that end in a recorded decision
One operating model
Strategy, money and work in one rhythm — from the team up.
Business Operations reads the same model as the portfolio, the budget and the strategy, so the weekly review is never a separate version of the truth. Each team’s work rolls up to the objectives and bets it serves, the status is the status everyone sees, and the decisions made in the room are recorded against the records they change.
Where other tools stop
OKR tools track goals. Work tools track tasks. Neither connects the work to the money and the strategy — so someone rebuilds the picture by hand every week.
The operating thinking built in
The operating rhythm — run on the model, not in slides.
Business Operations runs the management practices leadership teams already use, with every one of them reading and writing the same model.
Operating cadence
Management rhythm practice
Weekly, fortnightly and monthly forums, each with a clear question and a clear output.
Decision records
Decision quality practice
Every decision recorded with the options considered, the rationale and the dissent — so the next one starts from experience.
Team topologies
Skelton & Pais
Teams, their interactions and their dependencies made visible, so friction between teams is seen before it breaks delivery.
Cost of delay
Don Reinertsen
Prioritize by the value lost to waiting, so the most urgent work is done first.
Emergent strategy
Henry Mintzberg
Compare the strategy as intended with the strategy as practiced, computed from the work itself.
The rooms
The rooms inside Business Operations.
Each room answers one question a leader actually asks, with the view that answers it and the measures that say whether it is working.
A room is a ready-made view that answers one leadership question, built on the same shared data as every other room.
Room 01
OKR Hub
“Are our key results moving — and what work is behind them?”
Objectives with their key results against baseline and target, score distribution, the related work behind each one and a feed of status updates.
How you know it is working
- Key results with current readings, up
- Objectives with linked work, up
Room 02
Team Rooms
“What is each team working on — and how does it roll up?”
Each team’s delivery, cycle columns, dependencies, board, capacity and prioritization, with rollups across team, delivery and strategy hierarchies — shareable by link.
How you know it is working
- Teams with work linked to an objective, up
- Unresolved cross-team dependencies, down
Room 03
Status Board
“What is the status — and has it changed?”
Status updates grouped by initiative and team, with the hierarchy behind each update and a feed of what changed.
How you know it is working
- Status posted on cadence, up
- Time to assemble the weekly review, down
Room 04
Metric Room
“Are the metrics moving toward target — and which work is moving them?”
Metric trends against their targets, with the delivery work tied to each metric.
How you know it is working
- Metrics with a target and an owner, up
- Metrics off target with no work behind them, visible
Room 05
Strategy Ceremonies
“What do we decide this week, this fortnight and this month?”
Weekly intake triage, fortnightly bet shaping and monthly steering — each opening on the decisions requested and ending in a decision record with the options, rationale and dissent.
How you know it is working
- Ceremonies that end in a recorded decision, up
- Time from a request to a decision, down
Room 06
Intent vs Reality
“Is the company actually working on the bets?”
Where the effort really goes, computed from the work items, against where the strategy says it should go.
How you know it is working
- Effort traceable to a funded bet, up
- Drift between intent and actual effort, down
Agents and skills
The stitching is done for you. Leaders run the conversation.
Rollups, rollovers and checks run on the model behind the scenes. Dot drafts status updates and readouts from the records, answers questions about any team or objective and records nothing as decided until a person decides it.
Status Drafter
On cadenceDot drafts a status update for an initiative or team from the records that changed since the last one.
- What you get
- A draft update with the evidence linked
- Where you decide
- The owner edits and posts it
Rollup Builder
ContinuousRolls work and status up across team, delivery and strategy hierarchies, so every level sees its own view of the same numbers.
- What you get
- Rollups at every level, always current
- Where you decide
- Built in
Metric Signals
Every readingRanks unusual movements in metrics and key results against their trend, so the review starts with what changed.
- What you get
- The signals worth discussing, ranked
- Where you decide
- Owners explain the movement
Intake Triage
WeeklyLines up new requests and signals for the weekly triage; accepting one records it as evidence for the bets it bears on.
- What you get
- An intake queue ready for decision
- Where you decide
- A person applies any change
Decision Recorder
Every ceremonyRequires each ceremony to end in a decision with the options, rationale, dissent and what would reopen it.
- What you get
- A searchable record of every decision
- Where you decide
- The chair records the call
Dependency Watch
ContinuousTracks dependencies between teams and flags the ones at risk of blocking delivery.
- What you get
- Dependencies at risk, by team
- Where you decide
- Team leads resolve them
Readout Builder
Before each reviewDot drafts the review readout from objectives, status, metrics and decisions.
- What you get
- A draft readout, every number traceable
- Where you decide
- The chief of staff edits and shares it
Ask Dot
On requestAnswers questions about any team, objective or decision, citing the records behind every answer.
- What you get
- Answers you can drill into
- Where you decide
- Changes only with your approval
Use cases
Where leadership teams and chiefs of staff put it to work.
Chief of staff · Executive team
The weekly business review
Run the review from status and metrics that are already current — no stitching the week before.
- Status rolled up across the company
- Metrics against target with the work behind them
Executive team · Team leads
Quarterly OKRs that connect
Set objectives and key results, link them to the work that moves them and read the score from live data.
- Key results scored against target
- Work linked to every objective
Delivery leaders · Program managers
Cross-team dependencies
See the dependencies between teams before they break, and who needs to act.
- Dependencies by team
- Risks to delivery flagged early
CEO · Chief strategy officer
The strategy operating rhythm
Run weekly intake, fortnightly shaping and monthly steering on the same model as the strategy — each ending in a decision.
- Ceremonies that end in decisions
- A decision record that compounds
Team leads · Product owners
Capacity and priorities
Prioritize by stack rank or cost of delay and check the plan against each team’s capacity.
- Priorities compared across teams
- Plans checked against capacity
CEO · Board
Alignment the board can see
Show whether the company is actually working on the bets — computed from the work, not asserted in a slide.
- Intent against actual effort
- Drift surfaced early
How it compares
OKRs, team rooms and the operating rhythm — on one model.
OKR and strategy-execution platforms track goals and run reviews. Work management tools track tasks. Business Operations does both, and connects them to the portfolio, the budget and the strategy they serve.
| Capability | OKR & strategy-execution platforms | Work management tools | Business Operations |
|---|---|---|---|
| Objectives and key results with scoring | Partly | ||
| Status updates rolled up across teams | |||
| Team rooms — delivery, dependencies, capacity, priorities | Partly | ||
| Rollups across team, delivery and strategy hierarchies | Partly | Partly | |
| Metrics against target with the work behind them | Partly | Partly | |
| Ceremonies that end in a recorded decision | Partly | ||
| Intent versus reality computed from the work | |||
| Key results linked to funded work and its cost | |||
| Same model as the portfolio, budget and strategy |
Who it is for
Who opens it, and what they ask.
CEO
“Is the company actually working on what matters?
Chief of staff
“How do I run the weekly review without rebuilding the picture?
COO
“Which dependencies will block delivery this quarter?
Team lead
“How does my team’s work roll up to the company’s goals?
Program manager
“What is the status, and what changed since last week?
Board
“Are we executing the strategy we agreed?
What it replaces
Retire the workarounds — on your schedule.
- Status spreadsheets rebuilt every week
- Separate OKR tools disconnected from the work
- Review decks that leave no record
- Dependency trackers kept by hand
How it is licensed
Business Operations is licensed within Govern & Deliver, with Strategic Portfolio Management included underneath.
Start with one portfolio, one product area or your architecture team. Strategic Portfolio Management is included automatically with every module.
See pricingMethods and frameworks
Runs the methods you already use.
Dotwork does not ask you to adopt a new method. The frameworks your teams run become views over the same model.
More in Govern & Deliver
Same model. Next question.
Strategic Portfolio Management
“Is the work we are doing still the work we meant to fund?”
ExploreEnterprise Architecture
“What does this capability cost to run — and what depends on it?”
ExploreEnterprise Standards & Controls
“Can we prove our controls were actually working on what we shipped?”
ExploreAI Governance & Value Realization
“What AI is running, what can it access — and is it worth what it costs?”
ExploreProduct Management & Ops
“Are we building what customers need — and is it paying off?”
ExploreThe model underneath
Every module makes the next one smarter.
Steer, Fund & Optimize and Govern & Deliver all read and write the same Enterprise Operating Model. The first module you license builds the model. Every module after it adds context instead of another silo — and Dotwork AI reads all of it, stopping where the decision is yours.
See the Enterprise Operating ModelBe Decisive.Build Fast.Connect Everything.
Start ConnectingSolutions
Platform
Resources
© 2025-2026 Dotwork, Inc. All rights reserved.