Aleksandr Subbotin

TL;DR

Problem

Approval often moved through emails, offline documents, and manual review processes. By the time information reached senior leadership, it could already be outdated or disconnected from operational context.

• Data had to be visible across national targets, priority sectors, and individual projects.
• Decisions had to be traceable through multi-stage approval chains.
• Different roles needed different levels of detail and operational control.

Key insights

• Role-based permissions were not enough. The system needed different information architectures shaped around the decisions each role had to make.
• The hard part was not only the workflow logic — it was making that logic legible for non-technical administrators.
• Government-scale workflows, confidentiality limits, and dense data forced more disciplined design decisions.

Design decisions

• Designed separate information architectures for data officers, analysts, reviewers, administrators, and senior officials.
• Made approval chains configurable through admin UI instead of developer tickets.
• Used reusable components for dense dashboards, tables, filters, forms, side panels, and review actions.

Solution

Before / After

Impact

• Supported a multi-agency government reporting workflow.
• Designed for five distinct user roles.
• Created a configurable four-stage approval workflow.
• Adapted dense data experiences across desktop, tablet, and mobile.

Takeaways

• Design for the system, not just the screen.
• Different roles need different information architectures.
• Constraints clarify decisions.

TL;DR

Problem

The existing admin console had valuable functionality, but the experience felt fragmented. Admins had to move between users, groups, devices, policies, integrations, and reports with no clear system model.

• No entry point for understanding company security status
• User management lacked filters, bulk actions, and profile depth
• Policy settings were dense and hard to navigate
• SSO and SCIM configuration had no clear status visibility

Key insights

• Enterprise security tools rely on making operational responsibility visible, not just exposing features.
• The admin console needed to behave like an operational workspace, not a settings area.
• Policy screens need grouping, hierarchy, and helper text for admins to make confident decisions.

Design decisions

• Dashboard consolidated security score, license usage, user activity, and risk signals
• User tables designed with filters, bulk actions, and full user profiles
• Policy screens organized into Security & Access, RoboForm Data, and User Experience categories
• SSO and SCIM screens redesigned with clear setup states and connection status

Solution

Before / After

Impact

• 8 core admin areas redesigned with a shared interaction model
• Dashboard provides company-wide security and license visibility
• User and group management supports bulk actions and profile depth
• Policy configuration organized into meaningful categories for confident decision-making

Takeaways

• Admin UX is about responsibility, not just control.
• Complex products need strong information architecture.
• Enterprise usability is not simplification at any cost.

TL;DR

Problem

Password managers operate in sensitive, high-frequency workflows. As the ecosystem expanded, inconsistent patterns and accumulated UX debt made the product harder to use across surfaces.

• Inconsistent navigation patterns across platforms
• Dense management interfaces with buried key actions
• Fragmented autofill and generation workflows
• Legacy interaction patterns not aligned with platform conventions

Key insights

• Security products need to balance speed with clarity. Every shortcut must still feel intentional.
• Behavioral consistency across platforms matters more than visual uniformity.
• High-frequency daily-use workflows deserve the most optimization investment.

Design decisions

• Iterative evolution over full rebuilds, preserving user familiarity
• Shared interaction patterns across mobile, extension, and web
• Intentional friction preserved for sensitive security actions
• Wearable experiences distilled to essential workflows only

Solution

Before / After

Impact

• Clearer navigation structures across all platforms
• Reduced friction in high-frequency autofill and generation workflows
• Improved action discoverability for key security features
• Scalable cross-platform interaction patterns

Takeaways

• Mature products require evolutionary design, not full rebuilds.
• Security UX requires intentional friction at the right moments.
• Behavioral consistency reduces user learning cost across surfaces.