Who actually uses these products,
and what made them stay.

The Framer Interactive Designer

A product designer or creative developer who uses Framer for either high-fidelity interactive prototypes or production marketing sites — often both. They came from Figma and knew it wasn't built for interaction. They came from Webflow and wanted more design control. Framer sits between those two worlds and they've made it home. They are comfortable with the code escape hatch. They don't use it unless they have to. When they have to, they can.

“The shift was quiet.”

The Framer Motion Designer

A product designer or motion designer who gravitates toward Framer because it treats animation and interaction as first-class design elements. They don't just design screens — they design how screens transition, how elements respond to hover, how content enters and exits. They've used Figma for static design but find it limiting when the design's value is in how it moves. They are the person who insists that the ease curve matters and that a 200ms delay feels different from a 300ms delay.

“A teammate asked how they managed design and prototype complex animations and transitions that developers would struggle to implement from specs.”

The Whimsical Product Thinker

A product manager, designer, or architect who uses Whimsical when they need to think visually but don't need pixel-perfect precision. They create flowcharts to map user journeys, wireframes to sketch interfaces, and mind maps to explore problem spaces — all in the time it would take to set up an artboard in Figma. They value speed over fidelity. They are the person who brings a Whimsical link to a meeting and says "here's what I'm thinking" before anyone else has a concrete proposal.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about there's a ceiling — when wireframes need more detail, the transition to Figma requires starting over in two weeks.”

The Whimsical Fast Diagrammer

A product manager, designer, or engineer who uses Whimsical for the work that happens before the work — user flows, information architecture diagrams, quick wireframes, system diagrams. They chose Whimsical over Figma for this because Figma requires too much setup for a sketch. They chose it over Miro because they need structure, not freeform. They chose it over Lucidchart because Lucidchart is too heavy for what they're doing. Whimsical is the tool for the thinking phase. It is rarely the final deliverable. It is always the thinking that produces the final deliverable.

“A teammate asked how they managed get a flow or wireframe out of their head and onto a shareable canvas in under 15 minutes.”

The FigJam Product Team Facilitator

A product manager, design lead, or team facilitator at a product company who uses FigJam for team whiteboarding because their team already lives in Figma. They chose FigJam over Miro because the context switch is lower — design references, wireframes, and working files can be linked or embedded directly from Figma. They run planning sessions, retrospectives, decision workshops, and design crits on FigJam. Their team knows how to use it. This matters more than they expected it to.

“The shift was quiet.”

The Todoist GTD Practitioner

A knowledge worker — often a project manager, consultant, writer, or developer — who has read productivity books and tried multiple task managers before settling on Todoist. They've built a system. It works when they use it. The failure mode is not the tool — it's consistency. They believe in GTD or a GTD-adjacent framework. They have projects, labels, and filters set up in a way that feels logical to them and would confuse anyone else. They've rebuilt the system twice.

“It's Sunday evening.”

The Figma Product Designer

A mid-to-senior product designer at a tech company with 3–8 years of experience. Figma is where they spend most of their working day — from rough explorations to polished specs. They work across a shared team library and collaborate with PMs in comments and engineers in dev mode. They are fast, opinionated about component architecture, and quietly frustrated by how the tools around Figma still slow everything down.

“A teammate asked how they managed move from concept to spec without losing fidelity at each stage.”

The Runway AI Video Editor

A video editor, creative director, or content producer who has integrated Runway into their professional workflow — not as a novelty, but as a production tool that changes what's achievable in a given timeline and budget. They use Runway for AI video generation, background removal, inpainting, motion tracking, and generative effects that would require a VFX team or days of Premiere work otherwise. They have a traditional video editing background. They understand the craft. They are not using Runway to replace craft — they're using it to expand what they can produce without expanding the team or the deadline.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about consistency across generated clips — maintaining visual coherence between in two weeks.”

The Toggl Self-Tracker

A freelancer, consultant, or productivity-conscious knowledge worker who tracks time for one of two reasons: they bill by the hour and accuracy is revenue, or they've realized they have no idea where their hours go and they want to find out. Both types start Toggl for practical reasons and discover something unexpected — tracked time is honest in a way that memory and intention are not. They've had the experience of thinking they spent 4 hours on a project and the timer saying 2.2. They've also had the reverse. Both were useful information.

“It happened mid-workflow — they're a UX consultant.”

The Roam Research Networked Thinker

A writer, researcher, or knowledge worker who uses Roam Research as an extension of their thinking. They don't organize notes into folders — they write, link, and let the graph reveal connections. They use daily notes as their entry point, double-bracket references to build a web of ideas, and block references to connect thoughts across pages. They've read about Zettelkasten, spaced repetition, and evergreen notes. They've adopted some of these ideas and adapted others. They are building a thinking system, not a filing system.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about performance degrades with large graphs — search and page loads slow down over time in two weeks.”