Workflow-Tracing Product Expansion

This framework shifts the focus from "Total Addressable Market (TAM) chasing" to "Workflow Completion." Instead of building what looks biggest on paper, you build what naturally comes before or after your core product in the user’s daily life. This ensures high retention and a seamless ecosystem.

The Workflow Tracing Process

1. Identify "Adjacency Hacks"

Observe how users are misusing your core product. Look for patterns where users are forcing your tool to do something it wasn't built for.

• Identify the friction: Where is the UI becoming "clunky" because of these hacks?
• Quantify the behavior: Is this a niche use case or a widespread workaround?
• Figma Example: Users were using Figma Design for brainstorming and presentations, even though the tool was optimized for high-fidelity vectors.

2. Map the "Idea-to-Product" Journey

Trace the entire lifecycle of a project in your domain. Identify every stage a user goes through and mark where your company is currently absent.

• Ideation/Brainstorming (FigJam)
• Presentation/Pitching (Figma Slides)
• High-Fidelity Design (Figma Design)
• Developer Handoff/Implementation (Dev Mode / Dev Mode MCP)
• Publishing/Shipping (Figma Sites)