Orrery · Start here
What Orrery is for
Orrery is a map of how your organisation actually runs. It answers three questions: how does this piece of work happen, what is missing from it, and what would it be worth to change it.
Most processes are written down as the steps people take. The hand-offs between the steps are not. A request waits in an inbox until someone notices it. A decision is made in a meeting and never recorded. Nobody is blocked, so nobody sees the gap. Orrery draws every step, whether a person, an AI assistant or a system does it, and every link between steps, so those gaps show up.
What you get
- Every link says what makes it happen. Some run on their own: a system sends a message, or a schedule fires. Others run only when somebody remembers. The map draws the second kind in orange, so a fragile chain looks fragile.
- Every step says how you would know it ran. A record in a system, an email, an entry in a log. A step that leaves no evidence at all is marked, because what cannot be seen cannot be checked.
- Findings, worked out from the map. Orrery lists the places where work depends on memory or leaves no trace, most important first.
- Your organisation's map is yours. Each organisation's map is kept separate, and nothing on one is ever shown on another.
Who it is for
Operations and IT leads, and anyone responsible for how work flows between teams and systems. You read the map in your browser, or ask the AI you already use about it.
What it is not for
- Drawing diagrams. You cannot draw on the map. It is built and kept up to date from how the work really runs, so what you see is a record, not a sketch.
- Cutting people out. A step where a person uses their judgement is never flagged as a problem. The point is to take the remembering and relaying off people, so they have more time for that judgement.
- Tracking tasks. Orrery shows how work is shaped, not who is doing what today.
Updated 14 November 2026