Financial Operations Search Redesign
Problem: The operations search function was becoming cumbersome with the addition of new search fields to accommodate several classes of users.
Goal: New search architecture providing easy, efficient and quick searching that meets user needs
Solution: A quick search that expands to an advanced search, with similar search fields grouped together under meaningful headings
Team: Myself (content design), three experience architects, one UX researcher
Constraints:
Many fields to account for
Several user groups with different security clearance access levels
4 week timeline
Step 1: Establishing Context and Background Research
Cognitive Overload
The initial search function was created early in the project before several new user groups were added. When new users groups were added, their required search fields being added on without any underlying strategy to the architecture. It was becoming increasingly difficult for users to perform searches quickly, given the number of fields to be scanned visually in order to find the desired ones.
Original Search Design
Step 2: User Research and Synthesis
User Interviews
Our team held weekly user group meetings with representatives from all of the user groups. Users gave input on how previous systems functioned, as well as suggestions on useful features. The sessions also allowed us to show early designs and iterate with user feedback.
User Survey Analysis - Quick Search
We surveyed the user groups on the frequency of use of search fields. The survey insights helped to determine the most frequently used fields that would live in a smaller, quick search, to be accessed right off the dashboard. The remainder of the fields would be housed in the expanded advanced search section.
Information Architecture - Affinity Map for Advanced Search
In my analysis of advanced search fields, I grouped like fields together to reduce cognitive effort needed to find specific fields. Introducing descriptive headings for the groupings allowed for more organization and logic for the interface.
We had 4 overarching categories of search types, each category with a unique set of search fields. Some of the fields repeated in other search types, but many were specific to one type. Each of the four colors in the affinity map corresponds to a different search type: Transaction, File, Batch and Message.
Step 3: Design
With the insights from our research and my analysis, the team created a design for search that incorporated groupings in the advanced section.
Improvements:
Quick search section to allow easy access to frequently-used fields
Expandable advanced search section for more involved searching
Advanced search groupings of like categories under descriptive headings, creating easier scannability and reduced cognitive load
More white space highlighting the new visual hierarchy
Step 4: Validation and Results
“It’s like night and day from what we have been using”
~ A Business Ops Analyst User