Pulse meetings
RunOlga's weekly leadership rhythm: the 90-minute pulse meeting where the team reviews and resolves.
Roadmap
The pulse meeting (EOS: Level 10 Meeting) is the standing weekly meeting where the leadership team comes together, reviews the same set of numbers and commitments every week, and resolves the issues that are in the way. It is the heartbeat of running on RunOlga.
What it is
The pulse meeting is a leadership-team meeting with three things held constant week to week:
- Same day, same time. It is a standing meeting, not one that gets rescheduled around other work.
- 90 minutes. Long enough to do real work, short enough to demand focus.
- The same agenda, every week. Familiarity removes friction. The team knows exactly what comes next, so the time goes to the work rather than to deciding how to spend it.
The point is rhythm. A leadership team that meets on the same beat, against the same scorecard and the same priorities, stays aligned without a constant stream of side conversations.
The agenda
The pulse meeting runs the same shape each week. The early sections are a fast review — confirming the team is on track and naming anything that is off. Most of the time goes to the issues.
| Segment | What happens |
|---|---|
| Check-in | A brief opening so everyone arrives present. |
| Headlines | Good news, plus customer and employee headlines — the short list of what's worth talking about this week. |
| Scorecard review | A quick read of the weekly measurables. Anything off-track becomes an issue. |
| Priorities review | Each quarterly priority is on-track or off-track. Off-track ones drop to the issues. |
| Tasks list | The short-horizon tasks from last week — done or not done. Anything unresolved becomes an issue. |
| Issues | The bulk of the meeting. The team works the issues list with Identify, Discuss, Solve (IDS). |
| Conclude | Recap new tasks, confirm decisions, rate the meeting. |
The first half of the agenda is deliberately fast. Its job is to surface what's off-track and push it onto the issues list, where the team has the time and the method to actually resolve it.
What RunOlga does in Phase 1
Phase 1 does not run the pulse meeting. RunOlga does not schedule it, walk the team through the agenda, or facilitate the issues segment. The meeting happens the way the team already runs it.
What Phase 1 does support is read-only retrieval of the most recent pulse-meeting record. A leader can ask Olga what happened, and she retrieves it:
You: What happened in last week's pulse meeting?
Olga: Here's the most recent pulse meeting on record, from June 10. Three priorities were reviewed, two on-track. Four issues were worked; two were solved. Two new tasks were captured.
This is part of basic retrieval: Olga returns the stored record as-is. She does not analyze it, compare it to prior weeks, or draw out trends.
On the roadmap
Running the pulse meeting end-to-end is roadmap, not Phase 1. So is the analytical work that would make Olga a meeting partner rather than a record keeper.
In particular, pre-meeting briefings with analytical synthesis are explicitly deferred to a later phase. Phase 1 can pull current state, but it does not generate the kind of summary that reads the scorecard, the priorities, and the open issues together and tells the team where to focus. Olga prepares, surfaces, and captures in Phase 1 — she does not yet synthesize or advise.
See Scope and roadmap for the full picture of what is live now and what is on the way.