Role: Senior Product Designer — Design System Co-owner Focus: Built the foundation for complex industrial UIs: geo-maps, data-viz, diagram editor. Team Impact: Enabled consistent UI and faster delivery across teams with Figma + code parity.
More images in the Visual design section
Project overview
Prizm is an industrial design system for data-heavy operational software. It standardizes patterns, components, and complex UI behaviors to help teams ship consistent products faster.
Partners Built in collaboration with PJSC “Gazprom Neft” and SE “Zyfra”.
Users Operations, engineering, and production teams in industrial companies.
Where it’s used Desktop apps · Web apps · Video walls · Workstations
Domains Oil & gas · Metallurgy · Food production · Engineering
Distribution Open-source, released under the MIT license.
Stakeholders & needs
Developers
Optimized for implementation: tokens, states, and specs that match the codebase.
Designers
Optimized for speed: reusable patterns for complex modules (maps, data-viz, diagrams).
Business
Optimized for scale: consistent UX across products and faster rollout of new solutions.
Key problems
Faster delivery across products Reduce rework and decision churn by reusing proven UI patterns and templates across teams.
Consistent UX for complex industrial tools Unify visual language and interaction logic so maps, dashboards, and editors behave predictably in every product.
Design ↔ code parity Align components, states, and tokens between Figma and the code library to improve quality and cut UI regressions.
My role
Senior Product Designer (Design System)
Jan 2022 – Mar 2023
Co-owned the design system from foundations to adoption. I helped shape the structure and rules early on, then led the component library and design→code quality.
What I owned
Foundations: principles, structure, naming, component logic and states
Design↔code parity: specs, reviews, QA of implemented components
Adoption: workshops/demos and enablement for internal and external teams
Team
Two Heads of Design Gazprom-Nef, Zyfra
Me Gazprom-Neft
Design & Dev pod Team 1 Gazprom-Neft
Design & Dev pod Team 2 Zyfra
Key Design Work
Industrial-first principles
Designed for high-risk, data-dense workflows (control rooms, operations, engineering). Prioritized clarity, error-prevention, and predictable behavior over “pretty UI”.
Component system for complex states
Built a scalable component library with strict state logic (defaults, errors, empty/loading, permissions). Reduced one-off design decisions and made behavior consistent across products.
Design ↔ code parity
Defined specs, naming, and tokens to match implementation. Reviewed builds and aligned edge cases so components in code behave like in Figma — not “close enough”.
Modular architecture
Split the system into modules (core UI, maps, diagrams, data-viz, theming). Teams could adopt what they need without dragging the whole system into every product.
Data visualization for decisions
Created decision-oriented chart patterns (comparisons, trends, thresholds, anomalies). Focused on readability and meaning — so operators can act fast, not interpret charts.
Delivered
Core component library
Reusable UI kit in design + code, covering key patterns and complex states for industrial products.
Data visualization module
Standard chart patterns and rules for consistent, decision-ready analytics.
Diagram constructor
Diagram editor for industrial workflows (P&ID-style) to build and maintain process схемы.
GIS maps module
Mapping toolkit for ops scenarios: layers, controls, and map-specific interactions.
Documentation & usage rules
Specs, examples, and usage rules to keep implementation consistent across teams.
Light and dark theme, WCAG
Accessible light/dark themes with token-based palettes for control-room environments.
Future-proof modularity
Modular system that allows new patterns without breaking existing products.
Icon library
Structured icon set with clear naming and categories, readable across sizes.
Visual Design
Learn more about design system components
The design system is distributed under the MIT license. It is available for use in the public domain for any teams and industrial tasks.
Confidentiality note: This case is numbers-free under strict corporate NDA; focus is on decisions and outcomes.
More speed
Faster product kickoff with reusable patterns and ready-to-implement components — less reinventing UI from scratch.
Adopted by teams
Shared system used across multiple cross-functional teams and products, including complex modules (maps, diagrams, data-viz).
Less cost
Lower rework and coordination overhead thanks to design↔code parity, clear specs, and predictable component behavior.
Product quality
More consistent UX and fewer UI regressions with standardized states, accessibility-ready themes, and a unified asset library.
My personal impact & Key achievements
Co-owned Prizm — an industrial design system for data-heavy products. Delivered foundations, production-ready libraries, and adoption support across teams.
Delivery ownership
Learned: systems scale through rules, not just components.
Handled: set contribution/review flow, wrote usage docs, and ran demos/workshops to drive adoption.
Design ↔ Code parity
Learned: trust comes from matching behavior, states, and tokens.
Handled: defined tokens + state logic, reviewed implementations, and QA’d edge cases to reduce UI regressions.
Complex modules ownership
Learned: complex domains need modular patterns.
Handled: led reusable patterns for maps/GIS, data-viz, and diagram workflows, plus themes (light/dark) and shared icon/assets set.
Role: Senior Product Designer — research, UX/UI, experiments Focus: Redesigned marine weather tools and decision workflows; built continuous hypothesis pipeline with product team. Team Impact: Improved activation and retention via UX/UI upgrades and experiments.
Role: Solo Product Designer and owner Focus:Designed a system of 186+ widgets, themes and mini-apps; created a tiny theme editor; shipped full visual language and interaction model. Solo Impact: Independently delivered a full product lifecycle: market analysis, research, UX/UI, prototyping, development and App Store launch.
Role: Product Designer — UX/UI for complex B2B data workflows Focus: Designed data search and analysis experience; simplified workflows and information architecture. Team Impact: Improved data discovery speed for analysts by ~30–40%, depending on scenario.
Role: Product Designer — UX/UI for trading flows Focus: Designed product search, selling flow and trading network interactions. Team Impact: Reduced friction in transaction flow and increased conversion.
Role: Product Designer — navigation and safety interfaces Focus: Designed navigation dashboards, weather layers and emergency response flows. Team Impact: Reduced time-to-decision for captains by improving clarity of critical information.
Role: Product Designer — UX/UI for geospatial threat tools Focus: Designed ice-threat prediction maps and route-safety visualization tools. Team Impact: Improved clarity of risk zones and reduced decision time in safety-critical scenarios.
Role: Product Designer — UX/UI for marketplace flows Focus: Designed end-to-end flows connecting furniture studios and suppliers; built mobile and web experiences. Team Impact: Improved conversion and simplified multi-step purchase/renovation journeys.