About Oliver Hitchings

I design small automation systems around the work people already do.

My approach starts with the task: what triggers it, which evidence it uses, where judgement is needed and who owns the result.

INSPECTION.01 · WORKING FOCUS

STANCE.02 · OPERATING BOUNDARY

The model call is only one step.

The operational questions come first: which source of truth wins, when the system should stop, what gets logged and what a person should do when confidence is low. Once those boundaries are clear, the build can stay narrow, observable and easier to hand over.

RESPONSIBILITY MAP.03

Four rules for an operable system.

SRC.01 Source of truth

Show the work

Prompts, rules, assumptions and logs visible enough to review a bad run.

HUM.02 Human responsibility

Keep a person responsible

Stop for review when a step is uncertain or consequential.

STP.03 Failure path

Design the failure path

Make retries, stop conditions and escalation explicit.

OWN.04 Handover

Hand over ownership

Leave run instructions, logs and change notes with the owner.

A useful starting point

Bring one task that already repeats.

Describe the trigger, inputs, output, tools and reviewer. That is enough to decide whether a Task Map, First Build or Operator System is the sensible starting point.

View packages Start an enquiry