PROJECT #2
Federato
ACTIVATING SIMPLE,
SELF-SERVE EXPERIENCES
Turning complex, custom implementations into simple, self-serve experiences
SCOPE
MY ROLE
User research
UX Design
Technical Requirements
Design Lead
Planned and conducted user research activities
Took full ownership of design process from ideation
to dev requirements
Reviewed and validated designs with end-users
COLLABORATORS
Product Manager
Full Stack Developers
INITIAL PROBLEM DISCOVERY
Addressing scalability limitations with custom workflows
Due to the highly complex and varying needs of Federato’s clients, we created custom instances of the platform, each with its own unique triaging rules. This hindered scalability, as the team felt that custom implementations were necessary to accommodate the complexity of the triaging workflow setup.
INITIAL PROBLEM DISCOVERY
Clients cannot create their own triaging systems
Underwriters would have to communicate with engineering teams to implement custom rules
There was no front-end design in place for setting up triaging rules because of its back-end complexity
Challenge
CHALLENGE #1:
Empowering underwriters who may not have technical expertise to set up and modify complex triaging rules without needing to consult engineering teams.
CHALLENGE #2:
Translating the intricate back-end logic of triaging workflows into a user-friendly interface that could handle complex rule configurations without overwhelming the user.
PLANNING: INFORMATION ARCHITECTURE
Breaking down the structure of a rule
Ensuring that any and all types of rules can be created by the user with a single interface
Accounting for user error and the dependencies of different rule elements in the back-end
1
Timeline
2
Applicable Accounts
3
Applicable Objects
4
Conditions
4.1
Condition Filters
STRATEGY
Simplifying rule structure into
a step-by-step guided process
By guiding the user through a triaging rule setup, the interface becomes more digestible while not being as exhausting to complete
Rule setup needs to be paired with a dashboard that allows the user to view the impact of their rules
ITERATION #1-4
Bringing the back-end structure to the front-end
Too much of a literal translation from the backend rule structure
Breaking down a condition into characteristic, value, and criteria introduced too many layers
Overcomplicating the condition building process, making this design unusable for creating effective rules
ITERATION #5
Designing a simplified and familiar experience
Adding human-readable translation of conditions
Creating a unique front-end structure that translates seamlessly to back-end objects
PAIRING RULES WITH ANALYTICS
Adding a dashboard to measure rule impact
Insert Your Design Here
Macbook Pro
This helps encourage users to build robust rules
Allows internal teams to assess the complexity of rules and evolve with users’ rule structuring needs and challenges
DEV REQUIREMENTS
Shipping Faster
Establishing clear component requirements with value thresholds, expected data types
Designing new design system elements and variants
Outcomes
Expanded design system
New product vertical
Moving towards a scalable product
Complex Rules