From messages to
operational workflows
Product direction, UX and UI for an AI-assisted workspace that turns incoming requests into quotes, orders and operational tasks.
- Design lead
- Lorenzo Rogante
- Design scope
- Product direction · Interaction design · UI design
- Collaboration
- Management and development team
- Designed for
- Teams handling customer requests and operations
The initial concept centred on an intelligent email client. The design direction shifted towards the work created by each message: its requirements, progress, exceptions and handover between people.
or explore the workspace
Key decisions
Work beyond the inbox
Requests become connected workflows, preserving the source message as the work progresses.
Phase and status
A quote can be ready, blocked or awaiting a reply. Its stage and condition need separate signals.
Specific human input
Missing information opens a focused intervention rather than making the team repeat the entire task.
Column = phase · Badge = status · Explanation = next action
Keep the source beside the extracted data
The source message sits beside the information extracted from it. This arrangement supports checking an interpretation and supplying a missing value without reconstructing the conversation elsewhere.
From message to work
Known: quantity, format, delivery · Missing: paper weight
Separate progress from operational status
Request, Quote, Order and Production describe the stage of the work. Status explains its condition within that stage. Keeping these signals separate distinguishes a quote awaiting input from one awaiting a customer reply.
One connected workflow
Known: quantity, format, delivery · Missing: paper weight
Explain why a workflow is blocked
A missing paper specification keeps the example request in Quote while complete work progresses. The board makes the exception visible without suggesting that all activity has stopped.
Paper weight is missing
Known: quantity, format, delivery · Missing: paper weight
Ask for the missing value in context
The detail combines the message, extracted fields and missing paper weight. The intervention is limited to the information needed to continue, with the original request available for reference.
The right input, in context
Known: quantity, format, delivery · Missing: paper weight
Define the boundaries of automation
Confirmed steps and more automated processing share explicit intervention points. Missing information and consequential actions remain visible; in this scenario, a customer reply is required before the quote becomes an order.
Review before advancing
300 gsm confirmed · Review and customer confirmation remain explicit
Carry the request history into production
The message, specifications and decisions remain connected as the confirmed order moves to production. The handover preserves the context needed by the next person, rather than creating an isolated task.
Ready for production
300 gsm confirmed · Review and customer confirmation remain explicit
Phase and status answer different questions
This case study presents professional product design work. Interfaces have been recreated for the portfolio using synthetic records and generic names. Interactive sequences illustrate design decisions rather than record the original application. The figures are examples, not measured project outcomes.