Designing Interactive Prototypes

Customer discovery via functional prototypes + PostHog is night & day better than the old school way of asking for feedback on Figma mockups. Here's why: I get to observe actual user behavior instead of asking the user to guess how they might use my product. My favorite example of why this matters comes from a Sony Walkman user study. They asked a bunch of people what they thought about a yellow walkman and they said "so sporty! not boring like the black one!". And yet, when they were given the opportunity to take a walkman home after the study, everyone picked the black one. We learned a lot more from user behavior than we did expressed preferences. Here's my setup for now observing user behavior from prototypes: 1. Create a functional prototype in your favorite prototyping tool (Bolt, Lovable, Reforge Build, Magic Patterns, Claude Code) 2. Ask the prototyping tool to integrate PostHog analytics 3. Ask the prototyping tool to instrument key user actions in PostHog Then you get all of these ways of observing actual behavior: - DAUs \ WAUs \ retention curves - I can actually see if people come back and use my prototype instead of taking their word for it - Action metrics dashboards - I can see what actions people are taking vs not - Post-usage survey - I can add a built-in pop-up survey to ask the user a question about the experience after they have engaged with the prototype - Session replays - I can see exactly where people are clicking and how they are using the product to identify usability issues - Heatmaps - I can see what part of my design is working across all sessions I'd never go back to testing with just a mockup after this.

You can buy Growth. You cannot buy Engagement. Too many companies burn through massive ad budgets forgetting this simple truth. When you pay for marketing, you are buying a transaction. You are paying to get someone to show up at your front door. That is top-of-funnel acquisition. But once they step inside? Whether they stay, return, and find deep value is entirely up to the product. You cannot bribe a user into genuinely caring about your platform. Engagement cannot be bought it has to be engineered. If you want to build sustainable, long-term retention without relying on an ad-spend crutch, you have to design engagement directly into the product architecture: Shrink Time-to-Value (TTV) The moment a user lands in your product, the clock is ticking. If they have to jump through ten hoops before experiencing an "Aha!" moment, they will churn. Deliver value instantly. Build Core Habit Loops Design a self-reinforcing ecosystem: Trigger: What brings them back? (An internal need or a well-timed, contextual prompt). Action: The simplest step they can take to get a reward. Variable Reward: Deliver fresh, unpredictable value that keeps them curious. Investment: Get the user to input data, time, or customization. The more they invest, the higher their switching cost becomes. Focus on Stored Value A product becomes irreplaceable when a user builds a history within it. Accumulated insights, personalized configurations, and historical data turn attention into equity. Buying growth without engineering engagement is like pouring water into a leaky bucket. It looks impressive while the tap is running, but the moment you turn off the marketing spend, you're left empty. Stop focusing purely on vanity metrics. Shift the energy from just acquiring traffic to building deep, repeatable utility. Create value that pulls people back. Build things that last. #GrowthHacking #ProductDesign #Startups #Retention #UserExperience

I got rejected after this Interview answer 💔 Not proud of it. But this one still lives rent-free in my head. Company: One of the top product companies Round: Product Design Challenge Question: Design a feature to help users discover relevant content in our app? What I did: I jumped straight into wireframes. Added a "Recommended for You" section on the homepage, designed some cards with thumbnails and CTAs, picked nice colors, and called it a day. Result: A polite rejection email the next week. Here's what I should have actually done: Before jumping to solutions and wireframes, a good answer starts with thinking. 𝗜 𝘀𝗵𝗼𝘂𝗹𝗱'𝘃𝗲 𝘀𝘁𝗮𝗿𝘁𝗲𝗱 𝗯𝘆 𝗮𝘀𝗸𝗶𝗻𝗴:  - Who are the users? (new users? power users? different personas?)  - What kind of content? (articles, videos, products, connections?)  - What does "relevant" mean? (based on past behavior? trending? personalized?)  - What's the current discovery problem we're solving?  - What are the business goals? (engagement? retention? revenue?) 𝗔 𝗳𝗹𝗼𝘄 𝗹𝗶𝗸𝗲 𝘁𝗵𝗶𝘀: 𝟭. 𝗥𝗲𝘀𝗲𝗮𝗿𝗰𝗵 & 𝗖𝗼𝗻𝘁𝗲𝘅𝘁  - Understand user pain points through data/interviews  - Map the current user journey  - Identify where discovery fails today 𝟮. 𝗗𝗲𝗳𝗶𝗻𝗲 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗠𝗲𝘁𝗿𝗶𝗰𝘀  - What does success look like? (time spent? click-through rate? return visits?)  - How do we measure relevance? 𝟯. 𝗘𝘅𝗽𝗹𝗼𝗿𝗲 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀  - Consider multiple approaches (algorithmic, social, editorial, hybrid)  - Weigh trade-offs of each  - Don't marry one solution too early 𝟰. 𝗗𝗲𝘀𝗶𝗴𝗻 𝘁𝗵𝗲 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲  - Information architecture first, visuals later  - Think about empty states, loading states, error states  - Consider personalization vs. serendipity  - Design for accessibility and inclusion 𝟱. 𝗩𝗮𝗹𝗶𝗱𝗮𝘁𝗶𝗼𝗻 & 𝗜𝘁𝗲𝗿𝗮𝘁𝗶𝗼𝗻  - How would we test this? (A/B test? prototype testing?)  - What could go wrong?  - How do we handle edge cases? 𝟲. 𝗛𝗮𝗻𝗱𝗼𝗳𝗳 & 𝗜𝗺𝗽𝗮𝗰𝘁  - How does this scale across platforms?  - What's the technical feasibility?  - What's the rollout plan? This way, the solution is user-centered, strategic, and actually solves a real problem.

How to Gamify Product Engagement and Keep Your Users Coming Back for More Ever felt like life is just one big game? As a Product Manager, I often think about how the elements that make games fun—progress, rewards, competition—can make our products sticky. Gamification isn’t just for gaming apps; it’s a powerful tool to drive user engagement across industries. Let me break it down for you: 1) Tap into Core Human Motivations People love recognition, accomplishment, and even a little healthy competition. Use features like leaderboards, badges, or streaks to appeal to these instincts. Think Duolingo’s daily streaks or LinkedIn’s profile strength meter. Users get hooked on achieving that next milestone. 2) Design Clear Goals and Feedback Loops Ever notice how games make progress visible? That’s no accident. Create a roadmap for users that tracks their journey and celebrates their progress. This could be a progress bar for onboarding, a daily challenge, or personalized feedback. Take inspiration from fitness apps like Strava—those achievements feel personal, meaningful, and motivating. 3) Reward Effort, Not Just Results Not everyone wins, but everyone should feel valued. Gamified systems should reward engagement, not just excellence. For example, incentivize users for exploring features, completing surveys, or returning daily. Starbucks’ Rewards program nails this by turning coffee runs into a game of points and free drinks. 4) Create FOMO with Community Challenges Games are social, and products should be too. Adding community challenges, time-limited events, or collaborative goals can spark engagement. Think of how Peloton gets users hyped for virtual classes or Nike Run Club makes running a group achievement. 5) Iterate, Test, Improve Gamification isn’t a one-and-done deal. Track metrics like session length, feature adoption, and retention rates. Experiment with different gamified features to see what clicks with your audience. Remember: what works for a productivity app might not work for a B2B SaaS product. 📈 Food for Thought: How are you measuring the success of your gamification efforts? What’s YOUR Take on Gamification? Have you used gamification in your product? Which tactics have worked for you? Let’s swap ideas and make the comments section a treasure trove of insights for PMs and innovators alike. Gamifying engagement isn’t just about fun—it’s about creating meaningful, habit-forming user experiences that deliver value. And as Product Managers, it’s one of the most creative tools in our toolkit. Let’s play this game together! Drop your thoughts and stories below 👇. #Gamification #ProductManagement #Innovation #UserEngagement #ProductManagement #Product #PM #PeopleInProduct #PeopleInProductManagement #PMLife #PeopleInPM #PMCommunity #ProductCommunity #ProductManagementCommunity #LifeofaPM #ProductOwner

Stop building prototypes to get answers. Start building them to provoke the system. We’ve all been there. You spend weeks on a beautiful, high-fidelity prototype.  You run usability tests, and the feedback is glowing. You ship the feature. And… nothing. No adoption. No impact. The needle doesn't move. The problem wasn't the execution of your design. The problem was the question your prototype was asking. Most prototypes are built to ask low-level questions: → "Is this button clear?" → "Can the user complete this flow?" → "Do they like the color blue?" These questions seek validation. They confirm that your artifact is usable. But they fail to ask the one question that truly matters: "If we introduce this into their world, what changes?" A prototype isn't a demo. It's a question in disguise. It’s a strategic experiment designed to reveal the invisible system of habits, beliefs, and rituals your product lives in. Instead of asking, "Is this new dashboard clear?" Ask, "Does this new dashboard change the way a manager runs their 1:1s?" Instead of asking, "Can users navigate this new feature?" Ask, "Does this feature challenge a team's long-held assumption about their workflow?" The goal of a great prototype isn't to get a "yes" or "no." It's to generate learning about the system itself. Shift your questions from the artifact to the system, and you'll stop shipping usable features that nobody uses. What's the most powerful question you've ever seen a prototype ask? ___________ I use Systems Thinking to help leaders solve complex product and team challenges. On Substack, I explore the deeper layer: Memetic Design. ✺ Follow me Jake Redmond, MBA for more on strategic design.