Prototyping and Iterative Testing

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.

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).

𝗙𝗼𝗰𝘂𝘀. 𝗕𝘂𝗶𝗹𝗱. 𝗥𝗲𝗽𝗲𝗮𝘁. That’s not just a tagline. It’s the rhythm that has shaped every product I’ve ever created. From building custom FDM 3D printers with 1-meter build volumes… To deploying digital cinema software for studios across India… To developing CPR innovations that may one day save lives… I’ve come to realize: Most people overestimate ideation and underestimate execution.  • Ideas are easy.  • Building is hard.  • Building again—after feedback, after failure, after fatigue—is what defines product people. Here’s how I’ve applied this mantra: 🔹 𝗙𝗼𝗰𝘂𝘀: Deep dive into the problem. Cut the noise. Understand the user. 𝗙𝗢𝗖𝗨𝗦 — 𝗧𝗵𝗲 𝗣𝗼𝘄𝗲𝗿 𝗼𝗳 𝗦𝗲𝗹𝗲𝗰𝘁𝗶𝘃𝗲 𝗔𝘁𝘁𝗲𝗻𝘁𝗶𝗼𝗻 𝗖𝘂𝘁 𝘁𝗵𝗲 𝗰𝗹𝘂𝘁𝘁𝗲𝗿: Remove tasks that don’t align with your core goal this week/month. 𝗧𝗶𝗺𝗲-𝗯𝗼𝘅 𝘆𝗼𝘂𝗿 𝗱𝗮𝘆: 2–3 deep work sessions > 10 scattered hours. 𝗧𝗿𝗮𝗶𝗻 𝘆𝗼𝘂𝗿 𝗺𝗶𝗻𝗱: Mindfulness, journaling, and even a short walk can reset your focus. 𝗦𝗮𝘆 𝗡𝗢 𝗼𝗳𝘁𝗲𝗻: Every yes is a cost. Guard your attention. 🔹 𝗕𝘂𝗶𝗹𝗱: Don’t wait for perfect. Get a working version. Test it. Break it. Rebuild. 𝗕𝗨𝗜𝗟𝗗 — 𝗗𝗼𝗻’𝘁 𝗝𝘂𝘀𝘁 𝗧𝗵𝗶𝗻𝗸, 𝗗𝗼 𝗦𝘁𝗮𝗿𝘁 𝗺𝗲𝘀𝘀𝘆: Don’t wait for the perfect version. V1 is always ugly, but it works. 𝗕𝘂𝗶𝗹𝗱 𝗶𝗻 𝗯𝗹𝗼𝗰𝗸𝘀: Work in weekly deliverables or prototypes you can test. 𝗧𝗲𝘀𝘁 𝘄𝗶𝘁𝗵 𝗿𝗲𝗮𝗹𝗶𝘁𝘆: Launch small, fail fast, learn faster. 𝗨𝘀𝗲 𝘁𝗼𝗼𝗹𝘀 𝘀𝗺𝗮𝗿𝘁𝗹𝘆: Automate where possible. Don’t waste energy reinventing the wheel. 🔹 𝗥𝗲𝗽𝗲𝗮𝘁: What worked yesterday won’t work tomorrow. Evolve fast, or become obsolete. 𝗥𝗘𝗣𝗘𝗔𝗧 — 𝗕𝘂𝗶𝗹𝗱 𝗠𝗼𝗺𝗲𝗻𝘁𝘂𝗺, 𝗡𝗼𝘁 𝗝𝘂𝘀𝘁 𝗠𝗼𝗺𝗲𝗻𝘁𝘀 𝗪𝗲𝗲𝗸𝗹𝘆 𝗿𝗲𝘃𝗶𝗲𝘄𝘀: Ask, “What did I build this week?” Not just what you did. 𝗜𝘁𝗲𝗿𝗮𝘁𝗲, 𝗱𝗼𝗻’𝘁 𝗽𝗶𝘃𝗼𝘁 𝗿𝗮𝗻𝗱𝗼𝗺𝗹𝘆: Improve with intention. Don’t abandon too early. 𝗕𝗿𝗶𝗰𝗸 𝗯𝘆 𝗯𝗿𝗶𝗰𝗸: Small improvements compound into big outcomes. 𝗥𝗲𝘀𝗽𝗲𝗰𝘁 𝗯𝗼𝗿𝗲𝗱𝗼𝗺: Repetition creates mastery. It’s okay if it’s not always thrilling. If you’re working on a new product, startup, or even a creative project—just remember: 🚫 Don’t chase motivation. ✅ Build systems. ✅ Track progress. ✅ Stick to your loop. Focus. Build. Repeat. That’s how breakthroughs are born. #PingnaganPranavam #ProductDevelopment #StartupJourney #MakersMindset #ExecutionOverIdeas #FocusBuildRepeat #PPWrites #builtbypp

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.

Some of you disagreed with my last post. Fair. Let's talk. Let me explain the topic a bit more and give you a deep dive into how I see the new process. The old way: Think → Research → Wireframe → Design → Spec → Hand off → Build → Test → Iterate Weeks. Sometimes months. Before anyone touches real code. The new way: 👉 Step 1: Start with a problem, not a doc. I don't need a full PRD. I need one thing. Example: "𝘗𝘦𝘰𝘱𝘭𝘦 𝘴𝘵𝘳𝘶𝘨𝘨𝘭𝘦 𝘵𝘰 𝘨𝘦𝘵 𝘩𝘰𝘯𝘦𝘴𝘵 𝘧𝘦𝘦𝘥𝘣𝘢𝘤𝘬 𝘰𝘯 𝘵𝘩𝘦𝘪𝘳 𝘱𝘰𝘳𝘵𝘧𝘰𝘭𝘪𝘰." That's it. That's the brief. 👉 Step 2: Build the ugliest working version. I open Lovable or Cursor and prompt my way to a prototype. Not a mockup. Not a Figma file. A real, clickable, functional thing. 30 minutes. Maybe an hour. 👉 Step 3: Use it. Don't refine it. Don't show it to anyone yet. Use it yourself like a real user would. Click every button. Try to break it. Feel where it's awkward. 👉 Step 4: Now design. This is where design skill actually matters. You're not guessing what the experience should feel like. You already know because you felt it. Now you fix what's broken, remove what's unnecessary, and polish what works. Maybe pivot or try other solutions. 👉 Step 5: Show it, don't spec it. Instead of a 20-page spec, I send a link. "Here, try this. What's confusing?" Real feedback on a real thing beats hypothetical feedback on a hypothetical thing every single time. 👉 Step 6: Iterate in minutes, not weeks. Here's where this workflow really pulls ahead. Someone says, "This flow is confusing." You don't update a Figma file, write a ticket, and wait for the next sprint. You open Cursor, fix it, and send a new link. Same conversation. Same day. The feedback loop goes from weeks to hours. Sometimes minutes. And each round gets sharper because you're iterating on something real. 3-4 rounds of this, and you have something more validated than most products get after months of traditional process. 👉 Step 7: Document what you built, not what you plan to build. Documentation becomes a record, not a prediction. It's accurate because the thing already exists. You can do it at the end or during the process. Why this works: You make decisions with information instead of assumptions. You eliminate 80% of the back-and-forth. You design from experience, not imagination. And you iterate at the speed of conversation, not the speed of sprints. Why it feels wrong at first: Because we were trained to think before we build. And thinking first felt responsible. But we did that because we couldn't build. Now we can. And I don't think it's about ignoring thinking. (𝘔𝘢𝘯𝘺 𝘰𝘧 𝘺𝘰𝘶 𝘢𝘤𝘤𝘶𝘴𝘦𝘥 𝘮𝘦 𝘰𝘧 𝘵𝘩𝘢𝘵) I believe it's about doing it at every step. Refining it based on real feedback. Insights you can get internally and from user testing. If you're still reading this, let me know what you think about it all. ✌️

Designers, I used to think UX research was about talking to users as fast as possible. So I’d jump straight into interviews, surveys, usability tests, whatever felt right at the time. The problem? I’d come out with a lot of insights… and still struggle to make clear decisions. What I learned the hard way: Most research doesn’t fail because of bad tools. It fails because there’s no clear research plan. I made every classic mistake: → Vague research goals → Questions that quietly confirmed my own assumptions → Methods chosen because they sounded impressive → No clear idea of how insights would actually influence design Everything changed when I started planning research properly. Recently, I revisited my process using a guide from Lyssna, and it reinforced what experience had already taught me: a good research plan doesn’t slow you down, it saves weeks of rework. For example, on a checkout redesign project, my original question was: “Why are users dropping off?” Using a structured plan helped me reframe it into: → What assumptions are we testing? → Which user segment matters most right now? → What decision will this research unlock? That shift alone made the research more focused, easier to explain to stakeholders, and far more actionable. One quick tip that’s had the biggest impact on my work: Write research questions that drive decisions, not curiosity. Asking “Do users like this?” rarely helps. Asking “What prevents users from completing this on mobile?” actually does. If your research ever feels messy, hard to justify, or disconnected from design decisions, this is a solid reset. Lyssna’s user research plan guide walks through the process step by step, with real examples, and includes a free, practical template you can use immediately. User research plan guide + free template → https://lnkd.in/dtEB9p7e I hope that this will help you. Like & Repost, If you find this helpful. Share your thoughts in the comments. Enable notification 🔔 Don't forget to follow Abraham John #uiux #design #designgod #uidesign #uiuxdesign #uidesign #ui #uxdesign