Ryan Stephen - Creativity, Storytelling, and Prototyping Playful Ideas

2026-02-12 - 40 min - source - Read full transcript

Red (host)Ryan Stephen

Key insights

The tool and the idea inform each other in a two-way street, not a one-way pipeline from concept to execution.

Ryan describes starting a Vision Pro spatial-desktop idea with grander ambitions (windows flying in, etc.) but stopping once the physics of flinging Blender objects felt complete - the tool told him the idea was already done. He generalizes: working with a tool and letting it inform you gets you to 'finished' faster than expected, and code-based design exploration surfaces unplanned directions the same way.

tools-shaping-ideas

Effort fidelity, not visual fidelity, is what should signal how seriously to take a prototype.

Because AI tools have broken the old correlation between polish and time invested (a single good prompt can now produce something highly polished), Ryan judges his prototypes by how much time/effort went in (a day, a weekend, a week) rather than how smoothly the rectangles animate. This lets him decide when an idea deserves more investment independent of how slick it looks.

prototyping-fidelity

Keeping prototype fidelity artificially low to get 'alignment' before details creates a false sense of agreement that breaks later.

Ryan pushes back on the common design advice to stay low-fidelity as long as possible to avoid bad feedback on details. He argues people nod along with vague high-level concepts, then react badly once real details appear ('that wasn't what I had in my head'), so deferring fidelity just defers the real disagreement - and a slicker prototype earlier gets sharper, more specific feedback sooner.

prototyping-fidelity

Designers should ask which specific dimension of an idea needs to feel real, not assume everything does.

Ryan frames prototyping as choosing which axis to push toward realism: visuals, gesture/interaction, information architecture, or sometimes just the literal language on screen. Identifying the one dimension that actually needs to convince people lets him invest effort precisely instead of over-building the whole prototype.

prototyping-fidelity

A rolling, tool-agnostic note of outlandish ideas is the raw material; the tool and shape get decided later.

Ryan keeps a single running phone note of thousands of small, deliberately silly ideas (a mail app shaped like a hot air balloon, notifications as desk-scattered speech bubbles) captured without regard for feasibility or medium. He works backward from idea to tool, and treats scoping down to an MVP as valid for work projects but not for this personal capture practice.

idea-capture-and-ideation

Running Crazy Eights backwards turns a convergence tool into a generative one.

The standard Crazy Eights method (8 sketches in 8 minutes) is normally used after research has identified a problem, to converge on a solution - and most sketches get thrown away. Ryan instead uses the timer format to sketch on open prompts pulled from daily life (something seen at a gas station, a Twitter post), using the time pressure to force fast, exaggerated pulls from everyday experience rather than to filter down to one answer.

idea-capture-and-ideation

Publicly sharing playful, low-stakes work has an asymmetric payoff: the downside is silence, not shame.

Ryan and the host both argue the real floor of posting creative work online is 'nothing happens' (crickets), not public failure - so the risk is much lower than people assume, while the upside (feedback, friendships, mentors, career visibility) is close to uncapped. Even a failed post still means you made something and have a starting point to iterate from.

visibility-as-career-currency

Visibility functions as a form of currency that beats a static portfolio because it reaches people unprompted.

Ryan contrasts a portfolio website, which people must actively seek out, with sharing work on Twitter/X, which puts a playful idea in front of people passively at any moment (e.g. 7am on a Tuesday). He treats consistent public sharing as a more powerful career mechanism than a polished but passive portfolio.

visibility-as-career-currency

Design leaders increasingly weight personal experiments and side projects heavily when evaluating hiring candidates.

Ryan and the host observe that portfolio experiments without business impact or stakeholder framing are becoming a much bigger differentiator than in the past, because the constraints of new AI tools are unclear to most people and a compelling one-day project signals both craft and initiative in a way traditional case studies don't.

visibility-as-career-currency

Visibility works internally within a company the same way it works on public social platforms.

Ryan describes viewing organizations as internal social networks: a well-told short async video or screen recording of an idea can 'go viral' inside a company the same way a tweet does externally, and this internal storytelling skill is increasingly valuable as teams work asynchronously across global time zones.

visibility-as-career-currency

Storytelling has to be tailored to the audience: designers on a team need different framing than leadership.

Ryan's biggest growth area over several years of practice has been learning to shape a story differently depending on who's receiving it - iterative bite-sized posts for an online audience, versus prototypes that let a non-technical leader evaluate a concept directly instead of sitting through ten slides of context-setting.

storytelling-for-different-audiences

Time-boxing side experiments to a day or two removes the pressure that kills unfinished side projects.

Ryan attributes his consistent output partly to strict time-boxing: framing a project as 'a day or two' rather than open-ended removes the anxiety of a month-long commitment, which he identifies as the reason many side projects stall out unfinished.

idea-capture-and-ideation

Books referenced

Shape Up - Basecamp - Host asks if Ryan's Sharpie-only, uneraseable sketching technique comes from the 'fat marker sketches' concept in Shape Up, which forces low fidelity by constraining the tool.

Media referenced

Venn - other - A collaborative prototype (with Chandler Simon under the duo 'Super Random') letting users scroll Venn-diagram-style modifiers to blend an AI image generation prompt; cited as an example of an idea real enough to let people interact with it directly rather than just watch a video.

Companies

Microsoft - Ryan's day job as a designer; his spatial/prototyping experiments have almost no direct overlap with this work.
Mobbin - Sponsor; design inspiration and animation reference library, plugged mid-episode for its new animations feature.
Paper - Sponsor; a design tool where layouts are real CSS so shader/halftone effects can be one-click copied as React into a coding agent.
Inflight - Sponsor (host's own product); an async feedback tool for design teams, opened to Dive Club listeners.
Framer - Part of Ryan's closing product stack; how he builds websites.
Genway - Part of Ryan's closing product stack; how he does research.
Granola - Part of Ryan's closing product stack; how he takes notes during design crit.
Jitter - Part of Ryan's closing product stack; how he animates designs.
Lovable - Part of Ryan's closing product stack; how he builds ideas in code.
Raycast - Part of Ryan's closing product stack; a shortcut tool he uses at every step.
Claude Code / GitHub Copilot - Coding agents Ryan switches between when vibe-coding prototype tools, e.g. the Swift/Xcode tool that let him scrub playback speed on the 'crank' prototype's rendered frames.

Techniques and frameworks

Crazy Eights (reversed) - Standard UX ideation method (sketch 8 ideas in 8 minutes) that Ryan runs backwards for personal practice: instead of generative research into a defined problem, he sketches on outlandish prompts pulled from everyday life (something funny seen at a gas station, a metaphor) to generate raw material rather than to converge on a solution.
Rotoscoping - Film VFX technique Ryan uses in After Effects to composite people on top of placed scene elements, e.g. making a compass overlay feel physically present in a park video.
Effort fidelity over visual fidelity - Ryan's reframing of prototype fidelity: what should read as 'real' is how much effort/time went in (a day, a weekend, a week), not how polished the pixels look, since AI tools have broken the old correlation between visual polish and time spent.
Rolling idea note - A single running phone text note with thousands of small, deliberately outlandish, tool-agnostic ideas (e.g. 'what if your mail app was a hot air balloon'); Ryan works backward from the idea to the tool/medium later rather than starting from a tool.

Summary

Dive Club host Red talks with Ryan Stephen, a Microsoft designer known for a stream of spatial, film-inspired, and AI-assisted design experiments he posts on Twitter/X. The conversation walks through several of his projects - a rotoscoped After Effects compass overlay, a Vision Pro "spatial desktop" where folders physically fling around a room, a hand-shader city map, a crank-controlled music player prototyped through Figma sketches and a custom Swift/Xcode playback tool, and Venn, a collaborative AI image-blending tool built with Chandler Simon under the name Super Random. Across all of them Ryan describes a consistent working style: start from the loosest possible idea, reach for whatever tool gets him to a convincing version fastest (After Effects, Blender, a shader, Figma, a vibe-coded Swift app), and stop as soon as the idea "feels real," even if that's much sooner than originally imagined.

A recurring thread is that the tool and the idea shape each other in both directions - Ryan calls it a two-way street where sketching an ambitious concept and then discovering what a given tool can actually do often reveals that the idea is finished earlier than planned. He keeps a running phone note of thousands of small, deliberately outlandish, tool-agnostic ideas (a mail app shaped like a hot air balloon, notifications scattered like desk sticky notes) and works backward from idea to medium later. For structured ideation he runs the classic "Crazy Eights" method backwards: instead of using the eight-minute sketch sprint to converge on a solution after research, he uses the time pressure to generate raw material from everyday observations, sketched only in Sharpie so he can't erase or over-refine.

The middle of the conversation turns to prototype fidelity. Ryan argues for judging prototypes by "effort fidelity" rather than visual polish, since AI tools have broken the old assumption that visual quality correlates with time invested - a single strong prompt can now look highly finished. He also pushes back on the common design-team advice to keep fidelity low for as long as possible to preserve alignment: in his experience, people nod along agreeably with vague high-level pitches and then react badly once real details appear, so deferring fidelity just delays the actual disagreement rather than avoiding it. He frames the designer's real job as identifying which specific dimension of an idea needs to feel real - visuals, gesture, information architecture, or sometimes just the literal copy on screen - rather than assuming everything needs equal realism.

The back half covers career and visibility. Ryan and Red agree that publicly sharing playful, unpolished work carries an asymmetric payoff: the realistic downside is silence, not public failure, while the upside includes feedback, friendships, mentors, and career opportunities. Ryan treats ongoing public sharing as a more powerful mechanism than a static portfolio because it reaches people unprompted, and notes that hiring managers increasingly weight compelling personal experiments heavily, even without business-impact framing, because they signal skill and initiative that traditional case studies don't. He extends the same "visibility as currency" idea inward, describing companies as internal social networks where a short, well-told async video can spread the way a tweet does, which he sees as increasingly valuable given asynchronous, global team collaboration.

Closing out, Ryan reflects that his biggest growth as a storyteller has been learning to tailor a story's fidelity and format to its audience - iterative bite-sized posts for an online crowd versus a hands-on prototype that lets a non-technical leader evaluate an idea directly rather than sit through a slide deck of context. He says he's most excited going forward about treating AI itself as a playful material to prototype with, continuing to zigzag between serious, structured product work and unstructured creative experimentation.

Notable Quotes

"The tool is informing the ideas as much as the idea is informing what tool I use. It's like a two-way street." - Ryan Stephen

"I think the best case scenario for using more tools is not getting overwhelmed by them - using them to drive your decision." - Ryan Stephen

"The worst case scenario is nothing happens. And it's actually so important to recognize... the floor is that it's just crickets and people don't really care. So you have almost uncapped upside with a pretty safe floor." - Red

"What I like to think about is effort fidelity more than visual fidelity. If I can make something in a day or a weekend or a week, that fidelity is what matters, not necessarily how awesome the rectangles move around the screen." - Ryan Stephen

"As designers, we have a role of: if we're making ideas feel real, what aspect of the idea needs to feel real? Do the visuals need to feel real? Does this gesture need to feel real? Does this information architecture need to feel real? Maybe the only thing that needs to be real is the language you're using on the screen." - Ryan Stephen