<?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 Wren Lanier on Medium]]></title>
        <description><![CDATA[Stories by Wren Lanier on Medium]]></description>
        <link>https://medium.com/@heywren?source=rss-14bc3d130889------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*O_jBI7qzX7wsWWfD.jpg</url>
            <title>Stories by Wren Lanier on Medium</title>
            <link>https://medium.com/@heywren?source=rss-14bc3d130889------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 02:59:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@heywren/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[Building Your UX Process: a collaborative meetup event]]></title>
            <link>https://medium.com/@heywren/building-your-ux-process-a-collaborative-meetup-event-94640724e789?source=rss-14bc3d130889------2</link>
            <guid isPermaLink="false">https://medium.com/p/94640724e789</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Wren Lanier]]></dc:creator>
            <pubDate>Mon, 11 Mar 2019 17:11:37 GMT</pubDate>
            <atom:updated>2019-03-11T17:11:37.791Z</atom:updated>
            <content:encoded><![CDATA[<p>As an organizer for <a href="https://www.meetup.com/Ladies-that-UX-Durham/">Ladies that UX Durham</a>, I’m always thinking about activities we can do to help our members learn from one another. Recently we held an event about UX process that was extremely valuable, and I wanted to share about it for other groups who might want to do something similar.</p><p><strong>Where the Idea Came From</strong></p><p>I designed this event based one of my favorite UX articles: Ste Grainer’s <a href="https://uxcellence.com/2014/the-fuel-and-the-engine"><em>The Fuel &amp; the Engine: Building a Process that Purrs</em></a>.</p><p>This article has always resonated with me because when I first encountered it, I didn’t have a well thought-out, repeatable UX process. Reading about <a href="https://www.linkedin.com/in/tomillmensee/">Tom Illmensee</a>’s team &amp; their work was aspirational for me at the time. It helped me see the difference between the work I was doing and the work I wanted to do.</p><p>Tom has been a great mentor to me over the years, and I loved his collaborative approach to helping his team fill their tactical gaps and unify their process. I decided to take the activity that Tom did with his UX team, in which each person maps out their UX process on index cards, and bring that over to our Ladies that UX event.</p><p><strong>How we planned our UX process event</strong></p><p>On <a href="https://www.meetup.com/Ladies-that-UX-Durham/events/258358758/">our Meetup event page</a>, we shared Ste’s article as well as a link to his <a href="http://uxtoolbelt.com/">UX Toolbelt</a> site, which catalogs a wide variety of UX tactics.</p><p>We set the expectation that we’d be breaking up into small groups, and folks would have the opportunity to share or just listen and learn. We often have attendees who are new to UX or hoping to make a career change, so this seemed like an ideal way for them to participate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QA-XbTQ5cOJT7RQ0ZYENdQ.jpeg" /><figcaption>Small groups working in the Viget kitchen</figcaption></figure><p>Our event was hosted at the <a href="https://www.viget.com/">Viget</a> office here in Durham, which has a large kitchen as well as several conference rooms we could use. It was the perfect space for this activity and we’re so grateful they volunteered to host us.</p><p><strong>How we ran this event for our members</strong></p><p>We kicked off the event with everyone in the kitchen, where I introduced the activity and what we were about to do. Our attendees divided themselves into groups by counting off from 1 to 5 (groups had 4 or 5 members, which seemed like the perfect size), and then each group moved into its own space in the office with a pile of index cards and Sharpie markers.</p><p>Once we’d divided up, I let each group know that this was their time to use. Some groups started writing index cards right away, while others did some introductions and chatted a bit before moving into a share back.</p><p>I also let attendees know that they did not need to limit themselves to My Perfect UX Process. They could share their process from a recent project, or just one piece of the project. They could share something that went well, or something that didn’t go as planned. Our goal was learning, not standardization.</p><p>Within 20 minutes, all the groups were doing share backs, as each person walked the group through a process she’d used or been part of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QGoDDO-BcNevAkCdej-dLQ.jpeg" /><figcaption>Jane shares part of her personas process</figcaption></figure><p>The groups worked together for about 45 minutes before everyone reconvened in the kitchen to discuss what we’d learned.</p><p><strong>What we learned</strong></p><p>Among our attendees, I saw an amazing variety of processes and approaches shared. These included:</p><ul><li>fully mature Enterprise UX at scale</li><li>freelance UI design</li><li>government consulting on a years-long UX research project</li><li>UX Team of One at a startup</li></ul><p>Some of our members learned new terminology for steps they were already doing (“iteration!”) while others learned about Agile or product management processes they’d never encountered before.</p><p>Overall, this was a great chance for our members to get to know one another better and teach each other about the work they’re doing every day. And despite the wide variety of workplaces and approaches, we also learned how much we have in common and the similar challenges we each face in our UX practice.</p><p>We’re looking forward to doing this event again with our members next year!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94640724e789" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Email is a terrible notification vector]]></title>
            <link>https://medium.com/@heywren/email-is-a-terrible-notification-vector-ca3531e8cf01?source=rss-14bc3d130889------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca3531e8cf01</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Wren Lanier]]></dc:creator>
            <pubDate>Mon, 15 Aug 2016 17:05:23 GMT</pubDate>
            <atom:updated>2016-08-15T17:44:44.224Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Apps are sending too many email notifications about trivial events. It’s time to stop abusing our users’ Inboxes and design more meaningful notifications.</em></h4><p>This summer I spent three and a half days in the hospital giving birth to a tiny human. It was the first time in years that I’d ignored my Inbox for more than 48 hours, and when I finally dove back into Gmail after getting home from the hospital, I suddenly realized how much garbage I’ve been sifting through day after day — and almost all of it is generated by apps.</p><h3><strong>We Receive Too Many Emails from the Apps We Use</strong></h3><p>Someone tagged you on Facebook.<br>Someone mentioned you on Slack.<br>Someone sent you a message on Twitter.</p><p>Too many of the social apps we use as alternatives to email <strong>also</strong> send an email to notify us about the messages we’re getting that aren’t emails.</p><p>Collaborating online? Github, Basecamp, Trello, and the like generate a steady stream of email notifications, plopping another message into your Inbox each time someone on your team posts, tags, updates or mentions you or a project you belong to.</p><h3>CheeYi Ong on Twitter</h3><p>Finally switched to using another email address for GitHub notifications. So far so good.</p><p>Viewed individually, these might seem like meaningful updates worthy of time and attention, but taken together, the ecosystem of apps and tools that we use every day is generating more and more email noise. A handful of useful notifications are getting lost while important emails get buried under a pile of app spam — and it shows no sign of letting up.</p><h3><strong>Stop making me the janitor of my Inbox</strong></h3><p>I use Gmail’s Priority Inbox, which does a pretty good job of sifting out marketing emails and surfacing the important stuff. Nevertheless, I have to teach it what I want to see and what I don’t, and my return to an Inbox full of app notifications helped me realize that I’d been thoughtlessly deleting these notifications for months instead of teaching Gmail to ignore them. Without constant care and attention, app notifications quickly dominate my email stream and make it more difficult for me to process and complete important tasks.</p><h3>Top Conservative Cat on Twitter</h3><p>BREAKING: FBI discovers that Hillary&#39;s 30,000 deleted emails were all Facebook notifications from Biden tagging her on cat videos.</p><p><em>“Hey, why don’t you just set up some filters?”</em></p><p>Because I resent the time it requires; I have better things to do than build filters to clean up the notifications for every app that I use. That’s not my job.</p><p><em>“Hey, why don’t you manage your app settings better so that you stop getting so many emails?”</em></p><p>Again, that’s not my job — offloading notification management on to users is a dark pattern that allows apps to send tons of thoughtless transactional emails.</p><p>Notification emails are a lazy way for apps to try to boost their engagement metrics. They’re the junkfood of the app ecosystem: cheap, easy, and lacking any nutritional value.</p><p>Fix your app; don’t make me fix it for you.</p><h3><strong>UX teams — this is a design problem that needs a better solution</strong></h3><p>When I scan the stream of app notification emails that clamor for my attention, I’m struck by the apparent lack of design intention. Not a lack of visual design (I’m sure each and every email has been designed and coded to exacting standards so that it renders beautifully on any viewport size) but a lack of <em>communication</em> design. It appears as though each one of these emails was created in a silo, without belonging to any overall design strategy for how the app should be communicating with its users.</p><p>I understand how this happens; too often, overtaxed design teams treat notifications as an afterthought, rushing yet another email message into a product release at the last minute. But notifications are a UX problem that deserves attention, if only because clear, delightful communication is a competitive differentiator — and the field is wide open for innovation.</p><h3>Jason Pamental on Twitter</h3><p>Both @facebook &amp; @linkedin have made notifications completely useless. Underscores failure of ad-supported biz model. User always loses.</p><p>To be fair, some apps are beginning to support alternative notification vectors, such as pushing notifications into Slack channels. A growing number of web apps are also taking advantage of the ability to push notifications into the native OS, allowing users to get a small (but distracting) pop-up in the corner of their desktop. Nevertheless, these alternatives are usually treated as secondary notifications, and an email still goes out as the default or fallback.</p><p>Clogging up Inboxes with app notifications is lazy and low-value for everyone involved. Too many apps abuse their access to someone’s Inbox and offer little reward for the precious time &amp; attention our technology demands. It’s time for UX designers to end the firehose of email noise; instead, we should create new solutions that give our users a smaller number of high-quality notifications.</p><h4><strong>Take an inventory of all your notifications</strong></h4><p>In many cases, no single person or team “owns” notifications; instead, they proliferate on a feature by feature basis that inevitably leads to notification creep. Taming the beast begins with an inventory of every action that triggers a notification email. Once you have a complete list, consult your metrics and talk to users about which notifications they actually find valuable.</p><h4><strong>Design for the experience, not individual actions</strong></h4><p>In many apps, notifications and actions have a 1:1 ratio. Take the same action 5 times, receive 5 identical emails in a row. This is a missed opportunity to communicate with your users like humans instead of firing off emails like a robot. User interviews and journey maps can help identify opportunities to combine or eliminate notification emails and communicate in a more friendly way.</p><h4><strong>Stop using email as the default vector for communicating with users</strong></h4><p>Just say no to adding more notifications. Make in-app notifications and messaging more meaningful and robust, and treat email as a last resort for only the most serious cases. (Are you worried that your users will forget about you and never open your app again if you stop emailing them every 4 hours? If that’s really the case, then you have more fundamental problems and no amount of email will save you. Sorry.)</p><h4><strong>Learn and embrace the principles of calm technology</strong></h4><p>Amber Case has outlined <a href="https://www.calmtech.com/">a brilliant set of principles for designing better, more human communication in technology products</a>. Read through the list and try to imagine how much more time and focus you’d have each day if every product you use adhered to these precepts. My favorite: <em>“Technology can communicate, but doesn’t need to speak.”</em></p><p>If only we could make it so.</p><p><em>Thanks to Pam Drouin, Jenn Downs, and Sara Wachter-Boettcher for helping make this better.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca3531e8cf01" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>