Skippit
UX/UI Design
UX Research
About the project
Skippit was created by Redberry, gathering essential tools digital agencies need in general, including reporting, traffic management, vacation management, project/invoice management, recruitment and more.
Throughout the UI/UX design process, I collaborated closely with Developers and Project Owner. Applying a design thinking process enabled me to receive continuous feedback, allowing me to align business goals and user needs effectively.
Challenge
After working with the team to develop SkippIt as an internal tool, the business identified an opportunity to expand its reach by offering the platform to external agencies. Taking an internal tool public is a massive undertaking. While the business side worked on the long-term strategy for SkippIt’s external debut, the product team entered a "planning gap". We knew the destination—helping other agencies—but the roadmap was still being drawn.
Rather than letting the product stagnate during this strategic phase, we identified a crucial opportunity to refine our existing baseline. The challenge wasn't just about building new things; it was about validating years of internal decisions. We chose to pivot our focus to user research.
Approach
Through initial collaboration with the PO, we identified initial pain points requiring investigation and developed a research plan to uncover additional issues directly from users. We chose semi-structured interviews for it's flexibility—allowing us to probe deeper into unexpected insights while maintaining focus on key questions.
We established a research group of 10 users—including PMs, CFO, HRs and Sales. We synthesized interview findings into insights and workshopped them with the product team through collaborative brainstorming sessions. We moved quickly into wireframing, then validated solutions through a round of usability testing with the same user group before proceeding to final UI design.
UI Concepts
I'd like to share one key issue we identified and refined through our research process. User research revealed that the existing notification system created significant friction. Users struggled with a poor signal-to-noise ratio—urgent updates were buried alongside routine follow-ups, making everything feel equally important. This cognitive overload led to delayed actions and procrastination, directly impacting project efficiency.
During our brainstorming sessions, we generated an idea to separate notifications by priority and context rather than funneling them into one place. I explored this concept through wireframes, organizing the dashboard into two main zones: on the left, a financial report with bench stats and an utilization chart; on the right, three reminder-focused modules for upcoming items, unpaid invoices, and unpublished budgets.
Rather than forcing users to mentally filter notifications, the design separates time-sensitive reminders into dedicated modules. Each section addresses a specific concern (financial, scheduling, administrative), reducing mental load and enabling users to prioritize actions based on context.
Next Project
👇
Invite team members
Tablet
Mobile
