GLOSSARY

What is a Workflow?

Table of content
Definition

Definition

A workflow is a sequence of activities, decisions, handoffs, and system actions used to move work from an initial trigger to a completed outcome.

TL;DR

  • A workflow describes how work moves from trigger to outcome.
  • It can include multiple users, teams, systems, automations, and approvals.
  • Workflows are broader than individual task flows.
  • Good workflow design makes ownership, state, handoffs, and exceptions visible.
  • Enterprise products often succeed or fail on workflow quality more than screen polish.

What does workflow mean in software?

Consider an expense approval process. One employee submits an expense, a manager reviews it, finance checks policy, the system may flag exceptions, and the final result is reimbursed or rejected.

That is not one user flow. It is a workflow connecting several people and states.

What can a workflow include?

  • triggers
  • tasks
  • roles and owners
  • decision points
  • automations
  • handoffs
  • waiting states
  • exceptions
  • final outcomes

Workflow vs. task flow

A task flow follows one user completing one task. A workflow can combine many tasks across people and systems.

Workflow vs. user flow

A user flow stays close to a person’s interaction with the product. A workflow can include invisible system actions, organizational steps, and other participants.

How do you map a workflow?

  1. Define the trigger and final outcome.
  2. List the roles and systems involved.
  3. Map each step and owner.
  4. Add decisions and conditions.
  5. Make waiting and handoff states explicit.
  6. Identify failures, rework loops, and exception paths.
  7. Look for unnecessary coordination or duplicated work.

Common workflow mistakes

Mapping only the interface

Many workflow problems happen between people and systems rather than inside one screen.

Ignoring ownership

A state without a clear owner often becomes a queue nobody manages.

Skipping exception paths

Real workflows break at permissions, missing data, delays, and approvals.

The bottom line

A workflow answers: how does this piece of work move across people, systems, decisions, and states until it is done?

Related terms

Task flow · User flow · Decision point · Product state

Relevant Figr resource

Read User Experience Flows for deeper flow-mapping guidance.

Related Figr Projects

No items found.