What is Loop?
Loop is a productivity Dashboard that unifies the productivity tools you already use.
We integrate with Google, Microsoft, Slack, Jira, and even Twitter to organize your apps based on what's important to you right now.
Business Goal
Our aim was to achieve a substantial increase in user activation by at least 50% beyond the first week of onboarding. To ensure long-term engagement, we optimized onboarding, identified pain points, and made strategic improvements throughout the user journey. Key metrics for success:
Activation Rate: Percentage of new users completing onboarding and interacting with a meaningful feature in the first week.
Time-to-Value: Average time for users to experience significant value.
User Feedback: Gathered qualitative data through feedback, surveys, and interviews for deeper insights.
User's Problem
According to interviews and surveys, users misunderstood how the product performed. They had a misaligned mental model. A mental model is based on belief, not facts: that is, it's a model of what users know (or think they know) about a system. A misunderstood mental model leads to incorrect actions which cause frustration and eventual abandonment.
I led three rounds of rapid prototyping and usability testing to discover ways to improve the user's mental model.
My Design Process
Stage 1: Understand
1-2 días
Goal Collaborate with the team to gain a shared understanding of user needs.
How Define clear business goals and a plan to achieve success.
Deliver User interviews & Contextual inquiry, Competitor analysis, Internal expert interviews.
Stage 2: Define
4-7 días
Goal Synthesize research findings and identify user problems.
How Formulate user needs and metrics to track design success.
Deliver User Need statement, Persona, Track engagement Mixpanel, Heuristic Evaluation, User Flow.
Stage 3: Sketch
4-7 días
Goal Generate creative and effective solutions.
How Facilitate cross-functional brainstorming sessions.
Deliver Present Crazy 8's, wireframes, and a black and white prototype for user testing.
Stage 4: Decide
4-7 días
Goal Team and stakeholders decide what will be prototyped in high fidelity.
How Team review’s insights from usability tests and design artifacts.
Deliver Establish a clear path forward and document design decisions.
Stage 5: Prototype
4-7 días
Goal Bring ideas to life with a tangible representation.
How Define typography, color, style, and UI components.
Deliver Develop Figma components representing UI states, templates, and a high-fidelity prototype for user feedback.
Stage 6: Implement
4-7 días
Goal Transform the vision into a tangible product.
How Facilitate a smooth engineer handoff and engage in continuous testing.
Deliver Conduct usability tests, implement a design system, and collect quantitative metrics to validate success.
Solution
We led three fundamental changes
- Visual Hierarchy
The design challenge was creating a sense of hierarchy while minimizing the time front-end engineers would need to update the designs. I accomplished this by maintaining the overall layout but differentiating items using color, font size, and indentations.
- Convenient Notifications
User testing pointed to the ambiguity of "what just happened" after task completion or failure. In collaboration with the product manager and a backend engineer, I created a Notification library that demonstrated which notification to present to a user at the appropriate times.
- Onboarding
After implementing the UI for the Dashboard, I was re-hired to create a guided onboarding tutorial. The tutorial engaged the first-time users as their data was loading, leaving them with a more precise mental model, further increasing user retention. We achieved our business goal of improving user activation to over 70% past their first week.
