Introduction

RunOlga is a business operating system for leadership teams — one place to run the day-to-day operations of an organization. Olga is its embedded AI assistant, bringing chief-of-staff-quality thinking to every leadership seat. RunOlga is the platform; Olga is its central mechanism for distributing leadership capacity.

RunOlga is built on a familiar operating model (the EOS / "Traction" approach): a shared vision, the right people in the right seats, a short list of measurables, quarterly priorities, a weekly meeting rhythm, a clear issues process, and documented core processes. Olga is the layer that helps every leader work that model.

How to read these docs: This site describes how RunOlga must behave — its concepts, workflows, and the way leaders interact with Olga. Each page is marked Phase 1 (built now) or Roadmap (the fuller vision). When the product needs to change, change the docs first, agree on the wording, then make the system match.

The operating model

RunOlga organizes operations into a small set of connected building blocks — Vision, the Accountability Chart, Priorities and Tasks, Metrics, Issues, Processes, pulse meetings, people reviews, and the Knowledge Base. Start with The RunOlga model for how they fit together and which are live in Phase 1.

What Olga does in Phase 1

Phase 1 focuses on four capabilities that let a leadership team run on RunOlga by talking to Olga instead of filling out forms.

1. Conversational data entry — populate Priorities, Issues, Processes, and Metrics by talking to Olga. She collects the required fields and writes nothing until you confirm.
2. Basic retrieval — grounded answers about organizational state, scoped to your permissions: "What are our current priorities?", "Show me open issues."
3. Setup clarification — during setup, Olga flags incomplete or ambiguous entries so the operating system is fully specified.
4. Priority-to-task decomposition — when a Priority is created, Olga proposes a 4–8 task breakdown you iterate on and approve before anything is committed.

Across all four, the rule is the same: Olga proposes; you decide. Nothing is written without your explicit confirmation, every answer is grounded in your organization's real data, and everything respects your permissions. See Trust & safety.

Phase 1 vs. the full vision

The notes and architecture describe much more than Phase 1 delivers — Olga running meetings, tracking the scorecard, guiding people decisions, and making recommendations. Phase 1 deliberately stops at what can be built, tested, and shipped responsibly: Olga prepares, proposes, surfaces, and captures, but does not decide or recommend. Scope & roadmap is the source of truth for what is in Phase 1 today versus deferred to later phases.

Where to go next

• The RunOlga model — the building blocks and the weekly rhythm
• Working with Olga — how she composes answers, her voice, and her panel
• Capabilities — the four Phase 1 capabilities in depth
• Trust & safety — grounding, permissions, isolation, confirmation
• Scope & roadmap — what's in Phase 1, what's next
• Acceptance criteria — how we verify Phase 1 is done