Objective: To design an in-app broadcast system that allows the team to reach users directly within the Talenox platform (An HR platform). The feature streamlined employee communications, ensured critical updates were delivered in real time, and reduced dependence on costly external channels. This feature will be used mostly by the customer success team.
Role: User Research | Prototyping | Workflow Improvement | UI Redesign
Outcome: Reduced business costs by eliminating reliance on third-party tools that incur per-resolution fees.
Role: User Research | Prototyping | Workflow Improvement | UI Redesign
Outcome: Reduced business costs by eliminating reliance on third-party tools that incur per-resolution fees.
Discover
After gathering the user interview data, I ran an affinity mapping exercise to synthesize the key pain points
Define
The goals were refined to focus on these key areas, guiding us to explore potential solutions for each pain point.
Goals/Focus:
1. Create an intuitive page where users can easily access and review all past messages.
2. Simplify the process of targeting and segmenting audiences when sending messages.
3. Ensure users can acknowledge messages to support accountability and tracking.
4. Reduce overall communication costs!
Develop
The wireframes
I created quick wireframe drafts to collect feedback from Customer Success and Engineering. This process helped define a standardized visual hierarchy and layout and check if requirements are met.
I created quick wireframe drafts to collect feedback from Customer Success and Engineering. This process helped define a standardized visual hierarchy and layout and check if requirements are met.
An Index page
AB Testing of Wireframes
Objective:
To identify which flow made it easier for stakeholders to understand how to target companies effectively for broadcast messages
To identify which flow made it easier for stakeholders to understand how to target companies effectively for broadcast messages
Wireframe A displayed different options in tabs, each guiding users through a specific target flow, while Wireframe B presented its options after conventional filter methods.
Results:
70% of stakeholders found Wireframe A easier to follow compared to 30% for Wireframe B
Stakeholders described Wireframe A as 'clearer' and 'faster' while Wireframe B was seen as 'more time consuming to build' and 'unnecessary'
70% of stakeholders found Wireframe A easier to follow compared to 30% for Wireframe B
Stakeholders described Wireframe A as 'clearer' and 'faster' while Wireframe B was seen as 'more time consuming to build' and 'unnecessary'
All three options in tabs of Wireframe A
Deliver
All updates page
Create message page
Reflections
This simple exercise reminded me that good design isn’t just about aesthetics. Conducting interviews and extracting insights is essential for shaping and launching a successful MVP no matter how easy it seems.
This experience taught me that assumptions as a designer can be risky. The wireframe we created for targeting companies not only sparked discussions about the effort required to build it, but also revealed that conventional filtering methods (wireframe B) we often rely on aren’t always the best solution. This is why A/B testing is crucial. It helps challenge assumptions and uncover the most effective approach.