Users experienced notification fatigue because an app kept triggering notifications, leading to higher uninstall rates. The work focused on simplifying the notification system to reduce cognitive load. The change produced a measurable drop in uninstalls, demonstrating UX competency. However, the portfolio framing emphasized that users found the experience hard without explaining the stakes or outcomes in a broader context. Employers responded with interest but quickly moved on because the stakes were not clearly connected to the mechanism and impact. Research into the company context enabled the same design work to communicate a larger story and better showcase value.
"I heard uninstalls were up when I started this project." A client mentioned this to me offhand, not realizing it was the core of her work story. It sounded like a simple ask: users were experiencing notification fatigue from the app because it kept triggering. She went in, simplified the system, and reduced the uninstall rate."
"She wrote what she knew from a UX perspective: I reduced cognitive load by streamlining the notification system, resulting in a measurable drop in uninstalls. It was true, and it showed her competency. But employers were going "cool" and forgetting by the next slide. Why?"
"Cognitive load describes the mechanism of the work and stops short of the stakes. It read like "things were hard for users" without explaining what that resulted in. She wasn't sure what else she could say. Then I spent forty-five minutes researching her company."
"The design work hadn't changed. But once you understood the larger context, the same project told a far bigger story, one that showcased the..."
Read at Medium
Unable to calculate read time
Collection
[
|
...
]