Redesigning how to start
new AI workflows.

Creating something new is one of the product's most critical moments. This project redesigns that path end-to-end, a creation modal, Prompt to Flow (describe-to-build), an in-builder AI assistant, and improved template discovery.

Company

StackAI

Product

Enterprise AI workflow platform

Role

Product Designer

Year

Q4 2025

Impact

Raised the % of users who run a workflow after creating a project from 50% to 78%. 1,400+ builders across organizations adopted templates in a month.

DISCOVERY

What was broken

The modal had flat hierarchy and weak affordance, buttons didn't feel interactive and copy didn't guide users. Templates were buried; the category sidebar didn't read as a filter. Prompt to Flow had no entry point, and AskAI in the builder was hard to find and understand.

DESIGN PROCESS

UX audit, discoverability, flow, and UI issues mapped in FigJam Competitor mapping, blank-canvas and guided-setup patterns UX flow mapping, new project modal, P2F entry, and AskAI journeys in FigJam Flow design, in-builder AskAI, templates, and dashboard explorations

1. Research + UX audit

Mapped all current issues with the new project flow and AskAI assistant in FigJam, and analyzed usage patterns of what builders were asking the AI assistant to do.
UX audit, discoverability, flow, and UI issues mapped in FigJam

2. Competitor mapping

Reviewed competitors for blank-canvas-paralysis solutions, and benchmarked how Relay.app, n8n, Lindy, and Zapier handle guided setup and template onboarding.
Competitor mapping, blank-canvas and guided-setup patterns

3. UX flow mapping

Mapped the end-to-end experience in FigJam: P2F as the primary action in the new project modal, prompt-to-workflow entry behavior with PostHog tracking, and the three in-builder AskAI journeys, starting fresh, recovering from errors, and getting help mid-build.
UX flow mapping, new project modal, P2F entry, and AskAI journeys in FigJam

4. Flow design

Designed the in-builder AskAI experience, redesigned template preview and category filters, built a contextual checklist prototype for template setup, and began exploring P2F as the centerpiece of the projects landing page.
Flow design, in-builder AskAI, templates, and dashboard explorations

SOLUTION

New project creation
modal

Prompt-first entry with three clear paths (New Workflow, Use Template, New Agent) plus quickstart suggestions to reduce blank-canvas friction. The same pattern carries over to empty folder states.

New project modal with P2F prompt field and creation options

Prompt to
Flow

Describe a workflow in plain language, nodes stream onto the canvas in real time as it generates, including triggers, HITL, subflows, and integrations. Validated in an A/B test against the old creation popup.

Project template
experience

Template preview redesigned: proper back/use-template navigation, expand prompt box, and correct node rendering in standard mode. Category sidebar clarified as a multi-select filter, not navigation. Save as Template accessible from within any workflow, with separate entry points for browsing vs. starting blank.

Templates view with category filters and template cards
Template preview with workflow nodes and use-template navigation

Project setup
checklist

Auto-opens when a builder loads a template, surfaces what's missing (connections, knowledge bases, empty inputs, node configs, LLM variables) and guides run, interface, and publish before first run. Dismisses when complete, skips interface for trigger workflows, and collapses for experienced users.

Project setup checklist panel guiding setup before first run

INSIGHTS

The blank canvas is the real competitor

Most drop-off in workflow creation isn't from poor UX, it's from not knowing where to start. Quickstart suggestions and P2F directly address this.

The entry point shapes expectations

When P2F is the primary action in the creation modal, builders frame the whole experience as "describe → generate → refine" rather than "build from scratch." That mental model shift matters.

Templates need to be felt, not just listed

A category sidebar that looks like navigation and a static screenshot preview both fail to communicate what a template actually does. The redesign prioritized interactivity and clarity before the user commits.

The gap between "open template" and "first successful run" was the real problem

Templates looked finished but weren't, they required connections, knowledge bases, and configuration that users had no way of knowing about. The checklist makes the implicit explicit, turning a source of early errors into a guided activation flow.

OTHER PROJECTS