Processes
The handful of documented, repeatable ways the organization does its core work.
Phase 1
A Process is a documented, repeatable way the organization does something that matters. Processes (EOS: Core Processes) are the few ways of working that, when everyone follows them, make the business run consistently regardless of who is on shift that day.
What a Process is
A Process captures a way of working that should not be reinvented each time — onboarding a caregiver, handling a family complaint, reporting an incident. It is not a sprawling manual of everything the organization does. It is the short list of core procedures that hold the business together.
The point is consistency. A documented Process means the work happens the same way whether the person who usually does it is in or not, and whether it is the first time or the hundredth.
Why Processes matter
- Consistency. The organization's core work runs the same way every time, so quality does not depend on who happens to be doing it.
- Onboarding. A new person can learn the right way to do something from the record rather than from whoever is free to explain it.
- Explicit know-how. What lives in people's heads becomes part of the organization's content — durable, shared, and not lost when someone moves on.
What a Process record holds
Processes live in a library, organized by category:
| Field | Description |
|---|---|
| Name and description | What the Process is and what it covers. |
| Category | Where it sits in the library, for browsing. |
| Owner | The seat accountable for keeping it right. |
| Content | The actual process — the steps themselves. |
| Last reviewed | When someone last confirmed it still matches reality. |
Every change to a Process is kept as history, and a Process can be linked to related Issues — when something keeps breaking, the process it breaks against should say so.
Processes in Phase 1
In Phase 1, Processes live alongside Priorities, Issues, and Metrics as part of the organization's content. You can browse the library by category, view any Process in detail, and edit Processes based on your permissions — and you can work with them by talking to Olga.
Adding a Process
You add a Process to the library by describing it in conversation. Olga collects the details, repeats the structured record back to you, and writes nothing until you confirm.
You: Add the incident reporting process to the library.
Olga: What are the steps, and who is responsible for each?
This is the same flow Olga uses for every record — see conversational data entry for how she gathers fields, asks clarifying questions when something is vague, and confirms before saving.
Retrieving a Process
You can ask Olga for a Process that is already in the library, and she returns it grounded in the organization's content. See basic retrieval for how retrieval is scoped to what you have permission to see.
Review reminders
A Process that nobody rereads drifts away from how the work actually happens. The library shows when a Process is overdue for review, and Olga flags overdue Processes — a date check, not a judgment.
That is where the Phase 1 line sits: Olga captures, retrieves, and flags overdue reviews. She does not critique a Process's content, suggest improvements to it, or notice that one is missing — those arrive in later phases. See Scope and roadmap.