<?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 Astrid (she/her) on Medium]]></title>
        <description><![CDATA[Stories by Astrid (she/her) on Medium]]></description>
        <link>https://medium.com/@astridparisux?source=rss-ab908a26ef12------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SfmEvsVrTn5Gp1GYXn0W-w.jpeg</url>
            <title>Stories by Astrid (she/her) on Medium</title>
            <link>https://medium.com/@astridparisux?source=rss-ab908a26ef12------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:10:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@astridparisux/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[Connecting Across U.S. Party Lines by Honoring COVID-19 Losses]]></title>
            <link>https://astridparisux.medium.com/connecting-across-us-party-lines-by-honoring-covid-19-losses-71fdff52e62e?source=rss-ab908a26ef12------2</link>
            <guid isPermaLink="false">https://medium.com/p/71fdff52e62e</guid>
            <category><![CDATA[coronavirus]]></category>
            <category><![CDATA[grief-and-loss]]></category>
            <category><![CDATA[pandemic]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[inauguration]]></category>
            <dc:creator><![CDATA[Astrid (she/her)]]></dc:creator>
            <pubDate>Mon, 18 Jan 2021 19:34:22 GMT</pubDate>
            <atom:updated>2021-01-18T19:48:15.415Z</atom:updated>
            <content:encoded><![CDATA[<p>Regardless of how you feel about it, we’re inaugurating a new U.S. president on January 20, 2021. How can people come together in this country despite their differences? The pandemic. For better or for worse (and whether you like it or not), this global pandemic has <strong>interconnected</strong> us all. From decreased pay to job losses, from working from home or schooling from home, from entire industries on the verge of collapsing — we’re <em>all</em> directly or indirectly experiencing these changes <em>at the same time.</em> There are many parts of the puzzle of 2020+ that make the state of affairs seemingly impossible to improve (from whatever side of the fence you’re on). Here’s one thing you <em>can</em> do to ensure that these new connections we all now have are not totally wasted on anger towards either side. <strong>You can honor a fellow American’s COVID-19 loss.</strong></p><p>I recently lost my father to COVID-19. It’s a fair, natural reaction to say “he was old, anyways” or “we’re all going to die eventually.” While it is true that there’s a circle of life, and that my father had many comorbidities, he was <strong>#NotJustANumber</strong>.</p><p>For those of you who don’t think the virus is real, don’t believe it’s that big of a deal, or are dubious of the <strong>398,000 U.S. COVID-19 deaths</strong> on the charts, I understand. We all see the world through our own personal lenses, and I understand that what <em>you</em> see might not be what <em>I</em> see.</p><p>I see a father and husband who wasn’t protected by the very systems meant to do just that. I see daughters who pleaded for information and communication but were kept in the dark. I see a family who was robbed of the possibility of saying goodbye. I see family and friends who were deprived of the opportunity to mourn together and honor a kind, loving man who served his country. I see the trauma lived out over and over again each time these people hear about COVID-19 on the news or learn about friends and family contracting the virus, trying to show up for life each day with the fear that they might again lose another. I see the helplessness of not being able to do anything about any of it.</p><p>I can only imagine what my father saw, and if he felt as helpless as we did and still do now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*eGcrNW03gD7Y1NYJGsIDAw.jpeg" /></figure><p><a href="https://khn.org/news/bereaved-families-are-the-secondary-victims-of-covid-19/">Grief and loss during a pandemic</a> is an extra special hell. <strong>Whatever your political views are this inauguration day, I invite you to honor the losses experienced by your acquaintances, friends, coworkers, and communities by watching virtually the </strong><a href="https://bideninaugural.org/covidmemorial/"><strong>COVID-19 Memorial ceremony</strong></a><strong> on Tuesday, January 19, at 5:30 p.m. EST. </strong>You can witness the first-ever lighting of the Lincoln Memorial Reflecting Pool to memorialize the nearly <strong>400,000 people</strong> who have died in the U.S. from the virus. And maybe we can set aside our differences for just a short while to show compassion towards humanity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71fdff52e62e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project Retrospectives at Digital Agencies]]></title>
            <link>https://astridparisux.medium.com/project-retrospectives-at-digital-agencies-bbbc7ad0e2de?source=rss-ab908a26ef12------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbbc7ad0e2de</guid>
            <category><![CDATA[agency]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Astrid (she/her)]]></dc:creator>
            <pubDate>Sun, 19 Nov 2017 23:20:50 GMT</pubDate>
            <atom:updated>2018-02-05T04:03:40.141Z</atom:updated>
            <content:encoded><![CDATA[<p>If you work at a digital agency, I bet you love swirling on a client project. There’s just something about unspoken expectations, painful processes, finger pointing, and missed deadlines that keeps us all motivated to continue coming into work every day to do what we love to do. It’s all <em>so</em> awesome that we maintain this paradigm no matter the client, budget, team, requirements, or timeline! #winning</p><p><strong>…said no team member EVER. </strong>“Insanity is doing the same thing over and over again and expecting different results.” — Albert Einstein <em>(maybe)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*IfXreLZBToLYGZNBQYIJYA.gif" /><figcaption><a href="https://giphy.com/gifs/crazy-insane-will-ferrell-Dp7POJcVxRDUc">https://giphy.com/gifs/crazy-insane-will-ferrell-Dp7POJcVxRDUc</a></figcaption></figure><p>For healthier, happier agency teams, you need to <strong>inspect and adapt </strong>(whether you’re “doing agile” or something else). Agencies can help stop the insanity by adopting retrospectives as part of their project framework.</p><h4>What’s a retrospective?</h4><p><a href="http://www.dictionary.com/browse/retrospective">the definition of retrospective</a></p><p>Team retrospectives (“retros,” for short) were popularized by agile software development. One of the <a href="http://agilemanifesto.org/principles.html">principles of agile</a> is to reflect on the past in order to adjust the future: “At regular intervals, the team <strong>reflects</strong> on how to become more effective, then <strong>tunes and adjusts</strong> its behavior accordingly.”</p><p>The <a href="https://www.scrumalliance.org/community/articles/2014/april/key-elements-of-sprint-retrospective">Scrum Alliance describes a retro</a> as “…an important mechanism that allows a team to <strong>continuously evolve and improve</strong> throughout the life of a project.”</p><h4>How can retrospectives help agencies with client projects?</h4><p>I first learned about <a href="http://daxko.com/blog/2013/06/agile-retrospectives-as-group-therapy/">retros while working at a SaaS company</a>. There, product teams held retrospectives after each development sprint (so, every two weeks). Retrospectives are a great opportunity to squash tension, give kudos, and identify process improvements. But <strong>retrospectives aren’t just for agile development teams! </strong>This kind of meeting can benefit just about any group of people who have to work together. All you need is respect, candor, and a bias towards action.</p><blockquote>Retrospectives are a great opportunity to squash tension, give kudos, and identify process improvements.</blockquote><p>Retros are a team sport — they facilitate communication and trust-building because team members openly share wins, misses, and wishes. Great retros can help teams figure out:</p><ul><li><em>What</em> was painful during a project</li><li><em>Why </em>that thing was painful</li><li><em>How</em> to remove/reduce that pain for next time</li><li>Whether the project pains are <em>systemic</em> (e.g., at the client account level or even internally at the organizational level)</li></ul><p>Once teams actually reflect on a project and really start to understand <em>why</em> things happened the way they did, they can then identify what to keep and what to change so that they don’t end up repeating the things that they shouldn’t. Culture bonus: Getting everyone on the project team involved in deciding how to move forward encourages accountability and instills a sense of ownership.</p><p>Try scheduling a one-hour team retrospective after your next client project. If you end up getting even ONE improvement out of it, then now you’re #winning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbbc7ad0e2de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips for Being a Hackathon Design Mentor]]></title>
            <link>https://astridparisux.medium.com/tips-for-being-a-hackathon-design-mentor-bf94deb30f5a?source=rss-ab908a26ef12------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf94deb30f5a</guid>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Astrid (she/her)]]></dc:creator>
            <pubDate>Sun, 15 Oct 2017 22:59:56 GMT</pubDate>
            <atom:updated>2019-06-12T14:34:41.895Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently had my first experience in a mentor role at a hackathon. I’m sharing my top takeaways to help other designers be more prepared for <em>their</em> first time as a design mentor:</p><ul><li>Focus on the hackathon.</li><li>Share what you know. Don’t be afraid to say when you <em>don’t</em> know. Try really hard to not design FOR teams.</li><li>Don’t forget to network!</li></ul><h3><strong>First things first.</strong></h3><p>I’m in <a href="https://en.wikipedia.org/wiki/User_experience_design">UX</a>. I’d only been to one other hackathon before this one, a techforgood-type hack to help solve municipal problems. And I had such a bad experience that I left before midnight <em>on the first night.</em> In a nutshell, I joined a team that had already worked together at previous hackathons, had no interest in working with anyone new, and even worked separately from each other in different areas of the huge room that all the teams were hacking in. I was coming down with a cold, and after getting the cold shoulder from this team for a few hours, I ultimately decided to just pack up and go home. (In hindsight, if that ever happened again, I’d probably just go try to find another team to join or offer up myself in a mentor capacity.) That was many years ago, and since then, I’ve been <strong>turned off by the thought of going to hackathons.</strong></p><p>When I saw the <a href="https://www.womenwhocode.com/atl">Atlanta Chapter of Women Who Code</a> tweet about their second-annual <a href="http://www.wwcodehackathon.com/">WWC Hackathon</a>, I briefly considered participating. I’d gone to a WWC event a few years before and was impressed by the smarts, personalities, and professional drive of these ladies, so I felt like I’d have a much better hackathon experience this time around. But then I saw the APB for mentors they needed. I applied to be a UX/UI design mentor because I felt that would be a less-intense way to dip my toes back into that scene. I ended up only being able to participate for one of the three days the hackathon was going on, but it was still worth it. Here are some <strong>things to think about if you ever want to volunteer as a design mentor</strong> for a hackathon.</p><h3><strong>Focus on the hackathon.</strong></h3><p><strong>Don’t go out drinking with friends the night before.</strong> Don’t stay out late the night before. (Actually, just avoid doing <em>both</em> of those.) It’s probably in your best interest to NOT commit to anything else for the hackathon duration. You want to have a clear head when you’re mentoring since you’re not going to be intimately familiar with each project’s details, and that tequila from the night before probably isn’t gonna contribute to that clarity.</p><p>Since I had some weekend plans already before I was confirmed to be a mentor, I could only do the Saturday afternoon/night of the hackathon (about 10 hours). If I could have made it work, I would have been there for the whole thing. It would have been best if I went Friday night (the first night) to meet the teams, organizers, and other mentors. Hearing the project pitches that night would also have provided with me more context around team direction and goals when I did actually provide help on Saturday. And honestly, I wish I could have been at the hackathon even <em>earlier</em> that second day — because that’s when the teams were planning their product vision, business strategy, and high-level features (AKA the “big-picture, strategy stuff” I love thinking through).</p><p>Even though I was only at the hackathon for a relatively short time, I still had a lot of fun <strong>helping teams think through design problems.</strong> My project work IRL these days seems mostly about trying to create shared understanding (internally and externally), defining and documenting interaction details for design handoffs, and generally making sure the holistic design of a digital experience isn’t janky. Because I’m a senior practitioner and work with other, cross-functional senior practitioners, seldom do I need to verbalize my design process. So, <strong>it was a little awkward at first trying to coach non-designers.</strong> I quickly learned that my design process and critique is generally the same whether I’m doing billable work for a client or volunteering at a hackathon. Create shared understanding, ask questions, suggest best practices, suggest things to think about, communicate potential tradeoffs. SSDD.</p><blockquote>Create shared understanding, ask questions, suggest best practices, suggest things to think about, communicate potential tradeoffs.</blockquote><h3><strong>Share what you know. Try really hard to not design FOR teams. Don’t be afraid to say when you DON’T know.</strong></h3><p><strong>If you suffer from “</strong><a href="https://medium.com/the-year-of-the-looking-glass/the-imposter-syndrome-9e23e2326d88"><strong>imposter syndrome</strong></a><strong>,” then you should totally volunteer to be a design mentor at a hackathon. </strong>Regardless of how you think you stack up at work, if your <em>paid job</em> is UX, then you’re going to automatically have tools and frameworks at your disposal that non-UXers just don’t have. I’m not necessarily talking about actual <em>tools</em> like Sketch, Bootstrap, etc. I’m talking about <strong>design thinking, design patterns, interaction design principles, color theory, information design, guerrilla user testing</strong>…all the things we UXers have in our back pockets that come second-nature to us. These things probably won’t be second-nature to your hackathon teams, so <strong>you can help coach them to make better design decisions by sharing your knowledge about <em>how to approach </em>design problems.</strong></p><p>Which brings me to another point: <strong>Try your best not to DO the work for your teams.</strong> Guide them, share best practices (think <a href="https://developer.apple.com/ios/human-interface-guidelines/overview/themes/">iOS Human Interface Design Guidelines</a>), prod them, offer up choices. Try really hard to NOT pick up a marker unless you really need to whiteboard something to help communicate. (Again, this was my first time being a design mentor, so who knows how anyone else approaches this! My instinct was to teach them how to fish.)</p><blockquote>Guide them, share best practices…, prod them, offer up choices… My instinct was to teach them how to fish.</blockquote><p><strong>There will probably be times when you don’t have the answer(s) or can’t give a team what they need.</strong> Here’s an example: One team needed help with logo creation. I suck at illustration, but another design mentor did not. This mentor didn’t like the process of <em>getting to</em> a logo concept, so we split the task of helping the team with logo creation. I brainstormed word associations with the team, introduced them to the <a href="https://thenounproject.com/">Noun Project</a> (rabbit holes for days; you’ve been warned) for further inspiration, and then the other design mentor took over when it was time to actually design some concepts. Being an effective coach means being honest about what you can and can’t offer in terms of help.</p><blockquote>Being an effective coach means being honest about what you can and can’t offer in terms of help.</blockquote><h3><strong>Don’t forget to network!</strong></h3><p>One really surprising part of my mentor experience was connecting with all of the other mentors. It had been a couple of years since I worked in the software or startup space. I had basically stopped going to tech meetups altogether, so the kinds of conversations I had at the hackathon were the kinds I hadn’t even realized I was missing. Sharing stories about local startups, founders, connections in the SaaS space, dev tools, APIs, DesignOps, whaaa?! <strong>I forgot how much I loved talking shop like that with people who nerd out as hard as I do about that stuff.</strong></p><p>It was equally as cool to connect with the hackathon participants during breaks. It’s always fun to hear people’s stories about how they came into tech. I met a chick who started out in marketing and is now a legit coder who specializes in data analytics; a front-end dev who turned her focus from UI to to the UX of dev tools; and a student who still has some college left but now just wants to hit the ground running in order to make an impact and continue learning in the real world (because doing is better than watching).</p><p>All in all, I had a pretty damn good time, and I can’t wait for the next one!</p><p>Women Who Code has a <a href="https://www.womenwhocode.com/blog/117">great write-up</a> about why women should get more involved in hackathons. You should read it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf94deb30f5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX is Not UI, It’s…]]></title>
            <link>https://astridparisux.medium.com/ux-is-not-ui-its-83ef67419dc?source=rss-ab908a26ef12------2</link>
            <guid isPermaLink="false">https://medium.com/p/83ef67419dc</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Astrid (she/her)]]></dc:creator>
            <pubDate>Wed, 19 Nov 2014 00:00:00 GMT</pubDate>
            <atom:updated>2019-06-12T14:27:21.469Z</atom:updated>
            <content:encoded><![CDATA[<p>If you haven’t heard by now, there’s a camp of UX folks who shout from the mountain tops, “UX is not UI!” The adage gets many an eye roll from people who don’t identify as UX at their core. I’m not one to chime in on semantic battles like this, but once I was asked (lightheartedly) if I fell into the aforementioned camp. This is what I should’ve said…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C8SXulapA5c9E-kwLDSfkQ.jpeg" /></figure><p><em>Originally published at </em><a href="https://www.astridparis.com/blog/2014/11/ux-is-not-ui"><em>https://www.astridparis.com</em></a><em> on November 19, 2014.</em></p><h3>UX is not UI, it’s product strategy.</h3><p>The longer I work in the tech field, the more I refine my professional philosophies concerning UX and what a person in this role can bring to the table. The myriad of things that need to get done at any company certainly merits having different roles to make sure those tasks get completed. While I’m not advocating that a UX person be the “owner” of everything, I do believe that tapping these kinds of folks for input on a variety of issues will do your team more good than it will harm. At the very least, here’s what<em> I</em> think about as a UXer working on software product teams.</p><h3>Innovation</h3><p>Are we <strong>raising the bar</strong> on what we want to build (or have built), or are we sticking ourselves in with the <strong>status quo?</strong> (That ol’ “faster horse” thing.) UX folks can offer help by looking at the competitive landscape through the eyes of user motivations and needs, context of use, accessibility, usability, and aesthetics.</p><h3>Value</h3><blockquote>Are we building the right thing at the right time? Are we building the right thing for the right user?</blockquote><p>Are we building the <strong>right thing at the right time?</strong> Are we building the <strong>right thing for the right user?</strong> Existence is rife with problems. Just because you have a solution to address one of those problems doesn’t mean that there’s not a <em>better</em> solution. Maybe the better solution is one that’s not so obvious- <em>that’s</em> the one what we should be figuring out.</p><h3>Analytics</h3><blockquote>You can build all you want. Having some metrics to validate your assumptions can help steer product direction from going down the wrong path.</blockquote><p>Did the thing we built <strong>get adopted?</strong> Should we continue to enhance that feature, or <strong>do we need more data</strong> to inform whether to keep going? You can build all you want. Having some metrics to validate your assumptions can help steer product direction from going down the wrong path.</p><h3>Messaging</h3><blockquote>UXers should give a damn about anything users see: system-generated emails, marketing communications, in-app notifications, microcopy, etc.</blockquote><p><strong>Do users know</strong> about the thing we built? What kind of vibe are we giving them? Are we being helpful or are we being frustrating? UXers should give a damn about anything users see: system-generated emails, marketing communications, in-app notifications, microcopy, etc. A consistent voice and tone across the brand positively impacts the user experience.</p><h3>Team</h3><blockquote>Do we have the right people in the right seat on the bus?</blockquote><p>Do we have the <strong>right people in the right seat</strong> on the bus? Having skills gaps can detrimentally affect your product. You can have a stellar idea, but without a people wrangler to help make sure things get executed, you’ll just have lots of stimulating conversations (and no stimulating product). You can have a kick-ass product but without someone who can get it in the hands of the right people, you’re looking at a shiny paperweight.</p><p>If you have a team that collectively covers all of your bases in the can-do department, how are they working <em>together? </em>Kick-ass product + organizational dysfunction = visible corporate underpants. (Don’t Google “product showing underpants.” I was trying to find a great example of my metaphor but those search results definitely did <em>not</em> contain one.) What I mean by that is if you have people working in silos, and there’s a lack of communication, you could end up with inconsistent messaging and design patterns. Happens all.the.time. A UX person who cares about the product will always be thinking about how to break down barriers to collaboration. Team — barriers = collaboration = happier team = ideas = better product = happier users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83ef67419dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recipe for Agile UX Design]]></title>
            <link>https://astridparisux.medium.com/recipe-for-agile-ux-design-6cb3e1b77583?source=rss-ab908a26ef12------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cb3e1b77583</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Astrid (she/her)]]></dc:creator>
            <pubDate>Sun, 16 Nov 2014 00:00:00 GMT</pubDate>
            <atom:updated>2019-06-12T14:42:53.078Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/441/1*2pzY7oo9kPYrDHHBQQI9-Q.png" /></figure><p><em>Originally published at </em><a href="https://www.astridparis.com/blog/2014/11/recipe-for-agile-ux-design"><em>https://www.astridparis.com</em></a><em> on November 16, 2014.</em></p><p>I’ve had the privilege of working for a software company that really “got” it when it comes to agile UX design and development. While our processes were far from perfect, most a of the time we were able to strike a decent balance between designing too far ahead and designing just in time. Here are some things we baked into our process that helped us do just that.</p><h3>Shared understanding</h3><p>On the team I worked on at this company, the product owner team (product manager, lead dev, and lead UX) <strong>drafted user stories and acceptance criteria well in advance of the desired sprint</strong> we wanted to put them into so that we could make sure we fully understood the business value we were trying to achieve even before we introduced the rest of the team to the story/epic. Once we had a pretty good grasp on that, we’d start introducing the story or stories to the rest of the team through “grooming.” <strong>Story grooming</strong> gave the entire team a chance to</p><ul><li>hear the problem we were supposed to solve,</li><li>hear the product owner team’s hypothesis of how to address it,</li><li>ask questions, and</li><li>talk about proposed solutions.</li></ul><p>We found grooming to be a critical step in keeping the development ball rolling, as it created a <a href="https://astrid-paris.squarespace.com/blog/2014/10/3-ways-to-minimize-cycle-time-in-software-development">shared understanding</a> among the team before even one line of code for a new feature was written. When everyone has a chance to provide their input, teams feel more empowered. Even if we had some pre-designed solutions in mind before we got to story grooming, the product owner team was always open to changing things up based on conversations from grooming. A developer might have a less expensive way to implement a desired interaction. Another might ask probing questions that even challenge the need for the feature. Great things can come out of story grooming! It helps keep everyone on the same page as far as what value the team’s trying to provide for the user.</p><h3>Lean processes</h3><p>Skipping the traditional lengthy UX design process helped my team focus on what mattered the most — getting value delivered quickly to our users. If this meant all we did was <strong>sketch potential solutions</strong> for a feature and then jump straight into coding it, then that’s what we did. Designing too far ahead can attach stakeholders to an idea that might get bulldozed once you get into implementation. Sometimes, a higher-fidelity prototype was needed to really envision the user’s experience, but even in those instances, we generally didn’t “dot all the i’s and cross all the t’s.” Design and prototype just enough to give confidence that you’re in the right direction.</p><blockquote>Design and prototype just enough to give confidence that you’re in the right direction.</blockquote><p><strong>Dev/UX pairing</strong> allowed the developers to start putting in the framework for a feature and then later come back and work with the UX person to hone the UI. “Putting on the polish” can mean anything from offering suggestions for quick things like the final microcopy for a page all the way up to more detailed stuff like getting a CSS animation <em>just right</em>.</p><p>In a waterfall world, teams might go through several rounds of iteration and review before the stuff finally gets approval to be in the actual code. Designers might have to write up specs to get styles pixel-perfect or animations spot-on. When you handle these things at the time of development, you free the UX person to work on other tasks (since he or she isn’t wasting the time on documentation). You also usually wind up with a better experience because the designer is <em>right there</em> to suggest changes. Why waste your time writing specs only for them <em>not</em> to get implemented and then have to submit tons of styling bugs? Tweaking the details only right before you ship a feature can save tons of time on design deliverables.</p><h3>Continuous design and delivery</h3><p>Our team had moved from 2-week sprints to continuously delivering value, so there seemed to inherently be <strong>reduced pressure to start coding</strong> something that wasn’t thought out to the level it needed to be. If we were about to start a sprint and didn’t have a big feature quite ironed out yet, we would just pull in another story that was better prepared. That bought us a little more time to make sure that the next big thing was ready.</p><p>From a user experience perspective, “agilefall” shops often want big design upfront (which calls for documenting many, many details). If that big design upfront gets rushed because of an impending deadline for starting the next sprint, guess what happens? The team unnecessarily rushes through the design. I’ve seen firsthand how this practice can negatively impact the final experience. Sometimes, the team ends up building the wrong thing/uses the wrong interaction/etc. <strong>Agile design is all about adapting to change.</strong> If you learn something new in the fourth week of your design for a feature, and you’ve done big design upfront, and you have no weeks left to adapt, then you’re more than likely going to stick with building the wrong solution.</p><h3>Effective backlog management and release planning</h3><p>Continuous delivery is largely made possible by having a <strong>good grip on your product backlog</strong> and <strong>keeping up with your release planning.</strong> When the product backlog has a good inventory of groomed stories, teams can more easily make the go/no-go decision on stories to pull into a sprint. Feature A stories not ready on Tuesday? That’s okay. Pull in Feature B stories and start on Feature A stories by the following Monday if they’re ready.</p><h3>Constant communication</h3><p>I’ve been in more waterfall-like agile environments that weren’t run like above, but one thing that did allow us to keep things moving was taking just a few stories/epics at a time and having <strong>frequent checkpoints and design reviews.</strong> Design on Monday, review internally (e.g., with other designers) on Tuesday, iterate on Tuesday, review with stakeholders on Wednesday, etc. Keep things moving by sharing each iteration with your stakeholders as early as possible.</p><blockquote>Keep things moving by sharing each iteration with your stakeholders as early as possible.</blockquote><h3>Agile UX design recap</h3><ul><li>Focus on writing user stories and grooming with your team before getting knee-deep in design.</li><li>Make sure everyone understands the need for a feature and the “whys” behind a design direction.</li><li>Remove process inefficiencies by focusing on outcomes, not output.</li><li>Introduce dev/UX pairing to minimize the time your designer spends working on deliverables rather than designing the user experience for your product.</li><li>Use rapid prototyping tools like <a href="http://www.invisionapp.com/">InVision App</a>, <a href="http://solidifyapp.com/">Solidify</a>, <a href="https://marvelapp.com/">Marvel App</a>, or <a href="https://proto.io/">Proto.io</a> to quickly communicate flows through a system and/or to get some quick user feedback.</li><li>Only work on things that are ready to be worked on. You’ll save hours later by not having to trash something because it sucked or didn’t address the user’s problem. You’ll also possibly buy the design team some time to finish fleshing out the bigger features.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cb3e1b77583" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Research Facilitation Tips for Everyone]]></title>
            <link>https://astridparisux.medium.com/user-research-facilitation-tips-for-everyone-adc8dd90da29?source=rss-ab908a26ef12------2</link>
            <guid isPermaLink="false">https://medium.com/p/adc8dd90da29</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[research-methods]]></category>
            <dc:creator><![CDATA[Astrid (she/her)]]></dc:creator>
            <pubDate>Thu, 30 Oct 2014 00:00:00 GMT</pubDate>
            <atom:updated>2019-05-27T14:49:19.373Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*P6cTjl5fj9Ku6b0256c_aA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/K0c8ko3e6AA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Amy Hirschi</a> on <a href="https://unsplash.com/search/photos/user-interview?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>If you’re not painfully shy, it’s pretty easy to talk to customers. Most folks working on a product team would <em>love</em> to talk to customers, especially the team members who aren’t in customer-facing roles. A firm believer in balanced teams, I advocate participation in user research activities across the entire product team. User research is all about understanding user needs. Testers and developers have (or should have) the same goals as researchers, designers, and product managers — make a kick-ass product that addresses user needs. If you find yourself in the great spot of getting to conduct a user research interview, here are some important things to keep in mind:</p><ul><li>Practice “active listening” (listening with intent)</li><li>Use non-leading language</li><li>Always make the respondent feel comfortable</li><li>Focus on need (versus implementation)</li><li>Look for repeating patterns</li><li>Be adaptive</li></ul><h3>Practice “active listening” (listening with intent)</h3><p>When you’re writing copious notes while you’re facilitating a conversation, you’re taking away your ability to think critically about what’s being said. Try writing down only the salient bits or only waiting to write until there’s a natural pause in the convo. <strong>PRO TIP:</strong> Have a buddy to take notes for you while you do the talking.</p><p>Actively listening helps you better prepare for the next questions you should ask (based on what the participant just said). If you’re focusing on what you’re writing/typing, you’re not focusing on the person who’s talking. Focusing on the person who’s talking will also help you more quickly intervene when the conversation goes off track (and it will).</p><h3>Use non-leading language</h3><p>Phrase your questions so that they elicit responses that are descriptive of behavior. For example, “How would you use that info?” or “What would be your next move?” instead of “Where do you want to see it?” Avoid asking “yes/no” questions. Instead, ask questions that require open-ended responses. For example, “What do you like about this app?” instead of “Do you like this app?”</p><h3>Always make the respondent feel comfortable</h3><p>Avoid using affirmative language like “cool,” “perfect,” “good,” etc., after a participant has responded to an interview question or taken an action in a usability test. You don’t want the participant to feel like he/she is being tested in any way. So, no praises for “getting something right” and no reprimands if they miss something! A simple “thanks for your feedback” will do just fine.</p><h3>Focus on need (versus implementation)</h3><p>Aim to draw out users’ <em>needs,</em> not their requests for certain implementations or solutions. While users might have an interesting design idea, you still need to focus on what their problems are, the root of their suggestion. This is one of the tougher parts of research because you oftentimes have to read between the lines or put all of the many pieces of the puzzle together to figure out the underlying needs.</p><h3>Look for repeating patterns</h3><p>Look for patterns across participants to help inform where you take your subsequent interviews. <strong>PRO TIP:</strong> Outlier findings can be very interesting and tempting to act on. Use outlier feedback as a springboard to discovery, not as a commitment to build<em>.</em> You want to address the common denominators first.</p><blockquote>Use outlier feedback as a springboard to discovery, not as a commitment to build<em>.</em></blockquote><h3>Be adaptive</h3><p>As long as you’re still learning from a research activity, it’s okay if things don’t go exactly as planned. (You won’t always have enough time to get through all of the planned activities, especially during your first interview). Active listening requires you to think on your feet. After enough practice, it gets easier to flex plans as needed.</p><p><em>Originally published at </em><a href="https://www.astridparis.com/blog/2014/10/user-research-facilitation-tips"><em>https://www.astridparis.com</em></a><em> on October 30, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adc8dd90da29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Ways to Minimize Cycle Time in Software Development]]></title>
            <link>https://astridparisux.medium.com/3-ways-to-minimize-cycle-time-in-software-development-4b030480c500?source=rss-ab908a26ef12------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b030480c500</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Astrid (she/her)]]></dc:creator>
            <pubDate>Thu, 16 Oct 2014 00:00:00 GMT</pubDate>
            <atom:updated>2019-06-12T13:55:10.447Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Minimizing cycle time in software development </strong>would seem to be an obvious strategy for getting new products (or features) out the door and into the hands of users. How teams make that happen, however, <em>isn’t</em> so obvious. At a particular enterprise SaaS company I worked at, my teams and I were always in search of finding the perfect formula for getting it right. Of all the ways my teams and I experimented with process there, three things stood out as accelerators for design → development cycles.</p><h3>Upfront clarity</h3><blockquote>By creating <strong>shared understanding</strong> among the team from the start, you get everyone on the same page, greatly reducing potential rework.</blockquote><p>By creating <strong>shared understanding</strong> among the team from the start, you get everyone on the same page, greatly reducing potential rework. To help get that clarity, you can write <a href="http://blog.usabilla.com/how-user-scenarios-help-to-improve-your-ux/">user scenarios</a> (which help the team understand the “why” behind a set of features) and collectively <a href="http://www.romanpichler.com/blog/grooming-the-product-backlog/">groom user stories</a>. I’m a huge fan of having the whole team groom user stories (which should be done <em>ahead </em>of when the development actually begins for those stories) because it gives the new feature a chance to “marinate” with the team. Sometimes it helps designers to sit on an idea and then come back to it another day. Developers and product managers are no different in that respect. Giving the team time to process the story can lead to some really great questions and ideas that come later, which can often lead to improving the original intended experience.</p><h3>Smaller features</h3><blockquote>It’s not rocket science. <strong>Release early and often.</strong></blockquote><p>It’s not rocket science. <strong>Release early and often.</strong> Working in smaller batches allows you to push to production more quickly…getting the new feature into users’ hands more quickly…leading to getting user feedback sooner…allowing you to iterate the feature more quickly. (Yes, this might seem challenging if you have long release cycles because of some technology reason or organizational red tape. If that’s your case, then it’s up to you and your allies to effect that change. However, if you <em>don’t</em> fall into that boat, then why not give it a try?)</p><h3>Pairing</h3><blockquote>Communication should trump pretty deliverables every time.</blockquote><p>There are so many ways to do this, and all yield great results!</p><ul><li>The obvious match here is <strong>UX/product management.</strong> These two likely have the greatest overlap in responsibilities, mindsets, or focus. (We’ll save that for another blog post.)</li><li>A less likely pairing is <strong>UX/QA.</strong> In a lot of companies, QA is the last stop on the train. Some good things can come out of getting UX and QA together early, though. Pair them up in the beginning as designs are gelling to give QA greater awareness of intended interactions. (QA will usually have some great “gotchas” that the UXer can address before the design goes to code.) Pair them up during testing so that QA better understands which styling inconsistencies are acceptable and gets a sense of how to prioritize UX bugs.</li><li>Last but not least (and my personal fave), <strong>UX/Dev</strong> pairing is a super way to shorten the feedback loop when it comes to design. It makes zero sense to revise…and revise…and revise nitpicky details of a design artifact (e.g., a wireframe or mockup) and throw it over the wall if you can just pair up with the developer who’s working on it and change it right on the spot. Communication should trump pretty deliverables every time.</li></ul><p>A clear benefit of reducing your cycle time is that you can <strong>deliver value more quickly to customers.</strong> An added benefit (that I’ve seen firsthand) is that it can increase your team’s morale! It feels good when you make progress and aren’t stalling over creating perfection. It feels even better when you start getting that user feedback rolling in, knowing that the team’s equipped to quickly address issues.</p><blockquote>A clear benefit of reducing your cycle time is that you can <strong>deliver value more quickly to customers.</strong></blockquote><p>So, while I don’t have “the” answer to how to reduce cycle time in software development, I can say that the three things above have helped in the past. <strong>What are some things your teams have experimented with to get things out the door more quickly?</strong></p><p><em>Originally published at </em><a href="https://www.astridparis.com/blog/2014/10/3-ways-to-minimize-cycle-time-in-software-development"><em>https://www.astridparis.com</em></a><em> on October 16, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b030480c500" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>