<?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 Ashley Timm on Medium]]></title>
        <description><![CDATA[Stories by Ashley Timm on Medium]]></description>
        <link>https://medium.com/@ashleytimm90?source=rss-80853a7a35f5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*k5rA7c69gVKfcPpSZnndZQ@2x.jpeg</url>
            <title>Stories by Ashley Timm on Medium</title>
            <link>https://medium.com/@ashleytimm90?source=rss-80853a7a35f5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:43:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ashleytimm90/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[The Courage Gap: When your best ideas are useless]]></title>
            <link>https://medium.com/design-bootcamp/the-courage-gap-when-your-best-ideas-are-useless-5f779d476ce9?source=rss-80853a7a35f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f779d476ce9</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[woman-in-tech]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[courage]]></category>
            <dc:creator><![CDATA[Ashley Timm]]></dc:creator>
            <pubDate>Tue, 14 Oct 2025 14:39:59 GMT</pubDate>
            <atom:updated>2025-10-14T14:57:07.206Z</atom:updated>
            <content:encoded><![CDATA[<p>You’re in a meeting. A big one. The stakeholders are there, the VPs are dialed in. The conversation is happening, and a critical piece of the puzzle is missing. You see it. You have the idea, the insight, the one thing that could reframe the whole project.</p><p>It’s right there, on the tip of your tongue. Your heart starts to beat a little faster. Your brain kicks into overdrive, not with excitement, but with fear.</p><p><em>“What if they think it’s a dumb idea?”</em> <em>“Is it my place to speak up?”</em> <em>“Maybe I’ll wait for a better moment.”</em> <em>“I don’t have all the data to back it up perfectly yet.”</em></p><p>And just like that, the moment passes. The conversation moves on. Your idea stays locked inside your head, a brilliant solution in a prison of silence.</p><p>Sound familiar?</p><p>This is <strong>The Courage Gap</strong>. It’s the space between your potential and your impact. It’s the distance between the brilliant insights you have and the actions you actually take. And let me be blunt: it is the single biggest thing holding you back in your career.</p><h3>The Myth of the “Skills Gap”</h3><p>We spend our entire professional lives trying to close the <em>skills gap</em>. We take courses, get certifications, and attend workshops. We learn to code, to manage projects, to analyze data, and to build beautiful user experiences. We stack skills like we’re building a fortress, believing that if we just have one more credential, we’ll finally be ready.</p><p>Ready for what?</p><p>All the skills in the world are worthless if they’re sitting on a shelf. That expensive sports car in your garage is just a fancy sculpture if you don’t have the key to start the engine.</p><p><strong>Courage is the key.</strong></p><p>Courage is the activating agent. It’s the force that turns your knowledge into influence, your ideas into innovation, and your potential into performance. Odds are, you don’t have a skills gap. You have a courage gap.</p><h3>Designing for Action: A UX Approach to Courage</h3><p>As a UX Designer, my job is to make things effortless for the user. I identify points of friction. Moments of hesitation, confusion, or doubt; and I design them out of the framework. I build pathways that guide a user from an intention to a desired action as seamlessly as possible.</p><p>What if we applied this same thinking to ourselves?</p><p>Your brain is the user. Your fear and hesitation are the friction. Your great idea is the intention, and speaking up is the action. We need to redesign your internal “user experience” to make courage the easiest, most obvious choice.</p><p>Here’s how we do it.</p><h4>1. Identify the Friction: Name Your Hesitation Monster</h4><p>In design, we create user personas and journey maps to understand pain points. You need to do the same for your fear. What’s the real reason you hesitate? Get specific.</p><ul><li>Is it the <strong>Fear of Being Judged?</strong> (The “What will they think of me?” monster)</li><li>Is it <strong>Imposter Syndrome?</strong> (The “I’m not qualified enough to say this” monster)</li><li>Is it <strong>Perfectionism?</strong> (The “It’s not a fully baked idea yet” monster)</li></ul><p>Write it down. Name it. Look it in the eye. When you give your fear a name and a face, it stops being a vague, all-powerful force and becomes a specific problem you can start to solve.</p><h4>2. Define Your “Minimum Viable Action” (MVA) … yes, I just made that up.</h4><p>In a product lifecycle, we usually don’t try to build the entire, perfect product on day one. We often build a system with incremental improvement. And for better or worse, we start with an MVP. The smallest possible version that delivers value and allows us to learn. <em>(This will be one of the only times I encourage an MVP by the way… you’ll hear me being very adverse to this acronym in like… every other design situation.)</em></p><p>We need to apply this to our courage. You don’t have to deliver a perfect, game-changing monologue. You just need a <em>Minimum Viable Action</em>.</p><ul><li>Your goal isn’t to “win the argument.” Your MVA is to <strong>ask one clarifying question.</strong></li><li>Your goal isn’t to “solve the entire problem.” Your MVA is to say, <strong>“Could we pause for a moment and explore another angle?”</strong></li><li>Your goal isn’t to “sound like the smartest person in the room.” Your MVA is to simply state, <strong>“I have a thought on this I’d like to share.”</strong></li></ul><p>An MVA is small, low-risk, and gets you into the game. It breaks the pattern of silence. It moves you from passive observer to active participant.</p><h4>3. Prototype Your Courage with the 5-Second Rule</h4><p>This is where we borrow a trick from my friend <a href="https://www.melrobbins.com/book/the-5-second-rule/#:~:text=You%20can%20use%20the%20Rule,to%20take%20the%20actions%20that">Mel Robbins </a><em>(I love her, and you should listen to her podcast, </em><a href="https://www.melrobbins.com/book/the-5-second-rule/#:~:text=You%20can%20use%20the%20Rule,to%20take%20the%20actions%20that"><em>and read her book</em></a><em>)</em>. She teaches us that hesitation is a habit your brain uses to “protect” you. You have about a 5-second window before your brain kills your impulse to act. You have to physically move before that window closes.</p><p>The moment you have the instinct to speak up, start counting down in your head: <strong>5… 4… 3… 2… 1… GO.</strong></p><p>At “1,” you have to do something physical. Unmute your microphone. Lean forward in your chair. Raise your hand. Open your mouth and take a breath to speak. This physical action hijacks your brain’s hesitation loop and pushes you into your Minimum Viable Action.</p><p>This isn’t just a mental trick. It’s a physical launch sequence for your idea. It’s the “call-to-action” button for your brain.</p><h4>4. Iterate and Gather Feedback</h4><p>In design, we launch, we measure, we learn, we iterate. The same applies here.</p><p>Maybe your first MVA was a little clunky. Who cares? You did it. You broke the silence. The world didn’t end. You weren’t fired. In fact, people probably listened.</p><p>Now, what did you learn?</p><ul><li>Did you speak too softly? Next time, project more.</li><li>Did you get excited and interrupt? Next time, find a better opening.</li><li>Did your point land well? Great, double down on that approach.</li></ul><p>Every time you act, you are collecting data. You are user-testing your own courage. You’re learning that the “disaster” your brain predicted doesn’t happen. The more data you collect, the weaker the fear becomes, and the wider the pathway for action gets.</p><h3>Close the Gap. Ship Your Ideas.</h3><p>Your career, your impact, will not be defined by the ideas you have in the shower when no one is around, or with your friends at happy hour after the moment passed. It will be defined by the ideas you have the courage to share in the moments that matter.</p><p>Stop waiting for confidence. Confidence is a result, not a requirement. It’s the feeling you get <em>after</em> you do the hard thing. Courage is what you need to get started.</p><p>Your title doesn’t give you a voice. Your courage does. Your skills are just potential energy… your <em>courage</em> is what turns them into kinetic impact.</p><p>So, in your next meeting, when that idea strikes, don’t let it die in the silence of your own hesitation.</p><p>See the gap. Define your MVA. And then, <strong>5… 4… 3… 2… 1… Go.</strong></p><p><em>Thanks for reading. If this resonated with you, I’d love to hear about your experiences! What happened when you took that leap of faith for yourself?</em></p><p><em>PS. Typos are how you know this wasn’t AI ;P</em></p><h4>A little of the science, just for funzies:</h4><ol><li>Dr. Daniel Siegel, a clinical professor of psychiatry at UCLA, developed the “Name it to Tame it” concept, which is a technique to manage emotions by verbally labeling them. Naming an emotion activates the prefrontal cortex (the brain’s “thinking” center) and calms the limbic system (the brain’s emotional center), effectively reducing the intensity of the feeling. This simple act of identifying and verbalizing an emotion can make it easier to manage.</li><li>Narrative therapy, developed by Michael White and David Epston, is a psychotherapy approach that externalizes problems by framing them as separate from a person’s identity. This allows clients to re-examine and re-author their lives by creating new narratives that are based on their values, strengths, and skills, rather than being defined by their problems. The therapist acts as a collaborator, helping clients to challenge problem-saturated stories and develop more empowering ones.</li><li>In his 2002 book The War of Art, Steven Pressfield personifies the internal force of creative self-sabotage as “The Resistance”. By giving a name to the force that prevents artists, writers, and entrepreneurs from doing their work, he makes it a tangible enemy to be confronted and fought against daily.</li></ol><p><em>About the author: Ashley is a Principal UX Designer at Amazon, focusing on creating impactful digital experiences through strategic design thinking at a global scale.</em></p><p><em>Related articles: (1) </em><a href="https://medium.com/@ashleytimm90/navigating-input-a-new-designers-guide-to-prioritization-c2a4343d97bc"><em>Navigating Input: A Guide to Prioritizing Input for New Designers</em></a><em>, (2) </em><a href="https://medium.com/@ashleytimm90/stop-building-features-start-solving-problems-2fc84389248a"><em>Stop Building Features &amp; Start Solving Problems</em></a><em> (3) </em><a href="https://medium.com/@ashleytimm90/correct-design-process-doesnt-exist-079bad442cd7"><em>“Correct” design process doesn’t exist</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f779d476ce9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-courage-gap-when-your-best-ideas-are-useless-5f779d476ce9">The Courage Gap: When your best ideas are useless</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 most valuable design skill nobody talks about]]></title>
            <link>https://medium.com/design-bootcamp/the-most-valuable-design-skill-nobody-talks-about-692122011489?source=rss-80853a7a35f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/692122011489</guid>
            <category><![CDATA[ux-leadership]]></category>
            <category><![CDATA[design-innovation]]></category>
            <category><![CDATA[design-strategy]]></category>
            <category><![CDATA[woman-in-design]]></category>
            <category><![CDATA[design-skill]]></category>
            <dc:creator><![CDATA[Ashley Timm]]></dc:creator>
            <pubDate>Wed, 07 May 2025 17:27:53 GMT</pubDate>
            <atom:updated>2025-05-09T21:23:19.362Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A group of yellow arrows all going to the right, one pink arrow turning around and going left." src="https://cdn-images-1.medium.com/max/1024/1*yKzRoEE2uCmFmw5y8s-UHQ.png" /></figure><h4>It’s not what you think (and it’s definitely not in your job description)</h4><p>You know that feeling when you’re staring at a product brief <em>(or in Amazon speak: the PR/FAQ)</em>, and something just doesn’t sit right? Not the usual “this could be better” feeling, but that deep-in-your-gut instinct that maybe — just maybe — we’re solving entirely the wrong problem?</p><p>I’ve been there. And honestly, in my early years of design this is where I use to shrug it off and think “well, they know better than I do” or my impostor syndrome would kick in and I’d think “who am <em>I</em> to question this work?” and that doing so might make me look silly, or egotistical.</p><p>After over a decade of designing digital products, I’ve realized something that’s (now) both obvious and still terrifying: The most valuable skill in design isn’t what we think it is: It’s not our Figma expertise. Not our eye for grids and “Gestalt” proximity, or typography. Not even our ability to craft the perfect experience or architectural journeys, (<em>which I love deeply, but can you tell I’m trying to build suspense?</em>)</p><p>The most valuable skill in design isn’t technical expertise: <em>It’s courage.</em></p><p>Specifically, the courage to <strong>question fundamental assumptions.</strong></p><h3>The Uncomfortable Truth About Design Impact</h3><p>Look, I get it. When you’re working on products that affect potentially millions of users, suggesting that we might be approaching something completely wrong feels… risky. Especially when there are deadlines, and roadmaps, and that one senior leader who’s <em>really</em> excited about <em>this</em> particular solution.</p><p>But here’s the thing: Every truly transformative product decision I’ve been part of started with someone having the courage to ask “why?”</p><p>Not just once. Not just at the beginning. But repeatedly, persistently, and sometimes… uncomfortably.</p><h3>Story Time</h3><p>Let me tell you about a recent project. Classic scenario: I was asked to update a pretty neglected page to match our design system, and optimize how we were showing the information. Simple enough, right? The kind of project where you could just put your head down and knock it out. Maybe do some user studies, but ultimately a strait forward task.</p><p>But something felt off. So I started asking <em>why</em>.<br>Why <em>this</em> page?<br>Why <em>here</em> in the journey?<br>Why does <em>this</em> information need to stand alone?</p><p>What I discovered was that this “simple update” was masking a deeper systemic issue. The page wasn’t just poorly designed — it was an unnecessary step in the journey. The real solution? Remove it entirely and reshape the customer journey.</p><h3>Three Words That Kill Innovation</h3><p>This is usually where someone says those three dreaded words: That’s “<em>out of scope.</em>”</p><p>Can we talk about that phrase for a second? Because “out of scope” has become this catch-all term that we use when something makes us uncomfortable, or when we didn’t plan for it, or my personal favorite, “We tried something vaguely similar three years ago and it didn’t work.” Ok, no one actually says that <em>verbatim</em>, but you get the point… What I’m really saying is, “out of scope” is where the real opportunities hide.</p><h3>The Art of Strategic…. Questioning?</h3><p>I’m not suggesting we should ignore constraints or deadlines. This isn’t about being difficult or contrarian. And honestly, I know sometimes I can come across <a href="https://www.google.com/search?q=like+a+bull+in+a+china+shop&amp;rlz=1C5GCEM_en&amp;oq=like+a+bull+in+a+china+shop&amp;gs_lcrp=EgZjaHJvbWUyBggAEEUYOdIBBzIzN2owajSoAgCwAgE&amp;sourceid=chrome&amp;ie=UTF-8">like a bull in a china shop</a>, but the goal is to communicate and perpetuate that our role as designers extends far beyond the interface layer.</p><p>Think about the last major tech product that truly transformed its space. Was it just better designed, or did it fundamentally reframe the problem it was solving?</p><ul><li>Uber didn’t just improve taxi dispatch — it questioned why we needed dispatchers at all</li><li>Airbnb didn’t just make hotel booking better — it challenged what a “hotel” even means</li><li>Netflix didn’t only improve video rental — it questioned why we needed physical media</li></ul><p>Admittedly, to effectively challenge assumptions, you need more than <em>just</em> courage. You need data literacy, the ability to understand metrics beyond surface level and build compelling business cases. You need strategic communication skills to build trust with stakeholders and frame challenges in business terms.</p><p>But here’s the truth: all of that is meaningless if you don’t have the courage to speak up.</p><p>There are three critical moments when asking “why” can transform a project.</p><ol><li>The first comes at the brief stage, when assumptions are fluid and anything is possible. This is when we need to question everything about the problem we think we’re solving. And i mean everything! Take even just moment to take the things you feel confident in, and verify that you have conviction in what you’re pushing. And <a href="https://medium.com/@ashleytimm90/stop-building-features-start-solving-problems-2fc84389248a">ensure that you’re solving a problem, not just filling a feature gap</a>.</li><li>The second moment comes during discovery, when assumptions start hardening into “requirements.” This is when we need to push back and ask if we’re solving for true needs or just current limitations. I talk a bit more about how to prioritize all the feedback you get in this phase, in <a href="https://medium.com/@ashleytimm90/navigating-input-a-new-designers-guide-to-prioritization-c2a4343d97bc">one of my other articles about navigating input.</a></li><li>The third, and often most crucial moment, is when someone says “no.” This is when we need to dig deeper and understand what we’re really prioritizing and why.</li></ol><h3>The Real Cost of Playing it Safe</h3><p>Every major innovation in our industry started with someone questioning basic assumptions. Someone who had the courage to say “maybe there’s a better way.”</p><p>Does it feel uncomfortable? Absolutely. Will you sometimes be wrong? It would be weird if you weren’t! And that’s okay. Because the alternative — just executing on what we’re told? Thats not really design. <em>It’s decoration.</em></p><h3>Your Call to Action</h3><p>The next time you’re faced with a design challenge, pause for a moment. Ask yourself if you’re thinking broadly enough. Ask if you’re being brave enough. And most importantly, ask yourself what would happen if you dared to completely reimagine what’s possible.</p><p>Because in the end, the greatest designs don’t just solve problems… they redefine them.</p><p><em>Thanks for reading. If this resonated with you, I’d love to hear about your experiences challenging the status quo in design. What happened when you dared to ask “why?”</em></p><p><em>PS. Typos are how you know this wasn’t AI — no need to draw attention to yourself by pointing them out. </em>🙂</p><p><em>About the author: Ashley is a UX Designer at Amazon, focusing on creating impactful digital experiences through strategic design thinking.</em></p><p><em>Related articles: (1) </em><a href="https://medium.com/@ashleytimm90/navigating-input-a-new-designers-guide-to-prioritization-c2a4343d97bc"><em>Navigating Input: A Guide to Prioritizing Input for New Designers</em></a><em>, (2) </em><a href="https://medium.com/@ashleytimm90/stop-building-features-start-solving-problems-2fc84389248a"><em>Stop Building Features &amp; Start Solving Problems</em></a><em> (3) </em><a href="https://medium.com/@ashleytimm90/correct-design-process-doesnt-exist-079bad442cd7"><em>“Correct” design process doesn’t exist</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=692122011489" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-most-valuable-design-skill-nobody-talks-about-692122011489">The most valuable design skill nobody talks about</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[Stop Building Features & Start Solving Problems]]></title>
            <link>https://medium.com/design-bootcamp/stop-building-features-start-solving-problems-2fc84389248a?source=rss-80853a7a35f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fc84389248a</guid>
            <category><![CDATA[woman-in-tech]]></category>
            <category><![CDATA[ladieswhoux]]></category>
            <category><![CDATA[design-strategy]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[product-design-process]]></category>
            <dc:creator><![CDATA[Ashley Timm]]></dc:creator>
            <pubDate>Sat, 14 Dec 2024 06:29:14 GMT</pubDate>
            <atom:updated>2025-06-06T19:39:59.383Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="solid white puzzle with one missing piece in pink" src="https://cdn-images-1.medium.com/max/1024/1*bRRI5j4Co4yOF9yMprmksg.png" /></figure><h3><strong>Stop building features &amp; start solving problems</strong></h3><p><em>Congratulations, you just launched another solution desperately searching for a user problem — because clearly, what the people really need is yet another shiny button they’ll never click. Stop playing “Feature Bingo” and start solving actual user problems please. Unless you enjoy watching your hard work gather digital dust (with the other 80% of features that are rarely or never used).</em></p><p>The tension between Design, Product, and Engineering is one I have tremendous respect for. With the proper balance, these tensions can create exceptional products that are easy to use, fill market gaps, make money, scale, and launch quickly. In other words; they can harmonize better than <a href="https://www.youtube.com/watch?v=izGwDsrQ1eQ">George Michael’s Careless Whisper</a>. You’re welcome for that.</p><p>This idea of balancing desirability, feasibility, and viability isn’t new, and design strategy is only one aspect of overall product success. However, there is a common trap well-meaning individuals (<em>usually Product partners if we’re being honest here…if my PM is reading this I don’t mean you, you’re great</em>) and teams looking to create high impact features fall into, and it happens more often than we think: Subconsciously asking “What is our product missing?” rather than “What problems are we solving?”</p><h3><strong>The Feature Trap</strong></h3><p>As mentioned above, what I’ve seen happen time and again, perhaps not blatantly but in subtext, is that the question being asked in a project kick-off is not “what are users struggling with?” or “what do our users need”, it’s “<em>what don’t we have</em>?”</p><p>This can take many tactical forms, often using business analytics or behavioral data as a foundation for justification. It can look like a drop-off rate on a particular page, a feature gap, or the dreaded “our biggest competitors have it, so we should too.”</p><p>Now rarely, if ever, do these assumptions rear their ugly heads so blatantly, but the sentiment is the same; so what we end up with is products full of features and little value.</p><p>I’ll admit there are instances where adding features might be necessary for market competitiveness. However, even in these cases, the addition should be driven by validated user needs and anecdotes rather than market trends. Even looking at behavioral data in isolation is a huge pitfall for furthering this patten of thinking. The key is to maintain a balance between innovation and simplicity is always keeping the <strong>user’s</strong> core needs at the forefront. This will inherently lead to better business metrics too…</p><h3><strong>The Data Speaks</strong></h3><p>A study by Pendo found that 80% of features in the average software product are rarely or never used. This translates to considerable unnecessary expenditure in development and testing resources. The same study claims that up to $29 billion (<em>yes, with a big ‘B’</em>) was spent on developing these features.</p><p>More recent research supports this as well: A 2021 study by ProductPlan found that 51% of product managers struggle with feature bloat, and then there is the Standish Group’s CHAOS Report which consistently shows that unused or rarely used features contribute to project failures.</p><p>By pushing our businesses to move faster (too fast) we’re encouraging and launching products dripping with features, and leaving unimpressed customers in our wake.</p><p><strong>Ultimately, by framing product opportunities as customer problems, we risk creating solutions in search of problems.</strong></p><p>This approach leads to feature-bloat and decreased user satisfaction. And seriously, no one wants to be associated with the word ‘bloat’.</p><h3><strong>A Better Approach: Hypothesis-Driven</strong></h3><p>Instead of assuming that a feature deficit is inherently a customer problem, teams should adopt a hypothesis-driven approach. Consider this scenario: A product team muses that <em>“customers want to purchase items directly from search results.”</em> They may even go so far as curating a customer problem sounding something like <em>“customers have no way to make a purchase from search today”.</em></p><p>While this might sound like a customer problem, it’s actually a product opportunity masquerading as a problem. The true issue may be:</p><ol><li><em>“Customers struggle to find and complete purchases efficiently.”</em></li><li><em>“The current purchasing process is perceived as overly complicated.”</em></li><li><em>“Users are unsure of where to go to find a product they want to purchase”</em></li><li><em>“users would like a way to purchase content sooner in the journey”</em></li></ol><p>By reframing the issue, we automatically open a wide range of potential solutions beyond simply adding a purchase option to search pages. Sure thats ONE solution, but is it THE solution?</p><p>Using the same example, we could write a hypothesis: “If we simplify the purchasing process, and make it accessible from more placements (e.g., search results, landing pages, or deep links), we will see an increase in completed transactions and customer satisfaction.” Or if the problem is “Customers struggle to find and complete purchases efficiently” then is it a discovery problem, or a purchase problem? Based on this statement alone, it’s unclear. We need to generate a hypothesis as to why the problem is happening <em>(based on, you guessed it: data)</em></p><p>This approach allows for a much more flexible and targeted set of potential solutions, and possibly leading to innovations that may not involve adding features at all. In fact, sometimes the solution involves removing features.</p><p>It’s crucial to emphasize that effective hypothesis-driven development needs user research (uh, duh?). Understanding needs, motivations, and pain points is essential for identifying REAL problems and crafting meaningful solutions. The <a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">“Jobs to be Done” framework by Clayton Christensen</a> comes to mind as an example on how to understand motivations beyond surface-level feature requests.</p><h3><strong>Measuring Success</strong></h3><p>When focusing on solving user problems rather than adding features, success metrics need to shift beyond the behavioral data, and instead of tracking the number of features launched, or how many a/b tests we’ve run — teams should focus on user satisfaction, task completion, as well as overall product adoption as a KPI, not just $$ based metrics (gasp!). <a href="https://en.wikipedia.org/wiki/Kano_model">The Kano Model</a> for product development and customer satisfaction comes to mind as a great way to identify and prioritize features that truly matter to users.</p><h3><strong>A Call to Action</strong></h3><p>As we move forward in an increasingly competitive product landscape, it’s essential to challenge these assumptions when we see them, and dig deeper into what users <em>actually need</em>. Only by doing so can we create products that not only meet market demands but also provide real value. This means you (yes, you) need to start critically looking at the requests that appear in front of you. It’s way easier to be the design monkey that bangs out exactly that was requested, but then you’re just a big a part of a problem. Think critically about the problems you encounter, and identify if it’s a customer need, a feature gap, or even worse: just a thing someone wants to do cause they need to meet a project-count goal.</p><p>In my opinion<em> (which may be implied since I’m writing this specifically to share my opinion, which no one asked for</em>) The distinction between product opportunities and customer problems is crucial for creating high-impact, user-centric products. And who wants to build or create products with low impact!? By focusing on genuine customer problems, forming testable hypotheses, and conducting thorough user research, we can avoid the pitfalls of feature bloat and create truly innovative solutions. This will however, force us to think beyond the obvious gaps, and be intentional about every pixel our users see.</p><p><strong><em>For a little extra reading, and because citing your sources is sexy:</em></strong></p><ol><li><em>Pendo study on feature usage and development costs: </em><a href="https://www.pendo.io/resources/the-2019-feature-adoption-report/">https://www.pendo.io/resources/the-2019-feature-adoption-report/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fc84389248a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/stop-building-features-start-solving-problems-2fc84389248a">Stop Building Features &amp; Start Solving Problems</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[“Correct” design process doesn’t exist]]></title>
            <link>https://medium.com/@ashleytimm90/correct-design-process-doesnt-exist-079bad442cd7?source=rss-80853a7a35f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/079bad442cd7</guid>
            <category><![CDATA[ux-design-portfolio]]></category>
            <category><![CDATA[design-culture]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <category><![CDATA[product-design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ashley Timm]]></dc:creator>
            <pubDate>Mon, 25 Nov 2024 05:46:16 GMT</pubDate>
            <atom:updated>2024-11-25T06:10:09.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I6234LZG0ZFR7M5NqtqpxQ.png" /><figcaption>Image originally by <a href="https://stock.adobe.com/contributor/201100175/vector-tradition?load_type=author&amp;prev_url=detail">Vector Tradition</a>, but with some added flair.</figcaption></figure><p><em>These frameworks are inconsistent at best, and harmful at worst. Disclosure: Typos are my super power.</em></p><p>Sequential, concurrent, iterative, waterfall, agile, linear, double diamond, triple diamond, spiral, honeycomb. Ideation, conception, design, production. Discover, develop, deliver.</p><p>Ok ok, I think you get the point. And honestly, I’m sure there are even more. Each of these frameworks has their own unique quirks, but ultimately they’re attempting to accomplish the same thing: to capture the most effective, efficient, and collaborative process for design thinking and partnership across a company as a means to solve problems on behalf of users and businesses. So which one is the <em>right</em> one?</p><p>Here is my hot-take on this (if the title didn’t clue you in already): <strong>A correct design process doesn’t exist.</strong></p><p>When I started in my career, I was a firm believer in the whole “fidelity of the artifact should match the fidelity of the idea” concept. This was how I justified starting every design project in tangible sketches <em>(do the kids still do these now-a-days?)</em>, wireframes, and grey scale workflows. This idea that all projects needed to start at this exact stage was pretty cemented in my definition of design as a practice. There is a correct place to start, and that is with mountains of questions, and sketches.</p><p>I don’t think it’s <em>bad</em> advice — It’s just hopelessly optimistic.</p><p>The idea that design process had a ‘right’ and ‘wrong’ way was something I fully believed in. If it didn’t follow an exact order of operations and check the boxes, well then, you were doing it wrong. This is what, to me, separated Design from Art: Design had a correct and incorrect application, and Art was up for interpretation. There is something very comforting about that level of structure. But the longer I’m in the industry, the more I see what a load of crap that is…</p><p>Ok, admittedly that was harsh — but the truth is, design isn’t that tidy most of the time, at least once you’ve graduated beyond total beginner. Design is fluid. It’s the ability to acclimate to that fluidity that can make your design beautiful as well as impactful. Truly impactful designers can identify the correct tools at the correct fidelity at the right time to <strong>convey the idea</strong>. Sometimes thats a paper prototype, sometimes you can’t communicate the low fidelity idea without higher fidelity UI.</p><p>Now to clarify: Structure and definition isn’t bad, but <em>rigidity</em> around design process is. <em>That’s</em> what I’m calling out here. It’s the mark of a young designer, as well as a less mature design culture. Frameworks are helpful when learning design and explaining the general principals of the discipline. But if thats where the <em>designer</em> stops, then their growth (or lack there of) will forever be confined to those tools and single minded way of thinking. All you’ll ever know is how to use a handful of relatively linear phases that make up the basics. Your career, and your work, will suffer because of it. I think thats why so many of the case studies I see read so similarly… new designers are using the same tools in the same order. Every. Single. Time. Perhaps it gets you to <em>an</em> answer, but it’s not the road to innovation.</p><p><strong>Example 1</strong>: Lets say you want to build a bookshelf. Without any context in what you want to build, I give you wood, a hammer, screwdriver, and a saw. I didn’t know what you’d be building when I packed the tools, but it doesn’t matter cause I tell you those are the only tools you can use. I also tell you the way you should use them and in what order. Sure you can probably pivot between a couple here and there, but overall this is the way you should go about it. (already feeling pretty bland isn’t it?)</p><p>You will probably find a way to build the shelfs, but two things are happening:</p><ol><li><strong>You are now thinking just as much about the tools as what those tools are enabling you to do.</strong></li><li><strong>You’re immediately boxed in, and you haven’t even started yet</strong>. You’re not thinking about how to build the <em>best</em> bookshelf, your brain power is now prioritizing the tools and what they allow you to do.</li></ol><p><strong>Example 2:</strong> Imagine using the exact same blueprint for every singe house in a neighborhood (little boxes song comes to mind). It will technically get the job done. You’ll have a neighborhood with livable homes and streets. But this isn’t the best approach if what you’re after is the most lovable neighborhood as possible, expanding your skills, trying new things, or create any level of character/interest. The house template could be truly stunning — but even great things get boring and less innovative with consistent repetition.</p><p>I remember once when I started on a new design team, the manager was walking through our “new” design process: a triple diamond framework to help designers know what to do and when, as well as to help partner teams know how to engage with us. The sentiment was great. The application was well thought out. But the only thing I kept thinking while looking at it was “<em>this is great, but this will never happen</em>”.</p><p>I can see how this might make me sound like a jaded cynic. However I stand by it — diamond, circle, square, line; the process isn’t (shouldn’t be) that tidy. You may not even start a project at the beginning of that first diamond.</p><p>So then this begs the question: why do we keep trying to nail down a specific process? Who are we doing this for? Is it for new designers? Stakeholders? Leadership? These visual aids are inconsistent at best, and harmful at worst. Well intended as they are, often they end up holding designers back. Particularly mid level designers who may not need to rely on high levels of structure, but think they’re <em>supposed</em> to do exact steps at exact times. So like in the example above, they are thinking just as much about the correct tool/phase/step as what it’s enabling them to do.</p><p>Designers who really know their stuff caters their process to the problem, not the other way around. They look at what it is they are trying to solve for, and pick out a few tools in different orders to solve the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJ6Dw7hL7Rvz2bOl3wZENQ.png" /><figcaption><em>Beginner, diagram description: Drawing of a happy tidy linear design process. All is well</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W3NmQniok5xgTb6pOIDcFQ.png" /><figcaption><em>Mid level, diagram description: a little more chaotic but attempting to “do it the right way”. Using familiar go-to methods to solve problems, but running into some limitations while trying to do it the ‘right’ way.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RybJF3vvY52xbcDL5q3z3g.png" /><figcaption><em>Senior, diagram description: drawing of similar phases but with lines jumping between in a decidedly </em>non-linear<em> way. This could have even more lines, but i ran out of flows permitted by the free version of this plug in… the point is each of these phases is arguably optional and my occur more than once. It’s up to the designer to decide.</em></figcaption></figure><p><strong>Recommendation</strong></p><p>At the beginning of a project consider what the <em>problem</em> needs not what you think you <em>should</em> do. Lay out all your tools, and make a recommendation for which ones <strong><em>you</em></strong> think would be most effective, when and why. You can also change your mind mid way through — X isn’t working? Don’t keep cranking on it just cause it was part of the original plan, take a moment to consider if this is the right tool for the job and don’t be afraid to re-evaluate. It’s ok to completely pivot mid project and decide that a prototype usability study isn’t required and what you really need is a card-sort exercise.</p><p>A very tactical mechanism I’ve encouraged to help with this is a Project Page. This artifact can go by a few different names; <em>Design brief, approach document, kick off, one pager,</em> the sentiment is pretty much the same. However the critical element here is that it allows you to gather all the known information in a singular place, identify the gaps, THEN lay out what your process is going to be. Sometimes the first thing you need to do is research, and sometimes you don’t need additional research cause you have mountains of it already. This allows you to completely change the “design process” to what will best suit the project.</p><p><strong>Ok, now what?</strong></p><p>Just throw all these frameworks out the window? Everyone doing whatever willy-nilly idea comes to mind? Have full-fledged anarchy?</p><p>No, not at all. But perhaps <strong>identify who in your organization are you’re creating these processes for</strong>. Don’t create a one-size-fits-all system. What your stakeholders need to know about how to best partner with design and when may different from how your designers approach a problem. And coaching for new designers is very different from how a more tenured designer may work, so stop pushing for a ‘correct’ process.</p><p><strong>Leadership</strong>: Give your designers the freedom to tell you what <em>they</em> think the approach should be for each project. Don’t dictate the process, but allow them to take some time at the beginning of a project to let you know what they think the approach and process should be.</p><p><strong>Designers</strong>: Don’t connect lines between your tools and phases at the start. Lay everything out first, then recommend the ideal order of operations that will get you to the best solution. Even outline which are mandatory or ‘nice to haves’ (<em>Designing, design thinking? Nice.)</em></p><p>I’ve been privileged enough to have several managers who have allowed me this freedom, which is probably why I’m such a critic of rigid process. My current team has granted me the space to find a process for how MY mind likes to work through problems.</p><p>And if you’re on the nero-spicy side of the spectrum like me, then this will actually free you up to do some of your very best work. You won’t be thinking about how to morph your brain into a pre-determined box — you’ll create a process that fills the needs you have, and foster a culture of diverse approaches and ideas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=079bad442cd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identifying areas of growth: How to accelerate your advancement]]></title>
            <link>https://medium.com/@ashleytimm90/identifying-areas-of-growth-how-to-accelerate-your-advancement-59bc5cc31ea4?source=rss-80853a7a35f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/59bc5cc31ea4</guid>
            <category><![CDATA[woman-in-tech]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[career-goals]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ashley Timm]]></dc:creator>
            <pubDate>Wed, 06 Nov 2024 21:52:52 GMT</pubDate>
            <atom:updated>2024-11-25T06:08:16.834Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zJFK1FEIOAZYfmzWzpbwUQ.png" /></figure><h3><strong>Do your career a favor: Don’t be a design generalist forever</strong></h3><p>As we approach the end of the year, thoughts of New Year’s resolutions and annual reviews loom. While many focus on addressing weaknesses as much as praising strengths, if you’re looking to advance your career in 2025 here is what I’d recommend: Stop being a design generalist.</p><p>For beginners early in their career (0–2 years) being a generalist is great. I highly recommend this for all newbies out there. This is critical for not only identifying <em>what</em> you’re awesome at (it may be different than you thought!) but will ensure that you don’t have major skill gaps that actually hold you back. It’s ok to have strengths and weaknesses, but a gap in skills is a lot harder to overlook by potential hiring managers.</p><p>However for the more mid-level individuals (2–5 years) who want to jump-start their advancement, I encourage a different approach on goals and growth.</p><p><strong>Growth </strong>≠<strong> Fixing Weaknesses</strong></p><p>Growth areas are not things you’re bad at, and thus want to improve. At least they don’t have to be. Growth areas for those wanting to advance should be things you know you’re already good at, but want to double down on, expand, or go from good to expert. In fact, I’d argue that turning every area you’re not good at into a goal for growth is not only an inefficient use of time and energy, but is a one way ticket to mediocrity.</p><p>I was guilty of this for a long time. I looked at ‘areas of growth’ as highlighting the things I wasn’t good at. Personal and professional development centered on identifying and improving areas of weakness. I looked at the definition of ‘growth’ as “<em>areas I want to not suck</em>”. I’m not alone in this either; I’ve heard this narrative from tenured designers and managers alike.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PRT_sgBOw5mDd923rtLCtw.png" /></figure><p>This made a hard pivot for me several years back, and its completely changed my thinking on my own career. I had a manager several years ago who told me this exact principal: That “areas of growth are not things you’re bad at”. I think I did a little <em>‘smile and nod’</em> number, cause it just did not compute. In my mind, strengths were good-to-go check boxes of success and ‘areas of growth’ were the bad grades I needed to pull up. It wasn’t till several years later that this clicked for me as I was thinking through career goals, and I thought about how I didn’t want to just be good at something, I wanted to be <em>great</em>.</p><p><strong>Don’t waist your time</strong></p><p>I was recently talking with someone about this, and used how I’m horrible at spelling as an example. Full transparency, I’m not just bad, but <em>truly horrendous</em>. No red squiggly line? Looks right to me! Anyway the point is, this is something I regularly noted as a ‘growth area’ for years. Until eventually I decided that I didn’t think it was a good use of all the time I was investing in it. So much of my brain power was going into checking every single line of copy in Google (<em>this was back before Sketch had spell-check, and yes back when Sketch was a thing</em>) and all that energy could have been better used in growing a skill that could go from good to great. How much time and energy would I have saved if I hadn’t been so stressed-out about if I spelled something incorrectly?</p><p>Arguably, as long as it’s not complexly illegible and it’s not going into production, who cares about a few typoes? <em>(see what Idid there?)</em></p><p>Conversely, I’ve always been a decent communicator (if a bit verbose), and this translated into my ability to tell stories and present in front of groups. I didn’t seem to have the same struggle I’d seen in friends who were paralyzed by the idea of public speaking — sure it still made me nervous, but I’ve always been pretty good at talking. I decided a goal of mine would be to not just be good, but be great: To be comfortable speaking to large groups and come across completely at ease with complicated subject matter, avoid filler words (um, uh), and captivate my audience.</p><p>Focusing my energy on improving this single skill, that I already considered to be a strength, has led to huge improvements in my ability to articulate my ideas, and communicate to a broad range of people. I’m now able to better convey highly complicated ideas through stories and my work has improved as a result.</p><p>Am I ready to give a TED talk? <em>Absolutely not</em>. I’m still what I would consider decent, but not an expert. But this is an example where I took a self-identified strength and decided to invest my ‘growth energy’ on it, rather than focusing on my shortfalls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VOT6vZIDHV23y2CGcIPu2w.png" /></figure><p>This can be a bit of a tightrope. The exception to this, is if a weakness is <strong>holding you back from overall success</strong>. Using this same example of spelling: if it was bad enough that I wasn’t able to accurately communicate my idea, or it confused people when looking at my work, then thats when I’d need to implement goals or mechanisms for improvement.</p><p><strong>Time is a Limited Resource</strong></p><p>To clarify, I’m certainly not saying that improving upon deficits isn’t a worth while endeavor. It absolutely is. But it comes down to the value of the investment. What is the pay-off of improving a skill at this moment? Time is a precious and finite resource. When designers spend excessive time on weaknesses, they miss opportunities to excel. This can lead not only to mediocrity across the board instead of excellence in key areas but reduced innovation, and lower job satisfaction (<em>as people tend to enjoy tasks they’re good at more than those they struggle with</em>).</p><p>Tactically, this could manifest as designers spending time learning complex coding skills when their strength lies in architectural design, potentially resulting in both subpar code and less insightful UX frameworks.</p><p><strong>The last peace of the puzzle</strong></p><p>Probably one of the most important elements of all this is: <strong>Desire</strong>. What do you WANT to be good at? It’s entirely possible that one of your weaknesses IS what you want to be great at. What I’m advocating for is not choosing your goals simply <em>because</em> they are a weakness. Find the parts of your work and process you enjoy (which also tend to be what we’re good at), and find ways to build upon your existing talents in order to become a highly desirable expert on a team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vsck8AUXZ3BtznHM4W9SDQ.png" /></figure><p>Reframing growth from fixing weaknesses to leveraging strengths can help you separate yourself in this very saturated industry of design. Your goals will have higher impact on your advancement, and you’ll immediately start to see the results in your work.</p><p>It’s also my belief that a team of designers with deep, complementary expertise can create significantly better products than a team of generalists of the same size. A combination of specialized skills can lead to more innovative, refined, and user-friendly products than a team of generalists all tag-teaming a project together.</p><p>Don’t fixate on all the areas you feel like you’re <strong>missing</strong> the bar, but instead identify where you want to <strong>set</strong> the bar.</p><p>—</p><p>Thanks <a href="https://www.linkedin.com/in/kevin-mlz/overlay/about-this-profile/">Kévin Moënne-Loccoz</a> for the Figma assets!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59bc5cc31ea4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating Input: A New Designer’s Guide to Prioritization]]></title>
            <link>https://medium.com/@ashleytimm90/navigating-input-a-new-designers-guide-to-prioritization-c2a4343d97bc?source=rss-80853a7a35f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2a4343d97bc</guid>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[beginners-guide]]></category>
            <category><![CDATA[ux-feedback]]></category>
            <category><![CDATA[ladieswhoux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ashley Timm]]></dc:creator>
            <pubDate>Mon, 28 Oct 2024 14:22:08 GMT</pubDate>
            <atom:updated>2024-10-28T15:35:43.568Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Navigating Input: A Guide to Prioritizing Input for New Designers</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cmn7IiF9lnWAH9BmOa284A.png" /></figure><p>If you’ve been in the industry for more than five minutes, you’ve likely encountered the challenge of managing input from various stakeholders, and trying to prioritize feedback that often contradicts.</p><p>As you advance in your career, you start to encounter this more and more as the scope of your impact expands. It’s an inevitable hurdle, so I guess the first take away here is: <em>get use to it.</em></p><p>All is not lost however. I know it’s challenging when you hear one piece of feedback, and another, then another, and now you’re not sure who you’re suppose to be listening to (<em>insert dizzy face here</em>). Here is how I’ve found success in approaching these situations with confidence and clarity.</p><p><strong><em>Develop a solid perspective.</em></strong></p><p>The most important thing is knowing <em>why</em> you made certain choices, and know how to articulate your rational. This one can be tricky. Often we don’t think about our work in terms of a narrative. However, that narrative is exactly what is going to pull your thinking out of Figma, and into the real world. Being able to explain not only <em>what</em> you did, by <em>why</em> you did it shows that you’re choices aren’t arbitrary. It may seem like this should be a given, however anyone you show your work to is going to start poking holes; so anticipate what those may be and have a responce ready.</p><p>Now, I’m not saying to have an unwavering point of view, but if you don’t have a foundation on which to stand, you’re much more likely to be pushed around by every input thrown your way.</p><p>Ok, now bare with me… the way my mind visualizes this is in blob shapes (pictured). Your idea is a ball in the middle, and inputs are thrown at it from all directions. (1) Too ridged: This is the idea that starts and ends looking almost exactly the same. You don’t absorb the ideas of others. You hold to your own perspective so steadfastly, inputs bounce right off your work. (2) Too malleable: This is the idea that is unrecognizable from the original intent from all the ideas thrown at it. Your point of view is completely lost in the noise of inputs. You’re no longer able to accurately defend your work because you’re not quite sure how you got to this point. (3) Firm but flexible: This idea absorbs what makes it more durable, but is able to let some input bounce off. A way to differentiate between inputs that benefit the project is you can defend the ideas with confidence and explain them to a broad audience. If you can’t explain the rationale you’re ether not bought in or don’t understand why a choice was made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*myJT_TMQf-nIkMbdpnX-9Q.png" /></figure><p>What we’re looking for is a solid, but bendable point of view. This will allow you to assess each input, and decide which absorb, and which to reject.</p><p>This is why identifying your stance is so important: without it, it’s more likely you’re going to get overwhelmed by all the input you receive. Don’t wait for someone else to tell you what direction you should go in. Go into the conversation with a point of view, but be willing to pivot if better ideas come along — especially if they make your designs better (<em>spoiler: if you are able to prioritize your inputs, your work is always better for it.</em>)</p><p><strong><em>Articulate Your Rationale Clearly.</em></strong></p><p>Practice talking about your work with friends or mentors, and consider creating a design decision log to track and articulate your choices. I’ve even recorded myself explaining something out loud, alone in my office, just so I could hear how I was talking about my work. I’d also recommend recording your self, and waiting a day or two and listen to it fresh. You may, for better or worse, surprise yourself.</p><p><strong><em>Leverage Data to Support Your Decisions.</em></strong></p><p>We often make decisions based on intuition honed through experience. However, when faced with conflicting opinions, data becomes your strongest ally. People find it harder to disagree with numbers and facts than with subjective preferences, so as much as possible, your point of view should be anchored in established design principles and cold hard data.</p><p>It’s also essential for you to differentiate between your fact-based decisions and those driven by personal experience, anecdotes, and preferences. Facts trump feelings when it comes to defending your choices. This is also a good barometer for which aspects of your work you should defend, and which you are willing to sacrifice. After all, there really is no accounting for taste.</p><p>And don’t let a lack of company-specific data hold you back! You can draw from broader industry knowledge and established design best practices. I’ve personally used data from sources like Statista, or industry news published by Forbes when speaking about design rational.</p><p>Remember, your unique perspective in design is valuable. By developing a solid, data-driven approach to prioritizing input, I guarantee you’ll not only improve your designs but also build your confidence and influence within your organization.</p><p>What strategies have you found helpful in managing stakeholder input?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2a4343d97bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The double-edged sword of passion: When putting your heart in your designs holds you back]]></title>
            <link>https://medium.com/@ashleytimm90/the-double-edged-sword-of-passion-4167b09c8462?source=rss-80853a7a35f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4167b09c8462</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ladiesthatux]]></category>
            <category><![CDATA[woman-in-design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Ashley Timm]]></dc:creator>
            <pubDate>Wed, 23 Oct 2024 23:21:44 GMT</pubDate>
            <atom:updated>2024-11-06T22:00:26.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1rj2jOwUofkaDYhKUzB-cg.png" /><figcaption><em>image inspired by a </em><a href="https://stock.adobe.com/contributor/207466025/andrii-yalanskyi?load_type=author&amp;prev_url=detail"><em>Andrii Yalanskyi</em></a><em> photo</em></figcaption></figure><p>If you are in the design industry, odds are that you’re an inherently creative person; and as ‘creatives’ we put pieces of ourselves into our work. This, in fact, is a huge part of what makes us successful in what we do! It’s our job to put ourselves into the shoes of the people we’re solving problems for, and care deeply enough about those problems to formulate a solution and execute it. This is what ‘having empathy’ is all about, right? And when we give a presentation that knocks the socks off of leadership, we walk away with the after-glow of pride for days. But what happens when this emotional connection to our work becomes a liability?</p><p><strong>The Dark Side of Emotional Investment</strong></p><p>While passion fuels our creativity, it can also leave us vulnerable to criticism and rejection. Not only when we get tough critique, but it can also make us less likely to take risks.</p><p>The problem with putting so much of ourselves in our work is when it comes time for a critique or pitch, and the feedback is that the design or concept isn’t working as well as you thought. Maybe it isn’t ‘quite there’, or the worst of all… that you need to go back to the proverbial drawing board. You identify yourself with your work, and if your <em>work</em> is rejected then so are <em>you</em>. The work you were so proud of wasn’t perfect so you obviously need to throw your computer out the window, change careers and move to another state. None of that is true obviously (<em>mellow drama is one of my super powers</em>) but it can certainly feel that way in the moment. Our work is personal, and we wouldn’t be doing it if we weren’t passionate about it.</p><p>This emotional rollercoaster can be exhausting and potentially damaging to your growth as a designer.</p><p><strong>Finding the Balance</strong></p><p>So, how do we strike a balance between pouring our hearts into our designs and maintaining professional objectivity? The answer lies in learning to separate our personal worth from the outcome of our work.</p><ol><li><strong><em>Have a growth mindset: feedback is an opportunity.</em></strong> Look at critique as valuable input that can help improve your designs. Keep in mind that most input isn’t explicit direction either; sometimes it is, but often you can take or leave that input which makes it a great opportunity to pull in only the things that will make your ideas stronger. View challenges to your perspective as opportunities rather than threats.</li><li><strong><em>Practice emotional detachment.</em></strong> While it’s important to care about your work, learn to create a healthy emotional distance. This can help you evaluate your designs more objectively and handle feedback more professionally. And this can happen later in the process too! Think of your designs as your kids: they’re completely dependent on you in the beginning, but in order for them to become their best selfs, you need to pull back and allow for other inputs to have an impact (and hope that your idea is solid enough to withstand all that input).</li><li><strong><em>Celebrate the process, not just the outcome.</em></strong><em> </em>Find joy and pride in the creative process itself, rather than focusing solely on the end result. This is one I personally struggle with. The final product is when I tent to step back and revel in the accomplishment. However, learning to take just as much pride in the ‘<em>how’ </em>can help you maintain enthusiasm even when projects don’t turn out as expected.</li></ol><p><strong>The Power of Perspective</strong></p><p>Ok, so this whole idea of not getting too attached is all well and good, but here is the paradox: As designers, our ability to empathize and care deeply about our work is our superpower. So, what is the answer? Too much heart = potential devastation, no heart = soulless work.</p><p>Here is the advice I recently gave a mentee: <em>Pour your heart into your designs, but don’t leave it there. </em>Allow them to flourish and benefit from other perspectives. Doing this well ensures you can harness the power of your passion without being held back by it.</p><p>By finding the right balance between emotional investment and professional objectivity, we can create amazing designs while protecting our well-being and fostering long-term career growth.</p><p>Your passion is what makes you a great designer—let it propel you forward while maintaining a healthy perspective on your work and your worth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4167b09c8462" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>