Lesson 1 of 12 · 3 min read

What changes when you design the task instead of the app?

The unit of design moves from one application’s screens to the whole job a person is trying to finish, with agents carrying the steps between tools. The design work becomes deciding what the agent gathers, what it shows, and where the person decides.

Diagram: cards for Fleet, Hours, and Orders feed an Assign load card that lists its evidence, with Approve and Change buttons; the final call stays with the dispatcher.
The agent gathers fleet, hours, and orders. The dispatcher makes the one decision.

Nobody does their job in one app, so designing one app misses the job

A dispatcher assigning a load checks where each truck is, how many driving hours each driver has left, and what the customer was promised. Those answers usually live in different tools.

Designing each tool well still leaves the person carrying the job between them: copying, comparing, and remembering. That carrying is the part of the work no designer owns.

The same three tools drawn two ways: around the app, then around the task

Around the app

  • Truck map
  • Driver hours
  • Orders

Each tool is easy. The dispatcher carries the job between them.

Around the task

Assign this load

  • Truck map
  • Driver hours
  • Orders

The dispatcher decides

David Mahlmann calls this move from UX to AX: from user experience to agentic experience.

Using AI to build a product and designing a product that uses AI are different jobs. This lesson is about the second.

Two jobs that both get called designing with AI

Using AI to build

  • A coding agent writes the software
  • The customer may never meet an AI
  • The risk: the wrong thing, built well

Designing a product that uses AI

  • The AI is part of what the customer gets
  • Its behavior is the thing being designed
  • The risk: it acts where a person should decide

Start from the moment of the decision, not from a screen

When I built Dispatch Cockpit, a truck-dispatch prototype on synthetic data, I started from the assignment. No working dispatcher has tested it yet. What does one need in the second they choose a truck?

Dispatch Cockpit comparing trucks T-131 and T-118 row by row: distance to pickup and hours of service, with a note that one truck’s hours reading is 45 minutes old.
From my work Dispatch Cockpit. Two trucks side by side, with what each one trades. See Dispatch Cockpit

Not a better map. They need the evidence gathered and the rules already applied, so the choice is theirs and quick to defend.

One recommendation designed two ways: around a screen, then around the decision

Around a screen

  • “Truck 14 recommended,” and one button to accept it
  • The reasons are a click away, in another tool
  • Disagreeing takes longer than agreeing

Around the decision

  • Five numbers from the records, shown under the pick
  • The legal driving limit checked before anything is ranked
  • Saying no is as easy as saying yes

When two trucks come out level, the cockpit says so. It declines to pick. I think that refusal did more design work than any layout on the page.

The hard questions become questions about behavior

Once software carries the steps, the decisions that matter aren’t about where things sit. They’re about what the agent does at each step, and where it stops.

One task, and where the person comes in
  1. Gatherthe agent finds the records
  2. Checkthe rules that can’t bend
  3. Flagwhat’s missing, old, or unusual
  4. Recommendwith the evidence attached
  5. Decidethe person who answers for it

Screens still matter. A recommendation set badly gets ignored or, worse, trusted without a look.

Design the job first. The screen is where the person checks it.

Check yourself

In your product, what does a person still carry between tools?

That carrying is where an agent earns its place, and where the design work starts: what gets gathered, and what the person sees of it.

Could a new teammate point to where the agent stops and the person decides?

If they can’t find it on the screen, the line exists only in the code, and nobody is really deciding.

The idea: David Mahlmann, From UX to AX: The Unit of Design Is Changing. The example: Dispatch Cockpit, a prototype on synthetic data, on this site.