02 · SleekFlow · 2025 — 2026
Advanced Flow Builder.
Turned a powerful automation tool into something any business user could trust — without removing depth.
Client
SleekFlow
Role
Lead Product Designer
Year
2025 — 2026
Focus
The Observation
SleekFlow's Flow Builder is a no-code automation system that lets businesses build multi-step workflows across messaging channels — WhatsApp, Instagram, live chat, and more. Using triggers, conditions, and actions, teams automate responses, route conversations, and capture customer data at scale. In practice, users aren't just configuring rules. They're building interconnected systems with real business logic and real consequences. A misconfigured flow can affect live customer conversations — and users knew it.
The Problem
The issue wasn't that users couldn't complete workflows. Most could. The problem was that they didn't trust what they'd built. ~70% of workflows were simple responder-type flows, 73% of users did not find the experience clearly easy in post-build surveys, 30% cited logic complexity as their primary friction point, and 29% cited discoverability of features. The core insight: this wasn't a usability problem. It was a confidence problem.
The arc
- 01
Research
Confidence is a UX metric.
- 02
Insights
Three patterns of broken trust.
- 03
Design
Designing for confidence, not just completion.
- 04
Outcome
Trust, measurably improved.
Stage 01
Research.
Confidence is a UX metric.
To understand where confidence breaks down, I combined three methods: quantitative product data via Tableau and Userpilot, a structured post-workflow survey, and live moderated pilot sessions with screen recordings.
The data told a consistent story. Users were finishing flows — but they weren't confident in what they'd built. That distinction changed everything about how I approached the design.
- →~70% of workflows were simple responder-type flows — users avoided complex branching not because they didn't need it, but because they didn't trust themselves to build it correctly.
- →73% of users did not find the experience clearly easy in post-build surveys.
- →30% cited logic complexity as their primary friction point.
- →29% cited discoverability of features.
I want to know how much workload each team is taking so I can allocate resources properly.
For the marketing team, we'd like to know how each market is performing, but we can't get this data in the analytics so we use HubSpot to drill it down.
Stage 02
Insights.
Three patterns of broken trust.
Insight 01 — Users default to safe automations
~70% of workflows were simple responders. Users consistently avoided complex branching — prioritising safety over capability.
Insight 02 — Logic complexity creates cognitive overload
Users couldn't mentally simulate how their workflows would behave. Managing conditional branches and multi-step logic created significant load — even for experienced users.
Insight 03 — No safe way to test
Users manually verified flows by switching between Flow Builder, Inbox, Channels, and contact properties — cross-referencing across tools. There was no built-in way to test safely without risking live conversations.
Stage 03
Design.
Designing for confidence, not just completion.
Opportunity 01 — Guided progression
Rather than presenting the full canvas as a blank slate, I designed a progression layer that recommended the next logical flow to build after publishing, defaulted to safer configurations, and gave users a clear next step at every stage. The goal was to reduce the intimidation of the open canvas and lower the activation energy for building something more complex.
Opportunity 02 — Dry run testing
Designed a safe testing mode that let users simulate how a workflow would behave without triggering live actions. Users could input test conditions — keywords, contact properties, channel sources — and see exactly how their logic would route without touching a real conversation. This directly addressed the biggest source of anxiety: the fear of breaking something live.
Stage 04
Outcome.
Trust, measurably improved.
For users:
- →Reduced hesitation when building more complex workflows.
- →Improved confidence in handling multi-branch logic.
- →Encouraged progression beyond simple automations.
- →Reduced reliance on manual debugging across separate tools.
For the business:
- →Clearer onboarding direction for new accounts.
- →Stronger foundation for scaling automation features as the product grew.
- →Reduced support tickets related to flow setup in the first quarter post-launch.
Outcome
Reduced hesitation on complex workflows, encouraged progression beyond simple automations, and cut support tickets related to flow setup in the first quarter post-launch.
Reflection
Confidence is a UX metric. In complex B2B tools, the question isn't just "can users complete this?" — it's "do users trust what they've built?" These are different design problems with different solutions. Designing for confidence meant making the system's behaviour visible and predictable — not just making the interface look cleaner.