Risk Management System for Yandex
An internal web tool designed to centralise risk, process, and control data across multiple business units. The product replaces fragmented spreadsheet-based workflows with a structured system that supports accountability, traceability, and consistent decision-making
My role
My role
Lead product designer (intern)
Lead product designer (intern)
Product
Product
Internal tool, Desktop
Internal tool, Desktop
Timeline
Timeline
August 2025 – December 2025
August 2025 – December 2025
Design focus
Design focus
user flows
user flows
UX/UI design
UX/UI design
prototype
prototype
user profile
user profile
brand experience
brand experience
Problem
Problem
The client provided a draft tool that had no consistent UI and did not match neither company’s identity nor other internal services branding. Poor usability made complex data relationships hard to understand and misleading
The client provided a draft tool that had no consistent UI and did not match neither company’s identity nor other internal services branding. Poor usability made complex data relationships hard to understand and misleading
Goal
Goal
Design a clear and consistent user interface for an internal database tool, improving usability, making complex data relationships easy to understand, and visually aligning the product with the company’s branding and internal product ecosystem
Design a clear and consistent user interface for an internal database tool, improving usability, making complex data relationships easy to understand, and visually aligning the product with the company’s branding and internal product ecosystem
01.
Project background
The Risk Management System is an internal tool that works as a database created and maintained by its users. It replaces spreadsheet-based solution, which is difficult to keep up to date
The tool stores structured information about processes that contain risk to the business, so the interface must support efficient work with table data like sorting, filtering, and editing
The Risk Management System is an internal tool that works as a database created and maintained by its users. It replaces spreadsheet-based solution, which is difficult to keep up to date
The tool stores structured information about processes that contain risk to the business, so the interface must support efficient work with table data like sorting, filtering, and editing
Client expectations
The client provided detailed project specifications and functional requirements, along with information architecture and a draft interface concept in Miro
The client expected a clear, practical solution that made everyday work with data easier, supported different user roles, and aligned with the company’s internal ecosystem. The final result needed to be ready for development
The client provided detailed project specifications and functional requirements, along with information architecture and a draft interface concept in Miro
The client expected a clear, practical solution that made everyday work with data easier, supported different user roles, and aligned with the company’s internal ecosystem. The final result needed to be ready for development
Project challenges & limitations
limited timeframe (hackathon format)
no UI kit, component library or design system provided
design has to align with the company’s internal product style
complex data structure
02.
My role in the project
I managed the team’s workflow and ensured that our design solutions met the project goals and aligned with internal workflows. I also focused on improving usability and creating a consistent user interface
Key responsibilities:
analysing the client’s requirements
organising the team’s workflow, including task grooming and internal meetings mentoring
developing user flows
collecting interface references
working on visual design
building the component library
creating an interactive prototype
presenting the design to the client
I managed the team’s workflow and ensured that our design solutions met the project goals and aligned with internal workflows. I also focused on improving usability and creating a consistent user interface
Key responsibilities:
analysing the client’s requirements
organising the team’s workflow, including task grooming and internal meetings mentoring
developing user flows
collecting interface references
working on visual design
building the component library
creating an interactive prototype
presenting the design to the client
Collaboration and teamwork
The project was completed by a small design team working closely together. Responsibilities were clearly divided, while key decisions were discussed and agreed on collectively
We communicated regularly with the client through calls and reviews. The client shared our design drafts with his team and collected feedback internally. Based on this feedback, we iterated on the design and refined the solution to match expectations
The project was completed by a small design team working closely together. Responsibilities were clearly divided, while key decisions were discussed and agreed on collectively
We communicated regularly with the client through calls and reviews. The client shared our design drafts with his team and collected feedback internally. Based on this feedback, we iterated on the design and refined the solution to match expectations
03.
User research
This project did not include a separate user research phase. The tool was designed for internal use by the client’s team, and the client had already collected input and requirements directly from users
The information about user roles and jobs to be done was shared with us in the form of project specifications. Based on this input, we defined the target audience and created three user portraits to guide design decisions:
internal control specialists who actively manage data
team leads who review and approve changes
service employees who primarily consume information
This project did not include a separate user research phase. The tool was designed for internal use by the client’s team, and the client had already collected input and requirements directly from users
The information about user roles and jobs to be done was shared with us in the form of project specifications. Based on this input, we defined the target audience and created three user portraits to guide design decisions:
internal control specialists who actively manage data
team leads who review and approve changes
service employees who primarily consume information
User portraits
Key design requirements
04.
Information architecture & user flows
The information architecture was defined by the client and built around core data tables such as processes, risks and controls
I worked on creating user flows around three main actions according to user permissions: managing data, approving changes, and viewing information
The information architecture was defined by the client and built around core data tables such as processes, risks and controls
I worked on creating user flows around three main actions according to user permissions: managing data, approving changes, and viewing information
User flows
Internal control team staff – creating new cards and editing data
Team leads – editing data and approving cards
Other teams staff – viewing data and reporting issues
05.
Design ideation and references
The client shared screenshots of internal company tools used by other teams. These examples became our main visual and functional references and helped us align the interface with existing internal products. Due to confidentiality, these materials cannot be shown in the case
During the ideation stage, we mostly focused on functional patterns used in data-heavy products rather than visual design. We analysed admin panels and dashboards that support tables, forms, and role-based access
The client shared screenshots of internal company tools used by other teams. These examples became our main visual and functional references and helped us align the interface with existing internal products. Due to confidentiality, these materials cannot be shown in the case
During the ideation stage, we mostly focused on functional patterns used in data-heavy products rather than visual design. We analysed admin panels and dashboards that support tables, forms, and role-based access
Design reference examples
Moodboard
06.
Wireframes and structure
Wireframes were used to define page structure, navigation, and key interactions before moving to visual design
We focused on clear layouts, reusable patterns, and table-based views that support working with large amounts of data
Wireframes were used to define page structure, navigation, and key interactions before moving to visual design
We focused on clear layouts, reusable patterns, and table-based views that support working with large amounts of data
Wireframes
Design ideas and drafts
07.
Key design decisions
Personal profile screen
includes a standard top navigation bar to provide familiarity and quick access
the main area displays a staff information card and a section for relevant data, which can vary depending on the service
a menu shows all available data tables based on team and level of staff permissions
Personal profile screen
includes a standard top navigation bar to provide familiarity and quick access
the main area displays a staff information card and a section for relevant data, which can vary depending on the service
a menu shows all available data tables based on team and level of staff permissions
Personal profile – internal risk control team staff
Personal profile – internal risk control team lead
Personal profile – other team members
07.
Key design decisions
Standard data table screen
The table screen differs depending on user roles, but stays the same for each type of table selected in profile (matrix, services, etc.)
Internal Control staff and team leads can edit data, while other staff have read-only access and can leave comments
side filtering panel can collapse to increase screen space and reduce horizontal scrolling
row highlighting tracks mouse location to avoid losing context
no pagination, following client preference for continuous scrolling
Standard data table screen
The table screen differs depending on user roles, but stays the same for each type of table selected in profile (matrix, services, etc.)
Internal Control staff and team leads can edit data, while other staff have read-only access and can leave comments
side filtering panel can collapse to increase screen space and reduce horizontal scrolling
row highlighting tracks mouse location to avoid losing context
no pagination, following client preference for continuous scrolling
Data table screen
for internal control team staff and team leads
Data table screen
Data table screen
for other teams staff
07.
Key design decisions
Process card
Process cards are tailored to each user role using role-based permissions:
internal Control staff can create and edit cards and submit them for approval
team leads can edit and approve cards
other staff can view data and leave comments
The card appears as a side curtain to keep users oriented in the table they were working on. Information is structured for readability and efficiency, with most fields using dropdowns to minimise user errors
Process card
Process cards are tailored to each user role using role-based permissions:
internal Control staff can create and edit cards and submit them for approval
team leads can edit and approve cards
other staff can view data and leave comments
The card appears as a side curtain to keep users oriented in the table they were working on. Information is structured for readability and efficiency, with most fields using dropdowns to minimise user errors
Process card
for internal control team staff
Process card states – editing
for internal control team staff
Process card states – viewing and deleting
for internal control team staff
Process card
for team leads
Process card
for other teams staff
08.
UI kit
We were not provided with any existing UI kit, so we developed components based on visual and functional references from other internal tools shared by the client
The UI kit was built collaboratively. I was responsible for maintaining and updating it, making sure all screens used shared components. After each review, I updated the UI kit first and then applied changes across the interface to keep the design consistent and scalable
We were not provided with any existing UI kit, so we developed components based on visual and functional references from other internal tools shared by the client
The UI kit was built collaboratively. I was responsible for maintaining and updating it, making sure all screens used shared components. After each review, I updated the UI kit first and then applied changes across the interface to keep the design consistent and scalable
UI kit components
09.
Visual brand identity
The project did not include creating a full visual brand, as the focus was on designing a consistent interface for internal users. However, we aligned the design with the look and feel of other internal Yandex tools
We used colour palettes, typography, and interface patterns that reflect the company’s existing visual ecosystem, ensuring the product feels familiar to users
The project did not include creating a full visual brand, as the focus was on designing a consistent interface for internal users. However, we aligned the design with the look and feel of other internal Yandex tools
We used colour palettes, typography, and interface patterns that reflect the company’s existing visual ecosystem, ensuring the product feels familiar to users
Logo ideation
New logo
Colour palette and typography
10.
User testing
After designing the first working prototype, we ran usability testing with risk control team to validate whether the system actually improved workflow efficiency and reduced ambiguity
During the first test round we conducted four focused usability tests for which we engaged 7 users. Second round of tests was made to verify whether improvements have been made in usability after we refined the design. For second round 10 users were engaged
Test 1 – Data input accuracy
We tested whether users could input data correctly. We found out that the form required too much manual input. After the test we:
replaced open text inputs with limited selectable options where possible
added radio buttons for constrained choices
added placeholder examples and contextual guidance
designer error messages
Outcome
Error-free input increased from 57% to 90%. This significantly reduced required manual work and increased workflow confidence
After designing the first working prototype, we ran usability testing with risk control team to validate whether the system actually improved workflow efficiency and reduced ambiguity
During the first test round we conducted four focused usability tests for which we engaged 7 users. Second round of tests was made to verify whether improvements have been made in usability after we refined the design. For second round 10 users were engaged
Test 1 – Data input accuracy
We tested whether users could input data correctly. We found out that the form required too much manual input. After the test we:
replaced open text inputs with limited selectable options where possible
added radio buttons for constrained choices
added placeholder examples and contextual guidance
designer error messages
Outcome
Error-free input increased from 57% to 90%. This significantly reduced required manual work and increased workflow confidence
Test 1 – Data input accuracy
Process card before and after test
07.
Key design decisions
Test 2 – Process creation & submission speed
We tested time required to create a new process and submit it for approval. We discovered that only 57% of users created a process under 2 minutes
To streamline the process we:
replaced new process card screen with side curtain process cards that can be accessed from user profile
improved information hierarchy and readability
clarified primary actions
Outcome
users completing creation under 2 minutes increased from 57% to 90%
average creation time reduced from 65 seconds to 54 seconds
submission speed improved from 21s to 15s
This improved overall operational efficiency
Test 2 – Process creation & submission speed
We tested time required to create a new process and submit it for approval. We discovered that only 57% of users created a process under 2 minutes
To streamline the process we:
replaced new process card screen with side curtain process cards that can be accessed from user profile
improved information hierarchy and readability
clarified primary actions
Outcome
users completing creation under 2 minutes increased from 57% to 90%
average creation time reduced from 65 seconds to 54 seconds
submission speed improved from 21s to 15s
This improved overall operational efficiency
Test 2 – Process creation & submission speed
Process card before and after test
07.
Key design decisions
Test 3 – Process approval & rejection flow
We tested how quickly users could approve or reject processes. First round of testing showed that while users can perform each of tasks under one minute, there is some additional cognitive load when users are looking for the entry point for approval actions
What we changed to improve:
in team lead’s profile main CTA has been set to “Processes for approval”
Outcome
approval completion under 1 minute improved from 86% to 90%
rejection completion under 1 minute improved from 71% to 90%
shortened approval cycles and reduced friction
Test 3 – Process approval & rejection flow
We tested how quickly users could approve or reject processes. First round of testing showed that while users can perform each of tasks under one minute, there is some additional cognitive load when users are looking for the entry point for approval actions
What we changed to improve:
in team lead’s profile main CTA has been set to “Processes for approval”
Outcome
approval completion under 1 minute improved from 86% to 90%
rejection completion under 1 minute improved from 71% to 90%
shortened approval cycles and reduced friction
Test 3 – Process approval & rejection flow
Team leads profile before and after test
07.
Key design decisions
Test 4 — Process Discovery & Data Trust
We tested how easily users could locate a process and determine if the data was up to date. Before, only 29% correctly identified when data was last edited. Users also struggled to scan and filter the table efficiently.
What we changed:
added “Last edited” column
enabled sorting across table columns
improved filter and table data hierarchy and readability
Outcome
correct identification of last edit date increased from 29% to 90%
successful process discovery improved from 57% to 90%
reduced hesitation and clarification questions
Test 4 — Process Discovery & Data Trust
We tested how easily users could locate a process and determine if the data was up to date. Before, only 29% correctly identified when data was last edited. Users also struggled to scan and filter the table efficiently.
What we changed:
added “Last edited” column
enabled sorting across table columns
improved filter and table data hierarchy and readability
Outcome
correct identification of last edit date increased from 29% to 90%
successful process discovery improved from 57% to 90%
reduced hesitation and clarification questions
Test 4 — Process Discovery & Data Trust
Team leads profile before and after test
11.
Key outcomes
Our team delivered a practical, visually coherent solution that met project goals and supported the client’s internal users effectively, even with the strict time limitations:
20+ screens
a full set of screens covering personal profile, data tables, and process cards for all user roles
Reusable component library
we developed a shared UI kit and components to maintain consistency across the interface
Interactive prototype
we produced a prototype that was used for presenting and testing the design
Consistent and familiar UI and UX
the visual design followed the company’s internal product style
we improved usability and clarity for the main workflows
Our team delivered a practical, visually coherent solution that met project goals and supported the client’s internal users effectively, even with the strict time limitations:
20+ screens
a full set of screens covering personal profile, data tables, and process cards for all user roles
Reusable component library
we developed a shared UI kit and components to maintain consistency across the interface
Interactive prototype
we produced a prototype that was used for presenting and testing the design
Consistent and familiar UI and UX
the visual design followed the company’s internal product style
we improved usability and clarity for the main workflows
Reflection
During this project I learned the importance of frequent client communication and iterative feedback, which allowed us to make informed design decisions and quickly deliver the best result
My greatest achievement is that I learned how to manage the team’s design workflow through task grooming and prioritisation and how to lead design critiques and client design reviews, being responsible for the whole team's work
During this project I learned the importance of frequent client communication and iterative feedback, which allowed us to make informed design decisions and quickly deliver the best result
My greatest achievement is that I learned how to manage the team’s design workflow through task grooming and prioritisation and how to lead design critiques and client design reviews, being responsible for the whole team's work
