Issues
The open-problems list: how RunOlga captures what is in the way and works it to resolution.
Phase 1
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 — captured as it arises, worked at the weekly pulse meeting, and closed with a resolution the team can look up later.
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.
| Field | Description |
|---|---|
| Title and description | A short, plain statement of the problem, and what is happening. |
| Raised by, and when | Who surfaced it and the date. |
| Category and severity | What kind of problem it is, and how much it matters right now. |
| Affected seats | Which seats the issue touches. |
| Status | Open, In Progress, Resolved, or Closed. |
| Resolution summary | How it was solved, once it is. |
Issues can be linked to Priorities or Processes when they're connected — a problem that blocks a Priority should say so.
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, which in Phase 1 runs inside RunOlga:
- 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. Threaded comments on the issue carry the discussion between meetings.
- Solve. Decide what happens next — often an action item with an owner that lands on a To-Do list, sometimes a decision — mark the issue resolved, and describe how it was solved.
Working with Issues
- View the Issue List with filters — by status, severity, category, or seat.
- Create new issues — directly, or by talking to Olga.
- Discuss issues in threaded comments.
- Mark issues as resolved and describe how they were solved.
- Link issues to related priorities.
Capture an issue through Olga
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.
Retrieve issues through Olga
You can ask Olga for the current state of the list — open or resolved. See basic retrieval for the full retrieval model.
You: Show me open issues.
Olga: Here are the open issues, most severe first:
Olga also notices when an issue relates to an active priority — if you log an issue that touches a Priority in flight, she points at the connection so you can link them — and refers back to past issues in relevant conversations.
What Olga does not do here
Olga lists issues and surfaces direct connections. She does not identify patterns across history or recommend resolutions.
- She will not tell you that several issues over months point to a recurring problem — that arrives with Insights in Phase 2.
- She will not propose how to solve an issue or which to prioritize.
Olga surfaces and captures what is in the way; the team identifies, discusses, and solves it. See Scope and roadmap for the full boundary.