How to start: map your operating model
Most companies know where AI could help. Far fewer can say what "help" means in terms they could hand to someone else and hold them to.
That sentence is your operating model, and it is what a LeedAB Artificial Being needs to own real work. This chapter is about drawing it: a short, honest map of the outcomes, the roles behind them, and the one place work should be owned first.
Start from outcomes, not tools
List the outcomes your company is paid to produce: a reconciled month-end pack, a cleared port document, a resolved support case, a delivered load. Outcomes are stable even as tools change, and they are the unit an AB is measured against.
For each outcome, write the trigger that starts the work, the steps in between, and what "done" looks like. Keep it to a few lines. You are drawing a map, not a process manual.
Name the roles behind the work
Behind every outcome is a role - the person or team who owns it today. Naming the role tells you what context an AB will need, whose judgment matters, and where a human has to stay in the loop.
- Owner - who is accountable for the outcome.
- Inputs - the systems, documents, and people the work draws on.
- Decisions - the moments that need a human call.
Pick the first outcome to hand over
Choose one outcome that is high-frequency, well-understood, and low-blast-radius if it needs a second look. That is where your first Artificial Being should start. Depth on one role beats a shallow rollout across ten.
The map is done when a new teammate could read it and know what your company does, who owns it, and where the judgment calls are.
With that map in hand, you are ready to give a role its context. That is Chapter two.