Pulse meetings
RunOlga's weekly leadership rhythm: the standing pulse meeting, run inside RunOlga with notes, decisions, and action items captured.
Phase 1
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 — and in Phase 1, it runs inside 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. Weekly pulse meetings recur automatically.
- 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.
Running a meeting in RunOlga
The Meetings section is where meetings are scheduled, run, and documented — for pulse meetings and beyond.
| Meeting type | Cadence |
|---|---|
| Pulse Meeting | Weekly, recurring automatically |
| Quarterly Review | Each quarter |
| Annual Planning | Yearly |
| Ad-hoc | As needed |
Each meeting record holds the type, date, attendees, notes, decisions, and action items. The flow:
- View upcoming and past meetings.
- Start the meeting — this opens the live agenda.
- Take notes as the meeting runs.
- Capture decisions and action items as they happen.
- End the meeting — everything is finalized into the record.
Action items automatically appear on the assigned seats' To-Do lists, so nothing agreed in the room evaporates after it.
What Olga does here in Phase 1
Olga's role in meetings is deliberately limited in Phase 1:
- Answers questions like "What happened in last week's pulse meeting?" — part of basic retrieval:
You: What happened in last week's pulse meeting?
Olga: Here's last week's pulse meeting record, from June 10. Three priorities were reviewed, two on-track. Four issues were worked; two were solved. Two new action items were captured — one each for Care Director and Operations.
- Helps capture decisions and action items as they're spoken, so the person running the meeting isn't also the stenographer.
She returns and captures records; she does not analyze them, compare weeks, or draw out trends.
On the roadmap
Roadmap — Phase 2
Deeper meeting partnership — chief-of-staff-level meeting support — is Roadmap — Phase 3. See Scope and roadmap for the full phase map.