Platform McKinsey
E2E flow for Secure Project Management
Duration
Mar. 2024 - Jul. 2024
Role
Senior Product Designer
Team
1 Principal Designer
2 Contract Designers
Context
Platform McKinsey is a comprehensive, cloud-based platform designed to accelerate and de-risk the development of digital tools, data, and analytics.
The team is following agile process with daily design checkin and weekly calls with PMs and Developers.
I took ownership of three major responsibilities
in addition to other UI/UX improvement tasks.
User Research
Conducted baseline research to update outdated insights and understand changes in target user groups as the product matured over two years.
Permission Group Feature
Designed and implemented an E2E flow for a new feature that manages members' service access more securely.
Template Feature
To meet the needs of our largest stakeholder, I developed a template feature to streamline project creation and reduce risks in client work.
1.Permission Group Feature
Problem
Giving access to every team member poses data security risks and increases license costs.
The current mapping of project roles to service access is inefficient, as PMs and leadership roles don’t require high-level access to all instances.
We need a system to manage clients' access to instances.
In similar platforms, admins often forget to configure service roles or are unaware that it is a necessary step.
Complication
Separating service access from project management is a widely accepted concept among developers in the firm but not among regular consultants.
Potential confusion and increased administrative workload for managing varying levels of access.
Risk of accidental misconfiguration, leading to either excessive or insufficient access for certain roles.
Possible delays in project workflows as access levels are adjusted and refined.
2.Template Feature
Problem
Our primary stakeholders manage multiple projects involving high-risk personal data, necessitating specific restrictions such as mandatory training and location constraints.
Separate billing charge codes are required for certain types of projects.
Projects handling highly sensitive data need attestations to comply with firm policies.
The security team is overloaded with work and requires a simpler, more efficient, and secure way to manage projects in batches.
Complication
The template concept is new, requiring clear communication to ensure understanding.
The template will be shown in the 'create project flow,' a major flow in PMcK, with complex logic behind each field.
Adding features to manage projects will impact multiple flows, including the project home page and members page.
Cross-team collaboration and effective leadership communication are essential.
3.Post-MVP Evaluation Study
Research Objective
Understanding Journeys
Exploring diverse product development journeys across roles to identify pain points, unmet expectations, and desired features, aiming for a comprehensive understanding for our users that extends beyond PMs and developers to uncover future opportunities.
Collecting Knowledge resources for KB
Identifying challenges in accessing information both within and outside DevEx, and collecting other valuable content beyond our Knowledge Base to integrate.
Evaluating Designs
Getting feedback on mockups for refinement.
Findings were shared across the team to shape the 2024 roadmap and serve as the foundation for new features.