Appian
Overview
I designed several features of the Connected KYC solution and built up the internal Solutions design system.
Role
Product Manager Intern
Risk score display
Problem
The risk score allows customers to categorize their clients and is used in configuring how much weight each question poses in terms of business risk. We want to allow users to understand how risk scores are determined and calculated.
There are six primary problems identified:
Unclear what a risk score measures
Unclear risk threshold levels
Unclear risk score calculation
Unclear max possible risk
No directions as to how much risk per question should be added
Risk score display isn’t consistent → integer vs description
Solution
Determine a solution that clearly explains to the users what a risk score is, how it is calculated, and what constitutes each level.
Changes made include:
Updating the home page risk profile section to define overall risk score and view top changes in risk scores
Allow user to view / sort customer risk scores and customer risk score changes
Fixed design inconsistencies throughout the platform
Implemented cards to define and instruct users when building questions that involved calculating risk score
A crucial piece of this project was also ensuring each screen was AA compliant, especially given the new color palette we planned to introduce.
Solutions design system
The Head of Solutions Design created an internal design system containing common components and patterns used, along with branding guidelines. This was in the form of a Google Slides deck and called the Solutions Design Playbook. This was assigned to the Solutions interns this project for our Indie Time.
Competitive Analysis
We compiled reports analyzing four popular design systems in order to understand what works well and what may not translate over to Appian. We reviewed Atlassian, Salesforce, Microsoft, and Marvel.
UX Design Process
After interviewing several members of the Solutions team, we identified three user personas that utilize the Playbook:
User Experience Designer needing a refresh on Appian components or patterns
Product Manager on a team without a UX Designer who acts as one
Product Manager on a team with a part-time UX Designer who wants to take on some of the design workload
We used the research to organize our thoughts on a Miro board. This resulted in six categories that our users commonly referenced.
After
Ultimately, we identified six core user problems that were both high impact and feasible:
Unclear when to use certain components or patterns which results in inconsistency.
There is difficulty navigating to find the desired information.
Components can be too broad and unusable.
Non-UXDs have difficulty understanding designer-specific language.
There are no role-specific resources.
Users have no place to leave centralized feedback.
We summarized each category into key problems and placed each one on a prioritization matrix.
Brainstorming
Using the six problems listed above, we spent some time brainstorming possible solutions which we added under the relevant problem.
Site Map
We knew that the end product would be a website built using Appian SAIL so we begun building out a site map that structures the primary and secondary navigation. A card sorting activity helped us determine which topics go where and how important they are to users.
After
After
After
Mockups
