Most enterprises do not fail at writing OKRs. They fail at tracking them against the numbers the business already trusts. Strategy keeps objectives in a dedicated OKR tool, a slide, or a spreadsheet. Finance keeps KPIs in the EPM layer, fed from SAP or Infor. In the monthly review the two sets do not match, because nothing is joining them. Cipher SPEAR is Cipher's strategy execution platform for that join: OKR tracking, KPI scorecards, and actuals in one model.
What is OKR tracking software?
OKR tracking software holds objectives, key results, owners, and scores for a cycle, and shows progress as the cycle runs. In an enterprise the key result has to be the same number the EPM layer already uses, not a second copy in a goal app. Cipher SPEAR tracks that on a scorecard fed from SAP, Infor, and other operational sources.
If you need the method itself, the difference between an OKR and a KPI is on its own page: OKR vs KPI. This page is the software. It is for teams that already know they need both, and need them to stop living in two tools.
Why does enterprise OKR tracking fail in a separate tool?
Because the key result and the KPI become two definitions. Strategy types 92% into the OKR tool. The scorecard still shows 85% as the target. Both actuals are "from the ERP." They still disagree. Cipher SPEAR keeps the objective, the key result, and the KPI on one measure, so tracking is not a monthly reconciliation.
That split is normal in large organizations. OKR-native vendors are good at cascading goals, check-ins, and comments. They are not the EPM layer. They do not own the SAP extract, the Infor cube, or the close. Goal management software that starts from HR or from a project tool has the same gap: plenty of tracking, no trusted actual.
Three things then happen, quietly:
- The target in the OKR is not the target on the KPI. Nobody updates the measure definition in both places.
- The actual feeding the OKR dashboard is a different extract from the actual feeding the board pack. Both are labelled as source-system numbers.
- When the cycle ends, the OKR is left on a dashboard as a fake health measure, or the KPI is forgotten. Either way the organization loses the distinction it set out to track.
That is not an argument against OKRs. It is an argument against tracking them in a system that cannot see the numbers the rest of the enterprise already runs on.
What should an OKR dashboard show?
An OKR dashboard should show the objective, the key results, the owner, the cycle, the score, and the actuals those key results are built on. Status without a trusted actual is a status meeting. Cipher SPEAR puts that view on a scorecard, so the dashboard and the KPI are not two screens.
A useful OKR dashboard at enterprise scale also needs:
- A small set of objectives, not a catalogue. If everything is an OKR, nothing is being tracked as a change.
- Key results that name a number, a baseline, and a target. "Improve forecast quality" is not trackable. "Raise forecast accuracy from 82% to 92%" is.
- The standing KPIs sitting next to the OKRs. Health measures do not expire when the cycle turns over. They belong on the same scorecard.
- Initiatives under the objective. Tracking progress on the work, not only on the metric, is how you see a miss before the quarter ends.
- An approval path for the actuals. If anyone can type a number into the dashboard, leadership will not use it in the room.
When that dashboard also has to go to the board, the same scorecard should be the pack. That outcome is spelled out on the board reporting software page. Do not run an OKR dashboard for strategy and a second pack for directors. That recreates the split this page is about.
How do you track OKRs against SAP and Infor data?
Put the key result on the same measure the EPM layer already uses, then refresh actuals from SAP or Infor, with approval before the number publishes. Cipher SPEAR sits on top of the ERP and the planning tool. It does not replace them. The measure is written once. Actuals come from the systems that already hold them.
Typical connections, verified on the live SPEAR product:
- SAP. Hosting on SAP Cloud Platform with SAP HANA and SAP Identity Authentication Service, plus embedded SAP Analytics Cloud reporting where that is already in the estate.
- Infor and mixed estates. Scorecards and KPIs can draw on SAP, Infor, and other operational sources. Manufacturers and public-sector organizations often run both.
- Excel and structured uploads. Template-based collection for measures that still arrive through a finance cycle, with notifications so an approver sees the upload before it reaches the scorecard.
- Embedded BI. Power BI, Tableau, and SAP Analytics Cloud content can sit beside the OKR dashboard instead of in a tab someone toggles mid-review.
Cipher is services-first. We implement the model, the connection, and the operating cadence. SPEAR is the platform those sit on. If you are leaving SAP Strategy Management, SPEAR is also an SAP AppCenter-registered strategy execution platform built as the successor to SAP Strategy Management, by the team with more SAP SSM implementation experience than any other firm. That path is on the SAP Strategy Management page. This page is the OKR tracking problem, including for estates that never ran SSM.
What is the difference between OKR tools and a strategy execution platform?
OKR tools cascade goals, collect check-ins, and score a cycle. A strategy execution platform holds objectives, KPIs, initiatives, and scorecards in one model, fed by existing actuals. Cipher SPEAR is that platform. Use an OKR tool when the numbers live in the same app. Use SPEAR when they live in SAP, Infor, or the close.
OKR tools are the right buy for a software company that runs the business in the OKR product. They are the wrong buy for a multi-entity manufacturer, a utility, or a public agency whose official numbers already live in EPM. Goal management software in that second group becomes another export, another owner, and another meeting to explain why the dashboard and the board pack disagree.
Cipher SPEAR keeps the OKR structure: a time-bound objective, three to five key results, an owner, a cycle, and a score. It also keeps the KPI set that does not expire. Strategy maps, scorecards, and initiatives are the same building blocks Cipher has used in strategy execution work for years. Tracking is not a separate product. It is the scorecard.
Who should use Cipher SPEAR for OKR tracking?
Cipher SPEAR is for enterprises that already run SAP, Infor, or a mixed EPM estate and need OKR tracking on those numbers, not beside them. It fits strategy, finance, and performance teams that present to a board or an executive committee. It is not a personal tracker, a Notion template, or a Jira add-on.
It is a fit when:
- OKRs are written in one tool and KPIs are reported in another, and the monthly review is the integration layer.
- Leadership wants an OKR dashboard that can survive a question about the actual, in the room.
- The organization already has a scorecard or strategy-map model and does not want a second goal taxonomy.
- Someone has to approve the number before it is called official.
It is not a fit when the team wants a lightweight check-in app for a dozen people and has no EPM layer behind it. There are OKR tools for that job. This is not that job.
Royal Eswatini Sugar Corporation runs strategy execution for 150 users on Cipher SPEAR, drawing on both SAP and non-SAP data. That is the pattern: one model for the objective and the health measure, fed by data the organization already trusts.
See OKR tracking on your own data
A short demo is enough to see whether the split is a wording problem or a systems problem. We will look at how you set objectives today, where the KPIs actually live, and what a single scorecard would change. Book from here, or start from a Cipher demo and choose the SPEAR path.