Flow / Enterprise AI / Application design
I designed the UX/UI across an agentic application that helps people build workflows for recurring tasks, with a way to pause for approval during execution.
The context
Flow helps people map the steps of a task so an agentic workflow can carry it out. One example is fetching data, preparing an update and emailing it to the relevant people.
The product focuses on automating recurring operational tasks. The design needs to make the steps understandable while giving people a way to intervene when their approval is required.
Illustrative use case. The screens below use substituted sample workflows and values.
The design challenge
How the steps connect. What each agent needs. When a person should step in.
Build the workflow
The canvas presents tools, prompts, branches and input messages as connected steps. Each node pairs a step type with a name, while the connections show how work moves between them.
Labels, icons and colour help identify different types of work on the same canvas.
The input-message step gives approval a place alongside the automated actions.
Configure the agent
The agent drawer brings instructions, inputs, outputs, tools and execution settings into one configuration view. This connects a node on the canvas to the information it needs to perform its task.
An instruction area describes the work the agent should carry out.
Named parameters, descriptions and types show what the step receives and returns.
The drawer includes tool selection, argument values, iteration limits and caller input mode.
This screen shows the agent’s settings. The approval interaction is shown separately in the execution view below.
Approve during execution
When a workflow requires approval, the run can pause and ask for a response. The execution view places the workflow’s progress beside the request, so the person can see the context of the decision.
The progress path and step name locate the request within the running workflow.
The request, response field and Submit action sit together in the side panel.
Guidance explains that the response returns to the workflow and execution resumes, with the possibility of another pause.
What to evaluate next
The screens show the design work. Measured usability and time-saving results are not included in this case study.
Ask someone to map a recurring task. Observe whether they can select the right steps and understand the connections.
Look for: completion, assistance and corrections.Check whether someone can explain the inputs and outputs and configure a step with appropriate values.
Look for: field confusion and configuration errors.Check whether someone understands why the run paused, what they are approving and what submitting will do.
Look for: comprehension and decision time.Explore more work
Redesigning an enterprise regression-testing application around the people doing the work.
Read the testing case studyReach out about UX roles, my work or a conversation with your team.