<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Hooman Rezvani on Medium]]></title>
        <description><![CDATA[Stories by Hooman Rezvani on Medium]]></description>
        <link>https://medium.com/@hoomanrezvani?source=rss-7788676a95b2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4tViw95ttg0AhQXJ68adjw.jpeg</url>
            <title>Stories by Hooman Rezvani on Medium</title>
            <link>https://medium.com/@hoomanrezvani?source=rss-7788676a95b2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:03:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hoomanrezvani/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[We Reached 300 Users. Then We Realised Viathem Needed a Different Direction.]]></title>
            <link>https://medium.productcoalition.com/we-reached-300-users-then-we-realised-viathem-needed-a-different-direction-cb922994bd80?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb922994bd80</guid>
            <category><![CDATA[book-recommendations]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[self-discovery]]></category>
            <category><![CDATA[social-media]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 09:18:33 GMT</pubDate>
            <atom:updated>2026-11-10T09:29:10.067Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DUBXCNsgTQh2-4uhSPtAPA.png" /></figure><p><em>What we learned from our first users, why discovery feels broken, and what we’re building next.</em></p><p>Most of us have more ways than ever to discover new things. We have apps for movies, music, books, restaurants, travel, events, and almost everything else.</p><p>Yet finding something genuinely worth our time still feels surprisingly difficult.</p><p>You might find a great film on one platform, a new artist somewhere else, a restaurant through a friend’s recommendation, and an interesting destination while scrolling through social media. Each discovery happens in a different place. None of these platforms necessarily understands how those interests connect.</p><p>We started asking ourselves a simple question:</p><p><strong>What if discovering things you love could happen in one place, shaped around your taste rather than just your browsing history?</strong></p><p>That question led us to rethink Viathem.</p><h3>The first 300 users taught us something important</h3><p>When we started Viathem, we had an initial idea of what the product should be. But building something and watching people actually use it are two very different experiences.</p><p>After reaching our first 300 users, we tested the product, collected feedback, looked closely at how people interacted with it, and spent time analysing what was working and what wasn’t.</p><p>The conclusion was hard to ignore: improving the existing experience wasn’t enough. The product needed a fundamental change in direction.</p><p>We realised that the bigger opportunity wasn’t simply helping people save or browse interesting things. It was helping them <strong>discover what they genuinely love, understand their own taste, and find people who share it.</strong></p><p>So we made a major pivot.</p><p><strong>What we saw: people post, but few come back</strong><br> Early on, we noticed a pattern. Plenty of people signed up and posted, but very few returned to the app afterwards. Posting was easy. Coming back wasn’t.<br> Our hypothesis was that the product gave people one reason to visit, and not enough reasons to return. So we added a new Experiences category (restaurants, cafés, events, places) to make Viathem broader, give people more to share, and give them more reasons to come back more often.</p><h3>The problem: discovery is fragmented, and recommendations often feel generic</h3><p>Think about how you discover things today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OKIsgnz1ohFRBv_FPm0l4Q.png" /></figure><p>You use one platform to find films, another for music, another for restaurants, and perhaps Instagram or TikTok for everything in between.</p><p>This creates three problems:</p><p><strong>1. Your interests are scattered.</strong><br>Your taste in films, music, food, art, and travel is part of the same person. But the platforms you use treat these interests as separate categories.</p><p><strong>2. Finding something new takes too much effort.</strong><br>Endless feeds and large catalogues give us more options, but more options don’t automatically mean better discoveries. Sometimes they just mean more scrolling.</p><p><strong>3. Shared taste is difficult to discover.</strong><br>Friends can introduce us to great things, but it isn’t always easy to find people beyond our existing circle who have similar interests and can inspire our next discovery.</p><p>We believe discovery should feel more personal, connected, and meaningful.</p><h3>Meet the new Viathem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B8wCZd46cM66YD12HtE5WQ.png" /></figure><p>Viathem is a taste-driven discovery platform designed to bring two worlds together:</p><ul><li><strong>Content:</strong> Movies, series, books, articles, music, podcasts, and art.</li><li><strong>Experiences:</strong> Restaurants, cafés, events, exhibitions, live music, places, and travel.</li></ul><p>Instead of jumping between disconnected platforms, Viathem gives people a place to explore both what they want to consume and what they want to experience.</p><p>But the idea goes beyond putting categories under one roof.</p><p>We want Viathem to become a place where people can:</p><ul><li>Discover things based on their interests and evolving taste.</li><li>Express what they love and what they’re curious about.</li><li>Save discoveries into collections they can revisit and share.</li><li>Explore public collections and see what inspires other people.</li><li>Find people with similar taste and discover new things through them.</li></ul><p><strong>What we changed to bring people back</strong><br> We also rethought the positioning and added features that give people a reason to return:</p><ul><li><strong>Taste DNA:</strong> a picture of your taste, built from what you love, save and pass on.</li><li><strong>Daily taste tests:</strong> a quick, playful this-or-that you can do in a minute.</li><li><strong>Small interactions:</strong> simple ways to connect with each other, like sending a star to someone whose pick you liked.</li></ul><p>The goal isn’t to give people another endless feed. It’s to help them make better discoveries with less noise.</p><h3>What makes Viathem different?</h3><p>There are already excellent platforms for discovering specific types of content and experiences. We don’t need to pretend otherwise.</p><p>The opportunity we see is in connecting those worlds.</p><p>A movie you love might reveal something about your taste in music. Your favourite artists might lead you to an exhibition. A shared interest in food or travel might help you discover someone whose recommendations you genuinely value.</p><p>Most discovery experiences are organised around a category, a catalogue, or a content feed. <strong>Viathem is being built around the person: their taste, their interests, and the connections between them.</strong></p><p>That is the difference we want to create.</p><p>It’s not about replacing every platform people already use. It’s about creating a more connected layer for discovering what to watch, read, listen to, visit, and experience next.</p><p><strong>A more modern design</strong><br> There was one more thing users told us clearly: the first design felt dated. For many of them, that alone was enough to stop engaging. So we redesigned the whole experience to feel modern, calm and easy to come back to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ZE6lACZuZrqZmuYyn_SIg.png" /></figure><h3>This is only the beginning</h3><p>Viathem is still evolving. We know there is a lot to learn, test, and improve.</p><p>But the first 300 users helped us understand something valuable: the original idea was only the starting point. Listening, questioning our assumptions, and being willing to change direction helped us find a more meaningful problem to solve.</p><p>We’re building Viathem around one simple belief:</p><p><strong>Your taste is bigger than any single category, and discovering what you love should reflect that.</strong></p><p>We’re excited to build this next chapter.</p><p><strong>Discover what you’ll love next.</strong></p><p>Explore Viathem: <a href="https://viathem.com/">https://viathem.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb922994bd80" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/we-reached-300-users-then-we-realised-viathem-needed-a-different-direction-cb922994bd80">We Reached 300 Users. Then We Realised Viathem Needed a Different Direction.</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Real Threat Isn’t Replacement — It’s Compression]]></title>
            <link>https://medium.com/design-bootcamp/the-real-threat-isnt-replacement-it-s-compression-f9bd6e0b19b2?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9bd6e0b19b2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[future]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Fri, 22 May 2026 21:52:34 GMT</pubDate>
            <atom:updated>2026-05-27T22:37:29.089Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How AI is reshaping team structures, and what it means for designers at every level</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cPEoZPvybUhLilP2TsYJIA.jpeg" /></figure><p>The question keeping most designers up at night isn’t really “will AI take my job?” anymore. That debate has become almost too abstract. The more urgent — and more concrete — question is: <strong>what organizational strategies will companies actually adopt?</strong> And what does that mean for the people already inside those organizations?</p><p>Let’s be honest about what’s happening.</p><h3>Speed Is the Silent Disruptor</h3><p>AI isn’t replacing designers wholesale. But it is doing something arguably more disruptive: <strong>it’s compressing delivery timelines</strong>.</p><p>Work that used to take three weeks can now be done in one. That’s not a metaphor — it’s a workflow reality that product teams are already living with. Rapid prototyping, copy generation, user flow exploration, component variants — tasks that once required dedicated sprint cycles now take hours.</p><p>On the surface, this sounds like good news. Faster output. More iteration. Better products.</p><p>But here’s the organizational math that companies are quietly running: if one designer can now produce what three designers used to, you don’t need three designers anymore.</p><p>This isn’t replacement. It’s <strong>compression</strong>. And compression-driven layoffs are already happening — not because AI is doing the design work, but because AI is accelerating it enough to shrink the headcount required to deliver it.</p><h3>The Rise of the Product Builder</h3><p>As team structures get leaner, the traditional boundaries between roles are starting to blur — and in some cases, dissolve entirely.</p><p>One of the most significant emerging patterns is the convergence of the <strong>Product Designer</strong> and <strong>Product Manager</strong> roles into something new: the <strong>Product Builder</strong>.</p><p>The logic is straightforward. In an AI-augmented workflow, a single person can own the full arc of a feature — from identifying the problem, to defining the solution, to shipping a high-fidelity prototype — in a fraction of the time it would have taken a two-person team. Tools like Claude, Cursor, and Figma’s AI features are collapsing the distance between thinking and shipping.</p><p>In more aggressive configurations, particularly at early-stage and small-scale companies, this expands even further. Individual contributors are becoming end-to-end owners: responsible for design, development, and roadmap decisions across entire product surfaces. The generalist is having a moment — not because specialization isn’t valuable, but because AI is now doing a significant portion of the specialist’s execution work.</p><h3>The Senior vs. Mid-Level Question</h3><p>This brings up a genuinely thorny structural question: <strong>which seniority tier is more at risk?</strong></p><p>The honest answer is: it depends — and it depends on more variables than most people acknowledge.</p><p>Here’s a framework for thinking about it:</p><p><strong>Companies more likely to cut Senior roles</strong> tend to share a few characteristics:</p><ul><li>They’re under financial pressure and are optimizing for cost reduction</li><li>Their product is not deeply design-driven, meaning design quality isn’t a core competitive advantage</li><li>They have a larger proportion of mid-level designers than seniors, making mid-level layoffs politically or operationally riskier</li><li>They believe — rightly or wrongly — that AI can close the gap between mid-level and senior output</li></ul><p>In these organizations, the emerging bet is that <strong>mid-level designers, equipped with AI tools, can do the work that previously required a senior</strong>. Whether this plays out well for the product is a separate question. But as a financial and organizational strategy, it’s a coherent one.</p><p><strong>Companies more likely to preserve Senior roles</strong> tend to look different:</p><ul><li>Design is a genuine differentiator — product quality, taste, and strategic thinking are core to how they compete</li><li>They’re financially stable and not in cost-reduction mode</li><li>Their senior-to-mid-level ratio is roughly balanced, making it harder to absorb senior exits without serious knowledge loss</li><li>They understand that AI amplifies good judgment, but doesn’t manufacture it</li></ul><p>In these organizations, <strong>seniors become more valuable</strong>, not less — because AI raises the baseline for everyone, and the delta between “fine” and “exceptional” now comes almost entirely from taste, strategy, and the ability to ask the right questions.</p><h3>What This Means If You’re a Designer Right Now</h3><p>The uncomfortable truth is that the mid-tier — mid-level designers who are competent but not yet strategic — faces the most ambiguous future. They’re expensive enough to matter to a balance sheet, but not yet indispensable enough to be protected by their judgment and experience.</p><p>The designers who will navigate this well are the ones who move in one of two directions:</p><p><strong>Go broader.</strong> Develop enough product sense, business literacy, and cross-functional fluency to operate as a Product Builder. Own outcomes, not just deliverables.</p><p><strong>Go deeper.</strong> Become so specifically excellent — at systems thinking, at research synthesis, at design strategy — that you’re the person AI-assisted teams need to make sense of what the AI is producing.</p><p>The middle is getting squeezed. The edges — generalists who own outcomes, and specialists who provide irreplaceable judgment — are where the durable value lives.</p><h3>A Final Thought</h3><p>AI is not ending design. But it is ending the version of design careers that were built on execution speed as a primary value proposition. The designers who thrive will be the ones who treat AI as an amplifier of their thinking — not a threat to their output.</p><p>The question worth asking isn’t <em>will AI take my job?</em></p><p>It’s <em>what kind of designer does AI make more valuable — and am I becoming that person?</em></p><p><em>If this resonated, I’d love to hear how you’re navigating these changes in your own team or career. Drop a comment or reach out directly.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9bd6e0b19b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-real-threat-isnt-replacement-it-s-compression-f9bd6e0b19b2">The Real Threat Isn’t Replacement — It’s Compression</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Built a Social Platform in 3 Weeks Using AI — Here’s The Idea Behind It]]></title>
            <link>https://blog.startupstash.com/i-built-a-social-platform-in-3-weeks-using-ai-heres-the-idea-behind-it-7c18cddda8ef?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c18cddda8ef</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Fri, 08 May 2026 22:16:36 GMT</pubDate>
            <atom:updated>2026-05-14T10:32:04.831Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How a simple question — “what have you been reading lately?” — became the foundation for a new kind of discovery platform.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wIarKoPkr220fR4uFOIkoQ.jpeg" /></figure><p>There’s a question I’ve been asking people for years.</p><p>Not “what’s trending?” Not “what does the algorithm recommend?” Just a simple, human question: <strong>“What have you been reading lately? Any films you loved? What are you listening to?”</strong></p><p>And every time I ask it — the answer is better than anything an algorithm has ever served me.</p><p>Because the person answering isn’t optimizing for engagement. They’re not sponsored. They’re not a publication trying to hit a quota. They’re just a human whose taste I trust, telling me what actually moved them.</p><p>That question has given me some of the best books I’ve ever read. Films I would never have found. Albums that stayed with me for years.</p><p>And then I started thinking: why doesn’t a platform exist for exactly this?</p><h3>The Problem Nobody Solved</h3><p>We have Goodreads for books. Letterboxd for films. Last.fm for music. Pocket for articles. And Twitter/X for everything — wrapped in an algorithm that optimizes for outrage over discovery.</p><p>But none of them answer the actual question I want answered:</p><p><strong>“What is this specific person — whose taste I trust — consuming right now, across everything?”</strong></p><p>Not books only. Not films only. <em>Everything.</em> The book they finished last week, the documentary that changed their perspective, the podcast episode they keep thinking about, the article they’ve recommended three times in the past month.</p><p>That full picture of a person’s intellectual and cultural life doesn’t exist anywhere. It’s scattered across six different apps. You miss most of it.</p><p>Meanwhile, we live in 2026, where AI can generate any piece of content on demand. Where recommendations engines know everything about your behavior and still manage to suggest something you don’t want.</p><p>And in that world, the rarest and most valuable signal left is a real human — someone you respect — saying: <em>“I read this. It was worth my time.”</em></p><h3>The Idea: Viathem</h3><p>So I built <strong>Viathem</strong>.</p><p>The concept is simple: a social platform where you share anything you consumed — a URL, a book name, an image, a podcast, a song, an article — and the people who follow you see it all in one feed.</p><p>No algorithm decides what gets shown. No ads. No trending tab. Just a clean, chronological feed of what the people you follow actually consumed this week.</p><p>The name comes from the tagline: <em>“Discover everything, via them.”</em></p><p>Every piece of content you discover on Viathem arrives through a human you chose to follow. That’s the entire premise.</p><h3>How It Works</h3><p>When you share something on Viathem, you paste a link or type a name. The platform automatically fetches a smart preview — title, image, description — and displays it as a card in your followers’ feeds. They tap through to the original source.</p><p>Your profile becomes a living record of everything that shaped you intellectually and culturally. Not a curated highlight reel. Not a brand. Just what you actually consumed.</p><p>Profiles can be <strong>public</strong> — anyone can follow you — or <strong>private</strong>, where followers need your approval. For curators who want to build an audience, there’s a verified Curator plan that includes a weekly digest email sent to their followers, follower analytics, and an embed widget for their newsletter or website.</p><p>The content types are deliberately broad:</p><ul><li>📖 Books</li><li>🎬 Films and series</li><li>🎵 Music</li><li>🎙️ Podcasts</li><li>📰 Articles</li><li>🔗 Any link</li><li>🖼️ Images</li><li>✦ Anything else</li></ul><p>If you consumed it and it meant something to you — it belongs on Viathem.</p><h3>Why Now</h3><p>Three things are converging in 2026 that make this the right moment.</p><p><strong>First: AI is saturating content.</strong> When machines can generate unlimited articles, videos, and music on demand, the scarcest commodity is authentic human curation. What a real person actually chose to spend their limited attention on — that’s meaningful precisely because it’s not generated.</p><p><strong>Second: Goodreads is abandoned.</strong> 150 million users on a platform that hasn’t seen a meaningful update in years. Amazon acquired it in 2013 and largely left it to stagnate. Every week, you’ll find Reddit threads filled with people asking “is there a better alternative?” The migration window is wide open.</p><p><strong>Third: Human recommendations are winning.</strong> Recent research shows that personal recommendations from trusted people now rank as the #1 discovery source for books, films, and music — beating both algorithms and editorial curation. People are tired of being manipulated by recommendation engines. They want to know what <em>people like them</em> are actually choosing.</p><h3>Building It Alone — With AI</h3><p>Here’s the part that still surprises me when I think about it.</p><p>I built Viathem alone. No co-founder. No engineering team. No agency.</p><p>The full product — brand identity, business plan, financial model, pitch deck, competitive analysis, go-to-market strategy, legal documents, design system, and complete full-stack web application — was built using <strong>Cursor</strong> and <strong>Claude</strong> as my primary tools.</p><p>Cursor handled the code. Claude handled the thinking, the strategy, and the documentation. I handled the decisions and the vision.</p><p>The process looked like this:</p><p><strong>Week 1:</strong> Idea validation, competitive research, brand identity, business model. I worked with a virtual panel of personas — head of product, head of design, CTO, head of marketing — to pressure-test every decision. By the end of the week, I had a brand book, a one-page business plan, a pitch deck, and an 18-month financial model.</p><p><strong>Week 2:</strong> Architecture decisions, database schema, API design, complete technical specification. The super prompt I wrote for Cursor was over 1,400 lines — covering every screen, every API route, every component, every edge case.</p><p><strong>Week 3:</strong> Build. Feature by feature, screen by screen, following the specification.</p><p>The result is a production-ready web application with:</p><ul><li>Full social graph (follow, unfollow, follow requests for private profiles)</li><li>All content types with automatic Open Graph preview</li><li>Public and private profiles</li><li>Chronological feed with no algorithm</li><li>Like, comment, and save to collections</li><li>Weekly digest email (automated, cron-based)</li><li>Stripe payment integration for Pro and Curator plans</li><li>Full admin dashboard with user management, content moderation, and analytics</li><li>PWA support — installable on iPhone and Android</li><li>Complete dark mode</li></ul><p>All of this. One person. Three weeks.</p><h3>The Business Model</h3><p>Viathem is free for everyone who wants to share and discover.</p><p>For users who want more, there are paid plans:</p><p><strong>Pro (€6/mo):</strong> Personal stats, private collections, data export, custom theme.</p><p><strong>Curator (€14/mo):</strong> Verified badge, featured placement on the Discover page, weekly digest email to your followers, follower analytics, embed widget for your newsletter.</p><p><strong>B2B (€99/mo):</strong> For publishers, record labels, and media companies who want real-time trend reports on what trusted curators are sharing.</p><p>The B2B play is genuinely interesting. Viathem will accumulate real consumption data from credible humans across books, films, music, and podcasts. That’s a dataset publishers would pay for — not to know what sold, but to know what tastemakers are quietly picking up <em>before</em> it goes mainstream.</p><h3>What I Believe</h3><p>I believe the internet’s most valuable layer — human curation — has been consistently underbuilt.</p><p>Every platform we have treats curation as a feature, not a foundation. Goodreads is a database. Twitter is a firehose. Substack is publishing. None of them are built around the simple act of one person saying to another: <em>“I consumed this, and I think you might love it too.”</em></p><p>Viathem is built around exactly that act.</p><p>In a world full of generated content and optimized feeds, the most radical thing you can do is share what you actually read. And the most useful platform is one that lets the people who trust you find it.</p><p><em>Discover everything, via them.</em></p><p><strong>If you want to follow my build journey, I’ll be sharing updates as Viathem grows. The first version launches soon.</strong></p><p><em>Built with Cursor + Claude. Designed for humans.</em></p><p>#Viathem #BuildInPublic #SoloFounder #IndieHacker #ProductDesign #StartupLife #AI #Cursor #Claude #SocialDiscovery #ContentCuration #Goodreads #Letterboxd #HumanCuration #DiscoverEverything #Medium #Writing #Startup #Design #ProductThinking</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c18cddda8ef" width="1" height="1" alt=""><hr><p><a href="https://blog.startupstash.com/i-built-a-social-platform-in-3-weeks-using-ai-heres-the-idea-behind-it-7c18cddda8ef">I Built a Social Platform in 3 Weeks Using AI — Here’s The Idea Behind It</a> was originally published in <a href="https://blog.startupstash.com/">Startup Stash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why VoteMyPrice Is Entering Version 3]]></title>
            <link>https://medium.com/@hoomanrezvani/why-votemyprice-is-entering-version-3-6802c3566718?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6802c3566718</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[pivoting]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 20:59:10 GMT</pubDate>
            <atom:updated>2026-04-06T20:59:10.215Z</atom:updated>
            <content:encoded><![CDATA[<p>What launching, expanding, listening, and learning taught me about building a sharper product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RvrMSvwa3nTz_aZ6dNv-Mw.jpeg" /></figure><p>When you build a product, every version teaches you something different.</p><p>After launching <strong>VoteMyPrice Version 1</strong>, I moved quickly into <strong>Version 2</strong>, which was a major step toward turning the platform into a stronger <strong>marketplace / C2C experience</strong>. The idea was to make the product more social, more interactive, and more community-driven.</p><p>In Version 2, I introduced several important changes:</p><ul><li>a more solid marketplace and C2C structure</li><li>user profiles</li><li>the ability to follow other users</li><li>visibility into each user’s votes and listings</li><li>multiple UI and UX improvements to make the experience cleaner, smoother, and more intuitive</li></ul><p>The goal at that stage was clear: I wanted VoteMyPrice to become more than just a place to post and vote on prices. I wanted it to feel like a platform where users could build trust, follow interesting buyers or sellers, and engage more actively with the community.</p><p>It was an ambitious direction, and it helped me push the product forward quickly after launch.</p><p>But over the past two months, after analyzing user behavior, collecting feedback from around <strong>35 users</strong>, running surveys, and reviewing patterns with the help of AI-assisted product analysis, I reached an important conclusion:</p><p><strong>The product had become too broad.</strong></p><p>Version 2 improved the platform in many ways, but it also made one thing clearer: adding more marketplace and social layers did not automatically make the value proposition sharper. Users could see potential, but the core use case still needed more clarity and focus.</p><p>That insight led me to <strong>Version 3</strong>.</p><p>With Version 3, I am making a strategic pivot.</p><p>VoteMyPrice is now becoming more focused on a much clearer problem:<br> <strong>helping people validate whether a project price or quote is fair.</strong></p><p>Instead of trying to be a broad marketplace for different pricing scenarios, the new direction is centered around <strong>project price validation</strong>. The goal is to help users understand whether a quote is too high, too low, or aligned with what the market thinks is fair.</p><p>This decision was shaped by:</p><ul><li>direct user feedback</li><li>survey responses</li><li>behavioral analysis</li><li>product review and pattern recognition</li><li>AI-assisted strategic evaluation</li></ul><p>The biggest lesson from this journey is simple:</p><p><strong>Early-stage products do not always need more features. They often need more clarity.</strong></p><p>Version 2 was an important step because it helped reveal what users found interesting, but also where the product became too wide. Version 3 is about narrowing the focus, sharpening the value proposition, and building something that users can understand instantly.</p><p>This is the next chapter for VoteMyPrice, and I believe it is a much stronger one.</p><p><strong>You can check it out here:</strong> https://votemyprice.com</p><p><strong>#ProductStrategy #Startup #Pivot #UserResearch #UX #ProductDesign #SaaS #BuildinPublic #Marketplace #Founder #Journey</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6802c3566718" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Built a Startup MVP End-to-End With AI (From a 10-Year-Old Idea to a Live Product)]]></title>
            <link>https://medium.com/@hoomanrezvani/i-built-a-startup-mvp-end-to-end-with-ai-from-a-10-year-old-idea-to-a-live-product-aed6cfd0afb8?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/aed6cfd0afb8</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[ai-startups]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Fri, 06 Feb 2026 14:21:03 GMT</pubDate>
            <atom:updated>2026-02-06T14:21:57.901Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*Tkx0v41qJ4vQmKZNCRJD-Q.jpeg" /></figure><p>Ten years ago, my late uncle said something to me that sounded almost too simple:</p><p><strong>“If you’re not sure what something is worth, don’t guess. Ask people. Enough honest opinions will reveal the real range.”</strong></p><p>He wasn’t talking about startups. He was talking about everyday life, negotiation, and fairness.<br> But that sentence planted a seed in my head.</p><p>Because I realized: we <em>all</em> do this, informally.<br> We DM friends. We post in groups. We search forums. We ask strangers.</p><p>And yet “asking around” is messy. The answers are inconsistent, biased, and hard to trust.<br> So the thought that stayed with me was:</p><blockquote><em>What if the internet could turn “asking around” into a structured, trustworthy price signal?</em></blockquote><p>This weekend, I finally shipped that idea as a real product: <strong>VoteMyPrice</strong>.</p><h3>What VoteMyPrice Does (In One Minute)</h3><p>VoteMyPrice is a crowd-backed pricing tool.</p><p>You create a <strong>listing</strong> for something you’re unsure how to price and share it.<br> People visit the page and <strong>vote a price</strong>.</p><p>Over time, you get:</p><ul><li>a crowd-backed <strong>price estimate</strong></li><li>a <strong>typical range</strong></li><li>and better confidence to decide what’s fair</li></ul><p>It’s designed for everyday humans, not pricing experts.<br> Simple pages. Clear actions. No complexity where it doesn’t help.</p><h3>Why I Started This (And Why I Didn’t Earlier)</h3><p>I’ve had ideas for years. Honestly, too many.</p><p>The hard part wasn’t imagination.<br> The hard part was knowing which idea was worth the time and risk to build.</p><p>So I created a simple, ruthless filter. I evaluated my ideas with AI using <strong>seven practical parameters</strong>, things like:</p><ul><li>real user need (not “nice-to-have”)</li><li>realistic monetization potential</li><li>low competition / clear differentiation</li><li>SEO/discoverability</li><li>viral sharing potential</li><li>solo-build feasibility</li><li>minimal dependency on extra services</li></ul><p>That process was eye-opening. Most ideas sounded exciting, but collapsed under pressure-testing.</p><p>And then I came back to my uncle’s idea.</p><p>It was weirdly comforting, like finding a solid rock after too many shiny objects.<br> I realized: <em>this one actually fits the filter.</em></p><p>That’s when I got excited, because it wasn’t just emotional. It was logical.</p><h3>The Real Workflow (What I Actually Did)</h3><h3>1) I treated the idea like it was guilty until proven innocent</h3><p>Before I designed anything, I forced validation.</p><p>I used AI like a research assistant to:</p><ul><li>map how people solve pricing uncertainty today</li><li>scan the competitive landscape (and where existing options fail)</li><li>pressure-test the concept from multiple angles</li></ul><p>Then I asked the questions that matter:</p><ul><li><em>What exact value am I delivering beyond “people can comment”?</em></li><li><em>Why would someone trust this signal?</em></li><li><em>What would make them share it?</em></li><li><em>What would make them come back?</em></li></ul><p>That’s where market research stopped being “reading about competitors” and became “designing a real value proposition.”</p><h3>2) I defined value-add before I defined features</h3><p>One of the biggest lessons: features are easy to add. Value is hard to earn.</p><p>So I used research to decide what <strong>value-adds</strong> the product must deliver to be worth using:</p><ul><li>clarity and simplicity (non-technical users should “get it” instantly)</li><li>trustworthy results (avoid confusing stats, keep output human-readable)</li><li>fast participation (make voting frictionless)</li><li>shareability (every listing has a clean, obvious share flow)</li></ul><p>Only after that did I start designing the product around those value-adds.</p><h3>3) I explored business model options (without turning this into a finance document)</h3><p>I’m intentionally not sharing sensitive business numbers here, but I will share the thinking:</p><p>Market research helped me understand something important:</p><ul><li>The platform needs <strong>two sides</strong>: people who request pricing and people who vote.</li><li>If the “voter side” is weak, the product feels empty.</li><li>If the “creator side” can’t get results fast, they won’t return.</li></ul><p>So the business model had to align with that reality:</p><ul><li>keep voting as frictionless as possible</li><li>create a clear reason for creators to pay <em>when they want faster, better outcomes</em></li><li>and ensure incentives don’t turn into spam</li></ul><p>In other words, monetization wasn’t “how do I charge money?”<br> It was “how do I sustainably improve outcomes for the person who needs pricing.”</p><p>That framing changed everything.</p><h3>4) I built it with Cursor (and I learned how to “talk to software”)</h3><p>Most people think the magic is “AI writes code.”<br> The real magic is: <strong>you learn how to specify what you want.</strong></p><p>I built the MVP using <strong>Cursor</strong>, and I gave it a <em>lot</em> of prompts.</p><p>Not random prompts. Structured ones.</p><p>I’d ask it to implement features end-to-end (database + API + UI), but I also pushed it to:</p><ul><li>re-check the product logic when something didn’t feel right</li><li>run functional QA checklists and fix what failed</li><li>keep terminology and UX consistent across the whole system</li></ul><p>My background in <strong>software + product design</strong> helped here.<br> It helped me spot:</p><ul><li>corner cases and edge cases early</li><li>weak user flows</li><li>confusing terminology</li><li>and visual details that affect trust</li></ul><p>That combination (product taste + structured prompting) was the difference between “a demo” and “a real product.”</p><h3>5) I learned deployment with ChatGPT (and shipped it to a real server)</h3><p>I’m not going to share infrastructure details for obvious security reasons, but here’s the honest part:</p><p>I didn’t start this project as a DevOps person.</p><p>I used <strong>ChatGPT</strong> to understand, step-by-step:</p><ul><li>what deployment actually means</li><li>what needs to be configured</li><li>what to check when things break</li><li>and how to get from “it runs on my laptop” to “it’s live”</li></ul><p>That learning curve used to be a major blocker.<br> Now it’s something I can actually repeat.</p><h3>6) I shipped it</h3><p>Shipping changes your psychology.</p><p>Once it’s live, you stop imagining users and start watching behavior.<br> You stop debating hypotheticals and start learning reality.</p><p>And that’s the moment a project becomes a product.</p><h3>What AI Did (And What It Didn’t)</h3><p>AI didn’t replace the work.</p><p>It replaced the blockers.</p><p>It helped me:</p><ul><li>evaluate ideas with a structured filter</li><li>move faster through research and comparison</li><li>keep consistency across copy and UI</li><li>implement features and QA like a small team</li><li>learn deployment without being stuck for days</li></ul><p>But the direction, taste, and decision-making still had to come from me.</p><p>My main takeaway is simple:</p><blockquote><em>The new skill isn’t “using AI.”<br> The new skill is building products </em>with<em> AI as your partner.</em></blockquote><h3>What I’m Doing Next (Yes, with AI)</h3><p>Now that the MVP is live, the next challenge is distribution.</p><p>So I’m going to use AI for the next phase too:</p><ul><li>design a full go-to-market plan (channels, messaging, positioning)</li><li>plan SEO content and publishable articles</li><li>generate marketing materials (landing page variations, visuals, social posts)</li><li>analyze early user behavior and feedback to prioritize improvements</li><li><strong>create an investor-ready narrative (</strong>refine the story, build pitch, materials)</li><li>and produce a clean pitch deck to share with potential investors</li></ul><p>I’m excited because shipping the product was step one.<br> Learning how to grow it (and communicate it) is step two.</p><h3>What I’m Looking For Now</h3><p>VoteMyPrice is a first version.</p><p>Now I want to learn from real people:</p><ul><li>Does the value land instantly?</li><li>Do users actually share listings?</li><li>Do voters participate without friction?</li><li>What makes the experience feel more trustworthy?</li></ul><p>If you’re someone who builds products, ships MVPs, or just enjoys seeing ideas come to life, I’d love your feedback.</p><p>🔗 <strong>Try it here:</strong> <a href="https://votemyprice.com/">votemyprice.com</a></p><h3>A Short Blueprint You Can Reuse</h3><p>If you want to do your own “idea → MVP → launch” journey, here’s the playbook:</p><ol><li>Write your idea in one sentence</li><li>Evaluate ideas with a clear filter (and be ruthless)</li><li>Validate the problem before you design</li><li>Decide the value-add + business model before you build</li><li>Turn everything into acceptance criteria</li><li>Build in small loops, test constantly</li><li>Ship when it’s clear and works</li><li>Use AI to accelerate marketing and learning too</li></ol><p>That’s it.</p><p>Everything else is details.</p><p>#AI #BuildInPublic #Startups #ProductDesign #ProductManagement #IndieHacker #Entrepreneurship #MVP #UX #MarketResearch #Cursor #ChatGPT #GoToMarket #Marketing #PitchDeck</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aed6cfd0afb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your UI Isn’t the Deciding Factor (These 5 Invisible Signals Usually Are)]]></title>
            <link>https://uxplanet.org/your-ui-isnt-the-deciding-factor-these-5-invisible-signals-usually-are-6fa5f98c99f4?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fa5f98c99f4</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Thu, 01 Jan 2026 11:24:55 GMT</pubDate>
            <atom:updated>2026-01-01T11:24:55.973Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8lz-q8Um3g1d1zUjCG4zHQ.jpeg" /></figure><p>A lot of product designers spend most of their energy polishing UI: spacing, components, visual consistency, “cleaner” layouts.</p><p>That craft matters. But in interviews and day-to-day product work, UI quality is rarely the deciding factor.</p><p>What usually separates a “yes” from a “maybe” (or a quiet “not yet”) are signals you can’t screenshot in Figma: how you frame problems, how you reason about decisions, how you work with feedback, and whether you can move forward when the situation is unclear.</p><p>This is a practical guide to those signals, with simple techniques you can apply immediately. Think of it as the stuff that makes your portfolio and your interview answers feel trustworthy, not just pretty.</p><h3>1) Problem framing: Can you describe the problem in a testable way?</h3><p>Many case studies start with something like: “We redesigned onboarding.”</p><p>That’s a project name, not a problem.</p><p>A strong problem frame answers five things clearly:</p><ul><li><strong>Who</strong> is struggling (which user segment or context)?</li><li><strong>What</strong> behavior or friction is happening?</li><li><strong>Where</strong> does it occur (step, moment, channel)?</li><li><strong>Why</strong> does it matter (impact)?</li><li><strong>How</strong> will you know it improved (metric)?</li></ul><p>A simple, product-scientific tool is the hypothesis sentence:</p><blockquote><em>If we change </em><strong><em>X</em></strong><em> for </em><strong><em>Y</em></strong><em>, we expect </em><strong><em>Z</em></strong><em> to improve because </em><strong><em>reason</em></strong><em>, measured by </em><strong><em>metric</em></strong><em>.</em></blockquote><p>Why this works: it forces clarity, creates alignment, and makes your work testable. That’s basically the foundation of good decision-making in ambiguous environments.</p><p><strong>Practical tip:</strong> In your portfolio, put this hypothesis near the top. It instantly upgrades the perceived maturity of your work.</p><h3>2) Decision reasoning: Is your “why” defensible beyond taste?</h3><p>“Cleaner,” “more modern,” and “more intuitive” are not useless words, but they’re incomplete.</p><p>A stronger “why” connects to one (or more) of these anchors:</p><ul><li><strong>Human cognition:</strong> reduce cognitive load, memory burden, or decision complexity</li><li><strong>Behavioral evidence:</strong> analytics, session replays, support tickets, user feedback, usability findings</li><li><strong>Constraints:</strong> feasibility, platform limitations, existing design system patterns</li><li><strong>Trade-offs:</strong> what you sacrificed to win something else</li></ul><p>A lightweight but powerful technique is to add “decision notes” to your case study:</p><ul><li><strong>Decision:</strong> reduce options on the first screen</li><li><strong>Reason:</strong> decrease choice overload at a high-drop step</li><li><strong>Risk:</strong> users may not discover advanced options</li><li><strong>Mitigation:</strong> progressive disclosure + track clicks on “compare plans”</li></ul><p>This reads as professional because it mirrors how real product teams think: decisions, risks, mitigation, measurement.</p><h3>3) Feedback handling: Can you absorb critique without losing the plot?</h3><p>Feedback is constant in product design. The signal here is not “do you agree with everyone,” but:</p><ul><li>Can you clarify the underlying concern?</li><li>Can you separate intent from opinion?</li><li>Can you iterate without turning it into a debate?</li></ul><p>A practical response pattern that works in real teams and interviews:</p><ol><li><strong>Clarify</strong>: “Which part feels confusing, the label or the sequence?”</li><li><strong>Name the concern</strong>: “Is this about trust, comprehension, or effort?”</li><li><strong>Offer a path</strong>: “Let’s compare two variants and validate quickly.”</li><li><strong>Close the loop</strong>: “Here’s what we changed and what we learned.”</li></ol><p>This shows calm collaboration and confidence. Teams value that because it reduces friction and speeds up learning.</p><h3>4) Working under ambiguity: Do you reduce uncertainty, or get stuck?</h3><p>Product design is rarely a clean brief. Most of the time, you’re operating with partial information and competing opinions.</p><p>The core skill is not guessing. It’s <strong>reducing uncertainty cheaply</strong>.</p><p>A simple framework you can describe in any case study:</p><ol><li><strong>List assumptions</strong> (what must be true for this to work)</li><li><strong>Rank by risk</strong> (impact × uncertainty)</li><li><strong>Test the riskiest assumption first</strong> (prototype, experiment, staged rollout)</li><li><strong>Instrument learning</strong> (metrics + qualitative signal)</li><li><strong>Iterate</strong> based on evidence</li></ol><p>Scientifically, this is just good decision theory in practice: prioritize learning where uncertainty is highest and cost of being wrong is biggest.</p><p><strong>Practical tip:</strong> In your portfolio, add a section called “What we didn’t know (and how we learned).” It’s a maturity signal.</p><h3>5) Case study quality: Do you show screens, or do you show decisions?</h3><p>A portfolio can look great and still feel “light” if it’s just outputs.</p><p>Hiring teams and senior peers want to see decision-making:</p><ul><li>alternatives considered</li><li>constraints acknowledged</li><li>trade-offs explained</li><li>post-launch learning</li></ul><p>A simple way to do this without writing a novel is a “Decision Log”:</p><ul><li><strong>Decision:</strong> move pricing explanation earlier<br> <strong>Why:</strong> reduce surprise at the commitment step (trust)<br> <strong>Trade-off:</strong> adds content earlier (potential scanning cost)<br> <strong>Measure:</strong> CTR on CTA + drop-off between steps + help clicks</li></ul><p>This makes your thinking visible. And visible thinking is what creates trust.</p><h3>The real point</h3><p>UI polish can get attention.</p><p>But the signals that usually decide confidence are:</p><ol><li>problem framing</li><li>defensible reasoning</li><li>feedback handling</li><li>ambiguity navigation</li><li>decision storytelling</li></ol><p>If you want your work to land as “senior,” start making these signals obvious in your portfolio and in how you talk about your projects.</p><p>Your UI can stay great. This is how you make your <em>thinking</em> equally clear.</p><h3>Hashtags</h3><p>#ProductDesign #UXDesign #ProductThinking #DesignInterviews #PortfolioTips #DecisionMaking #UXResearch #Experimentation #DesignLeadership #CareerGrowth</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fa5f98c99f4" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/your-ui-isnt-the-deciding-factor-these-5-invisible-signals-usually-are-6fa5f98c99f4">Your UI Isn’t the Deciding Factor (These 5 Invisible Signals Usually Are)</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good, Bad, and Great Product Designers: What Actually Separates Them]]></title>
            <link>https://medium.com/@hoomanrezvani/good-bad-and-great-product-designers-what-actually-separates-them-47c6d40fad80?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/47c6d40fad80</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Fri, 26 Dec 2025 10:21:26 GMT</pubDate>
            <atom:updated>2026-01-01T11:07:50.174Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8RvFaO6__MpE_xToETr2VQ.jpeg" /></figure><p>A common mistake in design discussions is treating skill as a binary variable: someone is either “good” or “not good.” In reality, product design exists on a spectrum. A designer may be strong in execution but weak in problem definition, or confident in ideation but poor at validation.<br>No product designer excels equally at all skills. However, there <em>are</em> core competencies that reliably differentiate a weak designer from a competent one, and a competent one from an exceptional one. Understanding these distinctions is essential for building effective products, mature teams, and healthy design cultures.</p><h3>Core Premise: Design Is Decision‑Making Under Uncertainty</h3><p>At its core, product design is not about creating screens. It is about:</p><ul><li>Reducing uncertainty</li><li>Making informed decisions</li><li>Aligning user needs with business constraints</li><li>Translating ambiguity into actionable systems</li></ul><p>From this perspective, the quality of a designer is directly correlated with the quality of their <strong>thinking</strong>, not just their output.</p><h3>The First Critical Skill: Problem Definition</h3><p>One of the most fundamental and underestimated skills in product design is <strong>problem definition</strong>.</p><p>There is a crucial difference between:</p><ul><li>Discovering a <em>user pain</em></li><li>Designing a <em>solution</em></li></ul><p>A weak designer jumps quickly to solutions. A strong designer invests time in clarifying:</p><ul><li>What problem actually exists</li><li>For whom it exists</li><li>Why it matters</li><li>How it manifests behaviorally</li></ul><p>Many failed products are not the result of poor execution, but of well‑executed solutions to the wrong problems.</p><p>A good product designer is able to:</p><ul><li>Separate symptoms from root causes</li><li>Reframe vague complaints into testable problem statements</li><li>Avoid solution bias during discovery</li></ul><p>This skill alone can dramatically improve product outcomes.</p><h3>Strategic and Forward Thinking</h3><p>The second major differentiator is <strong>strategic and forward thinking</strong>.</p><p>Strategic thinking in design does not mean creating long presentations or abstract visions. It means:</p><ul><li>Understanding how today’s decisions affect tomorrow’s constraints</li><li>Designing solutions that are scalable, stable, and evolvable</li><li>Seeing beyond the next release</li></ul><p>A strategically mature designer can:</p><ul><li>Decompose a complex product into smaller, testable increments</li><li>Build roadmaps where each step validates the next</li><li>Anticipate second‑order effects and future edge cases</li></ul><p>Instead of designing only for the next step, they analyze:</p><ul><li>Scalability</li><li>Maintainability</li><li>System consistency</li><li>Long‑term user behavior</li></ul><p>This leads to more robust and defensible design decisions.</p><h3>What Defines a Bad Product Designer?</h3><p>A bad product designer is not defined by lack of talent, but by lack of rigor.</p><p>Common characteristics include:</p><ul><li>Creating without evaluating</li><li>Designing without forming hypotheses</li><li>Ignoring user behavior data</li><li>Treating validation as optional</li></ul><p>Such a designer builds structures without verifying whether they will stand. Their work may look polished, but it lacks evidence.</p><p>The absence of:</p><ul><li>Hypothesis‑driven design</li><li>Behavioral analysis</li><li>Post‑launch evaluation</li></ul><p>results in fragile products and repeated mistakes.</p><h3>What Defines a Good Product Designer?</h3><p>A good product designer operates with discipline.</p><p>They:</p><ul><li>Frame problems before solving them</li><li>Use research and data to inform decisions</li><li>Validate assumptions through testing</li><li>Collaborate effectively with cross‑functional teams</li></ul><p>Good designers reduce risk. They do not rely on intuition alone, but they also do not hide behind data. They balance craft, logic, and evidence.</p><p>However, they may still struggle with ambiguity, conflicting inputs, or high‑stakes decisions.</p><h3>What Defines a Great Product Designer?</h3><p>Great product designers demonstrate mastery in two hard‑to‑measure areas:</p><h3>1. Deep Listening</h3><p>Exceptional designers listen more than they speak.</p><p>They listen to:</p><ul><li>Users</li><li>Stakeholders</li><li>Engineers</li><li>Business constraints</li><li>Signals hidden in data</li></ul><p>Listening enables accurate understanding of the real problem space.</p><h3>2. High‑Quality Decision‑Making</h3><p>Great designers are decisive without being reckless.</p><p>They:</p><ul><li>Absorb diverse and often contradictory opinions</li><li>Apply critical thinking</li><li>Filter noise from signal</li><li>Make clear, defensible decisions</li></ul><p>Decision‑making in design is similar to walking a tightrope: balance is everything.</p><h3>3. Ownership and Defense of Decisions</h3><p>Great designers do not just decide; they <em>stand behind</em> their decisions.</p><p>They can:</p><ul><li>Clearly articulate rationale</li><li>Explain trade‑offs</li><li>Defend choices using evidence and logic</li><li>Change direction when new information emerges</li></ul><p>This combination of humility and conviction is rare and invaluable.</p><h3>Design Maturity Is a Journey</h3><p>Design excellence is not a fixed trait. Designers evolve over time through:</p><ul><li>Exposure to complexity</li><li>Feedback loops</li><li>Failure and reflection</li><li>Systems thinking</li></ul><p>The difference between bad, good, and great designers is not talent alone, but mindset, discipline, and learning velocity.</p><h3>Conclusion</h3><p>A great product designer is not defined by aesthetics, tools, or titles.</p><p>They are defined by their ability to:</p><ul><li>Define the right problems</li><li>Think strategically</li><li>Make and defend high‑quality decisions</li><li>Continuously learn under uncertainty</li></ul><p>In an industry obsessed with outputs, the best designers distinguish themselves through the quality of their thinking.</p><p>#ProductDesign #UXDesign #DesignThinking #ProductStrategy #DesignLeadership #UserCenteredDesign #DesignMaturity #UXResearch #DecisionMaking</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47c6d40fad80" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing an Effective Product Designer Hiring Process]]></title>
            <link>https://medium.com/@hoomanrezvani/designing-an-effective-product-designer-hiring-process-8b90d1b537cf?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b90d1b537cf</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[ux-management]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Fri, 19 Dec 2025 09:09:44 GMT</pubDate>
            <atom:updated>2025-12-19T09:47:42.486Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*14N3NTvSeUDCOi5D-Xvr0g.jpeg" /></figure><p><strong>Why structure matters more than tasks, and how to reduce bias, stress, and false negatives</strong></p><p>Hiring a Product Designer is one of the most complex recruitment processes in modern product teams.<br>Not because designers are “special,” but because the role itself sits at the intersection of multiple disciplines: problem-solving, analytical thinking, communication, visual craft, product reasoning, and stakeholder management.</p><p>From the very first interview to the final decision, candidates are expected to:</p><ul><li>Demonstrate theoretical knowledge</li><li>Solve ambiguous problems</li><li>Explain and justify decisions</li><li>Defend trade-offs</li><li>Persuade others</li><li>And do all of this under high cognitive and emotional pressure</li></ul><p>This environment alone increases the likelihood of error, bias, and false negatives, even when the candidate is highly capable.</p><p>Over the years, companies have adopted a wide range of hiring methods to evaluate Product Designers. There is no single “correct” hiring process, and there shouldn’t be. Each company must tailor its approach based on its maturity, product complexity, team structure, and role expectations.</p><p>That said, not all processes are equally effective.</p><p>In this article, I’ll make the case for a balanced, structured, and pragmatic hiring process grounded in my experience leading interviews (as a lead and consultant) and going through them as a candidate. The goal isn’t perfection, it’s signal quality: extracting meaningful insight while reducing noise, stress, and wasted effort.</p><h3>Common Stages in Product Designer Hiring</h3><p>Most companies rely on some combination of the following steps:</p><ul><li>HR interview</li><li>Hiring Manager interview</li><li>Case study review</li><li>Whiteboard or live problem-solving session</li><li>Take-home assignment</li></ul><p>The problem is not the existence of these steps.<br>The problem is <strong>how they are combined, ordered, and weighted</strong>.</p><p>Below is an optimized sequence that I’ve found to be both effective and respectful, for both candidates and teams.</p><h3>1. HR Interview: Alignment and Reality Check</h3><p>The HR interview is often underestimated, but when done correctly, it is a valuable first filter.</p><p>Its primary purpose should be:</p><ul><li>Verifying alignment between the resume and real experience</li><li>Understanding the candidate’s domain exposure</li><li>Checking expectations around role scope, seniority, and growth</li><li>Assessing communication clarity at a basic level</li></ul><p>This stage is <strong>not</strong> the right moment for deep design-process discussions.<br>Questions like <em>“Walk me through your entire design process”</em> can be postponed. They add little value here and are better handled by the Hiring Manager.</p><p>At this stage, the goal is simple:<br><strong>Does this profile roughly match what we are looking for, and is it grounded in reality?</strong></p><h3>2. Hiring Manager Interview: Lightweight Case Review</h3><p>The second stage should be led by the Hiring Manager and focus on <strong>one selected case</strong> from the candidate’s experience.</p><p>This is not a full portfolio presentation and not a performance show.<br>A single case is enough.</p><p>What this stage evaluates:</p><ul><li>Problem framing and clarity of thinking</li><li>Design decision rationale</li><li>Ability to communicate trade-offs</li><li>General understanding of product constraints</li><li>Collaboration and storytelling skills</li></ul><p>There is no need for a perfectly polished case study.<br>The goal is not aesthetics, but <strong>how the candidate thinks, explains, and reasons</strong>.</p><p>This step alone can eliminate many false positives and false negatives if handled thoughtfully.</p><h3>3. Whiteboard Session: Live Problem Solving with a Cross-Functional Panel</h3><p>A whiteboard session, when done right, is one of the most informative steps in the process.</p><p>The ideal setup includes:</p><ul><li>The Hiring Manager</li><li>One Product Manager</li><li>One Designer</li></ul><p>This is not about arriving at the “correct” solution.<br>There usually isn’t one.</p><p>Instead, it allows the team to observe:</p><ul><li>How the candidate structures ambiguous problems</li><li>How they ask clarifying questions</li><li>How they collaborate in real time</li><li>How they handle feedback and interruptions</li><li>How they balance speed vs depth</li></ul><p>This stage surfaces both <strong>hard skills and soft skills</strong> in a way no static artifact can.</p><h3>4. Take-Home Assignment: Controlled Signal, Not Free Labor</h3><p>Portfolios often fail to show how designers work under real-world constraints.<br>Time pressure, incomplete data, stakeholder limitations, and technical trade-offs rarely appear in polished case studies.</p><p>A well-designed take-home assignment can fill this gap, <strong>if and only if</strong>:</p><ul><li>The scope is limited and respectful</li><li>The task is clearly artificial and non-production</li><li>There is a presentation and defense session afterward</li></ul><p>The real value is not the output, but:</p><ul><li>How the candidate prioritizes</li><li>What assumptions they make</li><li>How they explain compromises</li><li>How they reflect on limitations</li></ul><p>Without a review and discussion, assignments lose most of their value.</p><h3>Final Thoughts</h3><p>There is no universal hiring formula.<br>Different companies, roles, and seniority levels may require different adaptations.</p><p>However, one thing is clear:<br><strong>Case study reviews are not inherently wrong</strong>, but they are rarely sufficient on their own.</p><p>A structured combination of:</p><ul><li>Alignment checks</li><li>Contextual discussion</li><li>Live problem-solving</li><li>Controlled practical tasks</li></ul><p>offers a far more reliable signal than any single method.</p><p>A good hiring process does not try to “trick” designers into proving their worth.<br>It creates the conditions for <strong>clear thinking, fair evaluation, and mutual respect</strong>.</p><p>And in the long run, that benefits both sides.</p><p>#ProductDesign #DesignHiring #UXHiring #ProductDesigner #DesignLeadership #HiringProcess #UXManagement #DesignOps <br>#ProductTeams #EvidenceBasedDesign</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b90d1b537cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why AI Won’t Replace Product Designers (But Will Reshape the Job)]]></title>
            <link>https://medium.com/@hoomanrezvani/why-ai-wont-replace-product-designers-but-will-reshape-the-job-467aec149865?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/467aec149865</guid>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 09:08:57 GMT</pubDate>
            <atom:updated>2025-12-16T09:08:57.523Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0LwEyzVF3Xf0usFmq0uMBw.jpeg" /></figure><p>Almost every product or design event these days circles around the same heated question:<br> <em>Will AI replace product designers?</em></p><p>Speakers usually reach a comforting conclusion.<br> “AI is just a tool.”<br> “At best, an assistant.”<br> “It will never replace us.”</p><p>That answer sounds reassuring. But it skips the most important part: <strong>why</strong>.</p><p>This article reflects my personal perspective. It may be right or wrong, but it is grounded in how product design actually works in practice, not how we wish it worked.</p><p>To reason about this properly, product design needs to be split into two fundamental dimensions:</p><ol><li><strong>Visual and aesthetic design</strong></li><li><strong>Problem-solving and decision-making</strong></li></ol><h3>1. Visual Design: The Inevitable Saturation Problem</h3><p>If AI were to replace designers purely on the visual side, the outcome would be predictable.</p><p>AI models learn by averaging patterns. Even when outputs look “creative,” they are statistically optimized variations of existing work. At scale, this leads to <strong>homogeneity</strong>.</p><p>If AI fully dominated visual design, we would eventually reach a saturation point where interfaces, layouts, and styles feel interchangeable. At that moment, the market would rediscover something it always does:<br> <strong>the value of tailored, context-aware, human-crafted design.</strong></p><p>In other words, the more automated visual design becomes, the more valuable customized and intentional design expertise becomes again.</p><p>AI accelerates production.<br> Humans restore meaning and differentiation.</p><h3>2. Problem-Solving: Where Design Actually Lives</h3><p>The second dimension is where the replacement narrative truly collapses.</p><p>Product designers are not just interface builders. They are problem solvers who continuously balance:</p><ul><li>User behaviors, needs, and pain points</li><li>Business goals and constraints</li><li>Stakeholder interests</li><li>Trade-offs and prioritization</li><li>Roadmaps, sequencing, and incremental delivery</li></ul><p>This type of work is <strong>non-linear</strong>, context-heavy, and often ambiguous.</p><p>AI, even with advanced prompting, still operates largely within linear reasoning frameworks. It can assist with analysis, summarize inputs, and propose options. But it does not <em>own</em> decisions, navigate politics, sense organizational tension, or adapt to incomplete and conflicting information in real time.</p><p>At best, AI becomes a powerful assistant.<br>It does not become the decision-maker.</p><p>There is also a quieter issue that gets overlooked. AI systems are learning systems. If humans only consume outputs without feeding context, critique, and direction back into the system, the learning loop stagnates. The result is not intelligence growth, but repetition.</p><h3>The Real Impact: Speed Changes Markets</h3><p>So no, AI is unlikely to “take” product design jobs outright.</p><p>But ignoring its impact would be equally naive.</p><p>AI dramatically increases execution speed. When speed increases, fewer people are needed to deliver the same output. That inevitably reshapes the job market.</p><p>The shift will not be about eliminating expertise. It will be about:</p><ul><li>Smaller teams</li><li>Broader scopes</li><li>Higher expectations per role</li></ul><p>Specialists and decision-makers will remain essential. Passive executors will struggle.</p><h3>A Necessary (and Messy) Transition</h3><p>One uncomfortable reality remains.</p><p>Many companies will not handle this transition well. They will overreact to the hype, reduce headcount aggressively, and attempt to replace judgment with automation. After the limitations surface, hiring will resume, often painfully and inefficiently.</p><p>This cycle is not new. It is a recurring pattern in every major technological shift.</p><p>What we are experiencing now is not the end of product design.<br> It is a <strong>necessary normalization</strong>.</p><p>A reset of scale, scope, and responsibility.</p><p>And like every reset before it, it will reward those who understand the system, not just the tools.</p><p>#ProductDesign #ArtificialIntelligence #UXDesign #ProductManagement<br> #DesignThinking #AIinDesign #FutureOfWork #TechStrategy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=467aec149865" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product teams and AI Tools: Between blind trust and Blind fear]]></title>
            <link>https://medium.com/@hoomanrezvani/-bf3711f783fd?source=rss-7788676a95b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf3711f783fd</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <dc:creator><![CDATA[Hooman Rezvani]]></dc:creator>
            <pubDate>Sun, 14 Dec 2025 20:50:11 GMT</pubDate>
            <atom:updated>2025-12-14T21:05:35.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d600fAwyE1SGESGDqBwbdQ.png" /><figcaption>Blind trust or Blind fear</figcaption></figure><p>As AI tools continue to multiply, product designers, product managers, and cross-functional teams now have unprecedented access to powerful capabilities. From research synthesis to ideation, prototyping, and even decision support, AI has quietly embedded itself into everyday product work.<br>Yet, when you look closely, teams tend to fall into two very distinct camps.<br>The first group embraces AI almost unconditionally. They rely heavily on its outputs, feel comfortable delegating thinking to tools, and are generally satisfied with whatever comes out. For them, AI represents speed, relevance, and staying “ahead of the curve.”<br>The second group takes the opposite stance. They observe AI outputs with deep skepticism, constantly question the results, and in many cases reject them outright. Nothing the tool produces is ever “good enough.”<br>As with most things in product and technology, the healthiest approach lives somewhere in between.<br>Neither blind trust nor total rejection leads to good outcomes.<br>If we look a bit deeper, both reactions often come from very human motivations.<br>Those who overly rely on AI tools are often driven by the desire to appear up-to-date and competitive in a fast-changing market. They want to signal relevance, adaptability, and modernity. Sometimes, that leads to outsourcing too much judgment to tools instead of using them as support.<br>On the other side, strong resistance to AI is rarely about quality alone. More often, it is rooted in fear. Fear of becoming replaceable. Fear of losing status, expertise, or professional identity. In some cases, ego also plays a role. Accepting that a tool can outperform years of accumulated experience is not easy, and questioning the tool becomes a defense mechanism.<br>Ironically, this second stance is usually the more damaging one.<br>Persistent resistance can slow down product development, create friction within teams, and block experimentation. Over time, it can also leave individuals behind, disconnected from how the industry is actually evolving.<br>From a product perspective, the real risk is not AI adoption. The real risk is refusing to engage with it critically and constructively.<br>Personally, I do not believe AI agents are here to eliminate jobs. Agents will remain agents. They are powerful collaborators, not replacements. Using them intelligently is a sign of maturity for both individuals and organizations. They bring real advantages: speed, scale, and new perspectives.<br>But they are not the whole story.<br>Human judgment, context, ethics, creativity, and responsibility still sit firmly with us. The smartest teams are not those who worship AI, nor those who fight it, but those who know exactly when to trust it, when to challenge it, and when to override it.<br>That balance is quickly becoming a core product skill.<br><a href="https://www.linkedin.com/search/results/all/?keywords=%23productdesign&amp;origin=HASH_TAG_FROM_FEED">hashtag#ProductDesign</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23artificialintelligence&amp;origin=HASH_TAG_FROM_FEED">hashtag#ArtificialIntelligence</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23aiinproduct&amp;origin=HASH_TAG_FROM_FEED">hashtag#AIinProduct</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf3711f783fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>