CASE STUDY
Studio Refactor
This project is a refactor of the Uiflow Studio no-code editor. This effort was intended to further empower engineers and product managers by enabling the ability to connect live data from any data source and elevate the logic tool for creating and managing workflows.
CLIENT/EMPLOYER
Uiflow
TIMEFRAME
August 2022 — October 2022
ROLE — SR. PRINCIPAL PRODUCT DESIGNER
Design Systems, UX Research, Product Thinking, Interaction Design, Visual Design, Concepting, Prototyping
TOOLS USED
Figma
Overview
ABOUT THE PROJECT
This effort was part of a larger strategic plan to deliver a more nuanced and comprehensive user experience surrounding the data connection and logic workflow features. In addition, we spent time refining the Studio experience to offer flexibility and scalability for planned upcoming releases such as themes, component library management, and more.
TEAM
1 Designer & 2-3 Engineers
THE PROBLEM
In recent weeks it was apparent there was difficulty in finding the logic and data tools. Once in those areas, creating data connections and logical workflows was unnecessarily restrictive in the available workspace.
Additionally, we had recently completed our feature roadmap for the next few quarters, which included many visual editor improvements and features, and considering we would need to adjust the placement and visibility of numerous features, it made sense to consider all of these usability issues simultaneously.
The challenge
Improve accessibility and usability of various features and adjust the UI to scale with upcoming roadmap features.
Friction R’ US
As with every project, we spent an hour each week with our beta customers and direct product partners to gather feedback, and a theme started to materialize.
Many of our users, while they we contending with the frustration of always needing to have the visual editor open when they wanted to work with the logic workflow feature. Users said that they’d prefer a dedicated space to work on flows and have a simple preview of the UI instead of having to share the same space.
On top of that, creating data connections ended up with having to pivot back and forth between the data section and the logic area. We enacted saved locations and states between them both, but that was not enough.
Outcomes & learnings
When presented both to our beta users and partners, the validation was palpable. The time taken to complete projects was reduced substantially.
When these new improvements were shown off at Saastr, it resulted in lead generation at our booth that we otherwise might not have gotten. Some leads were from folks who had been a beta tester but lapsed due to issues that were formerly unresolved. Our new release had solved those issues.
reduced by 32%
PROJECT COMPLETION TIME
5 NEW LEADS
3 RE-ENGAGED LEADS
3 NEW CUSTOMERS
LEADS GENERATED
We re-engaged several lapsed users and gained (at the time) 3 new customers.
Our testers and partners were ecstatic about the changes as our improvements reduced time to completion for projects that they had in progress.
OUR SUCCESSES