System Tool — SaaS B2B (Automation)

Workflow Builder

Workflow Builder

A system designed to create automation rules based on triggers, conditions, and actions.

A system designed to create automation rules based on triggers, conditions, and actions.

Role: Product Designer

Type: Concept project

Year: 2026

Overview

Overview

Workflow Builder is a SaaS tool that allows teams to create automated rules to handle recurring tasks.

It enables users to define logic in a structured way and reduce manual work.

Problem

Problem

Automation features in SaaS products are often difficult to use.

Users need to define rules, but interfaces are:

  • too complex

  • unclear in logic

  • overloaded with options

This leads to:

  • incorrect configurations

  • low adoption

  • confusion about how rules work

Product Approach

Product Approach

Instead of exposing complex automation logic, I designed a rule-based system focused on clarity and predictability.

The goal was to reduce cognitive load by guiding users through a structured decision process, rather than presenting all possible configurations at once.

The system prioritizes:

  • simplicity over flexibility

  • progressive complexity

  • consistency in how rules are defined

Core Structure

Core Structure

The system is structured around a simple and consistent logic:

Trigger

Conditions

Actions

  • Trigger defines when the rule starts

  • Conditions define when it applies

  • Actions define what happens

This structure creates a predictable mental model for users.

Prototype

Prototype

A short prototype shows how a rule is created step by step.

Deep Dive

Deep Dive

Dashboard — Workflow Overview

Dashboard — Workflow Overview

The dashboard shows all existing workflows.

Each item includes:

  • name

  • trigger

  • status

This allows users to quickly scan and manage rules.

Trigger — Starting the Rule

Trigger — Starting the Rule

The process starts from a predefined trigger.

Instead of requiring full configuration, the system uses pre-configured states.

This reduces friction and allows users to focus on the logic.

The process starts from a predefined trigger.

Instead of requiring full configuration, the system uses pre-configured states.

This reduces friction and allows users to focus on the logic.

Conditions — Building Logic

Conditions — Building Logic

Conditions define when the rule should apply.

Each condition follows a consistent structure:

Field

Operator

Value

The system introduces logic progressively:

  • first condition (simple case)

  • second condition (combined logic)

Multiple conditions are combined using AND logic.

Actions — Defining Outcomes

Actions — Defining Outcomes

Actions define what happens when conditions are met.

Users can:

  • add one action

  • extend to multiple actions

The structure mirrors the logic of conditions, creating consistency.

Validation — Handling Errors

Validation — Handling Errors

The system includes validation to prevent incomplete configurations.

For example, when a required field is missing (such as an assignee in an action), the interface clearly highlights the issue and prevents the workflow from being completed.

Interaction Model

The interaction model is intentionally simple:

  • linear flow

  • minimal steps

  • instant transitions

The goal is to keep focus on logic, not on interface complexity.

Key Design Decisions

Key Design Decisions

Linear flow instead of branching

Reduces complexity and improves clarity.

Linear flow instead of branching

Reduces complexity and improves clarity.

Pre-configured states

Removes unnecessary setup and speeds up the process.

Pre-configured states

Removes unnecessary setup and speeds up the process.

Progressive complexity

Users move from simple to more advanced logic step by step.

Progressive complexity

Users move from simple to more advanced logic step by step.

Consistent patterns

Conditions and actions share the same structure.

Consistent patterns

Conditions and actions share the same structure.

Focus on decisions, not inputs

The system supports logical thinking rather than form filling.

Focus on decisions, not inputs

The system supports logical thinking rather than form filling.

Outcome

Outcome

This project demonstrates the ability to design:

  • system-based interfaces

  • rule builders

  • configuration tools

It improves usability by:

  • making logic explicit

  • reducing cognitive load

  • guiding users through rule creation

Learnings

Learnings

Designing systems is about managing complexity.

The challenge is deciding what to include and what to remove.

A simpler structure with clear rules is often more effective than a feature-rich but confusing system.

Andrea Picariello

Product / UX Designer

Andrea Picariello

Product / UX Designer

Andrea Picariello

Product / UX Designer