AeventLi
Redesigning an event-logging system to reduce friction
and improve core data clarity
AeventLi
Redesigning an event-logging system to reduce friction and improve core data clarity
TL;DR
The problem
The problem
An existing event-logging system became outdated and unaligned with daily user needs.
Important data and high-priority features were hidden, and users were complaining about high cognitive load while interacting with the system.
An existing event-logging system became outdated and unaligned with daily user needs.
Important data and high-priority features were hidden, and users were complaining about high cognitive load while interacting with the system.
What I did
What I did
I led the full redesign process. Working closely with product managers who provided direct insights from user interviews, I translated user constrains into actionable UX solutions.
I led the full redesign process. Working closely with product managers who provided direct insights from user interviews, I translated user constrains into actionable UX solutions.
Initial impact
Initial impact
Initial rollout to super-users gained 100% positive feedback on the new screen structure, improved visibility of key data and streamlined daily workflow.
Initial rollout to super-users gained 100% positive feedback on the new screen structure, improved visibility of key data and streamlined daily workflow.
NDA Disclaimer
NDA Disclaimer
Due to a Non-Disclosure Agreement (NDA), sensitive details, specific domain terminology, and real client data have been anonymized or modified.
Due to a Non-Disclosure Agreement (NDA), sensitive details, specific domain terminology, and real client data have been anonymized or modified.
Redesigning the experience
Redesigning the experience
Aeventli is an enterprise platform used to document, track, and manage complex events. The redesign was driven by user feedback regarding daily workflow friction, the need to adapt feature sets, and a strong push to realign the system with evolving operator needs.
Aeventli is an enterprise platform used to document, track, and manage complex events. The redesign was driven by user feedback regarding daily workflow friction, the need to adapt feature sets, and a strong push to realign the system with evolving operator needs.
My role
Product designer -
Led the full redesign
process
Status:
Beta Launch &
User Validation
Team:
2 product designers
2 product managers
8 developers
The main pain points
The main pain points
Product team research revealed three primary user pain points:
Product team research revealed three primary user pain points:
Poor hierarchy
Poor hierarchy
Critical data was buried while secondary elements took up prime space.
High cognitive load
High cognitive load
Dense layouts and overcrowded forms made data entry overwhelming.
Outdated workflows
Outdated workflows
The rigid interface created constant friction in daily operations.
Goals & Success metrics
Goals & Success metrics
Optimized Screen Layout
Optimized Screen Layout
Reorganize screens to bring critical data upfront and relegate secondary information.
Cognitive load & Product alignment
Cognitive load & Product alignment
Simplify complex screens while respecting the product guidelines and keeping essential data visible.
Fast scanning & Intuitive features
Fast scanning & Intuitive features
Keep data entry fast and ensure new capabilities are seamless and friction-free.
The process: Before & After breakdown
The process: Before & After breakdown
"The information I actually need is buried or hidden, while less important things like images take up the whole screen."
User 1 / user research stage
"The information I actually need is buried or hidden, while less important things like images take up the whole screen."
User 1 / user research stage
*Sanitized mockups due to confidentiality limits.
*Sanitized mockups due to confidentiality limits.
Restructuring the event screen
Restructuring the event screen
The before
The before
• Low-priority elements (map & images) dominated the screen, while the critical "data" section was buried.
• Low-priority elements (map & images) dominated the screen, while the critical "data" section was buried.
• The event details section was visually overwhalming.
• The event details section was visually overwhalming.
The after
The after
• Scaled down map and images to the left column, accessible without stealing focus.
• Scaled down map and images to the left column, accessible without stealing focus.
• Placed "data" section front and center using progressive disclosure to show key info first.
• Placed "data" section front and center using progressive disclosure to show key info first.
• Reorganized the event details form into distinct categorized sections for better scanning.
• Reorganized the event details form into distinct categorized sections for better scanning.
"Adding or editing event details feels overwhelming because the layout is so crowded and disorganized."
User 2 / user research stage
"Adding or editing event details feels overwhelming because the layout is so crowded and disorganized."
User 2 / user research stage
*Sanitized mockups due to confidentiality limits.
*Sanitized mockups due to confidentiality limits.
Editing\adding event data & Iterative process
Editing\adding event data & Iterative process
The before
The before
• The most critical section to update, the "data" section, was cramped at the bottom left with dense cards.
• The most critical section to update, the "data" section, was cramped at the bottom left with dense cards.
• Low-priority map and images took up prime space during data entry.
The after
The after
• Moved the map and images to the side column and centered the "data" section.
• Moved the map and images to the side column and centered the "data" section.
• Used larger, categorized cards with progressive disclosure (data section).
DESIGN ITERATIONS & TRADE-OFFS
DESIGN ITERATIONS & TRADE-OFFS
Streamline the "data" section workflow
The challenge
The challenge
After restructuring the event screen, we agreed that a table layout worked best for viewing data, but failed during editing.
After restructuring the event screen, we agreed that a table layout worked best for viewing data, but failed during editing.
Design constraints
Design constraints
To preserve context, the edit state had to keep the viewing layout intact. However, editing directly within the table became cramped due to additional required inputs.
To preserve context, the edit state had to keep the viewing layout intact. However, editing directly within the table became cramped due to additional required inputs.
First iteration
Separate Modal
Separate Modal
First, I introduced a separated modal for data entry/editing. This allowed users to focus on editing using structured cards while keeping the table intact.
First, I introduced a separated modal for data entry/editing. This allowed users to focus on editing using structured cards while keeping the table intact.
Pivot reason:
Pivot reason:
Product & users required full context on one screen.They wanted to see event details side-by-side with the data they were editing without leaving the main page.
Product & users required full context on one screen.They wanted to see event details side-by-side with the data they were editing without leaving the main page.
Final design
The single screen solution
The single screen solution
We brought editing back to the single screen using expandable cards instead of the cluttered table view.
We brought editing back to the single screen using expandable cards instead of the cluttered table view.
The outcome
The outcome
Based on the beta testing, users appreciated having full context, a centered layout and clearly structured, spacious cards.
Based on the beta testing, users appreciated having full context, a centered layout and clearly structured, spacious cards.
"I wish I could see who made changes over time. Turns out the feature existed, but I missed it until someone pointed it out."
User 1 / user research stage
"I wish I could see who made changes over time. Turns out the feature existed, but I missed it until someone pointed it out."
User 3 / user research stage
*Sanitized mockups due to confidentiality limits.
*Sanitized mockups due to confidentiality limits.
Refining the event activity & notifications
Refining the event activity & notifications
The before
The before
• The activity tracking feature was buried behind a generic information icon because it was rarely used in early versions.
• The activity tracking feature was buried behind a generic information icon because it was rarely used in early versions.
• As the system evolved, operators increasingly needed a clear audit trail to track every change in real-time.
• As the system evolved, operators increasingly needed a clear audit trail to track every change in real-time.
The after
The after
• Moved the activity feed to a dedicated side panel triggered by a clear bell icon.
• Moved the activity feed to a dedicated side panel triggered by a clear bell icon.
• Grouped sequential changes by the same user to reduce clutter
• Grouped sequential changes by the same user to reduce clutter
"I can’t get a bird’s-eye view of all events. Relying only on a narrow sidebar makes searching and filtering older events really frustrating."
Superuser / user research stage
*Sanitized mockup due to confidentiality limits.
*Sanitized mockup due to confidentiality limits.
Superuser summery dashboard / Additional feature
Superuser summery dashboard / Additional feature
Why it was added?
Why it was added?
The narrow sidebar couldn't support high-level overview tasks for power users.
The narrow sidebar couldn't support high-level overview tasks for power users.
The solution
The solution
We created a master table view with quick filters, allowing superusers to sort, summarize and prioritize events in seconds.
We created a master table view with quick filters, allowing superusers to sort, summarize and prioritize events in seconds.
Early validation & feedback
Increased system adoption
Increased system adoption
Driven by positive user feedback and ease of use, the redesigned system attracted new teams who actively chose to adopt it into their daily workflows.
Driven by positive user feedback and ease of use, the redesigned system attracted new teams who actively chose to adopt it into their daily workflows.
Higher user satisfaction
Higher user satisfaction
The comprehensive redesign and requested features directly resolved user pain points, significantly improving the overall user experience and boosting satisfaction.
The comprehensive redesign and requested features directly resolved user pain points, significantly improving the overall user experience and boosting satisfaction.
REFLECTION
REFLECTION
What worked well and what I'd do diffrently
What worked well and what I'd do diffrently
WHAT WORKED WELL
Working closely with developers and addressing edge cases early sped up our beta release and ensured a smooth launch with almost no bugs and technical issues.
WHAT I'D DO DIFFRENTLY
Relying on feedback through product managers led to extra design iterations. Direct user communication from the start would have saved time.
NEXT PROJECT:
Regulab
BETA TESTED
SAAS B2B
Reducing cognitive load by consolidating 4 fragmented tools into 1 intuitive regulatory system
Atlas
ENTERPRICE B2B
Centralizing 6 different excel files into one employee management workspace for 70+ employees.
estherbilyar@gmail.com
Resume
NEXT PROJECT:
Regulab
BETA TESTED
SAAS B2B
Reducing cognitive load by consolidating 4 fragmented tools into 1 intuitive regulatory system
VIEW CASE STUDY