Agentic patterns

Agentic patterns, one shape at a time.

Workflow automation is pattern work. A pattern is a shape, and each box in it can be filled by code, a model, an agent or a person. This series takes the shapes one at a time: the principle, where it applies, and a small demo you can watch run.

Why patterns

The framework is the last question

When a team asks me whether an agent can take over part of a process, I start with four questions. What happens when the model is wrong? Who decides when it is unsure? Which rules may never bend? Where does a person sign off? Each pattern below answers one of them.

None of this started with agents. Wil van der Aalst and his colleagues in Eindhoven catalogued workflow patterns around 2000, and Gregor Hohpe and Bobby Woolf published Enterprise Integration Patterns in 2003. The agent catalogues from Anthropic and Microsoft describe the same shapes with a model in some of the boxes. So each page here shows its pattern three ways: built from code alone, as a hybrid, and with agents throughout.

Every demo runs on a real agent framework. In the four demos live today a scripted stand-in plays the model, so the runs are repeatable; the demos now in preparation replay recorded runs of a real model.

Collaboration

When do several agents beat one?

In preparation: Maker-checker, Group chat and round robin.

Choosing

Start from the problem

Real processes combine them. A digital mailroom routes each document by confidence, validates the fields it extracts, applies policy in a workflow and stops for approval before money moves.

If this is your problemStart with
The answer feeds other software and has to be well formedValidate and retry
High volumes of routine decisions from a known listConfidence routing
Some steps are law or policy, some need judgementAgents inside a workflow
An action is costly or hard to undoHuman approval gate

Contact

Questions, ideas or a conversation?

I’m always glad to hear from people working on AI, product strategy, transformation or software.