The common failure mode with any scorecard tool is that it becomes a second reality: the numbers on the dashboard and the actual state of the business drift apart because nobody is held accountable for keeping them in sync. This guide is about making OpScore the real scorecard, not the ceremonial one.
Weeks 1–2 — Baseline honestly
Have the leadership team take the self-assessment at Level 1 for every category. Do not strategise for a good result. Red everywhere is fine; it tells you where to spend the next two quarters. A pretty Level 1 dashboard on day one is a warning sign that you answered optimistically.
The single biggest rollout mistake is gaming the first assessment to look presentable. It defeats the tool before you use it.
Weeks 3–4 — Pick three reds
Do not try to fix everything. Pick three red focus areas that, if turned yellow, unlock the most follow-on value. For most companies two of those three will be in People & Talent and Production Readiness. Assign an owner to each.
Weeks 5–8 — Do the boring work
Open the "Improve This" page for each chosen focus area. Work through the tips literally. Document the current process, run the training, install the checklist. This is where the real work happens and where it usually stops in companies that fail.
Weeks 9–10 — Re-assess
Retake the self-assessment for the three categories you worked on. Expect movement on the focus areas you invested in and little elsewhere. If nothing moved, the work did not actually happen; don't pretend otherwise.
Weeks 11–12 — Set the cadence
Agree a rhythm: monthly self-assessments on rotating categories, a single weekly standup to review red alerts, and a quarterly level-up decision meeting. Put it in calendars. Protect it.
Rule of thumb: if the rollout survives the first reorg or crisis without being dropped, it will survive indefinitely. The first year is about making the tool load-bearing.