Delivery Pipeline and AI Judgment – A-CX Weekly

This week at A-CX we’ve been writing about where people still belong in AI delivery, from the five steps inside our delivery pipeline to why judgment, not coding, is what’s left to pay for.

Delivery Pipeline Steps

Ilpo has been writing about A-CX’s five-step AI delivery pipeline. He lays out what each step takes in, hands off, and where a human has to approve before it moves on. Check it out here.

Judgment Over Code

Mikko has been writing about what AI delivery still has to price for. He argues AI made human coding uncompetitive at any price, so judgment and discovery are what a buyer is really paying a vendor for. Check it out here.

Thoughts And Technology

Ville shared some thoughts about working the bow at the Rolex Big Boat Series, where the calls get agreed before the start because there is no room for interpretation at speed. His point for AI delivery is that the advantage is not the tools but the debrief, so read the full post.

Here at A-CX we’ve been talking about how machines almost always warn you before they fail. Our preventive maintenance demo turns the data off-highway fleets already produce into one call a service team can act on, and Ville and Mikko walk through the full demo.

What We've Been Reading

Building AI and getting people to use it are two different races, as this LinkedIn post by Chris Tottman argues, citing EY research across 23 markets in which the US leads on building AI but is not among the markets furthest ahead on adoption.