One node, run by your people.
Solo installs a small operation, called a node, around one piece of work and the data it runs on. Your people run it. This page says what a node is, what the install takes, and what comes after.
One piece of work and its data.
A node is one role, one team, or one department and the processes it runs, with the data they depend on. The processes can be data quality, the ownership of data rules, or any business process. The node runs on the systems your business already uses.
Every piece of the node's work enters its queue, and the node owns each item until it is done.
When something arrives that no rule covers, the node sends it up to its orchestrator, the manager that work already goes up to today.
What every node runs.
The same seven for every node and every kind of work. The assessment asks one question about each.
People & roles
Who runs the work, who backs them up, and who decides what the rules do not cover.
Intake Queue
One place where all the node's work arrives and is logged.
Prioritization
A regular rhythm for choosing what is done first and what waits.
Escalation path
What happens when something is beyond the node, so nothing sits without a next step.
Awareness
The node can say what is open, what is resolved, and what is stuck by looking, without preparing a report.
Definition of done
What finished looks like is written down before the work starts.
Communication cadence
A short report on a schedule, so the people who depend on the node know it is running.
Proven on real work. Then it is yours.
During setup, we draw the circle around the processes with your sponsor, name the operator and the backup, and fill the Node Canvas with the rules and their owners, the queue, the rhythm, and the definition of done. During supervision, the node runs on real work while we coach, and the backup runs it alone for one full cycle. Graduation comes when five real cases have closed against their definitions of done and seven proofs are witnessed, signed by your sponsor.
The Solo Playbook and the Node Canvas are free. The Coached Install adds a coach, a pace, and a certified graduation. Prices and sizes are on the Solo page.
The node runs itself. Ongoing services are optional.
A graduated node needs nothing from us. When it wants more, the ongoing services run on it. They are issue resolution, risk assessment, standards deployment, and certification of its work and data, each scoped to the node and priced on request.
Short answers to what people ask first, including whether a graduated node still depends on us, are on one page. Common questions →
The same canvas staffs a person or an agent.
A node is written down as roles, rules with owners, the places it reads and writes, work methods, and an escalation path. Those pages are also an agent's instructions. A Role node that runs well can hand its operator role to an agent, the Agent Upgrade, under the same rules and a named human orchestrator.
Growing past one node
A Department node holds Team nodes and Role nodes. Each fills its own canvas and escalates up. Only the size of the circle changes.
The worked example: Node Zero, staffed by an agent →
Several agents, one canvas each: the Agent Team example →
Seven questions, one per capability.
You get your Readiness Shape, which of the seven are absent, emerging, or functioning, and a Shape Report to download. No sign-up.