Talk at Product Heroes 2026 · 1 October 2026 · Milan

Who moved the design?

From the Happy Path to the Happy Goal in agentic design

For years we designed journeys. With agentic services, the service designer delivers rules and data access, and the interaction changes at every iteration. The talk explained how to design a goal and how to measure whether it is reached.

Luigi Greco · Founder & CEO (Chief Executive Officer), Conflux NH Milano Congress Centre
Page of the Conflux Agentic Design Canvas: A4 poster with nine numbered blocks and a validation checklist
Agentic Design Canvas v1.09 blocks · PDF (Portable Document Format) A4
The talk

Agentic design: the service designer writes the agent's rules, not the user's journey.

You define a goal, hand over rules and access, and measure whether the goal is reached.

Happy PathBefore
step 1 step 2 step 3 end every screen decided in advance
It is the customer journey drawn in advance: the user starts here and ends there, and service design describes every step.
Happy GoalNow
brief done three iterations, one criterion
The service designer delivers rules and data access. Every iteration is different; the completion criterion stays the same.

From the journey to the goal

An agentic service does not follow a fixed path: it chooses its own steps, and every iteration is different.

The service designer delivers rules, not screens

The project becomes a set of rules, data access and stop conditions. The Happy Goal is the declared goal, together with the criterion that says when it has been reached.

From brief to release

The talk follows a real agentic service, step by step, and explains why this frontier belongs to service design and not to engineering.

«You no longer design a journey: you define a goal and measure whether it is reached.»
Luigi Greco · from the talk abstract
The tool

Design the Happy Goal on one sheet.

The Agentic Design Canvas, a method by Luigi Greco, lines up the decisions to take before writing code. Nine blocks: if one stays empty, the risk reaches production.

1Target user

Who uses it, and how do they work today?

2Problem

Which process are you automating, and what does it cost today?

3Input

Which data, APIs (Application Programming Interfaces) and access are needed?

4Trigger

What starts it: an event, a time, a request?

5Actions

Which steps does it take?

6Orchestration

One agent or several? Who coordinates?

7Output

What value does it produce, for whom, in what format?

8Exceptions

When does it stop and ask a person for help?

9Done

When is the goal reached, and with which metrics?

The Happy Goal, in writing
6 yes · GO 4-5 · REFINE 0-3 · RETHINK

The canvas ends with six validation questions. The number of positive answers tells you whether to start, refine or rethink.

Further reading: Agentic Design Canvas: designing agents before the code.

When to use it

How do you use the canvas?

Before developing an agent

To decide what to build before deciding how.

When a PoC (Proof of Concept) doesn't scale

To find the block that was left empty.

To align the team

Product, design and engineering on the same sheet.

Download

Download the canvas

Two A4 PDFs, light and dark versions. To print and use with your team.

  • FormatA4 PDF, one page
  • Versionslight and dark
  • Content9 blocks, checklist and filling guide

Questions

Before you download it

What is the Agentic Design Canvas?

An A4 poster in nine blocks to design an agentic service before developing it.

Do I need to know how to code?

No. The canvas collects product and design decisions, not code.

Who is it for?

Product managers, designers and teams taking an agent from prototype to release.

Can I use it with my team?

Yes. It is designed to be filled in together, block by block.

Is it free?

Yes. We ask for your name, business email and role.

After the talk

Want to design your first agentic service?

Let's talk about it in a Discovery Call.

Write to us at sales@weareconflux.com