Guided Workflow
A guided workflow is an in-product experience that walks a user through a multi-step process from beginning to end, providing instructions, validation, and contextual assistance at each stage. Unlike a product tour that simply shows where things are, a guided workflow actively participates in task completion. It tells the user what to do, confirms they did it correctly, and moves them to the next step.
Guided workflows are the product equivalent of having an expert sit next to the user and point at the screen. They are most valuable for processes that involve multiple screens, require specific inputs, or have an order of operations that is not immediately obvious. Setting up an integration, configuring a billing workflow, or completing a compliance checklist are all processes where a guided workflow can mean the difference between success and abandonment.
The shift toward guided workflows, often delivered through a browser SDK, reflects a broader change in how SaaS products think about user education. The old model was to document everything in a help center and hope users found it. The new model is to embed the help directly into the process, so the user never needs to leave what they are doing to figure out how to do it.
Why it matters for SaaS
Complex SaaS products often have setup and configuration processes that require domain knowledge the user may not have. An HR platform needs the user to configure pay schedules, benefit tiers, and approval chains. An analytics tool needs the user to connect data sources, define metrics, and build their first dashboard. These are not single-click actions. They are multi-step workflows where getting one step wrong can invalidate everything that follows.
Without guided workflows, companies face a costly choice: either simplify the product to the point where setup is trivial (limiting its value for serious users) or accept that a large percentage of users will fail to complete setup and churn. Neither option is acceptable. Guided workflows offer a third path: keep the product's full power but make the path through it navigable for users at any experience level.
The support cost implications are equally notable. Configuration errors are one of the most common categories of SaaS support tickets. When a user misconfigures an integration or sets up a workflow with a logic error, the resulting ticket often requires a support engineer to screen-share, diagnose the issue, and walk the user through the correct process. A guided workflow that prevents the error in the first place eliminates the ticket entirely. For products with thousands of users, this translates to meaningful reductions in support staffing requirements.
How it works in practice
A well-built guided workflow in an invoicing platform might look like this: the user clicks "Create Invoice" and a step-by-step flow takes over the screen. Step one asks them to select or create a client, with a search bar and a "new client" shortcut. Step two presents the line items with inline validation that prevents negative quantities or missing descriptions. Step three shows payment terms with sensible defaults and explanations of when each option is appropriate. Step four previews the invoice and highlights anything that looks incomplete. The user never has to wonder what comes next.
The most effective guided workflows incorporate several design principles. They show progress visually, so the user knows how far along they are. They validate inputs in real time rather than surfacing errors after submission. They provide contextual help for non-obvious fields without cluttering the interface with permanent help text. And they allow users to exit the guided flow and complete the task manually if they prefer to work without guardrails.
Where guided workflows get interesting is when they become intelligent. Instead of following a fixed script regardless of context, an adaptive guided workflow can adjust based on the user's inputs and behavior. If a user has already completed a similar workflow before, certain instructional steps can be condensed or skipped. If a user is struggling with a particular step, as evidenced by time spent or repeated errors, additional help can be surfaced. This adaptive behavior transforms the guided workflow from a static tutorial into a responsive assistant.
Guided Workflow vs Wizard
The terms guided workflow and wizard are closely related and sometimes used interchangeably, but there is a meaningful distinction. A wizard is a specific UI pattern: a modal or full-screen multi-step form that collects information in a fixed sequence. Wizards are a subset of guided workflows. They are excellent for linear processes where every user needs to provide the same information in the same order.
Guided workflows are broader. They can include wizard-style flows but also encompass non-linear experiences where the user completes tasks in a recommended but flexible order. A guided workflow might involve actions across multiple screens, embed instructional content alongside real product interfaces, and adapt its behavior based on what the user has already accomplished. A wizard is always a guided workflow, but a guided workflow is not always a wizard.
The distinction matters for product design because it affects how you think about user agency. Wizards are inherently constrained. The user moves forward and backward through predetermined steps. Guided workflows can be more open-ended, providing guidance while letting the user make choices about sequencing and approach. For simple, linear processes, a wizard is ideal. For complex, multi-faceted processes, a broader guided workflow approach is usually more appropriate.
How Floe approaches this
Floe replaces static step-by-step scripts with a live AI agent that guides users through processes in real time. The agent understands the product's interface, knows what each step requires based on plans, and can walk users through workflows conversationally. When a user needs to configure an integration, the agent does not just display instructions. It explains what each field means, verifies the inputs look correct, and handles the back-and-forth that inevitably arises when users have questions mid-process.
This approach solves a persistent problem with traditional guided workflows: they assume the happy path. Static workflows break when a user encounters an unexpected state, needs to deviate from the planned sequence, or simply does not understand what a field is asking for. An AI-guided workflow adapts to these situations naturally, providing the kind of contextual problem-solving that previously required a human support agent. See how onboarding uses this approach.
FAQ
When should you use a guided workflow versus letting users figure it out? Use a guided workflow when the task involves more than three steps, when errors are costly or confusing to undo, when the process requires domain knowledge the user may lack, or when completion of the task is a prerequisite for experiencing product value. If users can reasonably discover the process through the interface alone and the cost of errors is low, a guided workflow may add unnecessary friction. The decision should be informed by data: if a specific process has a low completion rate or generates frequent support tickets, it is a candidate for guidance.
How do you keep guided workflows from feeling patronizing? Three principles: make them skippable, make them contextually aware, and make them substantive. Users should always be able to exit the guided flow and work independently. The flow should skip steps the user has already completed. And the guidance should provide real value, explaining not just what to do but why, rather than stating the obvious. A guided workflow that tells an experienced user to "click the blue button" will feel patronizing. One that explains "this field sets your default billing currency, which affects all future invoices" provides value regardless of experience level.
How do you measure the effectiveness of a guided workflow? Track the completion rate of the process with and without the guided flow, the time to complete, the error rate, and the downstream engagement of users who completed the guided flow versus those who completed the process unguided. The most important metric is whether guided workflow completion correlates with higher retention and expansion. If users who finish the guided flow retain at similar rates to those who skip it, the workflow may be covering the right process but not adding meaningful value.