Workflow automation brief
Define an automation that is understandable before it runs and observable when it succeeds or fails.
SaaS and dashboards · 45 min · Advanced · 22 questions
Triggers and actions
What starts an automation run?
In what order should automation conditions run?
How can users group conditions?
How can users preview which records match?
What happens when a condition has missing data?
What happens if the data changes during a run?
Which actions should the automation perform?
How will automation credentials be managed?
Duplicate prevention
How will the automation prevent duplicate work?
When may a completed run be replayed?
Can multiple runs change the same record at once?
Failure handling
When should a failed action retry?
Which errors should pause the automation?
Which errors may be skipped?
Which failures require human approval?
How will partial runs be compared with the source system?
How will ambiguous runs be compared with the destination system?
Operation
Where can operators see run history?
Which failures should alert an owner?
Who owns the automation?
How can a change be tested before release?
How will a changed automation roll out?
How to use this brief
Use this brief as a bank of questions for the conversation. Choose what is relevant, mark covered questions as you go, and skip anything that has already been answered.
Use this brief when...
Use when you need to define an automation that is understandable before it runs and observable when it succeeds or fails.
Best used as: Live call · Async intake
- Category
- SaaS and dashboards
- Discussion time
- 45 minutes
- Depth
- Advanced
- Last updated
- Jul 21, 2026
- Scope
- Design briefs
- Best used as
- Live callAsync intake
- Design roles
- Product designer
- Audience
- Product designersUX and UI designersProduct managersDesign leads
- Platforms
- WebAPIAutomation
- Company type
- B2BEnterprise
- Product stage
- GrowthMature product
- Tags
- saas-and-dashboardsworkflow-automationsystems-and-platformsrule-buildersystems-integration