← Acolad hub 01c / 21 — Selected Work Pedro Rodrigues — Treze413
Project No 01c

Lia Go

Designing the UX for multi-agentic AI — 60+ prototypes across four version branches.

Role
Lead Product Designer
Location
London, UK / Remote
Year
2025–2026
Engagement
End-to-end
01 — Overview

Multi-agentic orchestration made intuitive.

Lia Go is Acolad's flagship multi-agentic orchestration platform. A COO agent orchestrates Project Manager agents, who manage Specialist agents for translation, summarization, SEO, and content generation. Pedro designed the interaction model that makes this complex system intuitive for non-technical users, delivering 60+ Figma prototype iterations across 4 major version branches.

02 — The challenge

A fundamentally new UX problem.

Multi-agentic AI is a fundamentally new UX problem. Users must understand what autonomous agents are doing, why they made decisions, and how to intervene — without technical knowledge. Finding the right balance between conversational (chat), hybrid (chat + UI), and full UI-driven (dashboards, editors, workflows) paradigms.

The platform needed to support 9 distinct use cases: document digitization, smart summarization, guided content creation, video subtitling, AI transcreation, marketing content generation, multilingual SEO, MT evaluation, and SEO-enhanced post-editing. One interface framework, nine workflows.

03 — Process

Four moves, one platform.

/01
Research

User interviews with Leonardo and Jacqueline (Sep 2025). Competitive analysis of agentic AI platforms and workflow builders. Created a "Wall of Experience" mapping stakeholder journeys and pain points.

/02
Explore

Three interaction paradigms tested: conversational bottom-up, conversational top-bottom, and hybrid UI + chat. Each explored through dedicated prototype branches.

/03
Iterate

60+ Figma iterations across 4 major version branches (v0.1-v0.9 concepts, v0.10 validation, v2-v4 refinement). Agent configuration panels, execution monitoring, prompt editors. Design system and component library established.

/04
Document

Recorded Figma design system walkthrough. Documented design-to-development workflow in Linear. Established handoff practices between design and engineering.

System architecture — Lia agents platform
Lia Agents multi-agentic framework — 6 layer architecture
Agent hierarchy and data flow
COO to PM to Specialist agent hierarchy
Request lifecycle data flow
Design evolution — Figma prototypes and Linear workflow
Lia Go Figma design system walkthrough
FigmaDesign system
Lia Go Figma prototype iteration
PrototypeInteraction model
Acolad Product Design workflow in Linear
LinearDesign-dev handoff
Lia Go — interface exploration
Lia Go interface concept
ExplorationEarly concept
Lia Go interaction model
IterationInteraction model
Lia Go refined UI
RefinementUI direction
Lia Translate — the platform in practice
Translation empty state
Empty stateNew translation
Translation result
ResultFrench output
Context panel
ContextSource management
Clarify ambiguities
ClarifyResolving ambiguities
Translation complete
CompleteDownload ready
Dark mode
Dark modeAlternate theme
The hardest design problem wasn't the interface — it was deciding what to show and what to hide. Autonomous agents make hundreds of decisions per task. Users need to trust the system without being overwhelmed by its complexity. — Pedro Rodrigues
04 — Artefacts

What was delivered.

60+
Figma prototype iterations
9 UCs
Production use cases
Wall
Experience mapping
3 Paradigms
Chat vs hybrid vs UI
Design System
Component library
Linear
Design-dev handoff
05 — Outcomes

What the work delivered.

Quantitative outputs from the multi-agentic orchestration platform design engagement.

60+
Figma iterations across four major version branches
9
Production use cases supported by the orchestration platform
3
Interaction paradigms explored (conversational, hybrid, UI-driven)
06 — Toolkit

What was on the desk.

Figma FigJam Miro Linear React + TypeScript Vite GitHub
07 — Reflection

What I'd do differently next time.

The tension between the three interaction paradigms — conversational, hybrid, UI-driven — defined the entire engagement. Early prototypes tried to pick one. The breakthrough was realizing different use cases demanded different paradigms — document translation benefits from a UI-driven workflow, while ad-hoc queries work better conversationally. The design system had to be flexible enough to support all three.

Next time: start with the use cases, not the paradigm, and let the interaction model emerge from the workflow.