The intentional process environment.

“Here’s our onboarding SOP. It’s not implemented yet.”

The file had been finished five months earlier. Sections, owners, timelines. Then nothing. I asked the three managers who had hired since how they onboarded their people. Three different answers, none of them matching the document.

Most companies measure process maturity by counting SOPs. But people read an SOP once, during onboarding, and run the process from memory after that. The document is an artefact. It does not run anything.

What an intentional process environment is

In an intentional process environment, work does not depend on people remembering to do it.

Most people start the day by opening a task list. It holds what they need to do today. They do the tasks and mark them done. Doing a task, or marking it done, often creates new tasks, for themselves or for someone else. That is how work moves through the company.

And every task carries its own guide. When a task is created from its template, the SOP for doing it comes with it. The guide is no longer something you have to go and find. It is in front of you, in the task, at the moment you do the work.

Work is not something people magically remember to do. It is defined, it is presented to the person who owns it, and we know when it is done.

The five elements

1. Tasks are created in a tool, either by a person, by a trigger, or by the completion of an earlier task.
2. Tasks are assigned to people. One owner, not a team inbox.
3. Tasks contain their guide. The SOP is part of the task template.
4. Tasks are checked off when done. So you know what happened, and what did not.
5. Someone owns the routing. A named person makes sure tasks reach the right people, and that nothing sits unowned.

If you have worked in customer service, you know this already. It is how a ticket system works: a request becomes a ticket, the ticket is routed, it has an owner and a status, and it is closed when done. The idea is to run the rest of the operation with the same discipline.

How work moves: two chains

The value shows when one task creates the next, across teams. A market office orders parts from central. Completing that order task creates an order-processing task at the central warehouse. Completing that creates a task in finance to record the order.

Or delivery. Sales closes an order. That creates a delivery-preparation task in operations, which in turn creates the individual delivery tasks, each tracked on its own, so you can see exactly what stands between you and a delivery that is ready.

Once work moves like this, a lot follows almost for free:

• The backlog is visible. You can see what is open, what is late and who is overloaded, instead of guessing from inboxes and chat threads.
• You track outcomes, not adherence. If an invoice should be booked within 48 hours, an overdue task tells you, without anyone checking whether the SOP was read.
• Knowledge stops living in one head. When the guide is in the task, someone else can pick it up the week the usual person is out.
• New people become useful faster. Temporary help can take the repeatable tasks from day one, because the tasks explain themselves.

It is not about the tool

This can be built in almost any modern tool. I have set it up in support systems, in ClickUp, and in CRMs. It also does not need to be one tool. Usually the best choice is the tool each team already works in:

Team	Natural home for its tasks
Finance	The ERP
Sales	The CRM
Customer service	The ticket system
Operations	A project or task tool

Then you make the tools talk to each other, so a task completed in one creates the right task in the next. That used to be an integration project. With today’s workflow tools and AI, it is mostly configuration.

How to start

1. Pick one flow that crosses at least two teams, like an order or an onboarding.
2. Write down the steps and what should trigger each one. The recording method gets you the guides quickly.
3. Build a task template for each step, with the guide inside.
4. Connect the triggers, so done in one step creates the next.
5. Name the person who owns routing, and look at overdue tasks every week.

Then expand, one flow at a time. It only works if this is the one way the work moves. The moment people can get the same thing done by a chat message or a side spreadsheet, the environment starts to decay. That is the subject of the last note in the series: do not accept manual overrides.