Tango
How-to guides that create themselves
TL;DR
Process documentation was slow, inconsistent, and often avoided. I led design for Tango's editing and sharing experience, reframing the product from a simple recorder into a structured, enablement system.
In 5 weeks, guide creation time dropped from ~10 minutes to under 1 minute. The new system shipped to all customers and laid the foundation for team-based knowledge sharing. Product direction emerged through building and testing, not a pre-defined spec.
Problem
Teams with high turnover and repeatable workflows like sales, support, and ops had a documentation problem no one had solved well. Creating a single guide meant taking screenshots at every step, cropping, annotating, and ordering them, writing instructions from scratch, then sharing via Slack or email with no version control or discoverability.
The result wasn't just slow documentation. It was no documentation. Teams avoided it because the cost was too high. New hires ramped on tribal knowledge, and processes drifted without visibility.
Tango had the core insight with its Chrome extension that captured steps automatically. But it felt like a feature, not a product. There was no structure, no sharing model, and no reason to return.
The sprint
Week 1 — Discovery & reframe
Interviewed 5 users across sales, support, and ops. Key insight: people didn't want to document. They wanted documentation to exist as a byproduct of doing the work. This reframed the product.
Weeks 2–3 — Editor and sharing
Designed a lightweight editor and shareable link model. Core constraint: editing couldn't bring back manual effort. Solved with progressive disclosure.
Week 4 — PLG hooks and handoff
Defined the activation moment and upgrade path from individual use to team adoption. Delivered annotated specs and interaction flows for engineering handoff.
What I designed
The north star: Capture → Polish → Share
Before designing screens, I defined the product's core growth model. Tango wasn't a mouse clickrecorder. It was a workflow documentation and automation tool: capture user actions automatically in the background, turn those actions into clear structured steps, then publish as a persistent updatable link — not a file.
This framing clarified the product's job and created a natural growth loop: capture once, share widely, update as the process evolves.
The guide editor — lightweight, not overwhelming
Users needed to fix mistakes and add context without reintroducing manual work. The editor had to feel quick and optional, not like starting over.
Progressive disclosure
By default, guides are clean and read-only. A click enables inline editing. Annotations and highlights are available, but only when a step is selected. Drag-and-drop table of contents allowed for rapid reordering of steps. The persistent version felt like a full document editor. The contextual version kept the sense that the guide was already done and just needed light refinement. That framing helped users move faster.
Safety over speed
Destructive actions like delete and merge are intentionally tucked one level deeper. Accidental edits created outsized frustration in testing, so I prioritized avoiding mistakes over making recovery easy.
Sharing & distribution — from file to living resource
The default solution was a Google Doc with screenshots — static, hard to find, tied to one person's Drive. Tango needed to feel fundamentally different.
Links, not exports
A guide lives at a URL and stays up to date as the process changes. Anyone with the link always sees the latest version. Not export, not download.
Share the love, not the screen
Tango works wherever your team already works. Drop guides right into your favorite docs or how-to tools with simple embeds. The current set of supported tools comes straight from customer discovery, focusing on what most teams already use. It's a practical 80/20 approach that maximizes reach without overbuilding.
PLG foundation — designing the growth loop
Getting a user to create their first guide was essential. The real challenge was turning individual value into team adoption.
The "aha" moment
Activation isn't about creating—it's about sharing. The "aha" moment is when someone else opens your guide for the first time. That shift reframed activation from creating to sharing, not just producing.
Intent-based upgrade
The upgrade moment is when a user tries to share into a workspace they don't belong to. That's the moment to prompt them to upgrade to a paid plan. Contextual and timely, not a cold upsell.
Key decisions & tradeoffs
Speed over customization
Shipped a dedicated edit mode instead of letting users define structure. Editors can generate Tangos for free, but users are encouraged to upgrade to Pro for the full experience. Tradeoff: less customization. Outcome: faster time to value.
Intent-based grouping over click fidelity
Recording every click was accurate but unusable. We grouped actions by intent instead. Tradeoff: less granular detail. Outcome: outputs became clear and usable, not overwhelming.
Individual-first, team-second
Focused on solo value before building team features. Tradeoff: risk of needing to rework for collaboration later. Outcome: faster validation, with a sharing model designed to scale to teams.
Outcomes
Shipped
- Guide editing experience and shareable links to all customers
- PLG upgrade path from individual to team use
Impact
| Creation time | Cut creation time from ~10 minutes to under 1 minute. (90% reduction) |
| Activation | 68% of new users shared a guide in their first session. Value was immediate with no setup or training required. |
| Sharing rate | 43% of guides were shared within 24 hours. Faster creation made sharing a natural next step. |
| Retention | 61% of users who shared a guide returned within 7 days (2x increase) |
I lost count of how many 30-minute how-to meetings I had to set up with people. Death by 30-minute meetings. Now, I can just send a Tango, saving so much time and errors.