Role
Senior (Lead exp.) product designer
What was done
Team leadership · Design system · UX research · Processes
Audience
Large enterprises
Designing a modular low-code platform for large enterprises (VTB, Aeroflot, etc.)
Modus is a modular enterprise platform for automating sales, marketing, customer service, and other customer interaction processes. It is designed for large companies, complex role models, on-premise deployment, and integration with existing IT landscapes.
Deal activity timeline with documents and amounts
I joined at the start of the product and built the design function from scratch: assembled a team, defined the interface principles, created a design system, and set up processes for scaling the product.
Built and grew the team
I formed a design team of 8 people. I introduced 1:1s, design reviews, and mentoring, and set up a transparent task split.
Defined the concept
I formulated the interface principles: clear user flows, scalability, and consistency across modules.
Built the design system
Ready-made components sped up new module launches and kept a single language across the platform.
Established UX research
I organized and ran research. Based on the findings, the team improved user flows and product mechanics.
Led the creation of modules
Responsible for the development of modules: Contact Center, Loyalty, Marketing, CPQ, BPM, and DMN.
Task kanban inside a deal card — Contracting stage
System modules
Sales
A single pipeline and deal workflow
CPQ
A commercial-offer configurator and pricing
Contact center (Dialog)
An omnichannel operator workspace
Marketing
Campaigns, segmentation, lead management
Loyalty
Loyalty programs of any complexity
Service
Customer support and interaction history
Collections
A full debt-recovery cycle
Analytics
Reporting and management dashboards
Loyalty program flow — mechanics and participation terms
The design system is the foundation
The design system became more than a library of mockups: it became a shared language for designers, analysts, and engineers. Components were designed around states, roles, data density, and reuse across modules.
Connecting the design system and UI editor
- 01The UI kit is implemented as a library of web components
- 02Smart components combine common scenarios and settings
- 03The UI editor makes it possible to assemble most standard screens without manual layout work
- 04For non-standard tasks, the UI editor supports moving from no-code to low-code and high-code
- 05Shared components simplify updates and keep implementations consistent
Filter research — one of many examples
Users completed key scenarios in an interactive prototype: filtering the list and saving a set of conditions. We then collected quantitative ratings and feedback to validate the solution before development.
Deal list filters — filter conditions and saved views
Method and parameters of filter UX testing
Evaluation results for the new filter mechanics
Localization and dark mode
For a large enterprise system, localization and dark mode are not optional extras but essential parts of the product. The interface must preserve its structure, readability, and logic across languages and color schemes.
English-language version of the Modus interface
Intern training
I gave interns lectures on various product design topics, discussed practical cases, answered questions, and provided feedback on assignments. This helped participants better understand real-world workflows and apply their knowledge in practice.
Life at the office
