Stop People From Being Messengers

A lot of automation starts with the wrong question.

The question is usually: How do we make this process faster?

The better question is: Why is a person carrying this information in the first place?

Most internal back-and-forth is not collaboration. It is information transport. Someone needs something from somewhere else, so they send a message. Then they wait. Then they follow up. Then they forward the reply to a third person. The work keeps moving, but it moves through people who have no business being part of the decision.

That is the real foundation of automation: stop using humans as messengers.

The onboarding example

Take a typical onboarding flow. A new hire starts next Monday. HR creates the employee record, then messages IT to set up an email account. IT replies asking for the employee's department, job title, and start date. HR forwards that to the hiring manager, who confirms access needs. IT creates the account and tells everyone. By the time the employee logs in, three people have spent half a day shuttling information they did not shape.

Here is the problem: HR does not decide what information IT needs to create an email account. HR is just the courier. The hiring manager does not add much judgment either — access is usually standard for the role. The whole loop exists because the data lives in one place, the action lives in another place, and no system connects them.

The fix is not a faster message. The fix is removing the message.

If the HRIS collects department, title, start date, and role during onboarding — and those fields are mandatory — the system already has everything it needs. The trigger is the completed onboarding record. From there, the system can generate the IT request automatically, assign role-based access, and notify the manager without anyone writing a message.

HR's job was never to carry that data. Their job is to make sure the right person is hired and the right information is collected. Once the data is clean, the system should carry it.

The data exposure problem

There is a second, less obvious cost to messengers: they often see information they do not need.

Consider a finance onboarding step. The accounting manager fills a custom field in the HRIS that determines which legal entities the new accountant can access in the accounting system, and at what level. That information is specific to finance. HR does not need to see it. IT usually does not need to see it either — unless the setup is manual, in which case they only need the final configuration, not the reasoning behind it.

But in most organizations, that detail travels through Slack, email, or a ticket. It passes through HR. It sits in an IT queue. More people now know which entities the accountant can touch and why, even though the decision was already made by the accounting manager.

This is not just inefficient. It is a privacy and access-control leak dressed up as process. When a system carries the data, it can route only the required output to only the required recipient. The original decision and supporting detail stay with the person who owns them.

Automation is sometimes sold as speed. It is also a way to enforce need-to-know by design.

What the redesigned flow looks like

Here is the same finance onboarding step, described as a trigger-based flow:

Employee starts. A trigger fires in the HRIS.
The HRIS checks whether department, role, start date, and required access fields are complete.
If data is incomplete: the HRIS sends a structured request to the accounting manager to provide the missing fields. Once provided, the flow returns to step 2.
If data is complete: the HRIS passes the record to the accounting manager to set or confirm entity access rules and levels.
If the rules are invalid: the accounting manager corrects them, and the flow returns to step 4.
If the rules are valid: IT automation creates the accounts and applies the rules directly to the accounting system.
The manager is notified that access is ready.
The employee is notified automatically.

In this version, HR never sees the entity access detail. IT automation only sees the final configuration. The accounting manager still approves the rules, because that is a judgment call. Everything else is carried by the trigger.

A simple test

Pick any recurring internal request and ask two questions:

Who decides what needs to happen?
Who supplies the facts to make it happen?

If those are two different people, the supplier is a messenger. Remove them from the middle.

Then ask one more:

Does anyone in the middle see information they do not need to know?

If yes, the case for automation is even stronger. The system can carry the data to exactly where it belongs, and stop it everywhere else.

The goal is not fewer people. The goal is people doing the right work — and only seeing what they need to see.