home / skills / coowoolf / insighthunt-skills / marginal-user-framework

marginal-user-framework skill

This skill helps identify high-leverage improvements by analyzing the worst-case user to unlock growth for everyone.

npx playbooks add skill coowoolf/insighthunt-skills --skill marginal-user-framework

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

3.5 KB

---
name: marginal-user-framework
description: Use when facing conversion plateaus, expanding to new markets, or when aggregate data fails to reveal growth bottlenecks, to identify high-leverage improvements by focusing on worst-case users
---

# Marginal User Framework

## Overview

A method for identifying high-leverage product improvements by focusing on the user **"on the cusp"** of conversion or the **"worst-case scenario"** user. Solving for the user with the most friction often resolves hidden issues for everyone.

**Core principle:** If you solve for the hardest user, you unlock growth for everyone.

## When to Use

- High traffic but low conversion
- Expanding into new international markets
- Data funnels not revealing friction points
- Growth has plateaued unexpectedly

## The Five-Step Process

```
┌─────────────────────────────────────────────────────────────────┐
│  1. IDENTIFY      →  Find "Worst Case" User                    │
│                      (bad device, slow network, language gap)  │
├─────────────────────────────────────────────────────────────────┤
│  2. OBSERVE       →  Watch them try to use it (qualitative)    │
│                      Don't rely solely on analytics            │
├─────────────────────────────────────────────────────────────────┤
│  3. INVENTORY     →  List ALL friction points encountered      │
│                      (latency, language, UI complexity)        │
├─────────────────────────────────────────────────────────────────┤
│  4. FILTER        →  Which fixes help the "marginal" user?     │
│                      (next-most-likely to convert)             │
├─────────────────────────────────────────────────────────────────┤
│  5. EXECUTE       →  Remove barriers for many by solving       │
│                      for the few                               │
└─────────────────────────────────────────────────────────────────┘
```

## Quick Reference

| Worst-Case Dimension | What to Look For |
|---------------------|------------------|
| Device | Feature phones, low RAM |
| Network | 2G/Edge, high latency |
| Language | Non-primary language users |
| Tech Literacy | First-time smartphone users |
| Accessibility | Vision/motor impairments |

## Common Mistakes

- **Only using analytics** → Observe users qualitatively
- **Optimizing for average** → The "average" user doesn't reveal bottlenecks
- **Ignoring edge cases** → Edge cases are the growth lever

## Real-World Example

At Facebook, Adriel Frederick analyzed users on feature phones with Edge connections. He discovered the issues were language barriers and latency. Fixing latency for the "worst case" improved speed for the entire user base.

---

*Source: Adriel Frederick (Reddit, Lyft, Facebook) via Lenny's Podcast*

Overview

This skill applies the Marginal User Framework to find high-leverage product improvements by solving for the most frictional or "on the cusp" users. The core idea: remove barriers for the worst-case users and you often unlock improvements for the entire base. Use it when aggregate metrics hide conversion blockers or when growth has stalled.

How this skill works

The skill guides you to identify a marginal or worst-case user (poor device, slow network, language gap), observe them attempting key tasks, and inventory every friction point they hit. It then filters potential fixes for their impact on that marginal user and prioritizes execution on changes that remove systemic barriers. The result is targeted work that benefits both edge and mainstream users.

When to use it

You have high traffic but low conversion or completion rates
Growth has plateaued without clear funnel explanations
Launching or expanding into new international or low-connectivity markets
Aggregate analytics fail to reveal friction points
You suspect UI or performance issues disproportionately affect some users

Best practices

Recruit real marginal users for qualitative observation rather than relying only on analytics
Document every friction point—latency, language, UI steps, accessibility issues
Prioritize fixes that directly help the marginal user and are likely to improve overall performance
Test fixes with similar worst-case profiles before broad rollout
Combine quantitative funnels with targeted qualitative sessions to validate impact

Example use cases

Improve signup and onboarding in countries with 2G/Edge networks by optimizing payloads and language support
Increase conversions by simplifying checkout for users on low-memory devices
Diagnose why a feature underperforms by watching first-time or low-tech users complete the task
Reduce support volume by fixing an accessibility barrier discovered when observing screen-reader users
Expand into a new market by solving the top three friction points for non-primary-language users

FAQ

How do I find a true marginal user?

Look for users at the lowest-performing segments: old/low-RAM devices, slow networks, non-primary languages, first-time smartphone users, or those using assistive tech. Field recruitment, customer support logs, and social channels help locate candidates.

Won’t optimizing for edge cases waste resources?

Not if you target the marginal user whose problems are structural. Fixes like reducing latency, simplifying flows, or adding language fallbacks often benefit many users, turning focused work into broad wins.