Let's take a look on the most challenging parts.
Environment dashboard. Outdated, not fully informed about the whole system for a prior target audience.
Without a visual priorities and small CTA.
Hard to use, indeed.
Simplify and bring efficiencies.
123 RBAC roles, hundreds of use cases.
The main solution is to put the right information for a prior JTBD and create a whole new guideline for visibility.
Tiny to details.
All from a new Design System.
And 300+ other pages…
✉️ Let's talk email@example.com
The main goal is to redesign our product, Scalr Tacos from an Enterprise to a brand-new SaaS. During this time, I concentrated on reorganizing UX team, process, design system. Working closely with a CTO, product owners and an engineering team with a huge knowledge base.
Let's turn words into tangible, visual ideas that people rally behind.
Challenging any perceived legacy that turns a design system into an inhibitor of innovation. It takes years to launch Scalr TACOS. But there are a lot of issues everywhere in the product. Starting from onboarding:
April 2021 - ongoing
Design (3 people)
Product management (3 people)
Front-end (8 people)
Growth (4 people)
Individual DevOps engineers and their work environment. Hard to change it and integrate the whole new system.
UI compared to API and simplicity.
They don't understand how to config properly.
Starting from the beginning. Redefined our approach and the whole design process. Cross-functional teams in the center. From Enterprise based process (clients requests first) to a user-centered approach (feedback, qualitative and quantitative research).
3x onboarding conversion
3x invite flow
5x time CAC
Minimum to zero errors for DS
5x less time in QA stage
Mindset of productive re-use