UX Zen Studio Archives

Published Docs

Hey, there I am publishing an Impact Filter for the general workflow which has enhanced my working as a UX Lead over the past years and hope it helps your team gain clarity in the chaotic jungle we call UI/UX Design there are more parts to it elaborating on Design Documentation, Training requisites, and CX Analytics which also create your designer’s report card.

？Why to use an Impact Filter?

[Assumption: SaaS B2B industry where we work with reports as deliverables across multiple portfolios. Same can be replaced with phase launches/milestones, seasonal products, etc.]

Cheers!

Project

UX Initiative: Design Standard Operating Procedure, a guide for designers to enable collaboration and fluid work efficiency.

Situation

What do you want to accomplish? What is your motivation?

  1. To standardize the designer’s process of working.
  2. To enable usability of one’s design work for another by establishing ground rules for major variable at play, like nomenclature, design system structure, file handling, and version/iteration management.
  3. To promote library creation in Figma and its usage for faster turnaround time.
  4. To make hand-offs easy and independent of creators for all stakeholders with design documentation.
  5. To fetch feedback after project completion for UX analytics.

Importance

What is the difference this will make? What impact will this have?

  1. Team collaboration became efficient and independent of guidance.
  2. Setting a common ground for designers and developers related to UX work through intervention at multiple touchpoints in the pipeline.
  3. Adoption of a matured operation structure, elevating the quality of work.
  4. Enhance team collaborations leading to maturity in UX Center of Excellence.

Ideal Outcome

What does the completed project look like? What is the payoff?

  1. Enhanced process compliance to make design work free of unknown factors.
  2. Faster iterations and structured hand-offs.
  3. Better file and design library management to use across projects.
  4. Inception of UX analytics to track impact from UX work done.

Success Criteria

What specific results must be true for this project to be a success?

Created a SOP documentation based on:

  1. File organization structure: Set files and folder structuring rules for different repositories (SharePoint and Figma)
  2. Nomenclature: Followed standard naming formats for files, pages, sections, variables, layers, components, etc.
  3. Version & iterations: Easy rollback to prior designs, and efficient management of project iterations.
  4. Collaboration & access: Set rules for adding collaborators or dev-mode access with approvals from management.
  5. Design System & Libraries: UI kits/Design guidelines established to maintain a consistent look and feel across products and experiences and publishing libraries.
  6. Design Documentation: Followed a structured process on FigJam to cater various stakeholders for project related communication without dependency on designers during and post project tenure.
  7. CX Analytics: Sharing surveys with relevant stakeholders in a project to track designer’s performance by analyzing project success on a dashboard.

Best Result

What’s possible if you do take action?

  1. Reduction in unstructured parts in pipeline, focused on designing process apart from org-level compliances.
  2. Proficient designers, ready with pre-requisites for any upcoming project.

Worst Result

What’s at risk if you don’t take action?

  1. Complicated and varying design process of each designer, leading to gap in performances.
  2. Dependencies for knowledge transfer and guidance prevails.