Priorities and Tasks
Quarterly Priorities and the Tasks they break into: RunOlga's unit of focused execution.
Phase 1
A Priority is what the team commits to this quarter. A Task is one short step toward it. Together they are how a leadership team turns intent into work it can actually finish — and the path between them is RunOlga's signature flow.
Priorities (EOS: Rocks)
A Priority is a focused objective the team commits to for the quarter — roughly 90 days. It is deliberately a short list: a Priority is something the team can finish, not everything the team would like to do.
Each Priority carries:
- An outcome — what is true when it is done, stated as a result rather than an activity.
- A timeline — the quarter it belongs to and its target completion.
- Contributing seats — the seats accountable for moving it forward.
Across the quarter, 30/60/90-day checkpoints keep a Priority honest about whether it is on track. In Phase 1 these checkpoints are a lightweight way to think about pacing; structured milestone tracking against them is a roadmap refinement, not a Phase 1 feature.
Priority fields
| Field | Description |
|---|---|
| Outcome | What is true when the Priority is complete — the result the team is committing to. |
| Timeline | The quarter and target date the Priority is scoped to (about 90 days). |
| Contributing seats | The seats accountable for moving the Priority forward; the pool Olga draws task owners from. |
Tasks (EOS: To-Dos)
A Task is a short-horizon action item — typically a 7-day cadence — that moves a Priority forward. Where a Priority is the quarter's commitment, a Task is the next concrete thing someone does about it this week.
Each Task carries:
- An owner — a single seat accountable for it.
- An estimated effort — how many hours it is expected to take.
- A scheduled date — when it is planned to happen.
Task fields
| Field | Description |
|---|---|
priority_id | The Priority this Task moves forward. |
assigned_seat_id | The seat that owns the Task, drawn from the Priority's contributing seats. |
estimated_hours | The estimated effort for the Task, in hours. |
scheduled_for_date | The date the Task is scheduled for. |
How Priorities become Tasks
Priorities decompose into Tasks, and that decomposition is RunOlga's signature flow. When you create a Priority, Olga proposes a breakdown of 4–8 tasks based on the Priority's outcome, timeline, and contributing seats. Each proposed task comes with a suggested owner from the contributing seats, an estimated effort, and a suggested schedule.
The breakdown is a proposal, not a commitment. You iterate on it conversationally — accept all of it, edit individual tasks, reject ones that do not fit, or counter-propose — and nothing is written until you approve. On approval, each task is created with its priority_id, assigned_seat_id, estimated_hours, and scheduled_for_date.
You: Add a priority to cut caregiver onboarding time to under two weeks this quarter.
Olga: Got it. Which seats contribute to that outcome?
You: Office Operations Manager and Care Services Operations.
Olga: Here's a first breakdown of six tasks across those two seats, with estimated hours and dates. Want to adjust any before I create them?
This flow is the most significant Phase 1 capability. For the full mechanics — how the proposal is shaped, how you iterate, and what gets written — see priority-to-task decomposition.
Working with Priorities and Tasks in Phase 1
In Phase 1 you create and update Priorities by talking to Olga rather than filling out forms. She asks for the required fields, repeats the structured record back, and writes it only once you confirm. See conversational data entry.
You can also ask Olga about the current state of your Priorities:
You: What are our current priorities?
Olga: Here are the active Priorities for this quarter.
That query returns the active list, scoped to what you have permission to see. See basic retrieval.
Olga prepares, proposes, and captures here — she shapes the task breakdown and writes what you approve. She does not decide which Priorities the team should commit to or judge whether a Priority is realistic; those remain the team's call.