Break free from static flowcharts with Voiceflow
Conversation designers are making the switch from static flowcharts to Voiceflow.
.png)
Conversation designers are making the switch from static flowcharts to Voiceflow.
Here are the big questions we keep hearing
It's like cutting steak with a spoon. You'll eventually finish your plate, but it would have been much easier with a knife.
Figma is for building UI visuals.
Visio and LucidCharts are for diagramming.
Voiceflow is for conversation design.
.png)
A lot. Static flowcharts and spreadsheets can't simulate the actual conversational experience.
With Voiceflow
- Bring your early concept designs to life
- Spin up 1:1 shareable prototypes without dev help
- Spend less time explaining "how things works" and more time designing great experiences
“It’s a lot more difficult to present an idea with static screenshots or flowcharts in a slide deck. Being able to do a live presentation with a prototype demo is next level. You get a very different reaction.” - Jason Bejot, Director of Conversation Design, Rocket Mortgage
Nope. User testing without real, unmoderated conversations means slower and less meaningful iterations.
With Voiceflow:
- Run more tests in less time
- Iterate confidently using transcript insights
- Optimize assistant performance with user data from production
“I can share a hands-on, realistic version of the final product. We’re even able to get real-time feedback through user testing, which was not possible before.” - Peter Isaacs, Sr. Conversation Designer, WooliesX
.png)
Good one. Static flowcharts and spreadsheets create a blackbox between design and development.
With Voiceflow:
- Integrate directly with your existing dialog manager
- Publish production-ready design versions from the canvas
- Be confident that your designs will make it to production
“At handoff, developers would leave feedback in both Figma and Excel. Some feedback would be missed by the design team and would result in countless back-and-forth conversation for approvals and edits that slowed the team's process down.”
.png)
We know you get it, but share this side-by-side with your team.
The team used Excel, Word, Lucid Chart, and Figma, but found them suboptimal for conversation design. These tools limited their ability to design complex flows and create high-fidelity prototypes.
The team used multiple static tools (Figma, Gliffy, and Visio) to document designs, making it challenging for designers to consider all customer scenarios and for reviewers to grasp the conversational experience. As a result, Design Forum meetings lasted over 90 minutes and required extensive hand-holding.
The design team found it increasingly challenging to create and navigate flowcharts, particularly as bots became more feature-rich. Consequently, step-by-step walk-throughs with developers were excessively time-consuming.