<?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 Sepanta Pouya on Medium]]></title>
        <description><![CDATA[Stories by Sepanta Pouya on Medium]]></description>
        <link>https://medium.com/@sepantapouya?source=rss-b62141a96f7f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*A2l5V1Z8AsJqoMhrSWGT-A.jpeg</url>
            <title>Stories by Sepanta Pouya on Medium</title>
            <link>https://medium.com/@sepantapouya?source=rss-b62141a96f7f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:11:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sepantapouya/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 Put Away Figma and Started Prototyping with AI]]></title>
            <link>https://medium.com/design-bootcamp/we-put-away-figma-and-started-prototyping-with-ai-51addf2a3046?source=rss-b62141a96f7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/51addf2a3046</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sepanta Pouya]]></dc:creator>
            <pubDate>Mon, 23 Feb 2026 10:53:51 GMT</pubDate>
            <atom:updated>2026-02-23T12:14:18.232Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VbynNoX4pwc468pb3B_yyA.png" /></figure><p>For years, Figma was our default starting point for <em>everything</em> — from messy ideation to polished UI, from “quick prototype” to “please don’t touch this component or the design system will cry.”</p><p>And to be clear: we still respect Figma. It’s a modern classic. Like a really good chef’s knife.</p><p>But here’s the uncomfortable truth we ran into (and maybe you have too):</p><p><strong>We were using a chef’s knife to butter toast.</strong></p><p>At some point, the early-stage prototyping loop started feeling… slow. Not because we became worse designers — but because the world around design shifted. AI didn’t just add a new tool. It changed expectations:</p><ul><li>stakeholders expect <em>more options, faster</em></li><li>teams want to test <em>multiple directions in days, not weeks</em></li><li>product decisions need <em>prototypes that are “real enough”</em> to validate quickly</li><li>and honestly… we got tired of spending brainpower on pixels <strong>before</strong> we were confident about the problem</li></ul><p>So we did something that would’ve sounded unhinged a couple years ago:</p><p><strong>We closed Figma (for early-stage prototyping) and started using AI tools like Manus to generate and iterate on design prototypes.</strong></p><p>And yeah — sometimes the AI-generated designs were better than what we made.</p><p>Not always. Not even most of the time.<br> But often enough to force us to rethink how we work.</p><h3>The Real Reason Figma Started Feeling “Heavy”</h3><p>Figma is incredibly good at what it was built for:</p><ul><li>precise layout</li><li>scalable components</li><li>collaborative design files</li><li>systematized UI production</li><li>handoff</li><li>design ops</li></ul><p>But early-stage prototyping isn’t about precision. It’s about <strong>speed of learning</strong>.</p><p>In the first 20–40% of a project, you don’t need a perfect button radius. You need answers to questions like:</p><ul><li>What’s the simplest flow that solves the user’s problem?</li><li>What’s the quickest way to reduce friction?</li><li>Which concept feels obvious without explanation?</li><li>What interaction model will users <em>understand instantly</em>?</li></ul><p>The issue wasn’t “Figma is bad.”</p><p>The issue was: <strong>Figma’s core workflow still assumes a lot of manual effort to get to something testable.</strong></p><p>Even with templates, libraries, auto-layout, and plugins… the loop often looks like this:</p><ol><li>make a frame</li><li>pick a layout</li><li>place components</li><li>align, nudge, align again</li><li>set up interactions</li><li>realize the idea is wrong</li><li>repeat, but now emotionally attached to your pixel masterpiece</li></ol><p>And that emotional attachment part? That’s the sneaky killer.</p><p>Because when something takes longer to build, you protect it.<br> When something takes 2 minutes to generate, you’re happy to throw it away.</p><p>That shift is massive.</p><h3>As of Right Now, Figma Doesn’t Feel Fully “AI-Native”</h3><p>Let me phrase this carefully: this isn’t a dunk on Figma.</p><p>But <strong>in our day-to-day reality</strong>, Figma hasn’t fully evolved into what you’d expect given the <em>current AI hype cycle</em> and how fast product teams want to move.</p><p>A lot of “AI in design tools” (including in the broader ecosystem) still feels like:</p><ul><li>AI as a feature</li><li>AI as a plugin</li><li>AI as an enhancement</li></ul><p>Whereas what’s happening in practice is:</p><p><strong>AI is becoming the prototyping environment.</strong><br> Not an add-on.</p><p>The big difference is this:</p><ul><li>In Figma, you <em>draw</em> a prototype.</li><li>With AI tools like Manus, you <em>describe intent and constraints</em>… and a prototype appears.</li></ul><p>That sounds like a small UX change. It’s not.</p><p>It changes the cost of exploration. It changes how quickly you can try weird ideas. It changes who can participate (PMs, researchers, founders, even engineers). It changes the entire pace.</p><h3>What Changed When We Started Using AI Prototyping Tools (Like Manus)</h3><p>When we use AI for prototyping, the workflow becomes something like:</p><p><strong>Write the problem clearly</strong></p><ul><li>user goal</li><li>context</li><li>constraints</li><li>success criteria</li></ul><p><strong>Generate multiple UI directions</strong></p><ul><li>different layouts</li><li>different interaction patterns</li><li>different content structures</li></ul><p><strong>Iterate conversationally</strong></p><ul><li>“Make it denser”</li><li>“Move actions to the bottom”</li><li>“Add a review step”</li><li>“Assume the user is in a hurry”</li><li>“Use our brand voice, shorter labels”</li></ul><p><strong>Pick a direction and refine</strong></p><ul><li>fix UX logic</li><li>verify accessibility basics</li><li>ensure content clarity</li><li>align to design system principles</li></ul><p><strong>Only then bring it into Figma</strong> (if needed)</p><ul><li>polish</li><li>components</li><li>handoff specs</li><li>system consistency</li></ul><p>The biggest difference?</p><p><strong>We can explore 15–30 options before lunch without feeling like we wasted a week.</strong></p><p>That means our prototypes aren’t “precious.”<br> They’re disposable learning artifacts — which is exactly what prototypes should be.</p><h3>The Awkward Part: Sometimes the AI Designs Were Better</h3><p>This is the sentence designers hate admitting out loud, because it sounds like you’re saying “AI replaced design.”</p><p>That’s not what’s happening.</p><p>What’s happening is:</p><ul><li>AI can produce <strong>acceptable UI patterns extremely fast</strong></li><li>AI is weirdly good at <strong>layout variations</strong></li><li>AI doesn’t get tired, bored, or overly attached to one direction</li><li>AI will suggest a pattern you didn’t consider because you were trapped inside your team’s “default taste”</li></ul><p>Sometimes, the AI output is better than ours in very specific ways:</p><h3>1) It breaks our “same-same” habits</h3><p>Designers (especially experienced ones) have muscle memory. We reach for the same patterns because they work.</p><p>AI sometimes goes:<br> “Cool, but what if we try a radically different hierarchy?”<br> And annoyingly… it’s sometimes right.</p><h3>2) It explores faster than humans can</h3><p>A designer might sketch 3 variants before getting pulled into meetings.</p><p>AI can generate 12 variants in the time it takes to name a Figma page properly.<br> (And yes, we still name Figma pages like: Exploration v2 FINAL actually final.)</p><h3>3) It makes the tradeoffs visible sooner</h3><p>When you can see 10 options side-by-side, you start noticing:</p><ul><li>what’s consistent</li><li>what’s unclear</li><li>what’s missing</li><li>what feels “obvious”</li></ul><p>That’s product thinking fuel.</p><p><strong>Important note:</strong> “Better” doesn’t mean “ready.”<br> It means “a better starting point than our first draft.”</p><p>And that alone is worth the switch.</p><h3>The Hidden Benefit: We Spend More Time on Decisions, Less on Decoration</h3><p>When AI accelerates the <em>making</em>, the bottleneck moves to the right place:</p><ul><li>problem framing</li><li>user clarity</li><li>content structure</li><li>flow logic</li><li>prioritization</li><li>edge cases</li><li>accessibility</li><li>measurement</li></ul><p>In other words: <strong>actual design.</strong></p><p>Not pixel aerobics.</p><p>AI didn’t remove our job.<br> It removed the busywork that <em>pretended to be</em> our job.</p><h3>But Let’s Not Romanticize It: AI Prototypes Can Also Be Garbage</h3><p>AI-generated design can be:</p><ul><li>too generic (“SaaS dashboard #48”)</li><li>inconsistent in spacing and rhythm</li><li>visually impressive but logically broken</li><li>filled with placeholder content that hides real UX issues</li><li>overly “dribbblized” (pretty… and useless)</li></ul><p>So we added guardrails.</p><h3>Our non-negotiables when prototyping with AI</h3><ul><li><strong>Start with a clear user goal</strong> (not “make a settings page,” but “reduce failed payments”)</li><li><strong>Define constraints upfront</strong></li><li>device</li><li>accessibility requirements</li><li>brand tone</li><li>must-have content</li><li>key actions</li><li><strong>Force realism</strong></li><li>realistic copy</li><li>messy data</li><li>long names</li><li>empty states</li><li><strong>Critique like adults</strong></li><li>“What does this enable?”</li><li>“What does this hide?”</li><li>“Where does this break?”</li><li>“Is it understandable without explanation?”</li></ul><p>AI gives you <em>output</em>.<br> Your team still needs <em>taste, judgment, and accountability.</em></p><h3>When We Still Go Back to Figma (Because We’re Not Monsters)</h3><p>We didn’t delete Figma. We stopped using it as the <strong>first step</strong>.</p><p>We still use Figma when:</p><ul><li>we’re moving from concept → <strong>production-ready UI</strong></li><li>we need <strong>component-level consistency</strong></li><li>we’re updating a <strong>design system</strong></li><li>we need clean <strong>handoff</strong></li><li>we’re doing <strong>detailed interaction design</strong></li><li>we need collaboration at scale with clear source-of-truth files</li></ul><p>Think of it like this:</p><ul><li><strong>AI tools (like Manus)</strong> = exploration engine</li><li><strong>Figma</strong> = refinement + systemization engine</li></ul><p>The real win was separating those stages instead of forcing one tool to do both.</p><h3>What This Means for Designers (The Skill Shift Nobody Talks About)</h3><p>The core skill is shifting from:</p><p><strong>“How fast can you push pixels?”</strong><br> to<br> <strong>“How clearly can you describe intent and constraints?”</strong></p><p>Designers who thrive in this new workflow:</p><ul><li>write better briefs</li><li>define stronger constraints</li><li>know which patterns fit which problems</li><li>can evaluate output quickly</li><li>are comfortable discarding work without ego</li></ul><p>You’re not designing screens anymore.<br> You’re designing <strong>decision space</strong>.</p><p>And honestly? That’s a more senior kind of design.</p><h3>So… Is This the End of Figma?</h3><p>No.</p><p>But it might be the end of <strong>Figma-as-the-default-starting-line</strong> — at least for teams that need rapid prototyping and faster learning loops.</p><p>Right now, with AI accelerating everything, the expectation is no longer:</p><ul><li>“Can we prototype this?”</li></ul><p>It’s:</p><ul><li>“How many directions can we test this week?”</li></ul><p>And when that’s the game, using Figma first can feel like putting on a tuxedo to go jogging.</p><p>Looks great. Wrong activity.</p><h3>Closing Thought</h3><p>We didn’t “replace” Figma with AI.</p><p>We replaced a habit:<br> <strong>starting with pixels before we had clarity.</strong></p><p>AI prototyping tools like Manus helped us move faster, explore more, and stay less attached to our first idea.</p><p>And yes — sometimes the AI designs were better.</p><p>Not because AI is a better designer.<br> But because speed gives you freedom, and freedom gives you better options.</p><p>If you’re still starting every new idea inside a blank Figma frame… try flipping it:</p><p>Start with the prompt. Start with constraints. Start with intent.<br> Then bring the winner into Figma when it deserves the polish.</p><p>Your future self (and your wrist) will thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51addf2a3046" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/we-put-away-figma-and-started-prototyping-with-ai-51addf2a3046">We Put Away Figma and Started Prototyping with AI</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[What 400+ Hours of UX Mentoring Taught Me (That No Course Trailer Will Tell You)]]></title>
            <link>https://medium.com/design-bootcamp/what-400-hours-of-ux-mentoring-taught-me-that-no-course-trailer-will-tell-you-55b48f73b1e8?source=rss-b62141a96f7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/55b48f73b1e8</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[sepanta-pouya]]></category>
            <category><![CDATA[mentor]]></category>
            <category><![CDATA[mentee]]></category>
            <dc:creator><![CDATA[Sepanta Pouya]]></dc:creator>
            <pubDate>Sat, 25 Oct 2025 14:16:56 GMT</pubDate>
            <atom:updated>2025-10-25T15:39:48.672Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K30rqeeJNTv0EhTGrW5wJQ.png" /></figure><p><em>By Sepanta Pouya — Product Designer &amp; UX mentor who drinks cold coffee on purpose (fine… by accident).</em></p><p>If you’re here hoping I’ll tell you <strong>exactly</strong> how many hours it takes to break into UI/UX, let me disappoint you early: I can’t. And neither can anyone else who isn’t guessing or selling you a dream.</p><p>After 400+ hours of 1:1 mentoring, portfolio reviews, and “is this good enough?” DMs at 2 a.m., I’ve learned a few truths. They’re not shiny. They don’t fit nicely into a TikTok. But they’re real, and they work.</p><p>Here are the seven lessons I keep returning to — sprinkled with a pinch of humor, a lot of honesty, and some concrete ways to put them into action. And this time, I’m adding an <strong>eighth</strong> that hiring managers wish more people understood.</p><h3>1) I can’t tell you how many hours you need. No one can.</h3><p><strong>Why:</strong> People aren’t templates. Your background, learning pace, time, market, language, portfolio evidence, and network all change the equation. A former visual designer with strong craft but weak research will progress differently than a data analyst who interviews like a pro but struggles with layout. Hours don’t hire you. <strong>Competence + evidence</strong> do.</p><p><strong>Try this instead of hour-counting:</strong></p><ul><li><strong>Skills scoreboard (update weekly):</strong></li><li><strong>Research:</strong> plan interviews, conduct 5, synthesize findings.</li><li><strong>Product thinking:</strong> problem framing, metrics, trade-offs.</li><li><strong>Interaction &amp; UI:</strong> layout, hierarchy, typography, states, accessibility.</li><li><strong>Prototyping:</strong> clickable flows that tell a story.</li><li><strong>Collaboration:</strong> crisp documentation, dev handoff, feedback etiquette.</li><li><strong>Evidence:</strong> case studies that show decisions, not just screenshots.</li></ul><p><strong>Milestone checkpoints:</strong></p><ul><li><em>Bronze:</em> one real-ish problem → one usable flow.</li><li><em>Silver:</em> a complete problem framing → research → prototype → test loop.</li><li><em>Gold:</em> two end-to-end case studies with measurable impact or clear rationale.</li></ul><p>Hours are a vanity metric; outcomes are the hiring metric.</p><h3>2) People who crave super‑rapid outcomes often get passed by the ones who focus on doing good work.</h3><p>There’s a difference between <strong>moving fast</strong> and <strong>trying to fast‑forward the hard parts</strong>. The former is about tight feedback loops. The latter is skipping fundamentals and hoping LinkedIn notices.</p><p>I’ve watched “speedrunners” burn out at the portfolio stage while steady learners quietly build solid case studies and leap ahead. The market rewards <strong>clarity, craft, and judgment</strong> — not the ability to replicate a flashy Dribbble in 48 hours.</p><p><strong>Design for speed <em>and</em> depth:</strong></p><ul><li><strong>Small loops, real stakes:</strong> scope tiny problems and complete them end‑to‑end (frame → design → test → iterate).</li><li><strong>Time‑box learning, not quality:</strong> “90 minutes to explore 2 approaches,” then spend the time you need polishing the one that matters.</li><li><strong>Ship with receipts:</strong> every artifact gets a “why this, not that” note.</li></ul><p>Fast is fine. <strong>Shallow isn’t.</strong></p><h3>3) No one — no course, no mentor (including me) — can guarantee you’ll land the job.</h3><p>If someone offers a guarantee, check your wallet.</p><p>Hiring is a combination of <strong>skill × story × evidence × timing × luck</strong>. I can help with the first three and improve your odds on the fourth. The fifth is called life.</p><p><strong>What I <em>can</em> promise:</strong></p><ul><li>Uncomfortable honesty about your current level.</li><li>A path to build work that stands up to critique (not just praise).</li><li>Better interviews through clearer thinking and artifacts.</li></ul><p><strong>What you should demand (from any mentor or course):</strong><br> Transparent expectations. Real feedback. No fairy dust.</p><h3>4) Everyone has their own story — so your learning has to be customized.</h3><p>I’ve mentored people shifting from graphic design, psychology, customer support, engineering, and “I took a course and now I’m panicking.” They do <strong>not</strong> need the same plan.</p><p><strong>Build your Personal Learning Canvas:</strong></p><ul><li><strong>Starting point:</strong> what you already do well (be specific).</li><li><strong>Constraints:</strong> time per week, languages, tools, geography.</li><li><strong>Aspirations:</strong> role target + company archetype (early-stage? agency? enterprise?).</li><li><strong>Gaps:</strong> top 3 skills holding you back (validated by critique, not vibes).</li><li><strong>Projects:</strong> 2–3 scoped problems mapped to those gaps.</li><li><strong>Evidence plan:</strong> what artifact proves each skill? (e.g., research plan, insights, flow diagram, prototype, usability findings)</li><li><strong>Feedback loop:</strong> who will review and when (mentor, community, hired designers)?</li><li><strong>Checkpoint dates:</strong> set them; treat them like client deadlines.</li></ul><p>Your story is not a detour. It’s your differentiation — <strong>if</strong> your portfolio shows how it changes your decisions.</p><h3>5) Every session is a challenging learning session for me too.</h3><p>Surprise: mentoring isn’t a monologue. It’s a mirror. Every time we work through a flow, a sticky stakeholder story, or a tricky research plan, <strong>I learn</strong> — about your constraints, the market, and my own blind spots.</p><p><strong>What that means for you:</strong></p><ul><li>Expect questions — lots of them. Socratic, annoying, effective.</li><li>If I don’t know, I’ll say so — and we’ll find out together.</li><li>I’ll adapt. If a framework isn’t clicking, we’ll replace it, not force it.</li></ul><p>Mentoring done right is <strong>co‑design</strong>: we design your path, and I sharpen my craft alongside you.</p><h3>6) Being truly empathetic is hard — and necessary.</h3><p>Real empathy isn’t nodding while you spiral. It’s listening, <strong>understanding your constraints</strong>, and still telling you the uncomfortable truth kindly.</p><p>Sometimes empathy means saying:</p><ul><li>“This case study needs to be cut in half and made clearer.”</li><li>“You’re practicing tools, not design.”</li><li>“You’re underestimating the testing step.”</li><li>“You’re doing great — don’t move the goalposts today.”</li></ul><p><strong>How I practice empathy with backbone:</strong></p><ul><li><strong>Paraphrase first:</strong> “Here’s what I’m hearing…”</li><li><strong>Name the trade‑off:</strong> quality vs. speed, breadth vs. depth.</li><li><strong>Offer a choice:</strong> two viable next steps; you pick.</li><li><strong>Set boundaries:</strong> hustle is good; burnout isn’t a portfolio piece.</li></ul><h3>7) I empathize deeper with problems I’ve lived.</h3><p>I connect fastest with mentees facing familiar dragons: portfolio paralysis, feedback whiplash, imposter syndrome, stakeholder pushback, “how do I tell a business story in my case study?” If I’ve wrestled it, I can probably help you shortcut it.</p><p>When your challenge sits outside my lane, I’ll say so — and point you to sharper resources rather than bluff. That’s still empathy; it’s just <strong>honest</strong> empathy.</p><h3>8) Hiring managers are experts. They spot lies and copy‑pasted case studies quickly — and you’ll get rejected.</h3><p><strong>The people who hire you have done the job.</strong> They’ve shipped releases at 2 a.m., defended trade‑offs to executives, and survived design‑dev handoffs that felt like a reality show. They can sniff out inauthentic case studies like a barista can smell burnt espresso.</p><p><strong>What gets you rejected fast:</strong></p><ul><li><strong>Fabricated research:</strong> surveys with suspiciously round numbers, “5 interviews” with zero quotes or raw notes.</li><li><strong>Time‑traveling process:</strong> claiming <em>research → ideation → test</em> when your Figma history clearly shows <em>UI first, research never</em>.</li><li><strong>“Vice‑versa” storytelling:</strong> reverse‑engineering a narrative to make your final design look inevitable, while evidence says otherwise.</li><li><strong>Metric magic:</strong> “+200% conversion” with no baseline, no timeframe, no source.</li><li><strong>Full copy/paste:</strong> visual twins of popular Dribbble shots or someone else’s case study structure — down to their typos.</li><li><strong>Context-free polish:</strong> stunning mockups, zero constraints, no edge cases.</li></ul><p><strong>How hiring teams detect it (and they <em>will</em>):</strong></p><ul><li><strong>Probing follow‑ups:</strong> “Show me the messy middle,” “Open your Figma file,” “Walk me through the decision we <em>didn’t</em> take and why.”</li><li><strong>Artifact checks:</strong> raw interview notes, task lists, issue logs, version history. (Figma is a polygraph with a timeline.)</li><li><strong>Constraint sniff test:</strong> does your solution reflect platform rules, accessibility, technical limits, and business goals — or is it purely aesthetic?</li><li><strong>Consistency tests:</strong> does your story align across your résumé, portfolio, and how you talk? Inconsistency = 🚩.</li></ul><p><strong>Do this instead (a.k.a. how to be un-copyable):</strong></p><ul><li><strong>Label clearly:</strong> <em>self‑initiated</em>, <em>concept</em>, or <em>production</em>. Transparency builds trust.</li><li><strong>Credit inspiration:</strong> “Layout inspired by X; adapted to Y constraint.”</li><li><strong>Show the receipts:</strong> include a few real artifacts — sticky notes, flow charts, test findings, even a rejected option with your rationale.</li><li><strong>Own your limits:</strong> “I ran 3 interviews (not 30). Here’s why, and what I’d do next.”</li><li><strong>Tell the trade‑offs:</strong> what you <em>didn’t</em> build and why; risks you accepted; metrics you wish you had.</li><li><strong>Respect NDAs:</strong> anonymize properly, focus on decisions and process, not proprietary screens.</li></ul><p><strong>A quick “Truth &gt; Polish” checklist:</strong></p><ul><li>Can I show one messy artifact per stage?</li><li>Do my decisions tie to evidence (user need, metric, constraint)?</li><li>Did I clearly label scope and context?</li><li>Could I recreate this work live for an hour and tell the same story?</li><li>Have I credited influences and collaborators?</li></ul><p>Remember: authenticity isn’t a vibe; it’s <strong>verifiable</strong>.</p><h3>Signals that You’re Ready (and Red Flags)</h3><p><strong>Green flags:</strong></p><ul><li>You can explain a design decision without saying “because it looks cleaner.”</li><li>You can run a basic research cycle without freezing.</li><li>Your prototype feels intentional, not accidental.</li><li>Your case study fits on a phone without losing the plot.</li><li>You can describe impact or trade‑offs even if you lack production metrics.</li></ul><p><strong>Red flags:</strong></p><ul><li>You “redesigned” products you don’t understand.</li><li>You learned Figma but not design.</li><li>Your case studies are galleries, not arguments.</li><li>You chase badges/certificates instead of feedback.</li><li>You ask for a guarantee (see Lesson 3).</li><li>You treat “inspiration” as Ctrl+C / Ctrl+V.</li></ul><h3>How to Get the Most from a Mentor (Including Me)</h3><ol><li><strong>Bring the mess.</strong> Half‑formed flows, awkward notes, ugly drafts welcome.</li><li><strong>Ask sharper questions.</strong> “Which of these 2 options better serves this constraint and why?”</li><li><strong>Track your deltas.</strong> What changed since last session? Show the receipts.</li><li><strong>Protect the practice.</strong> Block calendar time like it’s a paying client.</li><li><strong>Own your story.</strong> We refine it together, but it has to be yours.</li></ol><p><strong>What I bring:</strong></p><ul><li>Feedback that’s specific, kind, and occasionally spicy.</li><li>Frameworks you can reuse — not templates you can memorize.</li><li>A bias toward evidence and craft.</li><li>Zero hype, zero guarantees, 100% partnership.</li></ul><h3>TL;DR (because, life)</h3><ul><li>I can’t estimate your hours to “get in.” No one credible can.</li><li>Chasing speed alone backfires. Doing good work wins.</li><li>No course or mentor can guarantee a job. Run from anyone who says otherwise.</li><li>Your path must be customized to your story and constraints.</li><li>I learn every session too — and that’s a feature, not a bug.</li><li>Empathy matters, especially when it’s paired with candor.</li><li>I empathize strongest where I’ve been. For the rest, I’ll point you to the right help.</li><li><strong>Hiring managers are experts.</strong> Lies, reversed narratives, and copy‑pasted case studies are easy to spot — and a fast pass to rejection.</li></ul><p>If this resonates and you want to build a portfolio that argues, not just decorates, I’m here to help you think clearly, design intentionally, and tell your story like a designer — not a brochure.</p><p>— <strong>Sepanta</strong></p><p><em>Explore my work and philosophy:</em> <strong>sepantapouya.com</strong><br> <em>Say hi on LinkedIn:</em> <strong>linkedin.com/in/sepantapouya</strong></p><p><em>(P.S. I will never ask you to buy a magic course. I might ask you to run five usability tests. Same thing, but cheaper.)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55b48f73b1e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/what-400-hours-of-ux-mentoring-taught-me-that-no-course-trailer-will-tell-you-55b48f73b1e8">What 400+ Hours of UX Mentoring Taught Me (That No Course Trailer Will Tell You)</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[Why I Came Back to the Company I Left a Year Ago — and Why It Feels Like the Boldest Move Yet]]></title>
            <link>https://sepantapouya.medium.com/why-i-came-back-to-the-company-i-left-a-year-ago-and-why-it-feels-like-the-boldest-move-yet-168dc7d0138b?source=rss-b62141a96f7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/168dc7d0138b</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[company]]></category>
            <dc:creator><![CDATA[Sepanta Pouya]]></dc:creator>
            <pubDate>Tue, 03 Jun 2025 05:41:33 GMT</pubDate>
            <atom:updated>2025-06-03T05:41:33.592Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why I Came Back to the Company I Left a Year Ago — and Why It Feels Like the Boldest Move Yet</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ND083RauCTowydDCD9BY0w.png" /></figure><p>One year ago, I packed up my digital sketchbooks, hugged my Figma files goodbye, and left Partnerz — the company I had been with for 2 years and 3 months — to pursue something new. A new challenge. A new culture. A new version of myself.</p><p>Today, I’m writing this with a grin, a slightly fuller beard, and a lot more life experience. Because yes, I’m back at Partnerz. And no, it’s not a tale of “oops, I made a mistake.” It’s the story of a transformation — personal, professional, and philosophical.</p><p>Let’s rewind.</p><h3>Chapter 1: The Departure — A Designer’s Need to Roam</h3><p>When I left Partnerz, it wasn’t out of frustration or fatigue. It was curiosity. I wanted to explore what was out there. I was craving the raw, unsanitized chaos of the startup world — the kind where your product may or may not exist next week and your salary is either paid or… sent to the metaverse for safekeeping.</p><p>So, I joined <strong>Pattern</strong> — a startup with its toes dipped in both <strong>web3 and AI</strong>. And let me say this clearly:<br> 👉 <strong>It was a great move.</strong><br> Sure, it was chaotic. Sure, it tested every nerve. But I <strong>learned more in that year than some people learn in five</strong>.</p><p>At Pattern, I wasn’t just a designer. I was <em>the</em> designer. Head of Design? Yes. But also: logo whisperer, UX researcher, UI polisher, Notion janitor, and occasional therapist to broken roadmaps. We worked on projects like <em>Soniva.ai</em>, <em>Pattern Flow</em>, <em>FaceDancer</em>, and more — all brave, ambitious, and ultimately, mostly dead.</p><p>But the point wasn’t the outcome — it was the ride. I explored what it meant to be a <strong>Swiss Army knife</strong> for all things design. I even dipped my toe into product management, which came with its own adrenaline — and its own <a href="https://sepantapouya.medium.com/two-months-of-pure-adrenaline-how-stepping-into-product-leadership-reshaped-my-design-journey-8e1cfac54d4d">Medium article</a>.</p><p>In short, Pattern pushed me. It stretched my thinking. It made me more resilient, more resourceful, and a hell of a lot more humble. It was the startup experience I didn’t know I needed — and I’m incredibly grateful for it.</p><h3>Chapter 2: A Product Designer in Existential Crisis (with a Burned-Out MacBook)</h3><p>Startups are romantic — on pitch decks. In reality, they’re raw, uncertain, and often underfunded. One month we had budget to onboard freelancers; the next, we were splitting ramen noodles on Slack.</p><p>At some point, I wasn’t just designing for users. I was designing around survival. That adrenaline rush? It eventually morphed into chronic stress. And the rebellious, wild and bold version of Sepanta started to crave something radical: <strong>stability</strong>.</p><p>Not stagnation. <strong>Growth</strong>. But the kind that doesn’t come with weekly existential dread.</p><h3>Chapter 3: A Change in Perspective (and Personality)</h3><p>I used to think growth only came from jumping into the unknown. But over the past year, I’ve realized growth can also come from going deeper, not just wider.</p><p>From building with people who challenge you <em>and</em> support you.</p><p>From shipping things that don’t get buried under pivots and Post-its.</p><p>From having a vision, not just a pitch.</p><p>I started to crave:</p><ul><li>Strategic mentorship.</li><li>Clear product goals.</li><li>A team that values design as a driver, not decoration.</li><li>And yes… a monthly salary that doesn’t need a crypto wallet to access.</li></ul><h3>Chapter 4: Coming Back Isn’t Weak — It’s a Power Move</h3><p>So here I am. Back at Partnerz.</p><p>Older? Yep. Wiser? Absolutely.<br> Still using dark mode in everything? Of course.</p><p>But more than that — I’m coming back with a new perspective. Not as the same designer who left. As someone who’s led, failed, shipped, pivoted, burned out, rebuilt, and now returns with hunger for <strong>impact</strong>.</p><p>Partnerz is not the same either. The team has evolved. The vision is sharper. And there’s space for me to grow — as a senior product designer, as a leader, and as a human who still gets nerdy over good microcopy.</p><h3>Chapter 5: What’s Next?</h3><p>I’m not here just to <em>resume</em> what I was doing.</p><p>I’m here to:</p><ul><li>Bring in everything I’ve learned from being a one-person design army.</li><li>Share leadership and mentorship lessons from wearing too many hats.</li><li>Co-create a more resilient, scalable design culture.</li><li>And of course, continue growing. Personally. Professionally. Pixel-by-pixel.</li></ul><p>Because sometimes the bravest thing isn’t leaving to explore. It’s coming back to build — stronger, more grounded, and ready to design with deeper intention.</p><h3>Final Thought</h3><p>Leaving was necessary. Failing was educational. Pattern was a wild and wonderful detour.<br> <strong>Coming back?</strong> That was strategic.</p><p>So if you’ve ever thought about going back to a company you once left, don’t see it as retreat. See it as <strong>re-entry</strong> — with more velocity, more vision, and (hopefully) fewer broken prototypes.</p><p>Let’s build something beautiful again.</p><p>— <br> <strong>Sepanta Pouya</strong><br> Senior Product Designer | Mentor | Ex-Jr Product Manager (by accident)<br> <a href="https://sepantapouya.com/">sepantapouya.com</a> | <a href="https://www.linkedin.com/in/sepantapouya">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=168dc7d0138b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Two Months of Pure Adrenaline: How Stepping into Product Leadership Reshaped My Design Journey]]></title>
            <link>https://medium.com/design-bootcamp/two-months-of-pure-adrenaline-how-stepping-into-product-leadership-reshaped-my-design-journey-8e1cfac54d4d?source=rss-b62141a96f7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e1cfac54d4d</guid>
            <category><![CDATA[soniva]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[cpo]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sepanta Pouya]]></dc:creator>
            <pubDate>Sun, 30 Mar 2025 13:45:09 GMT</pubDate>
            <atom:updated>2025-03-31T05:02:25.834Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Homw93Q8xYZ44782k-P5Q.png" /></figure><p>I’ve spent the last <strong>6+ years</strong> proudly wearing my <strong>Senior Product Designer</strong> badge, but these past two months? They’ve been unlike anything I’ve ever experienced. My role suddenly expanded far beyond crafting user flows and perfecting pixels. Suddenly, I found myself helping to steer the <strong>Soniva</strong> ship at a more strategic level — juggling product roadmaps, diving into code reviews, and living in a never-ending Slack ping-pocalypse.</p><p>And let me tell you: once you see what happens behind the curtain, it’s impossible to go back to being “just a designer.” Ready for the juicy details? Buckle up.</p><h3>Chapter 1: A Designer’s Heart Meets Product Leadership</h3><p><strong>Soniva</strong>, in case you’ve missed my previous ramblings, is our voice-first platform that lets users fill out surveys by simply talking — like a friendly chit-chat instead of those tedious, text-based forms. I used to be laser-focused on making the experience delightful and intuitive. Then, I started getting pulled into bigger questions:</p><ul><li><em>Which features should we prioritize first?</em></li><li><em>How can we balance speed vs. quality?</em></li><li><em>Is that Discord notification going to ruin my dinner plans?</em> (Yes. Yes, it did.)</li></ul><p>Shifting into this more expansive role felt like moving from being a painter to suddenly curating an entire exhibit — exciting, overwhelming, and downright exhausting.</p><h3>Empathy, Amplified</h3><p>As a designer, empathy for users is second nature. But when I started influencing product strategy, empathy needed to extend to everyone: like the devs squashing bugs at midnight. It was like learning a new language — one part business-speak, one part diplomacy, and one part Discord memes.</p><p><strong>Big Lesson</strong>: Every decision ripples through multiple team members , shaping not just a single screen but the entire product journey.</p><h3>Chapter 2: Embracing the Chaos (and All Those Discord Pings)</h3><h3>Micromanagement — From Both Sides</h3><p>I’d be lying if I said I always handled the pressure with Zen-like calm. Deadlines loomed, the Discord notifications went <em>ping</em> every two seconds, and I’d hover over tasks, occasionally double-checking everything. Meanwhile, higher-ups also hovered over <em>me</em> — hungry for daily updates or last-minute changes.</p><p>At one point, I joked that I’d change my Discord status to “Haunted by Feature Creep,” but I realized some jokes are just too close to reality.</p><p><strong>Why It Mattered</strong>: Balancing communication and trust is crucial. The team deserves space to innovate, but stakeholders deserve transparency. Discord turned into both our lifeline <em>and</em> our biggest distraction — it’s all about learning when to respond and when to, you know, breathe.</p><h3>Chapter 3: Design Debt, Tech Debt, and the Weird Joy of Code Reviews</h3><p>In the midst of orchestrating tasks, I found myself doing something <em>wildly</em> outside my comfort zone: <strong>peeking at actual code.</strong> Typescript, to be exact. Yes, the funny brackets, weird error messages, and occasionally hair-pulling syntax.</p><blockquote><em>“But you’re a </em><strong><em>UX</em></strong><em> person,” they said.<br> “Why do you need to know code?” they asked.</em></blockquote><p>Well, guess what? <strong>Understanding code</strong> helped me see the bigger picture — how the dev team thinks, why certain changes take longer, and how to reduce “design debt” by coordinating with them upfront.</p><ul><li><strong>Tech Debt</strong>: Devs sometimes skip perfect refactoring or quick fixes to meet deadlines, accruing a backlog of issues.</li><li><strong>Design Debt</strong>: We designers do the same when we leave inconsistent layouts, unpolished components, or half-baked prototypes.</li><li><strong>Code Reviews</strong>: Occasionally, I’d step in to see if my designs could be <em>easily</em> integrated — or if I was accidentally suggesting a feature that’d require a complete code overhaul. Spoiler: I definitely suggested a few of those.</li></ul><p><strong>Pro Tip</strong>: As I often tell fellow UX designers, <strong>learning how coders work — and how code actually functions — makes you infinitely more valuable</strong>. You’ll know what’s feasible (and what might make your dev team cry).</p><h3>Chapter 4: The Emotional Highs (and Near-Breaking Points)</h3><p>There’s something uniquely stressful about a new Discord message appearing every five minutes, each one potentially signaling a bug, a deadline shift, or a last-minute pivot. But amidst the chaos, there were brilliant moments:</p><ul><li><strong>Team Triumphs</strong>: Watching devs fix a nasty issue without missing a beat kept me inspired.</li><li><strong>Bonding Over Pressure</strong>: Late-night Discord banter, inside jokes about CSS breakpoints, and the mutual sigh of relief when a sprint ended successfully.</li></ul><p><strong>Moral</strong>: Stress can be a catalyst for unity. Sharing the load fosters an almost familial vibe — like we’re in this big, messy quest together.</p><h3>Chapter 5: Soniva’s Big Leap Forward</h3><p>It wasn’t all frantic Discord chatter. The team rallied to release a <strong>new, improved Soniva</strong> that left me beaming:</p><ol><li><strong>Pricing Model</strong>: We introduced flexible tiers, so whether you’re a solo entrepreneur or a giant enterprise, there’s a plan that fits your needs and budget.</li><li><strong>Enhanced Analytics</strong>: We now <strong>map questions and answers together</strong>, so you don’t have to slog through entire transcripts to grasp user insights. Think of it like a handy summary that highlights key points from each user session.</li><li><strong>Upgraded Q&amp;A Flow</strong>: Voice interactions now feel more natural, as if you’re chatting with a friend who asks just the right follow-up questions.</li><li><strong>Refined UI</strong>: Despite some lingering design debt, we polished core elements enough to provide a cohesive, user-friendly vibe.</li></ol><h3>Chapter 6: The Journey Continues (No, I’m Not Just a Designer Anymore)</h3><p>So here’s the plot twist: <strong>I’m still very much involved</strong> in product leadership. My official title might say “Senior Product Designer,” but the responsibilities and scope I’ve taken on go well beyond pixel-tweaking(Wait! who really cares about your title? Hoom?.. Title is not as important as how you are performing at that title). I’m deep in product strategy, people coordination, Slack wrangling, and yep, still occasionally scanning Typescript code.</p><ul><li><strong>Strategic Influence</strong>: Every design I propose now considers timeline feasibility, dev effort, and business impact.</li><li><strong>Inter-Team Synergy</strong>: I’ve built trust with devs by speaking their language — at least enough to understand their constraints.</li><li><strong>Future Vision</strong>: My brain is no longer just on the current sprint; it’s thinking six months ahead for Soniva.</li></ul><p><strong>Key Insight</strong>: Once you see the underlying architecture — code, business logic, user psychology — you can never go back to a small silo. And honestly, that’s a <em>great</em> thing.</p><h3>Chapter 7: A Personal Invite — Try Soniva Yourself!</h3><p>If you’ve read this far, you deserve a treat (and maybe a nap). Head over to <a href="https://soniva.ai/"><strong>Soniva.ai</strong></a> to witness our voice-driven survey magic in action. As a thank-you, I’ve got something special for you:</p><ul><li><strong>Code “HiMedium”</strong>: Grab <strong>30% off for 3 months</strong> if you’re up for a smarter way to collect user feedback. And yes, this is our way of saying, “We appreciate that you stuck around through all the Slack saga stories.”</li></ul><p>Trust me: once you try speaking your survey responses, typing them out will feel like a chore.</p><h3>Epilogue: Embrace the Unknown (And Keep Coding on the Side)</h3><p>My journey has been a wild mix of design, leadership, frantic Discord messages, and Typescript revelations. It hasn’t been easy, but it’s been incredibly rewarding — opening my eyes to the <em>entire ecosystem</em> that underpins a successful product.</p><p>So if you’re a designer curious about the broader world of product management — or if you’re already knee-deep in Discord notifications — remember this: <strong>Dive into the messy stuff</strong>. Learn how developers think, skim some code, and see how every cog fits into the machine. Because ultimately, it’ll make your work stronger, your team happier, and your product shine.</p><p><strong>Here’s to new challenges</strong>, continuous learning, and the unending quest to make technology more human — one voice-driven survey at a time.</p><p><em>Written by: </em><strong><em>Sepanta Pouya</em></strong><em>, a Senior Product Designer (and part-time Product Strategist, Typescript Wanderer, Slack Jester) who believes in the power of empathy, good humor, and code-savviness to transform how we build products. This articles has been written by the help of ChatGPT</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e1cfac54d4d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/two-months-of-pure-adrenaline-how-stepping-into-product-leadership-reshaped-my-design-journey-8e1cfac54d4d">Two Months of Pure Adrenaline: How Stepping into Product Leadership Reshaped My Design Journey</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[by The Empathy Trap: Navigating the Emotional Challenges of Being a UX Designer]]></title>
            <link>https://medium.com/design-bootcamp/by-the-empathy-trap-navigating-the-emotional-challenges-of-being-a-ux-designer-e2043f8399e5?source=rss-b62141a96f7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2043f8399e5</guid>
            <category><![CDATA[sepanta]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[pouya]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Sepanta Pouya]]></dc:creator>
            <pubDate>Sat, 18 Jan 2025 07:16:44 GMT</pubDate>
            <atom:updated>2025-01-18T11:06:57.062Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Empathy Trap: Navigating the Emotional Challenges of Being a UX Designer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p9XX3LPViaS5Dusq9unTAg.png" /></figure><p>In the realm of User Experience (UX) design, empathy is heralded as an essential skill. It allows designers to understand and anticipate users’ needs, frustrations, and desires, leading to more intuitive and effective products. However, while empathy is invaluable in a professional setting, its pervasive presence in a UX designer’s personal life can have unintended consequences. This article delves into the often-overlooked downsides of empathy for UX designers outside the workplace, exploring how excessive empathy can lead to emotional fatigue, strained relationships, and other challenges. More importantly, it offers strategies to maintain a healthy balance between professional empathy and personal well-being.</p><h3>The Role of Empathy in UX Design</h3><p>Empathy is the cornerstone of effective UX design. It enables designers to:</p><ul><li><strong>Understand User Needs:</strong> By putting themselves in users’ shoes, designers can identify and prioritize features that truly matter.</li><li><strong>Enhance User Journeys:</strong> Empathy helps in creating seamless and intuitive interactions that resonate with users.</li><li><strong>Drive Innovation:</strong> Understanding users’ pain points fosters the creation of innovative solutions that address real problems.</li></ul><p>Without empathy, UX design would lack the depth and relevance necessary to create meaningful user experiences. However, the same empathetic skills that make designers effective at their jobs can also permeate their personal lives in ways that may not always be beneficial.</p><h3>The Hidden Downsides of Empathy for UX Designers</h3><h3>1. Emotional Fatigue and Burnout</h3><p>Empathy requires significant emotional investment. When UX designers extend their empathetic engagement beyond professional boundaries, it can lead to emotional fatigue or burnout. Constantly tuning into others’ emotions — whether it’s friends’ personal struggles or family members’ concerns — can deplete a designer’s emotional reserves, leaving them exhausted and less effective both personally and professionally.</p><p><strong>Example:</strong> After a long day of user research and problem-solving at work, a UX designer might find themselves exhausted from listening to a friend’s ongoing relationship issues, leading to diminished energy and increased stress.</p><h3>2. Blurred Boundaries Between Personal and Professional Life</h3><p>Empathetic designers often struggle to maintain clear boundaries between their work and personal lives. The skills that make them adept at understanding users can inadvertently make them the “go-to” person for emotional support among friends and family. This blurring of roles can create tension and reduce the time and energy available for self-care and personal interests.</p><p><strong>Example:</strong> A UX designer may find that friends consistently seek their advice on personal matters, expecting the same level of insight and support that they provide to users, thereby encroaching on their personal time and space.</p><h3>3. Over-Involvement and Emotional Overload</h3><p>Excessive empathy can lead to over-involvement in others’ problems. UX designers might find themselves taking on others’ emotions as their own, which can compromise their ability to maintain a healthy emotional balance. This emotional overload can affect their mental well-being and diminish their capacity to perform effectively in both personal and professional settings.</p><p><strong>Example:</strong> If a close friend is experiencing anxiety, a highly empathetic UX designer might not only support them but also begin to feel anxious themselves, impacting their overall mental health.</p><h3>4. Decision Paralysis from Too Many Perspectives</h3><p>Empathy involves considering multiple perspectives, which is beneficial in design but can be detrimental in personal decision-making. UX designers might struggle to make choices that prioritize their own needs because they are overly concerned with how decisions will affect others. This can lead to indecision, frustration, and reduced personal fulfillment.</p><p><strong>Example:</strong> Choosing a vacation destination becomes challenging for a UX designer who feels obligated to accommodate everyone’s preferences, resulting in stress and a lack of enjoyment from the trip.</p><h3>Strategies for Balancing Empathy and Personal Well-Being</h3><p>While empathy is a vital asset in UX design, maintaining a balance is crucial to prevent its negative impact on personal life. Here are strategies to help UX designers manage their empathetic tendencies effectively:</p><h3>1. Establish Clear Boundaries</h3><p>Setting boundaries is essential to protect emotional energy. Clear boundaries help delineate when to engage empathetically and when to step back, ensuring that personal well-being is not compromised.</p><p><strong>Practical Steps:</strong></p><ul><li><strong>Define Personal Time:</strong> Allocate specific times for self-care and personal activities without interruptions.</li><li><strong>Learn to Say No:</strong> Politely decline requests for emotional support when you need a break.</li><li><strong>Clarify Roles:</strong> Communicate with friends and family about when you can offer support and when you need to focus on yourself.</li></ul><h3>2. Prioritize Self-Care</h3><p>Engaging in regular self-care activities replenishes emotional reserves and maintains mental health, enabling sustained empathy without burnout.</p><p><strong>Self-Care Practices:</strong></p><ul><li><strong>Mindfulness and Meditation:</strong> Helps center thoughts and reduce stress.</li><li><strong>Physical Exercise:</strong> Promotes overall well-being and reduces anxiety.</li><li><strong>Hobbies and Interests:</strong> Engaging in activities you enjoy provides a necessary break from emotional labor.</li></ul><h3>3. Develop Emotional Detachment</h3><p>Emotional detachment involves maintaining a healthy distance from others’ emotions, preventing them from overwhelming your own emotional state.</p><p><strong>Techniques:</strong></p><ul><li><strong>Mindful Awareness:</strong> Recognize when you’re becoming too emotionally involved and consciously detach.</li><li><strong>Perspective Shifting:</strong> Focus on the broader picture and your own needs.</li><li><strong>Professional Support:</strong> Seek guidance from therapists or counselors to develop effective detachment strategies.</li></ul><h3>4. Effective Time Management</h3><p>Balancing empathy with personal responsibilities requires efficient time management. By organizing your schedule, you can allocate time for both supporting others and attending to your own needs.</p><p><strong>Time Management Tips:</strong></p><ul><li><strong>Set Time Limits:</strong> Allocate specific periods for supporting others to prevent overextension.</li><li><strong>Prioritize Tasks:</strong> Focus on the most important tasks first to manage energy effectively.</li><li><strong>Use Organizational Tools:</strong> Utilize planners or digital apps to keep track of commitments and maintain balance.</li></ul><h3>5. Seek Professional Help When Needed</h3><p>Sometimes, managing the emotional demands of empathy requires professional assistance. Therapists and counselors can provide strategies and support to help navigate emotional fatigue and boundary issues.</p><p><strong>Benefits of Professional Help:</strong></p><ul><li><strong>Objective Perspective:</strong> Gain unbiased insights into managing empathy.</li><li><strong>Personalized Strategies:</strong> Develop coping mechanisms tailored to your specific needs.</li><li><strong>Emotional Support:</strong> Receive the necessary support to maintain mental well-being.</li></ul><h3>Real-Life Examples: The Impact of Empathy in UX Designers’ Lives</h3><h3>Case Study 1: The Overwhelmed Designer</h3><p><strong>Situation:</strong> Alex, a UX designer, excels at understanding user needs and is the go-to person for his team. However, his empathetic nature extends to his personal life, where he frequently listens to friends’ and family members’ problems. Over time, Alex experiences burnout, struggling to balance professional demands with personal support roles.</p><p><strong>Solution:</strong> Alex began setting boundaries by designating “no work talk” hours at home and scheduling specific times to support friends. He also incorporated regular self-care routines, such as evening walks and weekend hobbies, to recharge his emotional energy.</p><h3>Case Study 2: The Indecisive Designer</h3><p><strong>Situation:</strong> Samantha, another UX designer, applies her empathy to every aspect of her life, leading to decision paralysis. Whether choosing a restaurant or planning a vacation, Samantha finds it difficult to make choices without considering how they will affect others, resulting in stress and frustration. I personally experience this feeling with my friends.</p><p><strong>Solution:</strong> Samantha adopted decision-making frameworks that prioritize her preferences while still considering others’ needs. She communicated her decision-making process to friends and family, setting clear expectations and reducing the pressure to accommodate everyone.</p><h3>Achieving Balance: Embracing Empathy Without Compromise</h3><p>Empathy is a powerful tool in UX design, enabling the creation of products that resonate deeply with users. However, maintaining a balance between professional empathy and personal well-being is essential to prevent emotional fatigue and other negative consequences. Here are key approaches to achieve this balance:</p><h3>1. Selective Empathy</h3><p>Not every situation requires the same level of empathy. By assessing when to engage deeply and when to maintain a more detached approach, UX designers can conserve emotional energy for moments that truly matter.</p><h3>2. Enhance Emotional Intelligence</h3><p>Developing emotional intelligence (EI) allows designers to better understand and manage their own emotions alongside those of others. Higher EI leads to more effective navigation of empathetic engagements without becoming overwhelmed.</p><h3>3. Build a Support Network</h3><p>Having a strong support network of friends, family, or colleagues who understand the demands of your empathetic nature provides a safe space to share experiences and receive mutual support, preventing isolation and burnout.</p><h3>4. Redefine Success</h3><p>Shifting the focus to value personal well-being alongside professional achievements ensures that mental and emotional health are prioritized. Recognizing that personal well-being is integral to sustained success fosters a healthier approach to empathy.</p><h3>Conclusion: Sustaining Empathy with Self-Care</h3><p>Empathy is indispensable in UX design, enabling the creation of meaningful and user-centered products. However, when empathy extends into personal life without boundaries, it can lead to emotional fatigue, strained relationships, and burnout. By establishing clear boundaries, prioritizing self-care, developing emotional detachment, managing time effectively, and seeking professional support when needed, UX designers can harness the power of empathy without compromising their well-being.</p><p>Balancing empathy with self-preservation ensures that UX designers remain effective and fulfilled both professionally and personally. Embracing empathy responsibly not only enhances user experiences but also fosters a healthier, more sustainable approach to life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2043f8399e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/by-the-empathy-trap-navigating-the-emotional-challenges-of-being-a-ux-designer-e2043f8399e5">by The Empathy Trap: Navigating the Emotional Challenges of Being a UX Designer</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[The Ultimate UX Course Showdown: Google UX Professional Certificate, UXcel, and IxDF]]></title>
            <link>https://medium.com/design-bootcamp/the-ultimate-ux-course-showdown-google-ux-professional-certificate-uxcel-and-ixdf-694918ca5d72?source=rss-b62141a96f7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/694918ca5d72</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[uxcel]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ixdf]]></category>
            <dc:creator><![CDATA[Sepanta Pouya]]></dc:creator>
            <pubDate>Fri, 29 Nov 2024 14:13:44 GMT</pubDate>
            <atom:updated>2024-11-29T15:59:32.832Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RINlCs3XLBWreErem0pYSQ.png" /></figure><p>So you’ve decided to dive into the world of UX design? Or want to master your previous UX skills? Either way, you’re in the right place! Whether you’re starting from scratch or sharpening your expertise, there’s no shortage of online courses offering to make you a UX wizard. But with so many platforms to choose from, how do you decide which one will actually help you level up your skills (and not just fill up your inbox with “Hey, remember us?” emails)?</p><p>Let’s break it down. Today, we’re comparing <strong>Google UX Professional Certificate</strong>, <strong>UXcel</strong>, and the <strong>Interaction Design Foundation (IxDF)</strong> — three heavy-hitters in the UX education world. We’ll look at everything: pricing, course content, features, user feedback, flexibility, and more. By the end of this post, you’ll have a clear picture of which platform is the best fit for you.</p><h3>1. Google UX Professional Certificate (Coursera)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mq3RJvsG_uXr5tL2lIN1cg.png" /></figure><h4>Who It’s For:</h4><p>If you’re just starting out in UX design or if you’re looking to break into the industry with a strong, Google-backed credential, this course is the golden ticket. It’s perfect for people who need a structured path that takes them from <strong>beginner</strong> to <strong>competent designer</strong>.</p><h4>Course Content &amp; Structure:</h4><p>Google has done an incredible job of making this a comprehensive beginner’s course. Here’s what’s on the menu:</p><ul><li><strong>Foundations of UX Design</strong>: The course kicks off with user-centered design, explaining the basics of how to design products with the end user in mind.</li><li><strong>Empathy Mapping and Research</strong>: You’ll learn how to do user research and create personas, which is absolutely vital to UX design.</li><li><strong>Wireframing and Prototyping</strong>: You’ll learn the core tools of a UX designer, from paper sketches to digital prototypes.</li><li><strong>Usability Testing and Iteration</strong>: One of the highlights of this course is teaching you how to test and iterate designs based on real user feedback. It’s all about improving and refining.</li><li><strong>Final Project</strong>: At the end of the course, you’ll create a complete UX design portfolio — critical for landing that first job or freelance gig.</li></ul><p>You’ll learn by doing, with real-world projects that help build your portfolio. Plus, the course is taught by UX experts at Google, so you’re getting direct access to industry knowledge from a top-tier company.</p><h4>Duration:</h4><ul><li><strong>Approx. 6 months</strong> (if you spend about 10 hours per week on the course).</li><li>It’s designed to be self-paced, so if you’re a night owl, you can binge-watch the entire course in a couple of weeks. But, if you’re balancing work and life, take your time.</li></ul><h4>Pricing:</h4><ul><li>The Google UX Professional Certificate costs <strong>$39/month</strong> on Coursera. So, if you finish it in six months, it’s around <strong>$234</strong> in total.</li><li><strong>Financial aid</strong> is available for those who need it, which is nice if you’re on a tight budget.</li></ul><h4>Pros:</h4><ul><li>Well-structured, beginner-friendly.</li><li>Offers a <strong>Google-backed certificate</strong>, which may be recognized by employers.</li><li>Hands-on projects that build your portfolio.</li><li><strong>Financial aid</strong> is available.</li></ul><h4>Cons:</h4><ul><li>Not a ton of in-depth design theory or advanced concepts.</li><li>The pacing may be a little slow if you already have some UX knowledge.</li><li><strong>No live instructor support</strong> — it’s all self-paced and digital.</li></ul><h3>2. UXcel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s-O1djAljBFoUiWNhWQCgA.png" /></figure><h4>Who It’s For:</h4><p>UXcel is a great choice for those who want <strong>bite-sized lessons</strong>, a <strong>fun, interactive learning experience</strong>, and a platform that encourages gamification. If you like learning through quizzes, challenges, and short, engaging modules, UXcel will feel like a breath of fresh air.</p><h4>Course Content &amp; Structure:</h4><p>Unlike Google’s more traditional approach, UXcel emphasizes <strong>short, interactive learning sessions</strong> designed to fit into a busy lifestyle. Here’s what’s included:</p><ul><li><strong>Core UX/UI Principles</strong>: From information architecture to color theory and typography, UXcel offers a solid foundation in both UX and UI design.</li><li><strong>Usability Testing</strong>: UXcel’s hands-on approach also helps you practice usability testing, similar to what you’d do in a real job scenario.</li><li><strong>Design Systems</strong>: Learn how to create and use design systems to keep your projects organized and consistent.</li><li><strong>Interactive Practice</strong>: After each module, there’s a quiz, mini-project, or challenge to keep things exciting. Gamified learning is great for those who get easily distracted or bored.</li><li><strong>Pro Plan Features</strong>: The Pro Plan unlocks more in-depth content, like advanced prototyping, UI patterns, and deeper insights into designing for accessibility and mobile.</li></ul><p>One of the standout features is UXcel’s <strong>“skills dashboard,”</strong> which tracks your progress, shows areas for improvement, and lets you challenge yourself as you level up.</p><h4>Duration:</h4><ul><li>UXcel doesn’t have a fixed duration. You can take it at your own pace. Some users finish within a few months, but since the courses are shorter, you can easily digest them one bite at a time.</li></ul><h4>Pricing:</h4><ul><li><strong>Free Plan</strong>: This gives you access to some foundational lessons and challenges.</li><li><strong>Pro Plan</strong>: The paid version costs <strong>€35/month</strong> or <strong>€22/month</strong> if billed annually (which is <strong>€264/year</strong>). Not bad if you want to get the full experience, including exclusive content, design tools, and extra challenges.</li></ul><h4>Pros:</h4><ul><li><strong>Gamified learning</strong> makes it fun and engaging.</li><li>Short, digestible lessons ideal for busy learners.</li><li>Hands-on exercises and interactive practice help you apply what you learn.</li><li>Affordable <strong>Pro Plan</strong> with a lot of content for the price.</li></ul><h4>Cons:</h4><ul><li>The free plan has <strong>limited access</strong> to content (so if you’re serious about UX, you might need the Pro Plan).</li><li>The focus is more on practical skills than theoretical knowledge, so it’s better suited for those who already have a little design background.</li><li><strong>Less comprehensive</strong> compared to a structured, beginner-friendly course like Google’s.</li></ul><h3>3. Interaction Design Foundation (IxDF)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UEjECDMV-fdV_RSsX6Z_JQ.png" /></figure><h4>Who It’s For:</h4><p>IxDF is a <strong>powerhouse</strong> of design theory, and it’s perfect if you’re already familiar with basic UX concepts and want to dive deeper into <strong>advanced design thinking</strong>, <strong>research methodologies</strong>, and <strong>human-computer interaction</strong>. It’s also ideal for professionals who want to polish their existing UX skills.</p><h4>Course Content &amp; Structure:</h4><p>IxDF is all about <strong>high-quality, academic-style learning</strong> that covers both foundational principles and advanced concepts. Here’s what’s on offer:</p><ul><li><strong>Comprehensive UX Courses</strong>: Topics range from <strong>design thinking</strong> and <strong>cognitive psychology</strong> to <strong>interaction design</strong>, <strong>visual design</strong>, and <strong>UX strategy</strong>.</li><li><strong>Advanced Topics</strong>: Courses like <strong>Research Methods</strong>, <strong>Human-Computer Interaction (HCI)</strong>, and <strong>UX for Mobile Devices</strong> dig deep into specialized areas.</li><li><strong>Certification</strong>: Every course includes a certification upon completion, which looks great on your resume.</li><li><strong>Community</strong>: You’ll have access to a vibrant <strong>global UX community</strong> — a great resource for networking, collaborating on projects, or simply exchanging ideas.</li></ul><p>IxDF isn’t a gamified, short-lesson platform. It’s more like <strong>college for UX design</strong>, with readings, lectures, quizzes, and assignments. It’s ideal for those who like <strong>academic rigor</strong> combined with practical application.</p><h4>Duration:</h4><ul><li>Most courses take <strong>4–6 weeks</strong> if you spend about 4 hours a week. However, you can learn at your own pace and revisit materials anytime.</li></ul><h4>Pricing:</h4><ul><li><strong>Student Plan</strong>: <strong>€168/year</strong> — a steal if you want access to a huge library of content.</li><li><strong>Professional Plan</strong>: <strong>€240/year</strong> — for professionals who want extra perks like networking opportunities and exclusive webinars.</li></ul><h4>Pros:</h4><ul><li><strong>Comprehensive course offerings</strong> that span basic to advanced UX concepts.</li><li>Offers a lot of <strong>specialized topics</strong> not found on other platforms.</li><li>Access to a strong, global UX <strong>community</strong>.</li><li>Flexible learning with lifetime access to materials.</li><li>Certification is widely respected in the UX field.</li></ul><h4>Cons:</h4><ul><li><strong>Higher price tag</strong> compared to other platforms (though still affordable for serious learners).</li><li>The <strong>academic style</strong> can feel slow and theoretical if you’re looking for a fast-paced, hands-on approach.</li><li>Some courses might be a bit <strong>dense</strong> for beginners — this is best for those who already have a basic understanding of UX.</li></ul><h3>Conclusion: Which UX Course is Right for You?</h3><p>So, now that we’ve done a deep dive, which one should you choose? Here’s a quick recap:</p><ul><li><strong>Google UX Professional Certificate</strong>: Perfect for <strong>beginners</strong> who want a structured, industry-recognized certification backed by Google. If you prefer a <strong>step-by-step approach</strong>, this is for you.</li><li><strong>UXcel</strong>: Best for learners who want <strong>bite-sized lessons</strong>, a <strong>fun, interactive learning style</strong>, and flexibility. It’s great for those with some basic knowledge or those who want to jump into learning without too much theory.</li><li><strong>Interaction Design Foundation</strong>: Ideal for <strong>advanced learners</strong> or those who want to dive deep into <strong>design theory</strong></li></ul><p>No matter which course you choose, the important thing is to <strong>commit to the learning process</strong> and keep improving your skills. UX design is all about iteration and feedback, so embrace the process and enjoy the ride!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=694918ca5d72" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-ultimate-ux-course-showdown-google-ux-professional-certificate-uxcel-and-ixdf-694918ca5d72">The Ultimate UX Course Showdown: Google UX Professional Certificate, UXcel, and IxDF</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[Swimlane Diagram: A UX Designer’s Secret Weapon for Order in Chaos]]></title>
            <link>https://sepantapouya.medium.com/swimlane-diagram-a-ux-designers-secret-weapon-for-order-in-chaos-fb9aa00927d5?source=rss-b62141a96f7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb9aa00927d5</guid>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[sepanta-pouya]]></category>
            <category><![CDATA[swim-lane]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Sepanta Pouya]]></dc:creator>
            <pubDate>Tue, 19 Nov 2024 10:44:33 GMT</pubDate>
            <atom:updated>2024-11-19T10:44:33.415Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9rpYYcVY6mizIw5byck4bw.png" /></figure><p>Imagine a tangled ball of yarn, each strand representing a task, responsibility, or interaction in your project. Now imagine that you could untangle that mess and lay it out neatly, each strand separated and categorized. That’s the magic of a swimlane diagram. For UX designers like us, it’s a lifesaver when navigating the complexities of designing and delivering user experiences. Let’s dive deep into what it is, why it’s invaluable, and how you can start using it today.</p><h4>What is a Swimlane Diagram?</h4><p>A swimlane diagram is a type of flowchart that visually separates different elements of a process into distinct “lanes.” These lanes can represent departments, teams, individuals, or any other meaningful division. The goal is to clearly delineate responsibilities, actions, and interactions, making it easy to understand who does what, when, and how.</p><p>In essence, it’s a visual story of processes, divided into lanes like those in a swimming pool. Hence, the name: swimlane.</p><h4>The Anatomy of a Swimlane Diagram</h4><p>At first glance, a swimlane diagram looks like a grid:</p><ol><li><strong>Lanes (Rows or Columns):</strong> Represent entities such as teams, users, systems, or devices.</li><li><strong>Processes (Flow):</strong> The step-by-step actions or decisions depicted by arrows, rectangles, and diamonds.</li><li><strong>Transitions:</strong> Show how tasks or decisions flow between lanes.</li><li><strong>Artifacts:</strong> Additional notations, such as annotations or parallel paths, to enrich the narrative.</li></ol><p>For a UX designer, these components can map out the interactions between users, backend systems, and team members in the creation of a product or service.</p><h4>Why Does a UX Designer Need Swimlane Diagrams?</h4><p>As UX designers, we are the champions of clarity in chaos. Here’s how a swimlane diagram helps us achieve this:</p><ol><li><strong>Clarity in Complexity</strong> UX projects often involve multiple stakeholders, tools, and workflows. A swimlane diagram unravels this complexity, showing the relationships and interdependencies across the process. For instance:</li></ol><ul><li>Who initiates an interaction?</li><li>What system processes it?</li><li>How does it flow back to the user?</li></ul><p>This bird’s-eye view is indispensable for aligning stakeholders.</p><ol><li><strong>Identifying Bottlenecks</strong> Processes that seem smooth on paper often reveal hidden inefficiencies in practice. Swimlane diagrams highlight these bottlenecks, enabling us to propose UX improvements before development.</li><li><strong>Aligning Teams</strong> Miscommunication is the bane of teamwork. A swimlane diagram ensures everyone is on the same page, whether they’re developers, product managers, or marketing folks. It fosters cross-functional collaboration by visually answering, “What’s my role in this?”</li><li><strong>User Journey Meets Workflow</strong> While user journey maps capture the emotional narrative of a user’s experience, swimlane diagrams add a technical layer. They bridge the gap between what the user does and what happens behind the scenes.</li><li><strong>Prototyping and Development Aid</strong> When moving from design to development, these diagrams act as blueprints. They help developers understand how systems interact, reducing the back-and-forth clarification.</li></ol><h4>When Should You Use a Swimlane Diagram?</h4><p>Swimlane diagrams are not the hammer for every nail, but they excel in these scenarios:</p><ul><li>Mapping user flows in multi-channel or omni-channel experiences.</li><li>Designing processes involving multiple actors (e.g., user, admin, system).</li><li>Documenting service blueprints that outline what happens frontstage (user-facing) and backstage (behind the scenes).</li><li>Visualizing workflows in task-heavy applications like dashboards or SaaS products.</li></ul><h4>Creating a Swimlane Diagram: A Step-by-Step Guide</h4><ol><li><strong>Define Your Purpose</strong> What process are you visualizing? Is it a user flow, a system interaction, or an organizational workflow? Nail this down first.</li><li><strong>Identify Lanes</strong> Assign lanes to stakeholders, systems, or steps. For example:</li></ol><ul><li>User</li><li>Customer Support</li><li>Backend API</li><li>Marketing Team</li></ul><ol><li><strong>Outline Key Steps</strong> Write down all the steps in the process you’re mapping. Focus on clarity and avoid overcomplicating.</li><li><strong>Draw the Flow</strong> Using tools like Figma, Lucidchart, or Miro, begin placing steps in their respective lanes. Use arrows to connect them.</li><li><strong>Validate</strong> Share your diagram with stakeholders. Ask:</li></ol><ul><li>Is this accurate?</li><li>Are there gaps?</li><li>Does this highlight inefficiencies?</li></ul><ol><li><strong>Iterate</strong> Refine your diagram based on feedback. Simplicity and clarity are key.</li></ol><h4>Best Practices for Swimlane Diagrams</h4><ol><li><strong>Keep It Simple</strong> Use clear, concise labels. Overloading your diagram defeats the purpose.</li><li><strong>Start High-Level</strong> Begin with a broad overview, then dive into the details if needed.</li><li><strong>Color Code</strong> Colors can distinguish lanes, making the diagram visually intuitive.</li><li><strong>Use Standard Symbols</strong> Stick to conventional flowchart symbols (rectangles for steps, diamonds for decisions) to avoid confusion.</li><li><strong>Label Everything</strong> Arrows, lanes, and nodes should be labeled to remove ambiguity.</li></ol><h4>Tools to Create Swimlane Diagrams</h4><p>Several tools cater to creating swimlane diagrams:</p><ul><li><strong>Lucidchart:</strong> A versatile tool for diagrams.</li><li><strong>Miro:</strong> Great for collaborative mapping.</li><li><strong>Figjam + Figma:</strong> Perfect if you want to integrate diagrams with your design process.</li><li><strong>Visio:</strong> A classic option for more corporate settings.</li><li><strong>Whimsical:</strong> Light, intuitive, and great for quick drafts.</li></ul><h4>Real-Life Applications for UX Designers</h4><p><strong>Case 1: Multi-Channel Shopping Experience</strong> You’re designing a multi-channel retail experience where users can browse online, reserve items in-store, and return them via mail. A swimlane diagram can map:</p><ul><li>User actions across channels.</li><li>System interactions (e.g., inventory sync).</li><li>Communication between departments.</li></ul><p><strong>Case 2: SaaS Dashboard Workflow</strong> Imagine a dashboard allowing admins to approve users, assign roles, and generate reports. A swimlane diagram can visualize:</p><ul><li>User permissions.</li><li>Backend processes.</li><li>Notification triggers.</li></ul><p><strong>Case 3: Onboarding Flow</strong> For a mobile app, map the onboarding journey:</p><ul><li>User registration.</li><li>API validation.</li><li>Welcome email from the marketing system.</li></ul><h4>Final Thoughts</h4><p>Swimlane diagrams are more than just another tool in your UX arsenal — they are a lifeline for managing complexity and fostering collaboration. They offer clarity, align teams, and ensure that your designs are as effective in execution as they are in concept.</p><p>As a UX designer, you’re not just designing screens; you’re orchestrating experiences across users, systems, and teams. Swimlane diagrams help you do just that — with elegance, precision, and a dash of that strategic flair we UXers are known for.</p><p>So the next time you’re lost in the chaos of a complex workflow, grab your metaphorical goggles, jump into the pool, and start drawing lanes. You’ll find yourself swimming toward clarity in no time! 🏊‍♀️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb9aa00927d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Future of UX Design: Why Post-Launch Research is the New King]]></title>
            <link>https://medium.com/design-bootcamp/the-future-of-ux-design-why-post-launch-research-is-the-new-king-7426ee63c036?source=rss-b62141a96f7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7426ee63c036</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sepanta Pouya]]></dc:creator>
            <pubDate>Tue, 29 Oct 2024 15:32:09 GMT</pubDate>
            <atom:updated>2024-10-29T18:28:02.998Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="The Future of UX Design: Why Post-Launch Research is the New King by Sepanta Pouya" src="https://cdn-images-1.medium.com/max/1024/1*6xGjY_ZENSvIG5gmwLZ-nA.png" /></figure><h3>Introduction: The Framework Fever</h3><p>For years, we’ve been taught to revere certain frameworks like <strong>Design Thinking</strong> and other deeply research-focused methodologies. And to be fair, they’ve earned their place in the UX hall of fame. But is that place permanent? In an era of rapid AI development, platform evolution, and hyper-speed innovation, there’s a new sheriff in town — <strong>Post-Launch Research</strong>.</p><p>Now, before you come at me with your pitchforks, think about the last time you sat through a three-month-long research phase, only to have your market or technology pivot overnight. Or worse, when you finally launch, and <em>everything</em> about user expectations has changed. Frustrating, right?</p><p>In today’s competitive landscape, sticking solely to pre-launch frameworks is a bit like cooking a five-course meal for a party when you’re not sure if they’re even coming. Wouldn’t it be smarter to get some take-out menus on hand and be ready to serve the <em>actual</em> crowd when they show up?</p><h3>Why the Old Ways Might Be… Old News?</h3><h3>1. The Hyper-Competitive Reality</h3><p>In the current landscape, there’s a <strong>sense of urgency</strong> that didn’t exist a decade ago. As a designer, I’ve seen <em>companies pivot in weeks</em> and <em>ideas die in days</em>. What does that mean for us, the creators, innovators, and perpetual coffee consumers? It means that our approach to UX has to evolve as fast as the world we’re designing for.</p><p>The problem with traditional UX methodologies like Design Thinking is their emphasis on deep upfront research. It’s like hosting a workshop on how to use a fax machine while Elon Musk is over there inventing teleportation devices. By the time we finish the research and ideation phases, the market might have shifted, the users’ expectations might have evolved, and someone’s probably built a newer, shinier thing!</p><h3>2. Being Agile is Not Just a Buzzword</h3><p>I can already hear the Agile practitioners nodding vigorously. No, this isn’t me trying to slap “agile” on everything like those “keto-friendly” labels on snacks that are basically made of air. It’s genuinely about being agile in our <em>research</em>, <em>design</em>, and <em>development</em> processes.</p><p>Instead of getting stuck in a loop of ideation sessions with endless sticky notes (which, let’s be honest, often end up looking like a color-coded existential crisis), it’s time we pivot towards a more dynamic approach. Think of it like this: <strong>pre-launch research gives you a blueprint, but post-launch research hands you a user’s manual, complete with reviews, complaints, and hopefully a few five-star ratings.</strong></p><h3>The Case for Post-Launch Research: Fewer Sticky Notes, More Action</h3><h3>1. Embrace the Unknowns Like a Good Mystery Show</h3><p>Picture your product launch like a gripping Netflix series. The pilot episode gives you a teaser, a hint of what’s to come, but the <em>real story</em> unfolds with each episode. In the same way, launching a product isn’t the climax; it’s the start of a journey where <strong>each iteration</strong> is an episode influenced by real-time feedback.</p><p>By emphasizing post-launch research, we’re not throwing away pre-launch UX methodologies — we’re <em>reinventing their role</em>. Instead of relying solely on an exhaustive pre-launch analysis, we gather actionable insights from the wild, adapting and evolving as we go. It’s like being a chef who cooks with seasonal ingredients rather than sticking to a fixed recipe from 2005.</p><h3>2. The AI Elephant in the Room</h3><p>Artificial Intelligence is no longer just a cool buzzword; it’s reshaping industries at breakneck speed. Let’s be real: UX designers and researchers often find themselves trying to “out-innovate” or at least “keep up” with AI advancements. The idea of relying on <strong>rigid, research-heavy methods</strong> feels about as relevant as using MySpace to promote your startup.</p><p>Instead, embracing post-launch research allows us to work <em>with</em> AI-driven analytics tools, real-time user feedback, and rapid iterations. This way, we can be as responsive and adaptable as the technologies we’re designing for.</p><h3>But… Isn’t Pre-Launch Research Important?</h3><p>Absolutely! I’m not suggesting we toss it out like an old pizza box. Pre-launch research still plays a crucial role in defining the product’s foundations. But putting all our eggs in one basket pre-launch is like investing your entire budget in a single stock and crossing your fingers. Instead, a mixed approach helps us stay grounded while remaining agile enough to adapt to the market’s shifting winds.</p><h3>How to Shift Gears Without Losing the Wheels?</h3><ol><li><strong>Set Broad, Flexible Goals:</strong> Establish foundational research to guide the initial concept but avoid getting bogged down in endless nitpicking over early details.</li><li><strong>Launch, Learn, Iterate:</strong> Treat the launch not as a finish line but a <em>milestone</em>. It’s the green light for gathering fresh insights, validating assumptions, and debunking any myths you might have picked up during the initial research phase.</li><li><strong>Co-Create with Your Audience:</strong> Don’t just observe users — bring them into the conversation. Engage users post-launch to gain real-time insights and adapt faster than your competitors can say “design sprint.”</li></ol><h3>Conclusion: Changing the Game, One Launch at a Time</h3><p>Look, I get it. Change is scary. Abandoning the comfort of traditional frameworks is like tossing out your childhood blanket. But as designers and creators, we can’t afford to get <em>too comfortable</em>. Especially when the world is evolving faster than we can double-click on a file named “FinalFinalDraftV2.”</p><p>It’s time to embrace a future where <strong>post-launch research</strong> drives meaningful iterations and keeps us in sync with rapidly changing market demands. Let’s stop treating UX like an archaeological dig and start treating it like the <em>live concert</em> it’s supposed to be. Who’s ready to rock and roll?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7426ee63c036" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-future-of-ux-design-why-post-launch-research-is-the-new-king-7426ee63c036">The Future of UX Design: Why Post-Launch Research is the New King</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[What Has Sepanta Been Up To This Year?]]></title>
            <link>https://sepantapouya.medium.com/what-has-sepanta-been-up-to-this-year-bfe6ce037ce4?source=rss-b62141a96f7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfe6ce037ce4</guid>
            <category><![CDATA[sepanta-pouya]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[happy-birthday]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Sepanta Pouya]]></dc:creator>
            <pubDate>Sat, 12 Oct 2024 08:17:04 GMT</pubDate>
            <atom:updated>2024-10-12T08:17:04.058Z</atom:updated>
            <content:encoded><![CDATA[<p>To celebrate my birthday, let’s take a look at some fun, data-driven metrics from different areas of my life (keep in mind, these numbers might be a bit off).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*keJ6oeyZIoeoMISqhAQ2dA.png" /></figure><p>Hey there! 🎉 It’s my birthday, and what better way to reflect on the past year than diving into some cool, data-centric stats? This post will give you a peek into my health, finances, work, and personal growth — because numbers make everything more fun, right? 😎 Let’s jump in!</p><h3>Health:</h3><p>2024 has been all about movement, and I’m crushing it! 🏃‍♂️</p><ul><li><strong>Steps:</strong> In 2024, I walked <strong>36%</strong> more than in 2023! On average, I clocked <strong>9,387 steps</strong> daily, compared to <strong>6,882 steps</strong> in 2023. That’s almost like scaling a mountain every day! 🏔️</li><li><strong>Distance:</strong> I covered <strong>31%</strong> more ground this year. In 2024, I averaged <strong>6.63 km per day</strong>, compared to <strong>5.05 km</strong> last year. That’s almost like walking from home to my favorite café, twice! ☕</li><li><strong>Calories:</strong> Every day, I burned an average of <strong>717 calories</strong> (probably fueled by my love for snacks 🍕). Plus, I got about <strong>35 minutes</strong> of exercise daily — fitting in those workouts between design sessions. 💪</li></ul><h3>Finances: 💳</h3><p>Ah, the story of my wallet… let’s just say my bank’s app got a lot of action this year!</p><ul><li><strong>Transactions:</strong> Since my last birthday, I’ve swiped my card <strong>1,148 times</strong>! That’s about <strong>3 transactions per day</strong>. And yes, online payments count too. It’s not all “swipe and go” at the coffee shop! ☕💸</li><li><strong>Foodie Habits:</strong> No surprise here — <strong>75.6%</strong> of those transactions went to food. My biggest spending spike? Dinner time, obviously. Guess I should try leaving the house with a full stomach if I want to avoid impulse buys! 😅</li><li><strong>Food Costs:</strong> Brace yourself… I spent <strong>136 million IRT</strong> on food this year. That’s around <strong>372,000 IRT per day</strong> — almost a dinner for two, but it’s mostly me solo. 😬 My food expenses include restaurants, cafés, groceries, and everything edible. Let’s just say, my stomach and my wallet have been in a complicated relationship.</li><li><strong>Transport:</strong> On the mobility front, I spent <strong>6.2 million IRR</strong> on Snapp and Tap30. Again, mostly for dinner trips. Lesson learned: maybe I should carpool with my dinner buddies next time. 🚗🍲</li></ul><p>When it comes to investments, I’ve been stepping up my game. I diversified into multiple channels, but I’ll keep the actual numbers on the down-low — just between me and my portfolio. 😎</p><h3>Work:</h3><p>Now, let’s talk business. In this year-long stretch, my work stats look something like this:</p><ul><li><strong>Meetings:</strong> I spent about <strong>315 hours</strong> in online meetings — averaging about <strong>51 minutes per day</strong>. This doesn’t account for weekends, holidays, or in-person meetings, so the actual time is probably higher. My laptop’s webcam? Yeah, we’re practically best friends at this point. 💻👀</li><li><strong>Emails:</strong> I received <strong>1,082 non-spam emails</strong> (thankfully!). That’s roughly <strong>3 important emails per day</strong> — not too bad, but enough to keep me on my toes. 📨</li></ul><p>Now, on the creative front:</p><ul><li>I released <strong>7 podcast episodes</strong>, each more fun than the last. 🎙️</li><li>Hosted <strong>8 Design Factory events</strong> — and over <strong>300 people</strong> attended across these events! Design is definitely growing, and I’m here for it! 😍</li><li>My podcast was played <strong>437 times</strong>, which feels amazing! Thanks to everyone who tuned in. 😎</li></ul><h3>Social Media and Content:</h3><p>It’s been a growth-filled year on the content side:</p><ul><li>Over <strong>800 new members</strong> joined my Telegram channel! 📱</li><li>My YouTube channel racked up over <strong>230 hours of watch time</strong>, and my subscribers hit the <strong>500+</strong> mark. I’m super pumped to keep creating content that resonates with you all. 🎥</li></ul><h3>Personal Growth, Connections, and Mental Health:</h3><p>On the personal front, 2024 has been transformative in ways that go beyond the numbers.</p><ul><li><strong>Therapy:</strong> I started therapy this year, and it’s been a game-changer. Over the past year, I’ve had more than <strong>30 sessions</strong>, amounting to around <strong>55–60 hours</strong> of much-needed mental clarity. Therapy has been a huge help in improving my mental health, and I couldn’t be more grateful. 🧠💚</li><li><strong>Courses:</strong> I completed <strong>4 specialized courses</strong> to keep leveling up my professional skills. These courses, taken through Uxcel, have expanded my knowledge and helped broaden my network. 📚✨</li><li><strong>Meditation:</strong> This year, I also focused more on meditation. It’s something I want to make an even bigger part of my daily routine in the coming months. Finding inner peace has never been more important! 🧘‍♂️</li></ul><h3>Final Thoughts:</h3><p>Phew! That was a lot to unpack. 😅 But I’m super grateful for every step, every meeting, every transaction, and every personal milestone from this past year. Thank you all for being part of this journey with me.</p><p>Here’s to another year of growth, learning, and a whole lot more steps (and probably a lot more snacks, too)!</p><p>Cheers to what’s ahead! 🎉👟🍕</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfe6ce037ce4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>