Issues
The open-problems list: how RunOlga captures what is in the way and works it to resolution.
Phase 1 + roadmap
Issues (EOS: Issues List) are the open problems a leadership team needs to resolve. RunOlga keeps them in one list so nothing in the way of progress stays buried, and works each one to a clear outcome. Phase 1 captures and lists issues; the meeting-driven workflow that resolves them is on the roadmap.
What an Issue is
An Issue is an open problem, obstacle, or blocker surfaced for resolution. Anything slowing the team down belongs on the list: a stalled hire, a process that keeps breaking, a metric trending the wrong way, a decision waiting on someone.
Each Issue carries a status (such as open) and a severity. Status tracks where the issue stands; severity captures how much it matters right now. Together they let the team see, at a glance, what is unresolved and what deserves attention first.
| Field | Description |
|---|---|
| Title | A short, plain statement of the problem. |
| Description | What is happening and why it is in the way. |
| Status | Where the issue stands — for example, open. |
| Severity | How much the issue matters right now, used to order the list. |
The point of the list is honesty. An issue named is an issue the team can work; an issue left implicit keeps costing the organization without ever being addressed.
The Issues process (IDS)
The Issues process is IDS — Identify, Discuss, Solve. Issues are captured as they arise, then worked, most often at the weekly pulse meeting:
- Identify. Get past the symptom to the real issue. The first thing said is rarely the actual problem.
- Discuss. Say what needs to be said, once. The goal is to surface the relevant context, not to relitigate.
- Solve. Decide what happens next — often a task with an owner, sometimes a decision — and take the issue off the list.
Roadmap
In Phase 1
Phase 1 gives the Issues list its foundation: capture and retrieval.
Capture an issue
You log an issue by talking to Olga rather than filling out a form. See conversational data entry for how this works across all records.
You: Log an issue with caregiver retention in Oakland.
Olga: Got it. How severe is this right now, and is there anything specific behind it I should capture in the description?
Olga collects the required fields, repeats the structured record back, and writes nothing until you confirm.
List open issues
You can ask Olga for the current state of the list. See basic retrieval for the full retrieval model.
You: Show me open issues.
Olga: Here are the open issues, most severe first:
Under the hood, this queries Issues with status=open and returns them ordered by severity.
What Olga does not do here
Olga lists issues. She does not identify patterns across them or recommend resolutions.
- She will not tell you that several issues point to a recurring problem.
- She will not propose how to solve an issue or which to prioritize.
These are on the roadmap, not Phase 1. Olga surfaces and captures what is in the way; the team identifies, discusses, and solves it. See Scope and roadmap for the full boundary.