Workflow builder

Open-ended exploration after home cooking—push far, test in Make, ship ideas one enhancement at a time.

2026Product Designer

Overview

After a home cooking session, builders and stakeholders surfaced the same pains on the workflow builder: a cramped canvas, repeated requests to rearrange workflow nodes, errors discovered too late, documentation outside the build, nested modals for related workflow nodes, and autosave that helped on some workflow node types but not others. The team needed ideas that could be explored boldly, validated quickly, and prioritized separately—not a single big-bang redesign.

Situation

First-time users struggled to see the whole workflow at once without losing information. Customers have repeatedly asked to rearrange workflow nodes on the canvas, but reordering without guidance makes it easy to break a flow—and builders often don’t learn that until publish. Workflow-node-type help was generic or lived outside the build, with no quick way to document what a specific workflow node means in this workflow. There was no lightweight glossary of workflow node types, and nowhere to capture org-wide constraints—compliance rules, business preferences, no-tos—that should shape how they build. Configuring two related workflow nodes meant modal after modal. Autosave felt unpredictable—fine for some workflow nodes, wrong for others—with no clear save or discard when leaving a sensitive workflow node.

Enter the passphrase to continue

Don't have it?