top of page

Anjanesh Sharma

OPTIMIZING THE ECOSYSTEM SYNC EXPERIENCE

Ethnographic study of "Hyper-Traders" to identify critical feature gaps driving user migration to competitors.

Project Overview

Role

Lead UX Researcher

Timeline

3-week agile sprint

Methodology
Moderated Usability Testing, Unmoderated Task-Based Testing, Post-Task Surveys (SEQ)

DOMAIN
Health & Wellness / Ecosystem Integrations

Business Context

A major health and wellness app acts as a central hub for users’ health data, aggregating metrics from various third-party wearables and nutrition platforms. The product and design teams had developed a redesigned "Device & App Connection" flow to make it easier for users to centralize their data.

Before committing heavy engineering resources to build the new architecture, the team needed to ensure the redesigned flow actually reduced friction and improved the task success rate compared to the legacy experience.

The Challenge & Thought Process

The goal was tactical but high-impact: evaluate the usability of the new integration flow, identify points of friction, and iterate rapidly before launch. The core questions driving the evaluation were:

  • Can users successfully navigate the new flow to connect a third-party app (e.g., a smart bike or calorie counter) to the central hub?

  • Do users understand the data-sharing permissions they are granting?

  • Where does the mental model of the user break from the system architecture?

Research Approach: Agile Evaluative Sprints

Because this was embedded in an agile design sprint, I needed a mix of depth and speed. I deployed a two-pronged evaluative approach using a mixed-methods toolkit:

1. Moderated Usability Testing (Qualitative Depth)

  • Sample: 8 participants (mix of highly active fitness trackers and casual users).

  • Format: 45-minute remote sessions. Participants interacted with a high-fidelity Figma prototype.

  • Focus: Think-aloud protocol to observe micro-interactions, hesitation, and comprehension of data privacy screens.

2. Unmoderated Task Testing (Quantitative Validation)

  • Sample: 40 participants recruited via a remote testing platform.

  • Format: Task-based testing measuring Time-on-Task and Task Success Rate.

  • Metric: Administered a Single Ease Question (SEQ) after the core integration task to quantify perceived friction.

Key Findings & Usability Gaps

The research quickly validated that while the visual refresh was well-received, the information architecture introduced critical friction.

Finding 1: The "Bi-Directional Sync" Mental Model Mismatch

Users assumed that connecting an app meant data flowed both ways automatically (e.g., the hub sends steps to the calorie app, and the calorie app sends nutrition data to the hub). The prototype only allowed one-way syncing, but the UI did not clearly communicate this limitation.

  • The Verbatim: "I connected my calorie tracker, so why aren't my steps showing up over there? It says 'connected,' they should just talk to each other."

— Casual Runner, 29

  • The Friction: Participants spent an average of 2 minutes clicking around settings trying to "force" the sync to go both ways, resulting in a low SEQ score for the task.

Finding 2: Permission Fatigue Led to "Blind Accepting"

The new flow broke data permissions (Heart Rate, Sleep, Steps) into multiple consecutive screens. While designed by legal for transparency, users exhibited immediate permission fatigue.

  • The Verbatim: "There were like four screens asking for my heart rate, my sleep, my location... I just kept hitting 'Allow' to get it over with, but now I’m actually not sure what I agreed to."

— Daily Walker, 34

  • The Friction: Moderated sessions revealed users were blindly accepting terms to bypass the flow, but later expressed anxiety when asked what data they had shared. It was a failure of trust design.

Finding 3: Hidden Secondary Actions

Once an app was successfully connected, the "Disconnect" or "Manage" button was hidden behind a generic overflow menu (three vertical dots).

  • The Verbatim: "I just wanted to unlink my old smartwatch, but I kept clicking the brand logo and nothing happened. I didn't even see those three little dots at the top."

— Cyclist, 42

  • The Friction: 60% of unmoderated users failed the task "Disconnect the app you just linked" because the interaction pattern didn't match their expectations of where management controls should live.

The Agile Iteration (Working with Design)

Because this was an agile environment, I didn't wait to write a massive report. I facilitated a rapid synthesis session with the lead designer and product manager immediately after the 8th moderated session to lock in changes before handoff.

Iterations Implemented:

  • UI Redesign: Shifted the bi-directional sync toggle into a clear "Read" and "Write" permissions dashboard, aligning the interface with the user's mental model of data flow.

  • Friction Reduction: Consolidated the permission screens into a single, expandable accordion view. This allowed users to "Allow All" easily while keeping granular details accessible without multi-screen fatigue.

  • Visibility: Moved the "Manage/Disconnect" actions out of the overflow menu and placed them as primary ghost buttons on the connected app's detail card.

Impact & Outcomes

  • Task Success Rate: The subsequent round of unmoderated testing on the iterated prototype saw the task success rate for device disconnection jump from 40% to 94%.

  • Saved Engineering Time: By catching the mental model mismatch regarding bi-directional syncing before development, the team avoided shipping a flow that would have resulted in high customer support ticket volumes.

  • Product Alignment: Established a new baseline design system for how data privacy and permissions are presented across the broader ecosystem.

Synthesis: The Core Insight

The primary UX problem is not usability. It is decision confidence under uncertainty.

Advertisers don't optimize for performance alone. They optimize for explainability, defensibility, and internal alignment.

Any product that ignores this will struggle to scale trust regardless of performance.

Implications for Product & UX

This research suggests that effective automated systems should:

  • Treat explainability as a first-class UX concern

  • Surface system logic, not just outcomes

  • Support internal storytelling and reporting needs

  • Reduce organizational risk, not just operational effort

Reframe of success: A system succeeds when users feel confident choosing it again under scrutiny.

Impact & Value

This study:

  • Reframed the problem from "education" to "decision safety"

  • Provided a clear lens for evaluating future product directions

  • Created shared language across product, research, and design teams

  • Informed how automation should be positioned, not just built

Research Reflection: What Made This Study Work

This project reinforced a core research principle:

UX research is not about validating ideas. It is about reducing uncertainty so better decisions can happen.

The most meaningful insights were not about features they were about how people navigate pressure, accountability, and ambiguity. That's where real product decisions live.

The discipline of holding hypotheses internally rather than testing them directly with users created space for unexpected patterns to emerge. The insight about defensibility didn't come from asking "do you feel like you can defend this?" It came from listening to how people described their decision-making process when stakes were high.

bottom of page