Skeema Case Study

WHAT'S SKEEMA

Tab overloading is a problem, Skeema (now Skipper) helps you solve that

Many people today have multiple tabs open. After a point, it becomes hard to even read the name on the tab. Skeema helped you solve that by allowing to organize your mind and your tabs.

MOTIVATION FOR REDESIGN

A year after launch, users started to drop off after continued use 📉

Despite a significant number of downloads, data revealed that many users dropped after a short period. My task was to uncover the reasons behind this drop-off and identify strategies for Skeema to improve user retention.

UNDERSTANDING THE USERS

Designing for the heavy context-switcher - categorizing data

Instead of focusing purely on the profession of users, Skeema’s main user archetype is the context switcher—those who juggle multiple projects, keep numerous tabs open, and navigate multiple windows. Hence I used python to categorize the user data based on the tab usage.

INVESTIGATING THE PROBLEM

Using Tableau and Python, I created visualizations of user data collected from Skeema to generate insights

FINDING #1

Users liked sorting tabs into projects

From the survey responses, I discovered that users identified sorting tabs into projects as their favorite feature. This suggests that tab organization for optimized searching and finding is a key strength that Skeema offers.

(Tableau Data Visualization 1)

FINDING #2

Users rarely used tabs from their saved projects

Average number of tabs revisited from saved groups was significantly lower than the number saved.

This was an intriguing finding, suggesting that users might either be forgetting to save tabs and just keeping them open, or they may be saving tabs they don’t actually need.

(Tableau Data Visualization 2)

MORE SECONDARY RESEARCH

Heuristic evaluation revealed that it violated the "recognition over recall" principle, expecting users to remember to save tabs

I conducted a heuristic evaluation on the current version of Skeema to assess how users were saving tabs into projects and identify any usability issues.

Users were required to remember to switch tabs—the very problem Skeema aims to solve—before adding them to a group. This created an extra step of tab switching and also forced users to recall that they needed to save a tab, which is both ironic and problematic.I saw an opportunity to prompt users to save tabs proactively, rather than relying on them to remember.

This adjustment would help Skeema better achieve its goal of preventing tab overload and reducing unnecessary tab switching.

Solution:
An Easier Way to Save Tabs to Projects, Without Changing Tabs

To tackle the challenge of increasing the usage of the 'save to group' feature, I designed a floating widget in addition to the Skeema extension pinned on the left. This widget is aimed at prompting users to save a useful tab immediately, instead of having to remember to switch tabs and then save them.

MEASURING SUCCESS - NEXT STEPS

To see if this solution is successful in achieving the goals, these are the metrics that we can collect:

Click rate on widget

This will help determine how useful the widget is in prompting users to save tabs.

Number of tabs added

This will help assess the widget's impact compared to the original method on user behavior.

Hover rate on widget

This will help us determine the conversion rate from hover to click

REFLECTION

Read my reflection post on this project featured on UX Bootcamp!

The smallest, most strategic changes — such as changing the color from bright to dark or moving the CTA button from bottom to top — can have a huge influence on user engagement and, as a result, achieve UX goals.

I learned that you don’t always have to introduce a new feature; if your research indicates that something isn’t working, you can make minor strategic changes, observe how people engage with it, and use that data to influence your design decisions and further build on it. This has been my biggest learning!