My contribution
Led UX discovery process
Redesign the audit trail experience
Translate insight into actionable designs
Collaborated cross-team
UX KPIs
✔️ Decrease log investigation time
✔️ Simplify payloads readability
✔️ Improve user adoption
Product design KPIs
✔️ Reduce log-as dependancies
✔️ Reduce tickets for support team
✔️ 80% use cases covered
Collaboration team
Alexandra L.
Product Owner
Thomas L.
Full stack dev.
Quentin M.
Integration
Aurélie T.
Customer Care
Diana M.
Copywriter
Background
When I joined the project, the audit trail feature hadn't been updated over 4 years despite being a crucial tool for our integration and support teams. This feature is used to trace user actions in activity logs, enabling teams to debug issues quickly and accurately.
As our product and client base grew, so did the volume of logs—exposing significant usability challenges:
Time-consuming because there is no pagination
Logs loaded by default, slowing down the landing experience
Without specific details, users read many unnecessary results
Copywriting is misleading
Outdated filters leading to user frustration
On average, 50% of support issues involve an audit trail search at least once a week, highlighting the value of easy log access.
The main use case for our customers has a specific order and it is to check who made an action, when, on what item.
Design goals
Short-term: Improve usability and accessibility for internal users (support and integration teams), enabling them to investigate issues independently and more efficiently.
Mid- to long-term: Extend functionality to external beta HR users, ultimately enabling HR teams to have autonomy in checking their own logs without relying on support.
The main use case for our customers has a specific path:
Who performed an action → When it happened → On what item.
Before
After work
How I arrive at design solutions ?
Understand the feature and the project scope
Based on documentation, interviews with users and PO
To lay the foundation, I first developed a deep understanding of how audit trail systems work and how our platform logs, stores, and surfaces user actions
Grasp the logic and workflow of our company, test and document it
Test and document how different events are categorized, and stored
Improve filters criteria
One key UX opportunity emerged early:
users needed clear visibility into trigger type, event origin, and action name to make sense of the logs at a glance.
Pain points identified
Internal teams
Support, integration, implementation
Hard to find the correct log
Results are irrelevant
Logs are not self explanatory
Customer tickets are not enough detailed
Ex: they don't provide the file name
End users
HR administrators, HR Users
Depend on an external support team to get a quick information.
Qualify and detail the tickets created to support
How users research a log
User research and understanding of the mental model
Users search for history made on a specific item
Too many irrelevant results making users apply filters 1 at a time which makes the research process long and very frustrating
—We combined those qualitative insights with data analysis on Pendo. We mapped the actual filter pattern, confirming the misalignment between filter behavior and user expectations.
These insights led to a clear design priority:
→ Refine and prioritize filter criteria to match user mental models, reduce noise, and shorten search time — our KPI.
Keep in mind the technical constraints
From product brief, Dev interviews, documentation
Align Technical Constraints with UX
New DLS coming soon —> I ensured designs & components consistency & scalability
Some info and log are technically inaccessible
—
Improve Clarity Across Teams
I standardized date formats and filters in UTC to align technical teams and customers' timeline
Worked with copywriting team to reduce misinterpretation such as labels, system messages…
Design solutions
Improved empty state: focused XP and quick loading
Add contextual explanations to users on how to get relevant results + provide documentation on a Confluence page
Refined filter logic to provide better results
Order
Copywriting
Enter minimum of 3 filters
Standardized the order of log attributes to match user expectations and real-world workflows.
Competitors analysis helped me to present technical information
User tests results, feedbacks & design reviews
Using Axure to provide embedded filters
Validated concepts:
80% of the use cases were covered with the new experience
Filters are clearer and return relevant results
Show results only when user end at least 3 filters improved precision and help the "no pagination"
The new “All actions” filter was highly appreciated
Users valued the ability to export filtered results for further analysis and sharing it with customers
Improvements ideas :
Users would like to compare multiple logs at once which is technically impossible
Suggested to lighten payloads by highlighting only differences between log
Delete misleading and useless icons
Provide dual entry of employee selection : by name and UUID
Provide all the logs in filters and results for example permissions
