<?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 Alicia Nachman on Medium]]></title>
        <description><![CDATA[Stories by Alicia Nachman on Medium]]></description>
        <link>https://medium.com/@anachman?source=rss-99e7010726bd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*pauyE3TdY93--kjUD-9EWg.png</url>
            <title>Stories by Alicia Nachman on Medium</title>
            <link>https://medium.com/@anachman?source=rss-99e7010726bd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:28:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anachman/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[Why your first research hire should be in ops]]></title>
            <link>https://anachman.medium.com/why-your-first-research-hire-should-be-in-ops-88e3f082774a?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/88e3f082774a</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[researchops]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Fri, 22 Jan 2021 00:00:00 GMT</pubDate>
            <atom:updated>2021-01-22T20:51:50.500Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_smyoWe6qQHdib3S" /></figure><p>Congratulations, UX leader! You’ve finally convinced your company’s leadership that research is important, and you’ve been given the go ahead for more resources (or not, but more on that later). But where to start? The most obvious place to start building a research team is to hire a researcher. But when I had my first opportunity a few years ago to start building a UX research team, my first hire wasn’t a researcher — it was a research coordinator. Nowadays, that position would fit precisely into the realm of <a href="https://www.userinterviews.com/blog/research-ops-what-it-is-and-why-its-so-important">Research Ops</a>, a relatively new discipline within UX aimed at making research processes (and by extension researchers) more effective and efficient. It may seem like Research Ops is a role that only becomes necessary once your team has reached a certain scale, but here are some of the reasons to flip that notion on its head:</p><ol><li>UX Research has a relatively heavy administrative burden. Recruiting, scheduling (and rescheduling) participants, and managing compensation all take significant effort, even with 3rd party recruiting firms or tools. Research also generates mountains of data that need to be organized. Without a research coordinator, this burden is falling to your designers (who are the ones most likely running research if you are just starting to build a team), or later, your researchers.</li><li>Research Ops is a massive draw for potential hires. Do you know how excited a researcher will be to learn that you already have a research coordination role in place? They will rejoice at not having to take on the aforementioned administrative burden and applaud you as a forward-thinking employer.</li><li>Research coordinator is an excellent opportunity to bring in entry level talent. Of late, many in our industry have been calling out the lack of true entry level roles, with even junior positions requiring multiple years of experience. From new grads to career switchers, a research coordinator position can be an ideal way to break into a UX career and make a big impact very quickly on a team. Being in a coordination role provides a breadth of learning opportunities not only on how to conduct research, but also a healthy understanding of what it takes to pull off a study end to end. My first research coordinator went on to become a product manager in the team, while her replacement used it as a stepping stone into a UX Research role.</li><li>If you still haven’t quite convinced your company to start a research team, hiring a research coordinator can be a stealth way in, and sometimes we all have to be corporate ninjas to move our agendas forward. It’s not too difficult to build a case that removing some of the operational and administrative burden from your highly compensated designers or researchers is worth the investment. A research coordinator can easily be a part-time role or contractor if those are easier hires in your organization. And if hiring is not an option at all, you can also seek out help from administrative assistants who may have some extra bandwidth and would relish learning some new skills.</li></ol><p>Certainly Research Ops is about much more than the administrative aspects of coordinating research, but it’s such a critical need and is just as relevant whether you have a single designer doing ‘all the UX things’ or a full team of researchers. So if you find yourself in the lucky position to start up a research team, or if you’re just in desperate need of help to streamline your existing research process, Ops is the place to start!</p><p><em>Originally published at </em><a href="http://designinthelead.com/blog/why-your-first-research-hire-should-be-in-ops"><em>https://designinthelead.com</em></a><em> on January 22, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88e3f082774a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[’Tis the Season…for Virtual Holiday Parties]]></title>
            <link>https://anachman.medium.com/tis-the-season-for-virtual-holiday-parties-eaf298b5887c?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaf298b5887c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[christmas]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[holidays]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Thu, 05 Dec 2019 00:00:00 GMT</pubDate>
            <atom:updated>2019-12-06T17:30:48.335Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gBBvlO8D0qPyrJkA" /></figure><p>The holiday season is a time of togetherness. We prioritize extra time with our families, our friends, and yes, even our co-workers. But what if you and your team aren’t, well…together? Even if you have a distributed team, you can still take some time to make a virtual connection to acknowledge the hard work and successes of the year and just to have some fun. Here are some tips and ideas based on planning for our Macmillan Learning UX team’s virtual holiday party!</p><h3>1. Do a non-virtual activity</h3><p>As tech workers, especially remote ones, we spend an inordinate amount of work time on our computers. Design and research are primarily digital activities now, and even more so when the team (and our customers) are distributed. From Sketch to Mural to Google Docs to Zoom, much of our work requires a mouse, a keyboard, and a screen. When it comes to celebrating the holidays (or any get together for that matter), it’s nice to be able to break away from the norm and do something in the physical world. In the case of my UX team, I wanted to find something simple yet creative to pique our innate ‘maker’ sense. A quick Etsy search for ‘craft kits’ turned up some fun options. We decided to go with these <a href="https://www.etsy.com/listing/617902306/kids-craft-kit-suncatcher?crt=1&amp;ref=shop_home_active_3">suncatcher kits from HelloSprou</a> t, and ordered them sent directly to the team members.</p><h3>2. Put a spin on giving</h3><p>Last year, we had an in person get together for the holidays where we took a field trip to a design museum and did a white elephant gift exchange. It was a ton of fun but because it was in person, we weren’t able to include our extended team of contractors and vendor partners. This year with a remote celebration we were able to be more inclusive of the whole team — but the gift giving seemed like something we wouldn’t be able to pull off. After momentarily thinking how we could do a cross-country white elephant, I decided to eschew yet more <em>stuff</em> in favor of sharing gratitude. So the team will be exchanging acknowledgements instead — Secret Santa style! I entered everyone’s names into a free name drawing app (I used <a href="https://www.drawnames.com/">DrawNames.com</a>). The instructions were simple: find something positive to share about the person you draw — could be praise, a success to highlight, a word of thanks, or a fun anecdote.</p><h3>3. Keep it short and sweet</h3><p>Lastly, parties can be fun, but there’s a limit to how long you can keep up a social connection that thrives on mingling over a video conference. Based on the activities we have planned, our event will be an hour, but I’d say 90 minutes to 2 hours max. The last thing you want is for people to feel hostage to your “fun” celebration.</p><p>I hope you feel now that there’s no reason you can’t maintain a sense of togetherness over the holidays with your remote team — or that you picked up some good ideas for your co-located team too! Just grab your favorite holiday beverage (hello peppermint hot chocolate!), optional ugly sweater, and your video conferencing app of choice!</p><p><em>Originally published at </em><a href="https://designinthelead.com/blog/tis-the-season"><em>https://designinthelead.com</em></a><em> on December 5, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaf298b5887c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Story of Us]]></title>
            <link>https://anachman.medium.com/the-story-of-us-3e4c8f7c4ed8?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e4c8f7c4ed8</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-operations]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Wed, 03 Jul 2019 14:09:42 GMT</pubDate>
            <atom:updated>2019-07-03T17:05:30.399Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently hit a 3 year milestone as head of the UX team at Macmillan Learning. It’s been one of the most intense yet rewarding experiences of my career; one that has pushed me to grow tremendously as a manager and leader as I’ve grown my team. One of the unique opportunities I’ve had during that time has been to really define the shape of the team as we have scaled. If you are anything like me, you love hearing stories about how other design teams are organized to get ideas that might apply to your team as well. So here is a short history to bring you up to speed on the story of us!</p><p>Back when I joined the Macmillan Learning team from another business unit, there was already a small but mighty UX team of 3. Having the luxury of knowing quite a bit about the org, I also happened to know of 2 other people who were also doing UX research and design work but weren’t part of the UX team. So I insisted they join my team as well. At that time, I was based on the west coast, 4 team members were in our NYC headquarters, and 1 designer was based remotely in Massachusetts. This awesome-beyond-words team welcomed me with open arms as their leader in our new adventure together and set us up with a solid foundation. As that early team unit, we were able to make deliberate decisions about <em>how</em> to grow — who we would hire, the kind of team culture we wanted to cultivate, and type of relationships we aspired to have with other teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yubsLQXzTgO6z9u7k7fcGA.jpeg" /><figcaption>Team field trip to the Cooper Hewitt Design Museum last Dec. The team has grown since then so not everyone is pictured!</figcaption></figure><p>Fast forward 3 years, and we are now a team of 12 full-time staff (including me) across design, research, and ops. We’ve developed long term partnerships with 3 different UX firms, and we also have a few contractors on the team, bringing our total team size up to around 25, plus or minus a few at any given point as we flex to meet project demands. We are spread across the country in 8+ cities, with our largest team concentration in our Austin office. In our case, this rapid expansion was almost entirely fueled by a major new project that was being started right at the time I joined.</p><p>One of the most gratifying parts of scaling this team for me has been the chance to build off of a relatively clean slate in terms of the design org. We started out as a team of designers; granted, hybrid designers with skills in research and/or coding. Our first order of business was growth in order to support the wave of new development on our next gen platform. That meant building a team in Austin where our Technology team hub is located. But as we grew rapidly, so it became clear that it was time to expand beyond just a team of designers. Last year, we established both Design Operations and dedicated UX Research functions. It’s been especially fun watching the operations team take part in that growing community of practice (we sponsored Rosenfeld’s <a href="https://rosenfeldmedia.com/designopssummit2019/">Design Ops Summit</a> last year and will be again this year!).</p><p>In terms of our how we operate within our organization, we use the hybrid model. According to the <a href="https://zakiwarfel.com/dci-report/">Design Career Index</a> just published by Todd Zaki Warfel, hybrid (“reports centrally, operates embedded”), is the most common model with just over half the respondents identifying that way. The other half was pretty equally split between centralized and decentralized. Although we match the trend there, I’d be willing to bet that we are uniquely singular in one organizational aspect. Our UX team reports up through the Learning Science and Insights group — a strategic move at Macmillan Learning to ensure that our designs for edTech products are highly aligned with the best practices of learning research. Lastly, I’m proud that our company has recognized design leadership at an executive level by creating the company’s first VP level position in UX at the end of last year. Within our internal full-time team, we also have 3 directors, 1 manager, 4 seniors, and 3 mid-level team members.</p><p>I hope you’ve enjoyed learning a bit about my phenomenal team, how we’ve grown, and how we are structured. We are by no means sitting still though— while organizational stability is important, we are also constantly checking in to whether it is still working for us and those we collaborate with as the team grows and our priorities shift. My leadership team and I are also committed to ensuring clear career paths and opportunities for our team members to grow into the roles that suit them as individuals. In the end, it turns out that organization isn’t quite the apt ‘org’ word here— it feels more fitting that we are an organism that is constantly growing, learning, and finding ways to thrive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1CRxIm7Kqk4TQkZj7KVMXA.jpeg" /><figcaption>Extended team at our Austin UX Summit in Jan</figcaption></figure><p><em>Further reading: I highly recommend </em><a href="https://www.amazon.com/Org-Design-Orgs-Building-House/dp/1491938404"><em>Org Design for Design Orgs</em></a><em> by Peter Merholz and Kristin Skinner. It was and is our go to resource on org planning.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e4c8f7c4ed8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can I Give You Some Feedback?]]></title>
            <link>https://anachman.medium.com/can-i-give-you-some-feedback-e131c98449d9?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e131c98449d9</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Mon, 01 Jul 2019 00:00:00 GMT</pubDate>
            <atom:updated>2019-08-22T15:21:42.409Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5iVP1lLqxzxBxD3PAP79fA.jpeg" /></figure><p>Ah, feedback. It’s the lifeblood of being a people manager. After all, who among us didn’t get into management so that we could tell other people what they’re doing wrong, amiright? In her book, <a href="https://www.amazon.com/Making-Manager-What-Everyone-Looks/dp/0735219567">The Making of a Manager</a>, Facebook design leader Julie Zhou tells us that “giving feedback — both when things are going well and when they aren’t — is one of the most fundamental aspects of the job.” Luckily, the expert advice on how to give the best feedback is so straightforward and consistent, all you need are these 4 handy tips to have your employees singing your praises — and generally dressing, speaking, and performing better.</p><p>2. Identify and develop employee strengths</p><p>If you fall into the ranks of the 70% of managers who are <a href="https://qz.com/work/1171890/almost-70-of-us-managers-are-scared-to-talk-to-their-employees/">scared to talk to your employees</a>, then just let me introduce you to <a href="https://www.patriciaschwartz.com/what-is-strengths-based-coaching">strengths based coaching</a>. When using this approach, there is no need to fear 1:1s or performance reviews because we get to talk to our team about positive stuff — like how to get better at the things they are already good at! And that’s really the only thing worth doing since, according to <a href="https://www.forbes.com/sites/ianaltman/2015/09/15/dont-waste-time-fixing-your-weaknesses/#468d8cb6300e">this Forbes article</a>, “the person who is a lousy leader, might become a mediocre leader. But, they are not likely to ever be as good of a leader as the person who comes to it naturally.” And if that just made you super depressed, I think I’ve just proven the value of focusing on strengths!</p><p>2. Don’t waste time developing strengths</p><p>Now that we’re clear on the importance of a strengths-based approach, it’s important to note that <a href="https://hbr.org/2016/01/strengths-based-coaching-can-actually-weaken-you">“strengths based coaching can actually weaken you</a> “, according to business psychology professor Tomas Chamorro-Permuzic. Now there are many reasons for this, but suffice it to say that it’s possibly the worst idea ever. The good professor tells us that “If the focus is on making people more competent, productive, or effective, managers and decision makers should work instead on mitigating people’s weaknesses.” So mentally prepare now to start having those awkward conversations with your team.</p><p>3. Share your candid opinions at every opportunity</p><p>Speaking of awkward conversations, they are simply a necessity of life if you want to be a top notch manager. To achieve this, you must commit to being candid — radically candid in fact. In her book, <a href="https://www.google.com/aclk?adurl=&amp;ai=DChcSEwjO3-3_spDkAhWFnrMKHecIBOIYABAHGgJxbg&amp;ctype=5&amp;q=&amp;sa=L&amp;sig=AOD64_3djOrHkbsehCZt1I3iJyxnnuAdrA&amp;ved=0ahUKEwieg-T_spDkAhWuTd8KHdMgCBAQ9aACCDg">Radical Candor</a>, management guru Kim Scott tells us that we must “care personally” and “challenge directly” when giving feedback. Translated into layperson terms, that essentially means managers can say whatever we want as long as we remind employees it’s in their best interest. Pro tip — it’s best to give this candid feedback in the <a href="https://www.radicalcandor.com/blog/immediate-feedback/">immediate</a> aftermath of troubling behavior. Best not to have time to think through what to say or how to say it!</p><p>4. Recognize that your opinions are worthless</p><p>Once you get comfortable confronting sensitive topics and using the 2–3 minutes between meetings to address your employees’ flaws, you should probably just stop. Because as it turns out, humans are miserable at reviewing other humans. As researchers Marcus Buckingham and Ashley Goodall detail in a <a href="https://hbr.org/2019/03/the-feedback-fallacy">Harvard Business Review article</a>, “Our evaluations are deeply colored by our own understanding of what we’re rating others on, our own sense of what good looks like for a particular competency, our harshness or leniency as raters, and our own inherent and unconscious biases.” Looks like it’s best to just avoid feedback altogether.</p><p>Well, I hope these tips showed once and for all how easy it is to practice the art of good feedback and to up your management game. If you’re still feeling a bit unsure though, take heart. In the not too distant future, we can all just rely on <a href="https://www.washingtonpost.com/technology/2019/06/28/wearable-technology-started-by-tracking-steps-soon-it-may-allow-your-boss-track-your-performance/">surveillance and AI</a> to give the feedback we can’t.</p><p><em>Originally published at </em><a href="http://designinthelead.com/blog/feedback"><em>https://designinthelead.com</em></a><em> on August 22, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e131c98449d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The X-Factor: What Most Companies are Still Missing in the C-Suite]]></title>
            <link>https://anachman.medium.com/the-x-factor-what-most-companies-are-still-missing-in-the-c-suite-2b732f74ab42?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b732f74ab42</guid>
            <category><![CDATA[cxo]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Mon, 24 Jun 2019 00:00:00 GMT</pubDate>
            <atom:updated>2019-06-25T20:27:16.362Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0BLaKnfh-FsZRU9qGVEHew.jpeg" /><figcaption>Image by <a href="https://pixabay.com/users/422737-422737/?utm_source=link-attribution&amp;amp;utm_medium=referral&amp;amp;utm_campaign=image&amp;amp;utm_content=654963">Hebi B.</a> from <a href="https://pixabay.com/?utm_source=link-attribution&amp;amp;utm_medium=referral&amp;amp;utm_campaign=image&amp;amp;utm_content=654963%22">Pixabay</a></figcaption></figure><p>Where should User Experience report to in the organization? All of us, including UX teams of one, have probably confronted this question. I’ve got a simple answer that I’m more than happy to share with anyone who will listen, including every boss I’ve ever had: UX belongs in the C-suite. I’m certainly not alone in this position — <a href="https://www.ceo-review.com/2018-the-rise-of-the-chief-experience-officer">articles</a> about the rise of the Chief Experience Officer (CXO) abound, not to mention evidence that design-led companies perform better ( <a href="https://www.mckinsey.com/business-functions/mckinsey-design/our-insights/the-business-value-of-design">by as much as 2 to 1 in fact</a>). A quick scan of LinkedIn turned up CXOs at GE, MasterCard, and Qualtrics, among others. Just last week design celebrity John Maeda was <a href="https://finance.yahoo.com/news/publicis-sapient-announces-john-maeda-112300663.html">announced</a> as the new CXO for Publicis Sapient starting in August.</p><p>To understand why this question would arise in the first place, and why it still needs to be asked today, it’s useful to look at some historical context. UX is rooted in human factors, engineering psychology, and human-computer interaction, but really started its meteoric rise along with the web itself. So it happened that people hired to do this ever in demand type of design were put wherever in the organization that work was happening, typically under Engineering (in more tech focused settings) or under Marketing (in more creative or content centric businesses). We have generally moved past that era, yet UX is still searching for a more permanent home.</p><p>These days, it seems the place to be is under Product — as evidenced even by a shift in many titles from UX Designer to Product Designer. In <a href="https://www.amazon.com/Org-Design-Orgs-Building-House/dp/1491938404">Org Design for Design Orgs</a>, the authors advocate for both place and title, although with a caveat. They acknowledge that Product seems to be the most practical place to be based on the prevailing org structures of many companies building digital products. It certainly is a pragmatic approach, and I tend to agree it fits the best among a set of imperfect options particularly for smaller UX teams. When you start to unpack this though, the limitations of Product as the bounds of UX start to become clear, especially as the team starts to scale in any meaningful way. The reason for this in large part is due to the way companies are functionally siloed in the first place. There are sales and marketing teams which focus on customer acquisition, product teams that focus on the delivering what’s being sold, engineering teams that provide the infrastructure and execution, customer success teams that focus on support, retention, and satisfaction, and if your product relies on content to deliver value, you have a subject matter expert group responsible for content strategy and production. From a customer journey perspective, the experience spans touchpoints across each of those ‘functional’ areas. The functions are useful to the company, not the user. So by putting UX under Product, the investment the company has made in designers and researchers are inherently limited and not being applied to the full experience.</p><blockquote><strong><em>To deliver on their full potential, the UX team needs to be at a level where they can influence the end-to-end experience across functional groups.</em></strong></blockquote><p>Now, I’m not advocating for these functional groups to go away — organizations clearly need to rely on structures like this to operate efficiently. But when thinking about where a team of UXers should fit, the most impactful to the overall user experience would be as a peer to these other groups rather than a sub function. Consider how some UX teams are limited if they are under a Product group whose ‘ownership’ starts at sign in. The reality is that a user arriving at sign in just completed many key steps in a journey that colors their overall experience with the company, the brand, and the product. If there is a hand-off of internal ownership at that critical transition point — e.g. from a ‘Marketing owned’ corporate site to the ‘Product owned’ application, it’s very likely that we’ll introduce noticeable friction for our users. To deliver on their full potential, the UX team needs to be at a level where they can influence the end-to-end experience across functional groups.</p><p>Enter the Chief Experience Officer, a <a href="https://thenextweb.com/dd/2015/01/25/new-kid-digital-block-chief-experience-officer-actually/">role</a> that is increasingly catching on in organizations that have prioritized design and experience as a differentiator. The value of such a role is to unify the experience strategy across functions that play unique parts at key steps of the customer journey. It allows the UX team to flex in a way that they aren’t as easily able to when constrained to the traditional functional lines of business. In fact, it may be one of the only ways to counter the inevitable pull of <a href="https://en.wikipedia.org/wiki/Conway%27s_law">Conway’s Law</a>, which states that “organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.” Imagine if you will an experience team that truly spans the customer journey, orchestrating a seamless path throughout and obscuring glaring functional lines. This naturally points to some of the other trends around experience management in organizations. There are some companies where Customer Experience (CX) and UX are under one umbrella. <a href="https://hbr.org/2019/06/why-every-company-needs-a-chief-experience-officer">It’s been argued</a> that even Employee Experience belongs under a Chief Experience Officer, as there is evidence that positive employee experience can lead to great customer experiences. However these trends play out, know this: customers don’t care about our org chart, and our approach to designing for their optimal experience shouldn’t either.</p><p><em>Originally published at </em><a href="https://designinthelead.com/blog/missing-from-c-suite"><em>https://designinthelead.com</em></a><em> on June 24, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b732f74ab42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Layered Backlog (or That Time I Thought I Invented Story Mapping)]]></title>
            <link>https://anachman.medium.com/the-layered-backlog-or-that-time-i-thought-i-invented-story-mapping-853de4ea985f?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/853de4ea985f</guid>
            <category><![CDATA[storymapping]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Wed, 05 Jun 2019 00:00:00 GMT</pubDate>
            <atom:updated>2019-06-05T14:13:48.833Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*bSfIDGkGRYawFXpdjTv2Jg.jpeg" /><figcaption>Woven layers of wicker</figcaption></figure><p>I am a fan of agile development, and I think it can go hand in hand with good user-centered design. But one construct that has never quite worked for me is the product backlog. In theory, the concept couldn’t be more straightforward — the product owner maintains a list of user stories and/or epics that are needed or requested for the project. They vet things, fill in detail, and prioritize it. Anyone can take a look at the backlog and get a sense for what is most important and what is next. The problem I’ve found is that this list is flat — it represents priority and work in a linear fashion that doesn’t successfully reveal the interconnections among stories that can illuminate a bigger picture understanding of the product. Particularly for the large chunks known as epics, when it comes to breaking them down, the stories for that epic don’t necessarily fall contiguously into that flat backlog. They end up becoming fragmented as stories that have to prioritized based on resourcing, technical, and other constraints. And that’s a problem because epics or other higher level constructs can often represent that holistic vision of the product and where it’s going better than a disjointed collection of stories.</p><p>Early in my career, I found myself really struggling with this. What my brain really wanted to do was to look at the backlog and envision a whole suite of capabilities that would be built out over time. So I experimented with the idea and created what I decided to call a ‘layered backlog’. I experimented with a project I was working on at the time and broke out the product into 4 key user capabilities. I then filled out each capability with its own flat backlog of user stories that would build up that capability over time. Because of our focus on minimum viable product (MVP) and building complete workflows along the way, it made much more sense to me to imagine building the product up across the capabilities over time rather than thinking of any one piece as ever being done.</p><p>Of course, as I was soon to learn, what I thought was a new breakthrough in agile methodology was already well articulated by Jeff Patton’s concept of <a href="https://www.jpattonassociates.com/the-new-backlog/">story mapping</a>. Fast forward a good number of years, and his post is still a great read — although since then he also wrote <a href="https://www.amazon.com/User-Story-Mapping-Discover-Product/dp/1491904909/ref=as_sl_pc_qf_sp_asin_til?tag=jefpatass-20&amp;linkCode=w00&amp;linkId=NX2UXYQEFAANOFPO&amp;creativeASIN=1491904909">a book</a> on the topic! What Patton and I both were in search of with our solution was the context surrounding why we build what we build. As he says in his blog, “ <strong>I need that context in order for me to really tell a story about the system.”</strong></p><p>That story turns out to be what Patton calls the “backbone” of the product — and if created with a strategic mindset can also make for an effective product roadmap. With a layered backlog or solid story map in place, it is easy to envision taking slices off from each capability and bundling them into functional milestones or releases over time. There may be times where one capability has little or no stories to build out for a particular release, but you are always fulfilling that core end-to-end value of the product as a holistic delivery rather than churning out disjointed features. Story mapping isn’t perfect — my current challenges in using them have been around scaling them to a complex, interconnected system that seems to require many overlapping story maps. Yet I consistently come back to their value in being able to provide the missing element of context that has never been possible with a flat backlog.</p><p><em>Originally published at </em><a href="https://designinthelead.com/blog/the-layered-backlog"><em>https://designinthelead.com</em></a><em> on June 5, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=853de4ea985f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Innovator’s (Leadership) Dilemma]]></title>
            <link>https://anachman.medium.com/the-innovators-leadership-dilemma-1805e30f0653?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1805e30f0653</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Tue, 28 May 2019 00:00:00 GMT</pubDate>
            <atom:updated>2019-05-29T00:59:51.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*YU154DvIhY1UU1SjdHWVRQ.png" /><figcaption>Adobe Creative Types. Innovator (left) and Producer (right)</figcaption></figure><p>A few weeks ago, Adobe Create generated some fun buzz around my UX team’s Slack channel with their <a href="https://mycreativetype.com/">Creative Types quiz</a>, promising to “Discover your creative personality.” It turned out to be a great opportunity for our distributed team to generate discussion and learn more about each other, and everyone enjoyed guessing and sharing the results. While I don’t put a ton of stock into the results (one of the questions was “Are you a fortune cookie or a birthday cake?”), what turned out to be the most interesting to me was the difference between my quiz results and the outcome guessed by my team.</p><p>While the quiz branded me as <a href="https://mycreativetype.com/type/innovator/">The Innovator</a>, whose strength is the “Ability to generate new ideas and innovative solutions”, my team pegged me as <a href="https://mycreativetype.com/type/producer/">The Producer,</a> with “strong leadership skills, ability to make things happen.” Now in no way is this a negative — what would it mean if they didn’t guess the one with strong leadership skills?! Yet, I couldn’t help but wonder (channeling Carrie Bradshaw here) if design leaders have to give up some of their natural creative tendencies in order to succeed in leadership. Do we lose ourselves as we become leaders?</p><p>The Innovator resonated with me, and made me reflect a bit on where I’ve been and what I might be missing out on. The description says “Change may be scary for most people, but for you, it’s fuel for your creative fire.” It’s true I’ve always thrived on change — it’s where my biggest career leaps have taken off. Times of change, whether personally or externally initiated, always feel like a fresh place to try something new. As a leader though, change is something that can be hard to manage through, especially with the varied reactions and comfort levels that team members bring. Cultivating a sense of stability has become more important for me as my team has grown. The Innovator also thrives in roles that “allow you to <strong>experiment and play with ideas.</strong>” I love experimentation and encourage it in my team, but it is something I’ve seen become a lesser part of my own day to day. If the majority of my role now is making my team successful and managing people, it seems a little reckless to experiment on them. Frankly, it is the part of my work that I miss the most though as I’ve transitioned away from individual contributor roles.</p><p>Yet I am also The Producer. I pride myself on my “grounded realism and ‘get it done’ attitude.” I’m proud that I’ve been able to demonstrate that I have what it takes to “motivate and inspire others.” But as a leader, am I destined to limit my creative personality to what feels more managerial? Luckily, I don’t think so, but it will take some deliberate work. I’ll have to take a closer look at my day to day projects to reexamine where I might have room to bring a more innovative mindset. Whether it’s more experimentation in process, operations, management techniques or even taking on a personal passion project, tapping into this part of my creative personality will just take more conscious prioritization than before.</p><p>Taking this Creative Types quiz led to a surprising level of introspection about my personal path from individual contributor to design leader. It was an important reminder for me to nurture all aspects of what I can bring to my work — not just what makes me a good manager, but what makes me a good designer and researcher as well. And as a leader, it’s also a good reminder of how every member of my team is a multi-faceted individual who needs to have opportunities to let their creative personalities shine.</p><p><em>Originally published at </em><a href="https://designinthelead.com/blog/the-innovators-leadership-dilemma"><em>https://designinthelead.com</em></a><em> on May 28, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1805e30f0653" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I love doing homework! (said no student ever)]]></title>
            <link>https://anachman.medium.com/i-love-doing-homework-said-no-student-ever-17503da112cc?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/17503da112cc</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Mon, 13 May 2019 11:56:00 GMT</pubDate>
            <atom:updated>2019-05-13T15:57:31.222Z</atom:updated>
            <content:encoded><![CDATA[<p>User Experience practitioners are in the business of creating positive experiences for our users, no matter what they are trying to accomplish. Some might even say we are in the business of creating <em>delightful</em> experiences — or at the very least, key moments of delight where we truly surpass expectations. But what if your product supports something that is universally NOT considered delightful? Things like doing your taxes, making a dentist appointment, or in the case of my team at Macmillan Learning, doing your homework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*HSexzlWNhSSWl_50I4HaXg.jpeg" /><figcaption><a href="https://www.flickr.com/photos/25676674@N03/2529643802"><em>“Bored”</em></a><em> by</em><a href="https://www.flickr.com/photos/25676674@N03"><em> s3127</em></a><em> is licensed under</em><a href="https://creativecommons.org/licenses/by-nc-nd/2.0/?ref=ccsearch&amp;atype=rich"><em> CC BY-NC-ND 2.0</em></a></figcaption></figure><p>What’s worse, students using our products (and classroom tech in general) don’t get to choose our system among a raft of others competing for their dollars, their instructor or institution does. So I hope I’m painting a clear picture here — students have no choice but to pay for a system someone else chose for them to do something decidedly <em>undelightful.</em> It may seem like a dismal starting place to strive for delight, but where’s the fun in design if there isn’t a challenge?</p><p>First off, let’s unpack the term delight. Much has been written (<a href="https://hbr.org/2010/07/stop-trying-to-delight-your-customers">and maligned</a>) about it in the UX community, but, honestly, what hasn’t gotten that treatment as trends fall in and out of favor? It’s still a popular part of our lexicon, and some of us have even built it into our ‘elevator pitch’ to explain to our jobs to others. Most of us have probably seen or heard a variant of this a number of times: “I design products so that they are usable, useful, and delightful.” With synonyms like please greatly, charm, enchant, captivate, entrance, bewitch, thrill, excite, and take someone’s breath away, it’s no wonder UX designers chase this kind of reaction in our users.</p><p>But what about the role of delight in education? If an activity is ‘captivating’ or ‘pleasing’, are students more likely to learn? Our UX team at Macmillan Learning is privileged to work closely with learning researchers throughout our process to make sure that our products are designed to maximize learning. So while we know that things like <a href="https://www.macmillanlearning.com/Catalog/uploadedFiles/Six_Key_Principles_Learning_Experience_Design.pdf">developing motivation and enabling metacognition</a> drive better learning outcomes, it turns out that delight in and of itself isn’t something that leads to better learning. There is evidence however that the absence of delight, in particular when boredom takes over, can negatively impact learning. In <a href="https://www.sciencedirect.com/science/article/pii/S1071581909001797">a study</a> looking at different cognitive-affective states and their impact on how students interacted with different learning systems, the authors looked specifically at the behavior of gaming the system (e.g. cheating, bending the rules, etc.), which has been shown to be associated with reduced learning. Boredom was found to be the most likely to be followed by gaming behaviors, and even beat out frustration for that dubious honor. The other states studied included confusion, engaged concentration, delight, and surprise, none of which were associated with gaming the system. It is also interesting to look at how the researchers coded delight: behaviors such as clapping hands, laughing with pleasure, and statements such as, “Yes!” or “I got it!”</p><p>So we know that moments of delight aren’t likely to impair learning, and at the very least can keep boredom away. That may seem rather ‘meh’ in terms of a reason to design for delight in our products. But we also know that even a system designed with the best learning science principles in mind can’t drive learning if students aren’t using it. So on top of embedding the key learning principles into our work, we still must design for usefulness, usability, and, yes, delight. When I asked my team to think of cases where students have expressed delight when using our products, they came up with some great examples. Sometimes delight comes from microinteractions where we try to sprinkle in a bit of fun, such as use of the “confetti” function on the iPhone when they receive 100% on a practice quiz.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*jqy9yjOgb8HXYyc7H1xO-g.gif" /><figcaption>Confetti effect when a student gets 100% on a quiz</figcaption></figure><p>Other times, it’s the scaffolding we can provide that students report as delightful — like when they figure out they’re able to read about the problem they’re being asked about in the text with a click of a button or when they get feedback on why their answers were wrong so that they gain understanding. And if laughing out loud is considered delight, we’re even happy with this student’s reaction:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/1*N5Z3MdB4pQtIDde0dcQfvg.png" /><figcaption>Student tweets “LMFAO” about our iClicker attendance feature.</figcaption></figure><p>To truly drive learning, our design team is focused on principles proven out by learning research. We will still strive to design for those moments of delight — sometimes that may be just the thing that gets us in the door and keeps a student sticking around so that the products we build can make a difference in their education and in their life. Now <em>that</em> is what delights us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17503da112cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our users are basking sharks]]></title>
            <link>https://anachman.medium.com/our-users-are-basking-sharks-4ba1bb4589bc?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ba1bb4589bc</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Mon, 13 May 2019 01:51:38 GMT</pubDate>
            <atom:updated>2021-02-23T20:27:00.868Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Originally published in 2010 on my tumblr blog</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4tFhwPR08UBl_CAWzDeYUw.jpeg" /><figcaption>Basking shark feeding</figcaption></figure><p>Well, maybe not quite…but humor me a little. As is the typical case, this idea was triggered by an NPR segment on the drive home from work. I learned that the basking shark, a giant filter feeder, is now a ‘species of concern.’ Until last year, these sharks were thought to be a cool-water fish of the North Atlantic, but new satellite data revealed that they actually migrate into the tropical waters off South America. For whatever reason, this fact struck me as an apt metaphor for understanding users. I mean, can’t you imagine those sneaky users having the whole product team fooled into thinking their behavior was one way only to be doing something totally different all of that time?</p><p>The reality is that we can’t be there 24–7 with our users. And even if we were there, we all know that a user being watched, whether in a lab or over a WebEx, is going to act differently than ‘in the wild.’ We may subtly influence them through inherent biases, or they may be trying to please us as the researchers. Lately, I have been experimenting with Omniture and Google Analytics as additional ways to understand user behavior to supplement our rich qualitative data. There are just some things that we can never get at through traditional qualitative research methods, such as what percentage of our users are using a certain feature or common paths through the site. Not that it isn’t possible to come close, but the resources and number of participants required is too cost prohibitive.</p><p>I’m under no illusion that this tracking data is the key to unlocking the mind of the users, but it can direct us into more fruitful inquiries. If a certain feature isn’t used, maybe no one wants it — or maybe they can’t find it. It’s all about triangulation. My next crusade beyond the basic page view stats that we can get with our current implementations is to track user actions within a page. Especially with our AJAX &amp; Flex portions of the site, I have very little insight into what users are doing on a page. So while observation and interviewing will give you an amazing understanding of user behavior, think about those unassuming basking sharks pulling the wool over our eyes for so long.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ba1bb4589bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does your UX design get to the finish line?]]></title>
            <link>https://anachman.medium.com/does-your-ux-design-get-to-the-finish-line-178efa1437b8?source=rss-99e7010726bd------2</link>
            <guid isPermaLink="false">https://medium.com/p/178efa1437b8</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alicia Nachman]]></dc:creator>
            <pubDate>Mon, 13 May 2019 01:37:17 GMT</pubDate>
            <atom:updated>2019-05-13T01:46:49.884Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Originally published in 2010 on my tumblr blog</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*gDry9lSkGO5oILh4E9YSDg.jpeg" /><figcaption><a href="https://www.behance.net/gallery/1041825/Finnish-Sports-Federation"><em>“Finnish Sports Federation”</em></a><em> by aleksi hautamaki, Tuukka Koivisto, BOND Creative Agency is licensed under </em><a href="https://creativecommons.org/licenses/by-nc/4.0/?ref=ccsearch&amp;atype=rich"><em>CC BY-NC 4.0</em></a></figcaption></figure><p>We’ve been actively recruiting for a second UX designer the past few months, and we recently brought in a candidate with an extensive agency background in UX design. She could clearly crank out the wireframes and produce good, solid work, but as she described her process and spoke about her design decisions, there seemed to be something missing. We all recognized that in her position, she often didn’t have the authority she needed to do the kind of research and design process that she would’ve liked, and so we were willing to cut her some slack there. But still, I had this nagging feeling that her designs somehow felt half-baked.</p><p>Over the weekend, I thought more about our interview, and the candidate’s fit with our team. Suddenly it hit me what had been bothering me about her work — she never got to see a design through to its realization. Her role and the agency’s modus operandi dictated that once the wireframes were delivered, she was on to the next project. She didn’t get to go all the way to the finish line.</p><p>How many UX designers really get to take their designs all the way? Without being involved through engineering, QA, and release, designs are often more like suggestions than full-fledged product definition. When designers have to throw their work over the proverbial wall, they miss out on a valuable process where many important design decisions can end up being made without any design input at all. It’s also a critical time where gaps in your design and new requirements come to light.</p><p>No matter how thorough you are, you will not cover all of the cases that QA will find, the impasses that come up in development, or your own last minute realizations as the system comes together. Iterating through the design phase based on stakeholder feedback and usability testing is a great way to mitigate this, but it isn’t enough. Our designs don’t exist in a vacuum, they must be implemented. And that’s often where the system starts to show its true complexity, where all the individual modules must begin to mesh.</p><p>This deep level of UX involvement is not only beneficial to the success of the project, but it also helps develop a strong instinct for systems thinking. I consider myself lucky to work in a place where I am expected to be involved in projects end to end, from the research plan to engineering to hearing first-hand the support calls coming in from customers. When the unexpected comes up, I am able to make the decisions that define how my designs will ultimately get realized for our customers, and for me, that is truly making it to the finish line.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=178efa1437b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>