Dmitry Moystsrapishvili

LinkedInEmailResume
Home

March–June 2023

Summary

In 2023 Product Design team at RBC has been transformed. All design processes and tasks documentation were transferred from Notion to Jira to consolidate Designers, Managers and Developers in one space

Team

5 Product Designers
8 Product Managers
4 Project Managers
1 HR Business Partner
1 Design Operations

Problems

Notion legacy

RBC held all product design processes at Notion, which should have been adapted to Jira framework

Non consistent and non transparent product processes

Managers and designers working in different products had different processes, which led to miscommunication between business units

Water Flow legacy without sprints

The delivery process was working disorderly. There wasn’t any common entry point for incoming tasks

Working process

Discovery

Analysis

I aimed to analyse the current Work Flow of the RBC Product Design team to identify ways to implement gradual and seamless improvements

Interviews with Stakeholders

On 1–1 sessions with Product Designers, HR Business Partner, Product Managers and Head of Design Department I gathered insights on pain points in the current Work Flow and identified areas for improvement

Main scope of work at this stage

Collaboration with Product Designers and Managers
Collaboration with Design Operations and HR Business Partner
Collaboration with Head of Design Department
Data analysis

New Jira columns with transparent statuses for each task

Solutions

Modified Work Flow with old legacy taken into account

All tasks now have clear and understandable statuses in Jira: Backlog, Paused, In Progress, In Review, Closed

For the cases, when Product Designer should take some recourses helping Q/A testers or Developers, we have a status “Support” (added after Work Flow testing). It means that the task is completed, all the layouts are done, but Product Designer supports the result: makes a review of pre-prod version, grooms Figma files with Developers, collaborates with Q/A testers

Unified delivery process in Jira for all the ecosystem products

New tasks have a clear product framework, which helps managers better describe the problem to product designers. New epics are divided into subtasks (user flows). Each task is properly described by Product Managers

New default Product Design task template in Jira

Jira is optimised for new processes

Each Product Designer now may filter his/her name in Jira and get the access to the tasks faster

Product Managers, Team Lead and other Stakeholders have a clear and transparent system of task’s statuses

Developed onboarding document for product processes

All information about new product processes are collected and described in Notion-document. New members of RBC may onboard themselves into the product processes faster

Product Design Work Flow guide in Onboarding

Testing

Overview

At this stage, I tested the new Work Flow with team members to ensure it addressed the Stakeholders' pain points effectively. The primary goal was to verify that the adjustments resolved key issues and improved overall efficiency of team work

Adjustments

After Work Flow testing I've added the status "Support" and made some adjustments to Jira settings

Feedback from Product Manager

Metrics

Communication costs

Reduced by 30%. Managers and Designers don’t waste a lot of time for additional communication about each task

NPS of working in Jira and updated product processes

Increased by 60% according to the survey of HR Business Partner among Designers, Product Managers and C-level Stakeholders. Feedback from some Product Managers was shared in the internal Telegram channel. This open communication helped keep everyone informed and aligned on potential Work Flow enhancements

Onboarding costs

Reduced by 20% for Product Designers and Product Managers

My role

UX research

Team leadership

Communications