← All posts

Nobody owns agent experience. Put a gate in the process instead

Listen · 2 min 19 s

ı w
Ask who owns how an agent experiences your company and you’ll get four answers: SEO, engineering, product, support. Each is partly right. None is accountable for the whole.

That’s why nobody measures it.

The usual fix is to name an owner. It rarely holds. Whoever gets the title inherits a problem that spans systems they don’t run and decisions they’re not in the room for. A common practice with fancy titles in business cards.

A gate works better. No decision that adds or changes a channel moves forward until it states which outcomes that channel is allowed to end in.

A new partner listing. A redesigned flow. A chatbot pointed at the help center. An integration with a reseller. Each one is a channel, and each gets approved today on whether it works, not on what it commits the company to.

The gate sits where approval already happens: the change review, the launch checklist, the partner onboarding form. One required field, checked against the declared list for that result. If the list doesn’t exist yet, writing it is the first task, and the business writes it.

Why a gate and not an audit? An audit tells you where channels diverge today. Six months later new ones have shipped, old ones have been edited, and the map is stale again. Audits decay because nothing makes them repeat. A gate repeats on every change without anyone remembering to run it.

It also needs no new owner. Whoever runs the approval process already has the formal authority. The only thing added is a question: the business answers it, product checks the flow against it, engineering instruments it.

Expect friction in the first week. Some changes turn out never to have been tied to an outcome at all, and the gate is where that gets noticed instead of after launch.

Look at the last three channel changes your company shipped. For each one, find a written answer to this: what is it allowed to end in?

If you can’t find it, that’s where the gate goes.

Discuss on LinkedIn