Prototype Development Methods

Prototyping is how ideas turn into evidence. It surface hidden assumptions, generate better stakeholder conversations, test specific hypotheses, reveal unforeseen interactions, and give you a concrete artifact to evaluate before code or tooling locks you in. Use low fidelity sketches and storyboards when you need speed and divergent thinking. They help teams externalize ideas, reason about user goals, and map flows before pixels appear. They are deliberately rough to avoid premature polish. Move to click through wireframes in Figma when the question is structure and navigation. Validate information architecture, menu depth, labeling, and path efficiency while changes are still cheap. When the feel of interaction matters, use interactive digital prototypes to evaluate micro interactions, timing, and visual polish. Treat them as validation instruments, not trophies. Plan change criteria up front so attachment to a pretty artifact does not silence real feedback. Some questions require real performance and materials. Coded prototypes and functional hardware mockups tell you about latency, reliability, durability, ergonomics, and safety. In medical devices and other regulated domains, high fidelity functional and contextual testing is expected for Human Factors validation. Not every question lives on screens. Experience prototyping and bodystorming put bodies in space to surface constraints that lab tasks miss. Acting out a shared autonomous ride with props reveals comfort, cue timing, and social norms. Wearing a telehealth mockup for a week exposes stigma, routine friction, and alert patterns that actually fit domestic life. Before building intelligence, simulate it. Wizard of Oz studies let a hidden human drive system responses while participants believe the system is autonomous. You learn vocabulary, trust dynamics, acceptable latency, and recovery strategies without heavy engineering. AI of Oz replaces the human with a large language model so you can study conversational realism early. Manage risks like model bias, hallucinations, and outages with guardrails and logging so findings remain trustworthy. Strategic prototypes also matter. Provotypes and research through design artifacts challenge assumptions, surface values, and force early conversations about privacy, power, and trade offs that slides tend to dodge.

This is how Anthropic decides what to build next—and it's brilliant. Instead of endless spec documents and roadmap debates, the Claude Code team has cracked the code on feature prioritization: prototype first, decide later. Here's their process (shared by Catherine Wu, Product Lead at Anthropic): Step 1: Idea → Prototype Got a feature idea? Skip the spec. Build a working prototype using Claude Code instead. Step 2: Internal Launch Ship that prototype to all Anthropic engineers immediately. No polish required—just functionality. Step 3: Watch & Listen Track usage religiously. Collect feedback actively. Let real behavior, not opinions, guide decisions. Step 4: Data-Driven Prioritization - High usage + positive feedback → roadmap priority - Low engagement or complaints → back to iteration This "prototype-first product shaping" flips traditional product development on its head. Instead of guessing what users want, they're measuring what users actually use. The beauty? They're dogfooding their own tool to build their own tool. The feedback loop is immediate, honest, and impossible to ignore. The takeaway: Your best product decisions come from real user behavior, not theoretical frameworks. Sometimes the fastest way to validate an idea isn't a survey or interview—it's a working prototype.

Are you getting the right insights from your design process? Wireframe ≠ mockup ≠ prototype. And if you're mixing them up... You're not just betraying your lack of design understanding. You're committing an even more insidious mistake: you're not getting the right type of insights. Here's what you need to understand about their different: 1. Frequency of use 2. Core purpose 3. Ideal creator 4. Level of effort 5. Quality of insights — WIREFRAMES Wireframes range from low-fidelity to high, but generally are a step below a mockup. They: 1. Should be used frequently 2. Are great for alignment and early feedback 3. May be created by PMs lo-fi ("sketches"), but otherwise are by designers 4. Are relatively low effort 5. Generate mid insights The reality is: a whole lot happens in between a wireframe and a functioning product. So, using them for evaluative research and calling it a day is a mistake. They are good for "low effort, quick insights." — MOCKUPS Mockups are static designs that show what the product will look like, but without any working interactions. They: 1. Should be used often 2. Are ideal for visual feedback and detailed feedback 3. Should be created by experts in design: designers, not PMs 4. Require more effort than wireframes 5. But generate higher quality insights They're useful for getting stakeholder buy-in on the visual direction, but don't confuse them for the real thing. If you really want to harness the power of evaluative research, you haven't gotten to the promise land yet. They're for "mid effort, mid insights." — PROTOTYPES Prototypes are interactive and can range from simple click-throughs to fully functional. They: 1. Should be used occasionally, for big features 2. Are great for user testing and identifying issues before dev 3. Are created by designers, sometimes also with a developer 4. Require significant effort - both to build and maintain 5. Generate very high quality insights However, jumping into a prototype before a mockup can lead to premature judgments on design elements. They excel in usability testing scenarios, providing invaluable insights into user behavior and preferences. They're for "high effort, awesome insights" — Don't let sloppy terminology derail your design process. Use the right tool at the right time. A lot of design stakeholders misuse these terms at the expense of good product work. It's worth learning when to use what.

I’ve made games for 12+ years. My biggest mistakes? All ideas started with bad prototyping. Here are 5 hard-learned: 1. Prototypes don’t lie. ↳ Your prototype is brutally honest. 2. Don’t wait for perfection. ↳ Learn fast, move on - ugly is fine. 3. No one claps for your design docs. ↳ Let real people play, not your mom. 4. Prototypes boost morale. ↳ Long dev kills vibe, quick fun fuels it 5. Prototyping ≠ polishing. ↳ It’s a sketch, not a sculpture. 💡TIP: Build the smallest playable version of your core loop. → No art. → No polish. → No menus. → Just see if it’s fun. If it isn’t, nothing else matters. 🧱 Example: Want to make a horror roguelike? Just prototype: ↓ One room ↓ One enemy ↓ Basic tension mechanic If the loop isn’t scary now, it won’t be scarier with shaders. Prototype checklist: ✅ Core mechanic is in ✅ It feels something (tension, joy, etc.) ✅ Testers “get” what the game is about ✅ It breaks (but teaches you something) If YES: you’re on track. Prototyping isn't just for mechanics. Try these: → Visual style (Can I sell this mood?) → Control feel (Does jumping feel good?) → Onboarding (Can players figure this out?) All count. PROTOTYPING PITFALLS TO AVOID: ❌ Falling in love with your first idea ❌ Building full art assets too early ❌ Showing only to friends & family ❌ Refusing to cut features 🔥 Final tip: A prototype should answer this: "Should I keep building this?" If the answer is no, that’s not failure. That’s a massive win that saved you months (or years).

Prototypes aren't for testing your product. They're for testing your assumptions. Most teams get this backward, and it costs them weeks of wasted effort and a product nobody wants. A prototype isn't a tiny product; it's a medium for learning. It's a tool designed to ask a specific question and test a core assumption with the right audience. An unintentionally designed prototype is a flawed input, and even with advanced teams and tools, flawed inputs only amplify flaws. The true power of a prototype isn't in its polish, but in the intentional "message" it sends. To unlock this power and truly accelerate collective learning across your organization, you must design with intent: ✺ Low-Fidelity Prototypes: These are for asking foundational, "Does this even solve the right problem?" questions. They signal that everything is up for debate. The intentional message is: "Let's explore the idea, not the pixels." ✺ Medium-Fidelity Prototypes: Use these to test core user flows and information architecture. The intentional message is: "Is this journey intuitive?" By keeping them a little rough, you prevent stakeholders from getting fixated on visual design. ✺ High-Fidelity Prototypes: Reserve these for the final stages to test things like micro-interactions, brand consistency, or subtle emotional responses. The intentional message is: "We're almost there. What are we missing?" This is how you turn prototyping from a simple task into a strategic lever for change and Team Learning. It ensures your team isn't just building things, but is learning together and making better decisions about what to build and why. It's how you break down silos and create a "Holding Environment" for generative dialogue. What's a time you intentionally used a low-fidelity prototype to prevent a high-stakes meeting from spiraling? Let’s discuss in the comments below. #ProductDesign #SystemsThinking #StrategicDesign #UXStrategy #DesignLeadership #ComplexSystems #TeamLearning #Prototyping #OrganizationalDesign #Innovation

𝐖𝐞 𝐬𝐭𝐨𝐩𝐩𝐞𝐝 𝐰𝐫𝐢𝐭𝐢𝐧𝐠 20-𝐩𝐚𝐠𝐞 𝐏𝐑𝐃𝐬. Now we build prototypes instead — and it’s completely changed how Databricks PMs align on solutions. A product manager’s job is still the same at its core — identify a problem that, if solved, drives adoption or revenue. But what we’ve learned is this: aligning on the problem isn’t the hardest part. Aligning on the solution is. Traditionally, this meant messy slides, slow UX cycles, and static mockups. PMs would test ideas with customers using decks or clickable Figma files that took days (or weeks) to build. Each round of feedback felt like a mini product cycle. With 𝐯𝐢𝐛𝐞 𝐜𝐨𝐝𝐢𝐧𝐠, we’ve flipped that. We now prototype directly to test and iterate live with customers. When customers can use something, not just look at it, the insights are richer, and we can see where expectations diverge from design. We tweak the prototypes between user interviews, learning faster than ever before. Before GenAI, PRDs were 20+ pages long and few people read them. Now we skip them entirely. PMs replace written specs with working prototypes and run “prototype reviews” instead of doc reviews. We’ve even developed a Plan/Build workflow, inspired by Claude Code: 🧠 𝐏𝐥𝐚𝐧 𝐌𝐨𝐝𝐞: use an AI assistant to reason through the design — feeding it jobs-to-be-done, API specs/information architectures, and refining until the assistant truly “gets it.” ( 💡 Pro tip: many on our team use Wispr Flow for voice-to-text — it makes iterating on ideas faster and more natural than typing) ⚡️ 𝐁𝐮𝐢𝐥𝐝 𝐌𝐨𝐝𝐞: prompt your AI assistant to generate *page-by-page* UI prompts for your vibe code tool of choice, switching between modes until the design feels right. Incremental building by page is key here! Most of our prototypes today are UI-only (no backend), but they’re powerful enough to test flows, get real feedback, and lock in what the MVP should be. ➡️ Our next step: connecting to real data — turning prototypes into Databricks Apps customers can actually use. We joke that “no engineers were harmed in the making of this prototype” — but the impact is real. We’re moving from writing about ideas to feeling them. 👋 Would love to hear how other teams are replacing PRDs with prototypes in the comments.

What’s the difference? Problem Framing vs. Foundation Sprint vs. Design Sprint. Before discussing differences, let’s talk about the one thing they have in common—and why every team should use these methods. They break the norm of work as usual: 🚫 Siloed teams 🚫 Endless meetings with no decisions 🚫 Juggling multiple priorities but making little progress Work as usual keeps us busy. It’s soul sucking. Instead, these methods are about bursts of work that give teams intense focus to tackle one important goal collaboratively. But…when do you use which one? 🎯Problem Framing When to use it: ✅ When dealing with complex problems ✅ When uncovering root causes before jumping to solutions ✅ When you need leadership buy-in for high-stakes decisions Format: 1-day workshop (with heavy pre-work) Level: strategic Who’s involved: Leadership, senior stakeholders (6-8 people) Difficulty: Hard – requires deep preparation and skilled facilitation Key Inputs: Customer insights, data, business goals Key Output: A validated problem statement or opportunity ❓Foundation Sprint When to use it: ✅ When you have a general solution approach but need to refine it ✅ When exploring alternative strategies before committing ✅ When you want to align a team quickly Format: 2-day workshop Level: both strategic & tactical Who’s involved: Founders & leadership (startups) / Decision-makers & SMEs (enterprises) Difficulty: Medium – no pre-work required, but deep thinking needed Key Inputs: Team knowledge, expertise, and insights Key Output: A hypothesis that needs testing 🚀Design Sprint When to use it: ✅ When the problem is well-defined ✅ When you need to rapidly test solutions with real users ✅ When you want quick validation before building Format: 4-day workshop Level: tactical/operational Who’s involved: Cross-functional team, SMEs (7-10 people) Difficulty: Easy but intense work – clear steps, structured process Key Inputs: Validated problem statement (from Problem Framing) OR Founding Hypothesis (from Foundation Sprint) Key Output: A customer-tested prototype Which One Should You Use? 👉 If the problem is unclear or complex, start with Problem Framing—especially in enterprises where stakes are high and risk is a major concern. 👉 If you feel confident about a solution but want to test different angles, use a Foundation Sprint to challenge your assumptions and align the team. 👉 Once you’re ready to validate a solution with real users, the Design Sprint helps you quickly test and refine before investing in execution. TL;DR: Problem Framing → Foundation Sprint → Design Sprint. Each plays a different role, but together, they create a structured system for solving problems and validating solutions efficiently. More importantly, they help people work together and actually enjoy it.

20 years of building software taught me this: 1 killer prototype > 10 PowerPoints. Everyone talks about validating ideas. Nobody explains how to prototype fast without burning a week. Here’s the simplest way to build a prototype without burning a sprint: 1. Map the core flow Not the whole product. Just the path from “start” → “success.” Most teams overbuild here and drown. 2. Wire real behavior Fake buttons and placeholder data hide the problems. Move real data. Trigger real state changes. 3. Run the flow like a user Click every button. Fill every field. Refresh the page. Try to break it. This is where the real requirements show up. 4. Fix the first 5 issues You’re building direction, not perfection. A prototype only needs to work once end-to-end. 5. Put it in front of someone Stakeholders. Users. Your team. A working flow sparks better decisions than any deck. And here’s where Anything Max came in handy: Instead of wiring everything myself, I described the flow, and Max built the UI, the routes, the logic, the DB model, the emails, and the tests. Then it did the part nobody wants to do: - Opened the app in a real browser - Logged in - Clicked through the flow - Found what broke - Fixed it - Ran it again If you want faster validation without blowing up your roadmap, use tools that help you prototype, not plan. I put together a guide on building a working prototype using Anything. Comment "Anything" and I'll send it over.

For founders, building a successful product is often less about the idea and more about the process. Knowing when to use a Proof of Concept (PoC), Prototype, or Minimum Viable Product (MVP) can be the difference between scaling up or burning out. 🌱 Proof of Concept (PoC): Testing “Possible” vs. “Impossible” Insight: PoC is about finding limits, not solutions. It’s the stage to test if your concept is even technologically achievable with current resources. This stage isn’t about showing off or impressing; it’s about brutally honest assessments. It’s where you ask, “Are we chasing something we can’t feasibly build?” Use it when: You’re unsure if a novel tech component will work in practice. Example: Is the AI algorithm actually capable of processing data at this scale? Founder's takeaway: Don’t fall in love with the concept just because it’s new. PoC is where you might need to abandon the idea early, saving resources and learning key constraints. 🎨 Prototype: Bringing Ideas to Life, Not to Market Insight: The Prototype phase isn’t about building a working product; it’s about exploring user interactions and design flow. A good prototype reveals what’s broken in the user journey before you commit resources to coding and development. You’re here to answer, “Is this something people will want to use? Is the experience intuitive?” Use it when: You need a vision, not a finished product. Example: How will users navigate the app? Does the layout make sense? Founder's takeaway: Prototyping forces you to confront your assumptions about user behavior and design. A great idea with poor UX is doomed, so listen to feedback carefully and iterate. 🚀 Minimum Viable Product (MVP): Testing If People Actually Care Insight: MVPs are not meant to be “perfect”—they’re meant to be functional enough to test market need. The MVP is your experiment in real-world conditions. The goal isn’t to sell the product but to learn what will make it sell. This is where startups often discover whether they’re solving a problem worth paying for or just building something “cool.” Use it when: You have a clear problem you’re solving and need to validate that users care enough to engage (and hopefully, pay). Founder's takeaway: An MVP is not your “launch” but a learning opportunity. Don’t be afraid to fail or pivot based on real-world feedback—it’s cheaper and easier than overbuilding a product people don’t want. 🔍 Key Takeaway: Not Every Stage Is Necessary Founders often assume they need to go through all three stages, but the reality is that many products don’t need a PoC, and some products might skip a Prototype if the MVP serves that purpose. Final Thought: Think of PoC, Prototype, and MVP as tools for falsifying assumptions. Each stage should help you eliminate uncertainties before moving to the next. #startups #productdevelopment #founderinsights #innovation

7 prototyping rules I wish someone told me earlier. (would've saved me months) 1. Ugly is fine ↳ You're testing the idea, not the aesthetics. 2. Speed beats polish ↳ A prototype in 3 hours > a mockup in 3 weeks. 3. Real users, not teammates ↳ Your team already knows too much. 4. One question per prototype ↳ "Does this solve the problem?" That's it. 5. Kill bad ideas early ↳ A failed prototype costs you a day. A failed product costs you a year. 6. Don't fall in love with version 1 ↳ The first prototype is a conversation starter. Not the final answer. 7. Prototype the riskiest part first ↳ Start where you're least certain. Prototyping isn't a step you "skip." It's the step that saves everything after it. Happy building ✌️ P.S. Which rule above hits hardest for you? (1-7)