Metrics (the Scorecard)
The short list of measurables RunOlga tracks each week: the Scorecard, owned by seat.
Phase 1 + roadmap
Metrics are how a leadership team sees the pulse of the organization in numbers. RunOlga calls them Metrics, or collectively the Scorecard (EOS: Scorecard) — a short list of measurables, each owned by a seat, each with a target.
What a Metric is
A Metric is a measured signal the team tracks over time. It is one number that tells you something true about how the organization is running — caregiver retention, hours filled, days to onboard, cash on hand.
Each Metric belongs to a seat, not to a person by name. The seat that is accountable for the work is accountable for the number. Each Metric has a target: the value that means "on track." When a leader looks at a Metric, the target is what tells them whether the number is good news or a problem to raise.
| Field | Description |
|---|---|
| Name | What the measurable is — stated plainly, so anyone reading the Scorecard knows what the number means. |
| Owner (seat) | The seat accountable for the number. |
| Target | The value that means "on track." |
| Current value | The most recent measurement. |
Metrics are deliberately few. The point of a Scorecard is a glance, not a report — a handful of numbers that show at once whether the week was on track.
The Scorecard
The Scorecard is the full set of Metrics seen together: the short list of weekly numbers that gives leadership an at-a-glance pulse on the organization. Each row is owned by a seat; each row has a target.
In the EOS operating model, the Scorecard is reviewed at the pulse meeting — leadership scans the numbers together, and any measurable that is off-target becomes an Issue to work through. Phase 1 does not yet automate this weekly rhythm; see the roadmap below.
Roadmap
In Phase 1
Metrics exist as a Phase 1 record. You can create and maintain them, and you can ask Olga what they are.
Capturing and updating Metrics
You create and update Metrics by talking to Olga, the same way you do every other record — see conversational data entry. Olga asks for the fields a Metric needs, repeats the structured record back to you, and writes nothing until you confirm.
You: Add a metric for caregiver retention.
Olga: Which seat owns it, and what's the target?
You: Care Services Operations. Target is 90 percent monthly.
Olga: Here's the Metric: Caregiver retention, owned by Care Services Operations, target 90% monthly. Add it?
Updating the current value works the same way — you tell Olga the latest number, she reads back the change, and it is saved once you confirm.
Retrieving Metrics
You can ask Olga about Metrics through basic retrieval. She returns what is recorded — the measurable, its owner, its target, and the most recent value — scoped to what you have permission to see, formatted to read at a glance rather than as a raw dump.
You: What's our caregiver retention target?
Olga: Caregiver retention is owned by Care Services Operations, with a target of 90% monthly. The most recent value on record is 87%.
What Phase 1 does not do
Phase 1 stores and returns Metrics. It does not analyze them.
- No scoring or automated Scorecard view. Olga does not mark a Metric on-track or off-target, and there is no automated weekly Scorecard view that rolls the numbers up for review. The Scorecard review rhythm is roadmap.
- No trend analysis or pattern recognition. Olga reports the current value of a Metric; she does not chart its history, compare weeks, or tell you whether a number is trending up or down. Phase 1 has no pattern recognition across history — see Scope and roadmap.
When you ask for something Phase 1 does not do — "Is retention getting worse?" — Olga says so plainly and gives you what she can: the current value on record.