<?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 Mark Wehner on Medium]]></title>
        <description><![CDATA[Stories by Mark Wehner on Medium]]></description>
        <link>https://medium.com/@mark_31534?source=rss-34e658f2c153------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oEMEMnPXWqD2jMFsXiObpw.jpeg</url>
            <title>Stories by Mark Wehner on Medium</title>
            <link>https://medium.com/@mark_31534?source=rss-34e658f2c153------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:58:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mark_31534/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[How Volunteering Made Me a Better UX Researcher]]></title>
            <link>https://medium.com/@mark_31534/how-volunteering-made-me-a-better-ux-researcher-8d736ca6680c?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d736ca6680c</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Tue, 20 Jun 2023 13:47:40 GMT</pubDate>
            <atom:updated>2025-02-06T19:11:55.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYMuQFP2FEZ1a-OoJSuIhg.jpeg" /><figcaption>The JW House kitchen where I served guests</figcaption></figure><p>When I decided to take a <a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634">sabbatical</a>, I knew that I wanted to spend my time volunteering. It was an activity that I have enjoyed in the past, yet I could not always find the time to commit. With more time opening up, now seemed like the perfect opportunity to serve others.</p><p>After scouring the volunteer boards, two opportunities stood out to me. The first gig was a teaching program that allowed me to work with primary school children and teach science topics. I would take classes, learn these topics, and I would in turn teach the topics to students at their schools or on field trips. Having previously worked in EdTech and having an interest in education, I thought it was a perfect way to spend my volunteer time. Not only would I be serving my community, but I would also grow as I learned these topics and improve my teaching skills.</p><p>The second gig was at an organization called the <a href="https://jwhouse.org/">JW house</a>. This house was strategically located next to a hospital and was a refuge for caregivers when a family member was in the hospital. The house provided a place to sleep, eat, and in general gather peace during rough times. My role at the house was to simply serve the guests. I welcomed them to the house, gave tours, served lunch, and made myself available if they needed someone to talk to. When there were no guests to serve, I spent my time doing household chores such as cleaning, laundry, and light home improvement tasks. I had no expectations of the gig, and I frankly chose it out of convenience as it was a few miles from my home.</p><p>Yet unexpectedly, it was the JW house, not the science program, where I experienced growth and gained skills. First, I learned a lot about myself as the experience gave me perspective on how to spend my energy. Nothing humbled me more than substituting my time at a high-paying tech job discussing product strategy, with folding laundry. And yet each was valuable and important in its own context. I also learned countless skills as I became “Mr. Fixit” attempting to be the handyman before the house manager called in a more experienced and expensive professional. Yes, there are so many things I learned and could write about. But there was one skill that the house taught me which surprised me — a UX research skill that I thought I had already mastered. The JW house taught me how to be a better listener.</p><h4><strong>How I became a better listener</strong></h4><p>When I applied for this volunteer role at the JW house, one of the relevant skills I listed was my ability to listen. One of the tasks listed in the volunteer job description was interacting with guests, and I thought, “I got this!”. As a UX researcher, I had been trained in qualitative methods which required me to be a good listener and observe others. Being a thoughtful listener was critical to my success as a UX researcher and was a skill I had greatly honed over my career. Even in my interview, I bragged about my ability to empathize with others, describing UX research to the house manager, and explaining how it would be a great asset for the house. I was ready to show guests my stuff.</p><p>One day, about two months into my volunteer role, a gentleman came to the house. He was curious about the house and wanted a cup of coffee. After he signed in, I asked him if he wanted a tour. He accepted and I took him around the house, telling him the story of how the house was founded and all the amenities. He politely asked questions, to which I divulged and lectured about my experience with our guests. When we eventually made our way to the kitchen, I explained how we served lunch, how it was prepared by outside volunteers from the night before, and all the available food and snack items. I specifically showcased the brownies I and my volunteer partner prepared, and I described the adventure we had preparing the snacks as we both were non-bakers. He politely accepted a brownie, and I began to brew the coffee he requested. As the Kuerig did its job, he mentioned he was a retired teacher, to which I probed him further about his school and subjects, then as an attempt to relate/connect, I shared my family history as we were a tribe of teachers. He stood there patiently, with his coffee and brownie in hand as I finished my sermon, then politely asked “My I sit and have my coffee now?”</p><p>“Of course!”, I said embarrassed that he had to ask permission to do the one task he originally came to do 40 minutes ago.</p><p>This interaction haunted me over the stint of my volunteer role at the house. It served as a great example and reminder of how I still had room to grow to become a better listener. You see most of my listening skills had been honed as a UX researcher, and as a UX researcher, I have control over the communication interaction. I know the agenda of what I want to understand and the questions to ask. I know the context and situation I’m going to place people in, and most of the time the emotions I can expect. Even in the most explorative research methods, where unexpected twists and turns in the conversation require fluidity in my moderation style, there is still a structure for me to follow, a guide to the conversation, or at least an established goal of what I want to know. Not to mention that they are <strong>participants</strong> and I’m most likely paying them for their time. In short: I’m running the show.</p><p>At the JW house, I was not running the show, nor did I have control. Each person came in with their own context which I know nothing about nor was it proper for me to actively probe into. Their situations were precarious: a family member was in the hospital dealing with an illness, some treatable and some fatal, and the fact that they were using our facilities meant that this episode was causing further inconvenience and hardship emotionally and/or financially. What is the right approach in such a situation? What is the right emotion to display? How do I interact with others I don’t have control or a defined context? These were all new questions I had to consider in my role as a volunteer.</p><p>So, I learned to be a better listener and a better observer. My goal was to serve them and serving them meant simply attending them how they wanted to be attended to. I learned to let them lead the conversations and follow their cues. I learned how to shadow their emotions and behaviors to essentially be the person they needed. If they came in joking, then I was there to joke and share a smile. If they came in somber or tired, I was there to give them peace. Some people wanted someone to talk to, others wanted to be left alone. And if they wanted to talk, I listened and let them lead the topics. Sometimes they wanted to talk and vent about their situation at the hospital, other times they wanted to take their mind off the situation and discuss other topics. Sometimes they wanted to talk about themselves and so I listened and probed. Other times they were curious about me, and I spoke and presented.</p><p>All of this required me to sharpen my skills of listening, observing, and essentially reading people. This is an essential skill of a UX researcher conducting qualitative research. Matching and reading personalities are essential for gaining rapport with a participant, making them feel at ease, and opening them up to conversation/feedback. Observing others as they interact with a product is crucial to capturing unarticulated needs and discovering additional insights beyond what people say. These are skills that I have learned and honed as a UX researcher. However having the ability to apply these skills outside of my core field leveled up these skills in ways I never expected. Had I truly mastered these skills before volunteering, I wouldn’t have allowed that gentleman’s coffee to get cold and instead I would have kept my lecturing brief.</p><h4><strong>Improve your core skills outside your field</strong></h4><p>There are many benefits to volunteering (a topic that merits its own article). And there are many benefits to broadening out your experiences, gaining completely new skills, and in general being a more well-rounded person. However, I never expected that broadening myself through this volunteer experience could make me better at my <strong>core skills</strong> as a UX researcher. Perhaps this should not be surprising as UXR and UX in general is an interdisciplinary field, mixing a broad range of subjects (technology, psychology, design, anthropology, statistics, etc.), and thus inspiration can come from a variety of experiences.</p><p>Ultimately, this may have been the greatest lesson my volunteer experience taught me: that skills, even core skills, can be learned and improved greatly from the most unexpected places. This lesson has led me to be more open to unique experiences as a place to learn and grow, and not necessarily just sticking to traditional scenarios. As I write this, I am volunteering at my son’s baseball snack shack serving hotdogs and candy — something in the past I avoided. Now I welcome the opportunity as who knows what interesting things I may learn?</p><p>No doubt focusing on the work you perform within your discipline is great for building your craft early on in your career. But when you’re ready to take your skills to the next level, I urge you to seek experiences to apply your craft outside your discipline, instead of within.</p><p><em>This writing is part of a series of contemplations in User Experience Research. </em><a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634"><em>Check out some of the other writings</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d736ca6680c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building at High Altitudes: Understanding the Power Individual Contributor]]></title>
            <link>https://medium.com/@mark_31534/building-at-high-altitudes-understanding-the-power-individual-contributor-136bb2539861?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/136bb2539861</guid>
            <category><![CDATA[individual-contributor]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[career-coach]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Thu, 06 Oct 2022 12:16:36 GMT</pubDate>
            <atom:updated>2022-11-03T17:31:07.169Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GnFZqwdv4vx5WHKtZ_2b2A.jpeg" /></figure><p>When I decided to take a sabbatical from my career, I knew that I would miss conducting research. While taking a break from the day-to-day work was much needed, I still enjoyed conducting qualitative research. So, to fill the void, I decided to do my own research project.</p><p>I had many options available, but the topic that personally interested me was understanding Individual Contributors within the tech industry at a deeper level. You see I very much considered myself dedicated to this path, and yet I never really felt there was much guidance about this path — especially ways to perform this path at a high level. From my experience, most organizations define and coach success as part of the people management path. Even my managers, as wonderful, helpful, and inspiring as they were, specifically chose <strong>not </strong>to stay on the IC path and as such, I felt often struggled to provide guidance on this path.</p><p>So, with my time during my sabbatical, I went out and looked for guidance. I reached out to my colleagues who seemed dedicated to, or at least enjoying, the path of an IC. And not just any ICs, but those who have been ICs for many years, who I knew were well respected among their peers, and performed their roles with much success. I call these people <strong>Power</strong> <strong>ICs</strong> or as I will shorten for this writing: <strong>PICs</strong>.</p><p>My goal for this project was simply to understand these PICs further and for myself to personally grow from the process. I talked to them about their journey, motivations, and how to be a successful IC at a high level in the tech industry. I ended up talking to 8 colleagues who were working as ICs within corporations with an average of 15+ years of career experience. They represented a mix of User Experience Researchers, UX Designers, Product Managers, and Product Marketing Managers. I purposefully refrained from talking to my engineering colleagues, as I felt the IC path for Engineers/Developers is a bit more common, expected, and quite frankly too unique to be comparable to my role as a UX researcher.</p><p>While I approached it like a research project, my larger goal was to simply learn from others and reconnect with old colleagues. It was never my intention to share out any learnings, yet my researcher brain couldn’t help but synthesize interesting trends from those conversations. So here is my attempt to share out these top trends and insights from the conversations. This is not a formative or exhaustive research project on ICs, but rather a discussion of the simple and broad observations that I hope you find interesting.</p><h4><strong>Power ICs don’t have it all figured out, but they know themselves well</strong></h4><p>As I sought out people who saw themselves as ICs, I went into the project hypothesizing that they had it all figured out. My thought was that they knew deeply they wanted to be an IC and had chosen their path with as much certainty as one chooses a meal off a menu. I was wrong.</p><p>I suppose I shouldn’t have been surprised that these PICs’ lives were as “zig zaggy” as everyone’s. How they landed as a PIC was not 100% planned, although it wasn’t a complete accident either. I understood this through the way they responded to my questions. When I asked questions such as “what motivates you?” or “why be an IC?”, they responded thoughtfully and genuinely. I could tell they had no canned responses nor trained talking points they’ve learned from books or career coaches. Instead, they responded deeply, reflectively, and sometimes curious towards my line of questioning. It was as if it was the first time thinking through the question — although I’m certain it wasn’t. I could tell they were still thinking their path through, even some stating that outright. While some knew they were on the path that was a fit for them, they were honest in admitting that their path could very well change.</p><p>But while they acknowledged their path was not always clear, they clearly knew themselves well. I was often surprised at how well they understood what they wanted and didn’t want out of their career. What they enjoyed, didn’t enjoy, and aspects in their work/life that truly made them happy. One word that came up over and over again was “energy”, as they constantly asked themselves, “Is this how I want to spend my energy?”. Energy is the central resource of the PIC. Realizing the scarcity of this resource, they were careful in how they chose to spend their energy in their career and life in general.</p><p>In fact, they talked about what they <strong>don’t</strong> want to do with their energy as much as what they <strong>do</strong>. This came about in choosing <strong>not</strong> to be a people manager and rejecting the tasks that came about with management. Tasks such as: engaging in the politics of an organization, the people management process of hiring, firing, promoting, and disciplining others, and rejecting dedicating their time to discussions and meetings. The fact that these PICs started with “no” and what they don’t want, I believe, was not because they were overly negative people. I believe instead that this position was needed because pursuing the management path, as they would admit, was often the expected path. Thus, they needed to be able to confidently say “no” to the tasks and management path they were expected to go down and where their career naturally led them. Some even dabbled in the management path only to discover later they did not want to spend their energy in this manner.</p><p>In the same vein, they felt the management path would take them down a path that would try and shape them to be someone they are not. I heard variations of<em> “I’m not a people leader”, “I’m not a salesman, “I’m not aggressive enough”,</em> or <em>“I don’t have an A type personality” </em>— all personality traits they felt were the wardrobe of a manager. Whether or not this perception is true is debatable, but the larger point is that knew themselves well enough to perceive that this path would ask them to go against the grain of who they are.</p><p>Finally underlining their question <em>“Is this how I want to spend my energy”</em> was a more fundamental question of <em>“Is this going to make me happy?”</em> These PICs admitted that pursuing a management path will earn them more money and more prestige but questioned if it would make them happier. This led to a flood of other questions as to what they really care about. <em>“Is this work that I enjoy?”, “Does this work fit with my natural skills and make me a better version of who I am?”, “Does the work give me meaning and purpose?”</em>. Money and titles were certainly nice, but it was not what was motivating to them — as several honestly admitted. As one PIC put it, <strong><em>“I don’t aspire to build a team. I don’t aspire to be a millionaire. I want to do interesting intellectual work with kind-hearted people”.</em></strong></p><p>Again, I believe knowing themselves well was necessary for saying “no” to the expected path of management. I asked if they felt a stigma from others by staying down the IC path. Most did not feel there was a stigma, however, they did feel it was expected of them to go down management from colleagues and the tech culture in general. So much that they had to wrestle with this decision themselves — if everyone else is expecting me to go down the management path, shouldn’t I as well? So they had to be very clear to themselves and what they did and did not want and be honest about what motivated them. Otherwise, they might be caught up in the current taking them down the management river. But with every clear “no”, comes a “<a href="https://www.amazon.com/Power-Positive-No-Relationship-Still/dp/0553384260">yes</a>”. So what were they saying yes to? If aspects of management weren’t motivating, what was motivating them?</p><h4><strong>Power ICs are motivated by curiosity</strong></h4><p>What stood out to me most with these PICs was that at their core was curiosity. They had a hunger to learn and satisfied this hunger in many ways. For some, it was learning skills, whether they be new tools of their trade or learning tangential skills represented in other roles. For others, it was being able to explore a new topic/product area. And not just scratch the surface, but really go deep in understanding this area as they found interest in both big picture thinking as well as getting into the “nuts and bolts” of a problem. Finally, there was a more abstract interest in ideas and desiring the opportunity to experiment and “play” within a space of ideas and tackle really interesting problems.</p><p>Surrounding this was the desire to not be stagnant and be able to explore a variety of topics. Once they’ve exhausted their understanding of a problem space deeply, they desired the ability to move on to the next. And to them, this is what they believed the IC track allowed them to do: the freedom to explore and express their curiosity. While certain tasks can be redundant, PICs did not see their work as an IC as boring and even seemed puzzled when I inquired how they manage to keep their lives fresh or interesting. They naturally believed that working as an IC, especially in the tech industry where things change so rapidly, put them in the best possible place to explore and find fresh problems to solve. They often questioned whether their colleagues in middle management positions had that same freedom as they observed them less able to move around industries, fields, and problem spaces effortlessly. To the PIC there was always a new product space just beyond the horizon to explore and grow from. This leads us to their next motivation: producing.</p><h4><strong>The Power IC is not just motivated to build things. It’s their goal.</strong></h4><p>PICs wanted to get their hands dirty and create something. Now each role has different ways of getting your hands dirty, but each PIC desired to have an active hand in the creation of a product. They wanted to have a very active role in the creation process and a tangible outcome they could confidently point to and say, “I helped produce that”. Now, this is what I expected going into these interviews. If there was anything I heard about ICs it was the common description that they are “<a href="https://uxdesign.cc/leading-with-craft-a-series-on-hands-on-career-paths-in-our-industry-25aea911e708">craftsmen</a>”. So hearing this was not surprising. But what I found interesting about this motivation was how it tied to their career goals.</p><p>None of the PICs explicitly talked about their career goals and not in the language I often hear in corporate talk about goals (e.g. 5 year plans, growing their career, building a personal brand, etc). That’s not to say they weren’t goal-oriented, but the sense I got from these PICs was that personal growth was not tied to who they are or who they can become, but instead what they can explore and produce. A career was not perceived as an end in itself with the outcome being higher titles, prestige, or money. While these outcomes were appreciated and a practical necessity, as I mentioned before, many openly rejected them as their primary motivators.</p><p>Instead, the perception of their career was as more of a means-to-an-end. They didn’t seem to perceive their career as a “thing” they were working to build, but rather their career is <strong>working for them</strong> by providing an outlet to express their curiosity and skills. As such, goals were very much associated with the product. Was the product successful? And even more importantly, was I able to leave my mark on the product and team? Was I able to have true impact? Impact, as I learned, was crucial for the PIC.</p><h4><strong>Impact equals success</strong></h4><p>If their core motivations are curiosity and getting their hands dirty, then the outcome that matters is impact. A very tangible impact, which they believed being an IC is the right place for impact.</p><p>I came to these PICS with this question: how can you have impact as an IC? Underlining this was a premise that I have noticed colleagues go into management specifically thinking they can have more impact within an organization. The PICs I spoke with rejected this premise and in fact felt the opposite was true. They believed that the “real” impact, or at least the impact they were looking for, happened within the IC path. The impact of the actual production and creation of the “thing” and not merely talking about the thing. Since goals were tied to products, the real impact was measurable and visible. They acknowledged that there is a power dynamic within an organization and larger decision-making is often out of their control as an IC. But at the same time, they’ve noticed some of their management peers become detached from the product and sometimes even the customers. They feared losing this connection as they believed that a close connection to products and customers was necessary from having the impact they were looking for.</p><p>The PICs also looked at how to have a broad impact as possible. Greater impact either within their organization or scaling their influence to other teams. I heard the word “altitude” come up a lot among the PICs. As ICs can get into weeds on issues, they understood that they also needed to “rise up” to see the broader landscape. This was how many saw themselves growing as an IC and what they believed helped become a Power IC. Yet there is a delicate balance here because they still want to stay in touch with the product and customers. They are looking for that goldilocks role where they have the high “altitude” to achieve greater influence, but are still not detached from the day-to-day meaningful product impact. As one PIC put it, <strong><em>“I don’t want to move so far up to the top that I lose that connection (with the product and customer). But still high enough that I can have influence.”</em></strong></p><p>Scaling their impact fundamentally came down to people. To have a great impact, PICS realized they could no longer just work independently as they did in their early years as an IC. Instead, they needed to learn how to bring others into their process and how to effectively bring people together with their work. Whether it be with upper management or collaborating with other ICs. This also means growing their field and knowledge base for others. In one sense, they needed to be mentors.</p><h4><strong>Power ICs want to mentor, not manage</strong></h4><p>All the PICs I spoke to desired to mentor others. This was somewhat surprising to me as I logically assumed the fact that they avoided people management meant a desire to move away from grooming others. While they were saying no to many aspects of management, the one aspect that did intrigue them and perhaps drew them closer to considering management was having the opportunity to mentor other junior ICs. In fact, they often sought out ways to help groom junior and senior peers without having to be a manager. A PIC, who held a management position, remarked, <strong><em>“I like the mentoring aspect of managing people. I hate the focus on writing, delivering feedback, the bureaucracy of it. Drives me batty”.</em></strong></p><p>In general, they alluded to a difference between mentorship and management. With a manager, they believed, existed a tricky power dynamic. While a mentor, on the other hand, has more of a collaborative peer relationship which they believed may be more conducive to learning and growing. One PIC remarked, <strong><em>“It’s totally different. As a manager, you are responsible for their career. They feel they need to listen to you, even if it is just suggestions. It’s a whole different dynamic.”</em></strong></p><p>And their desire for mentorship didn’t mean just 1-on-1 relationships. Some expressed their mentorship desire by growing and helping others through organizational initiatives such as facilitating training or classes. While an IC role can seem isolated, they were in fact very sensitive to their relationships with others — again they perceived growing impact came down to people and facilitating important relationships. With this in mind, how did they see their relationships with their own managers?</p><h4><strong>PICs desire managers who provide Autonomy, Support, and Compassion.</strong></h4><p>I was intrigued to talk to these PICs about managers because as seasoned ICs with lots of experience I was curious as to whether they even cared about who managed them. For junior ICs, managers can be extremely important as they can help support and develop skills. But these PICs had plenty of skills. So was it even important to them who was their manager?</p><p>As it turned out, these PICs very much cared for who was managing them. It wasn’t so much who their manager was, for example, they didn’t necessarily have to have a similar background (i.e. if I am a researcher, they don’t need to come from a research background). It was much more about what they do and were able to provide. There were three common aspects of managers between these PICs</p><p><strong>Autonomy: Let me do the things I can</strong>: As a Power IC striving to have impact, it was important that they have autonomy. As one PIC put it, <strong><em>“A manager who gives me space and appreciates what I can bring to the table”. </em></strong>This went beyond not wanting to be micromanaged. There was a much deeper level of having the ability to earn the trust of their manager such that they don’t just take a high-level goal and run with it, but that they are also able to help <strong>define </strong>what that high-level goal is. It’s not just doing the work, but being part of defining the work. One PIC described it as: <strong><em>“Being part of deciding a project. It’s not just, ‘we need personas’, and I go out and do personas. I should be a part of defining what we need to be doing.”</em></strong></p><p>This desire to go beyond just executing a goal and defining the goal, I believe, is a big difference between how Power ICs operate compared to my observations of lower-level ICs</p><p><strong>Support</strong>: <strong>Help me with the things I can’t do: </strong>If autonomy was allowing the PIC to shine with the things they can do and excel at, support was clearing the path of the obstacles they can’t do or have difficulty doing. For example, corporate politics was an area that many PICs did not want to engage in, nor did they feel was a strength. PICS appreciated managers who helped navigate them through potentially hairy political situations. As one PIC remarked,<em> </em><strong><em>“I know that my manager will always have my back. Even if there is disagreement, there is still a shared respect”.</em></strong></p><p>It was always a bonus if their manager was someone who complimented their own skills, and someone who excelled in areas they knew was not one of their strengths or expertise. A PIC stated this plainly as, <strong><em>“The good managers that I’ve had they’ve had experience in areas I didn’t or were smarter in areas I wasn’t or struggled with or quite frankly wasn’t passionate about”.</em></strong></p><p><strong>Compassion</strong>: <strong>Care about me personally: </strong>Compassion came down to the simple fact of whether their manager cared about them as a person. Now perhaps this is important to everyone, not just ICs, or even in the tech industry. But I think this aspect was especially salient for PICs because their role and goals were so tied to the building of products. Perhaps it was important that they be perceived and treated as more than just a resource — more than just a cog in the production wheel. Underlining this aspect was desiring a manager who has honest and transparent, such that they could see that compassion. One PIC described this as,<em> </em><strong><em>“Having a real authentic person who brings their ‘real self’ to work and cares about me as a human first.”</em></strong></p><p>When all was said and done, the way PICs talked about the managers they enjoyed the most in their career were people that they viewed as peers more than managers per se. As one stated, <strong><em>“It’s less about management and more about collaboration and intellectual trust. I can trust you to be a resource for me and you can trust me and what I bring.”</em></strong></p><h4><strong>Conclusion: How might you support or evolve into a PIC?</strong></h4><p>As a researcher, I’m always looking for the “so what” from my research. If this were a normal research project I would work with my stakeholders to discuss and <a href="https://medium.com/@mark_31534/mantras-for-an-influencer-in-user-experience-research-1b7183ea0b5a">collaborate</a> on the implications from these insights. However, this is not a normal research project nor do I have any concrete stakeholders to collaborate with.</p><p>So instead, I’ll leave you with some questions. Questions to think about, whether you are a manager or an IC to think through your own takeaways from these interviews.</p><p><strong>If you are an IC, how to think about evolving into a Power IC</strong></p><ul><li>How do or don’t you relate to these PICs I spoke with? Which of these motivations speaks most to you and is your current role helping to satisfy these motivations?</li><li>What is important to you in your manager? Are you communicating this to them?</li><li>How do you want to spend your energy? Do you know yourself well enough to state this clearly?</li><li>How might you try and scale your impact?</li><li>Are you seeing at a high altitude to have increased impact?</li><li>Are you building relationships or merely working independently?</li><li>Are you helping to define goals and not just execute goals?</li><li>Are you looking for mentorship opportunities — whether it be receiving or providing mentorship?</li><li>Are you just curious or are you looking for ways to execute on that curiosity in a meaningful way?</li><li>Are you exposing yourself to as many problems surrounding your organization and not just the ones you’ve been assigned? Are you a catalyst for solving those problems?</li></ul><p><strong>If you are a manager, how to think about supporting a PIC effectively</strong></p><ul><li>How might you provide autonomy, support, and compassion, the three aspects they desire out of a manager? If for some reason you aren’t able to provide this, is there someone else in your organization who can?</li><li>How might you offer opportunities that allow them to mentor other ICs?</li><li>How might you tap into their curiosity and provide a productive space for them to explore and satisfy their curiosity?</li><li>How might you help them scale their impact and allow them to gain altitude to not just execute goals, but be a part of defining those goals?</li><li>How might you be mindful of working with your PIC at personal goal setting, recognizing that at a deeper level what motivates them may not fit within the corporate laddering culture? Remember that as a manager, and someone who chose to <strong>not</strong> stay on the IC path, what motivated you might not be the same as your PIC. Ask and learn — you may be surprised!</li></ul><h4>Parting thought: Engage and Listen</h4><p>Finally, I would recommend to everyone to spend time engaging and talking to other colleagues about their career journey. And by this, I don’t mean seeking others to advise you on your own career — although that is certainly important as well. Instead, listen to others tell their story about their career path, their motivations, and how they perceive their role — especially those who may be on the same path as you. As interesting as these insights were to think through, what I gained most from this process was simply listening to others tell their story. How their story related or didn’t relate to my own, helped me think about my own path and gave me a better understanding of myself. Some of my interviewees commented that our conversation felt like a therapy session, which made me smile because I definitely found the conversations therapeutic as well.</p><p>So as you hike down your career path, take a moment every now and then to greet those along your trail and ask/listen to them tell the story of their journey — it will help increase the meaning and purpose you find in your own trek.</p><p><em>I’m still interested in learning more from PICs. Feel free to connect and contact me as I’d love to listen to your story or share/learn from each other. </em><a href="http://www.linkedin.com/in/mark-wehner">www.linkedin.com/in/mark-wehner</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=136bb2539861" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Xtra Benefits of User Experience Research]]></title>
            <link>https://medium.com/@mark_31534/the-xtra-benefits-of-user-experience-research-4625bddf2a12?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/4625bddf2a12</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Tue, 13 Sep 2022 13:02:49 GMT</pubDate>
            <atom:updated>2025-02-06T19:10:11.356Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Xtra Benefits of UX Research</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*Nifgr6j54jpWncawl4fw4A.jpeg" /><figcaption>“Fancy X” by Simon Wehner</figcaption></figure><blockquote><strong><em>Mark’s inner monologue when thinking about this writing</em></strong></blockquote><blockquote>“Ok, I’d like to write about the less tangible benefits that come with a user experience research project that goes beyond core insights and recommendations.</blockquote><blockquote>But what do I call these benefits? In my mind, I’ve always referred to them as the “soft” side of research — the “hard” side being those core insights. But “soft” makes these benefits sound weak and unimportant. Hmmm. Maybe a metaphor would be better. Ok, let’s see, what’s soft? A down pillow or comforter is soft. It’s not the substance of your bed, but the extras that give a good night’s sleep.</blockquote><blockquote>So, the “Down” side of research.</blockquote><blockquote>Oh dear lord, that doesn’t work. Ok so maybe another metaphor that doesn’t have to be soft. How about icing? As in the “icing on the cake”. Let’s look that up. According to good old <a href="https://www.merriam-webster.com/dictionary/icing%20on%20the%20cake">Webster</a> the phrase “icing on the cake” is “something extra that makes a good thing even better”. Perfect.</blockquote><blockquote>Hmmm. A little bit cliché. And I don’t really like icing or cake for that matter. I can’t very well write in a metaphor I’m not passionate about.</blockquote><blockquote>I’m more a savory person than sweet. Maybe spices? That’s similar to icing. The extra “something” that enhances the base flavor. The “spice” of research? Makes sense as a metaphor, but as a title, I’m not so sure. It doesn’t come across right away that these are benefits.</blockquote><blockquote>Oh forget it.. this is going nowhere. I’ll just use a placeholder for now. Like “X”. Or maybe the “Xtra” benefits.</blockquote><p>For years, I have come to think of user experience research as having two sides when it comes to benefits. There is the hard and practical side: data, insights, results, and recommendations. And then there are other benefits that come from a research project. Not the main benefits, but the other side benefits — sort of an “X factor” of research. Here are 3 such Xtra benefits that I’ve observed</p><h4><strong>Xtra Benefit #1: Brings empathy</strong></h4><p>Customer empathy is discussed a lot when it comes to research. The effect where stakeholders go beyond simply rationally recognizing a customer’s pain point, to having a deeper understanding and emotional tie to their customers’ needs. The idea is that having a closer bond with your customers leads to a greater understanding, which then leads to better products.</p><p>This benefit of research is well understood. Out of all the Xtra benefits, this is the one that is most obvious to stakeholders as it is felt at the surface level. This is especially true for qualitative research which can involve listening to customer stories and perhaps having face-to-face interaction. In fact, this is so well understood that there are often non-research company initiatives, such as listening in on customer care calls, with the sole purpose of creating greater customer empathy.</p><p>Feeling the immediate impact of empathy is a great reason to start research ASAP. Whenever I’m starting with a new team, especially one that has not had a prior history with research, the first thing I try to do is complete a research project as quickly as possible. This not only collects insights and more questions we didn’t know needed answers, but also simply brings empathy where there was none before. This can often include myself, especially if the customer base is new to me.</p><p>This benefit is like icing. It’s something everyone can taste right away. Even though it’s not the more substantial cake part (i.e. the insights), the icing (customer empathy) may be what lingers with you the most.</p><h4><strong>Xtra Benefit #2: Moves a project forward</strong></h4><p>I once worked on a product that was always at odds from a process standpoint. I’m not sure what the reason was. Perhaps it was not having a proper project manager, enough resources, or more likely because the space was at odds with its traditional “money-making” product versus the emerging space that was developing within the industry.<em> </em>The<em> </em>result was that there were a lot of stops and stalls with the product never really moving forward. Things did get better as time went on, but I also noticed that the product leader had a habit of planning research without having a firm sense of what we wanted to accomplish. We’d start scheduling research ASAP and then backtrack on what we wanted to know. Eventually, I approached him saying that it seemed that we always have the “cart before the horse” so to speak and we should really start with our questions first before jumping to putting research in place. He acknowledged the point, but also said, “You know Mark, I schedule the research early because it gets everyone moving and gets us out of the constant discussion on what we’re doing. You’re the only one who’s helping us move forward.”</p><p>I’m still not quite certain that was the best development process, but it did open my eyes to the Xtra benefit of how research can move a project forward. Now I don’t mean the “hard” value research brings in moving the <strong>product</strong> forward in terms of quality or avoiding costly changes later. Instead, I’m talking about the benefit to the <strong>process </strong>and moving the <strong>project</strong> forward, especially when on a team that is process-challenged. Simply put, scheduling a research project puts a stake in the ground. Now there are plenty of other stakes and checkpoints that can be put in place, but a research stake is different. For some reason, the act of talking to and showing customers a product, even a rough prototype, feels closer to launching a product. And in my experience, this feeling pushes the team a bit more than other checkpoints. I believe this is because:</p><ul><li><strong>Research forces asking key questions about what we need to know about our customers.</strong> We’re going to talk to customers, so what is it that we really need to know? What are the key questions important to moving the product forward?</li><li><strong>Research forces getting out a rough prototype</strong>. Most likely we’re going to show customers something, so we’re going to need a prototype based on our key questions. The benefit of getting a rough prototype out quickly is that we now have something for our internal stakeholders to visualize and react to. Something that may feel more natural and interactive than what stakeholders might see in a design review.</li><li><strong>Research forces issues/insights for us to react to.</strong> Yes, there is the “hard” value of insights I have described, but simply from a process standpoint having insights and more information pushes our conversations forward. Sometimes insights and information seed the important questions we need to know and reveal the conversations we need to have.</li><li><strong>Research aligns a team. </strong>This is different than the Xtra benefit #3 of bringing a team together, which I’ll discuss in the next section. This is more about helping us improve that golden “team alignment” attribute that business consults write about. Research not just brings forward knowledge, but a s<strong>hared knowledge</strong>. Having this shared information about our users helps streamline our decisions. Information about our users that we can all agree on and get past our individual ideas and focus on what’s best for the customer. Ultimately, this alignment makes the team more efficient. I’m always a bit perplexed when stakeholders say, “­there isn’t enough time to conduct research”. On one hand, I get it — you have to set time aside for research before moving forward. However, if you think more deeply from a process standpoint, research is actually saving us time by helping to align our team and making us more efficient.</li></ul><p>This benefit is like spice. It naturally blends with the other benefits or “flavors” to enhance the overall experience. Its benefit may not be immediately obvious, but if you’re paying attention, as that product leader was, you can taste this secret ingredient.</p><h4><strong>Xtra Benefit #3: Brings a team together</strong></h4><p>Good research is a collaborative process. Sure, you can conduct research in isolation, but you’re not going to get very far from an impact standpoint. A researcher can’t move in the right direction without <a href="https://medium.com/@mark_31534/the-3-lenses-of-user-experience-research-planning-2e3861d1176f">goals and questions</a> from others. Stakeholders’ observation and involvement during a study can be a breeding ground for discussion. I’ve always advocated for dedicated observation rooms in UX research labs simply because they physically brought teams together and often led to interesting discussions on insights as they were discovered in real time. Insights can also spur conversations between stakeholders during research readouts and serve as wonderful inspiration for brainstorming sessions. While user experience research is a practical tool, I’ve also noticed that it is an “event” that brings people together.</p><p>Whenever I conduct home visits, I usually open up observation as broadly as I can. While I limit my travel party to around 2 observers, so as not to overwhelm the participant, I do my best to encourage anyone to join and come along. I know the practical effect of seeing research insights firsthand as well as the Xtra benefit of increased empathy for the customer by being in their home. But what surprised me, was the number of times the pair of observers who came along were meeting each other for the first time! In one instance I had two team members who shared a cubicle wall, yet never talked to each other before the field visit. Even more surprising was to see how research bonded these two around a shared experience of customer insights and empathy. What a wondering thing to bond over!</p><p>Personally, I’ve always tried to make research a <a href="https://medium.com/@mark_31534/mantras-for-an-influencer-in-user-experience-research-1b7183ea0b5a">group effort</a>. From listening to <a href="https://medium.com/@mark_31534/the-3-lenses-of-user-experience-research-planning-2e3861d1176f">everyone’s questions</a> to broadly inviting everyone to research sessions, report readouts, and brainstorming sessions. I always believed that it was better to be as inclusive with research, rather than hide it away. The motivation was the very practical reason for garnering better questions, insights, and outcomes from the research. But the Xtra effect was bringing my team closer together. Just a minimum amount of effort in including people led to bonding the team around the research event. While it’s not the aim or goal of the research, it’s really satisfying to see.</p><p>Similar to a down comforter on a bed, it’s not the focus. If someone were to ask you to describe your bed you might talk about the size, the kind of frame, or perhaps even the mattress quality and firmness. You probably wouldn’t discuss your bedding. But once you lay down for the night, you sure are happy that down comforter is there.</p><h4><strong>Why are Xtra benefits of research important?</strong></h4><p>It’s important to talk about the value of research during the planning stage of research where you are trying to get everyone clear on why we should do a research project and what we’re going to get out of it. So, we talk about the insights and recommendations we’ll gather and how this will lead to better products and a better business. All perfect justifications for conducting research.</p><p>But we shouldn’t feel shy about the Xtra benefits. Sure, you won’t sell a research project solely based on these benefits and it will be hard to measure ROI of these benefits, but they have value. And to be honest for a few unique teams, these Xtra benefits may be as critical as the actual insights themselves. What’s brilliant about these Xtra benefits is that they just naturally happen. You don’t need to do anything special. For example, you could optimize a research project for customer empathy and take steps to bring stakeholders <a href="https://medium.com/@mark_31534/mantras-for-an-influencer-in-user-experience-research-1b7183ea0b5a">closer</a> to the data. But even the simple act of conducting research will get you on your way to customer empathy.</p><p>So don’t hide these benefits. It’s ok to bring up these benefits before, during, or even within a postmortem conversation. Who knows? These benefits could be exactly what pushes a team who is on the fence on whether to commit to a research project. You don’t need a metaphor or catchy name to explain these benefits to your stakeholders. You can talk about both the straightforward practical outcomes of conducting research while also highlighting those less tangible, yet no less important, benefits that make research so valuable.</p><p><em>This writing is part of a series of contemplations in User Experience Research. </em><a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634"><em>Check out some of the other writings</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4625bddf2a12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Investigating Questions, not Testing Products]]></title>
            <link>https://medium.com/@mark_31534/investigating-questions-not-testing-products-afbb2c02620?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/afbb2c02620</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Tue, 23 Aug 2022 13:04:15 GMT</pubDate>
            <atom:updated>2025-02-06T19:07:37.302Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*b3cm7wisjIc_dzpY7dBAXw.jpeg" /><figcaption>“Test” by Simon Wehner</figcaption></figure><p>Ever since I started my career in user experience research it was ingrained in me by my managers, peers, and experts to test early and often. The theory is that for research to have the most impact it is best to be involved in the product development process as early as possible. In the early days, before prototyping tools were prevalent and sophisticated, I learned to praise the concept of paper prototyping. Paper prototypes were easy to create, change/iterate on, and crude. But their crudeness really pushed to the forefront the idea that it was better to explore rough ideas and directions early before getting too far down a solution path. I came to believe that there is also a benefit in a rough and unpolished product, especially when testing concepts because users would give more honest feedback with more rough materials or even add their own ideas.</p><p>This idea of “test early and often” logically makes a lot of sense and has been written, shared, discussed, and presented within the field for <a href="https://www.nngroup.com/articles/paper-prototyping/">many years</a>. So for years this is what I myself preached to my stakeholders: test early and test often. And while my preaching was successful, it was not always easy. There was always a natural uneasiness among stakeholders in conducting research on something that felt incomplete. It seemed their natural tendency was to want to wait on researching with users until we felt we were in “a good state”, whatever that meant. So, it often became a struggle to test early and often.</p><p>Thus over time, my technique has changed from simply preaching, “test early and often”, towards trying to change the mindset of how my stakeholders think and talk about research. That is, changing from the mindset that we are testing the product to the mindset that we are investigating questions.</p><h3><strong>Testing the product mindset</strong></h3><p>The “testing the product” mindset is the base-level mindset we all have with user experience research. Isn’t that what user experience research is after all — testing products? Of course, we can easily dismiss this right away from a methods perspective because user experience research includes a lot of methodological approaches — many that don’t even involve product (e.g. ethnography).</p><p>However, I’m not talking about a method, but a mindset — how my team thinks and talks about my research. In this case, the mindset that the research we plan, develop, and conduct is aimed toward the end goal of testing the product. Often this mindset is represented crudely as understanding, “Is this working?”. Now there is a time and place for this mindset, such as towards the end of the project right before/after we launch the product or within specific methods like benchmarking studies. However, I believe this is the only appropriate time and place for this mindset, and yet this is the mindset that I find most stakeholders naturally have throughout the whole development process.</p><p>What’s wrong with this mindset? First, it causes stakeholders to not want to test early. There is a reluctance to wait till “we’re ready” to test it or until the product is in a “good shape”. In the same vein, this mindset makes stakeholders reluctant to use rough versions of the product. After all, if it’s too rough, then will we be able to get an accurate assessment of “is it working”? Even in situations where we may be exploring many different product variations, this mindset puts our research towards the goal of understanding “which one is better”, instead of a much richer goal of understanding which aspects within these variations are most useful/valuable to our customers.</p><h3><strong>Investigating questions mindset</strong></h3><p>Instead, I’ve learned to try and shift the mindset of my team that we are “testing the product” to “investigating questions”. I’ve found that this mindset shift first makes us ask ourselves what <a href="https://medium.com/@mark_31534/the-3-lenses-of-user-experience-research-planning-2e3861d1176f">questions</a> are important to explore and understand with our research. Now, these are still questions relevant to the product. This is not an academic study, and the goal is still very much the practical improvement of the product. So I may very well get the question, “Is this product working?”. This is fine as a starting point, but not good enough for me. These kinds of dichotomous yes/no questions are the least informative questions and not very helpful. I don’t believe I’m doing my job right if I come back from a research project with only “yes” or “no” answers. There is power to asking “<a href="https://medium.com/cheggux/if-time-travel-were-possible-what-would-i-tell-myself-as-a-junior-ux-researcher-30c5dfd7dc70">why</a>?”, and so I’ll want to understand what areas concern us the most in the experience, key problems we’re struggling with, and ultimately get to the bottom of the questions we need to investigate to make the product successful.</p><p>Second, if my team is within this mindset of “investigating questions” instead of “testing the product”, then we no longer care about the product being rough. Instead, we may tailor our prototype specifically to answer these questions and even create parts that we would never have in a finished product. I’ve been on teams where during our research we discovered typos in our copy, however we decided to leave those typos in. Why would we do this? Because participants noticed the typos, told us it was incorrect, which was then a signal to us that they were actually reading the copy! We didn’t care about an imperfect prototype, because that imperfect prototype was helping us reach the goal of answering our question — in this case, were they noticing the copy? Stakeholders with the investigating questions mindset relax and are no longer nervous about testing something unfinished.</p><p>Finally, stakeholders with this mindset are also fine with testing early in the process. In fact, I’ve noticed that they have an urgency to test early rather than a desire to wait for the product to be in “good” enough shape. Their motivation is to get answers to these critical questions ASAP.</p><p>This mindset naturally fits well with early foundational and generative user experience research methods (ethnography, participatory design, card sorting, etc), and it’s easy for stakeholders to assume this mindset in these methods simply because we often don’t have a product to test. However, I want stakeholders to have this mindset throughout the whole research process from our early foundational research to our more tactical design/usability research when we do have a product.</p><h3><strong>Let’s stop using the word “test”</strong></h3><p>So what does changing this mindset look like in practice? I couldn’t think of a better example than dropping the word “test” from our conversations. Calling what we do “testing” (i.e. “user testing”, “product testing”, “user experience testing”, etc) keeps us from getting into investigating questions mindset. I get why we use it, as at the surface user experience research looks and feels like a test. I have used the word “test” plenty, however over time I have shifted away and dropped it from my language. While it is one simple word, it engrains a mindset of dichotomous pass/fail, “Is this working?”, mindset. What is a test if not a graded and scored assessment? The purpose of user experience research is much more in-depth and focused on understanding our users and building great experience around their needs and behaviors; not a simple pass/fail assessment. I would argue that this isn’t even the point for more evaluative studies, like benchmarking research, which do actually have scores. From my experience, the scores in those methods aren’t the end goal, but just a mechanism of drawing attention to the important, potentially troubling, aspects of the product.</p><p>So join me in dropping the word “test” from our language. A simple word with a lot of baggage, and a first step towards shifting to an investigating question mindset.</p><h3><strong>The power of shifting mindsets and perceptions</strong></h3><p>There are lots of ways to shift mindsets and they are as easy as choosing the language we use when describing the goals of our research, why we are conducting the research, and what to expect.</p><p>Perhaps this seems overly simplistic, but I found in the world of user experience we’re constantly struggling with adjusting other’s perceptions. I’ve never seen any other discipline that struggles with how others perceive their roles like User Experience. No doubt this is why many design and research teams go through so many iterations of what to call themselves. I’ve been on teams called, “Usability Engineers”, “UER”, “Design Research”, “Product Researchers”, “UX Research”, all while conducting essentially the same work. Simple words can matter in conveying the point and value of our work.</p><p>So when it comes to trying to achieve the “research early, often, and rough” agenda I’ve found shifting the mindset of others on my research to be the most effective. It’s not a silver bullet and dropping words like “test” won’t solve all my issues with how people perceive my research. However, starting with the right mindset shapes how others perceive my research, and thus sets a proper foundation. A foundation that I can then build a successful relationship with and avoid fighting, struggling, and undoing misperceptions later.</p><p><em>This writing is part of a series of contemplations in User Experience Research. </em><a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634"><em>Check out some of the other writings</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afbb2c02620" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scale Your Research Influence: Include, Listen, and Share Broadly]]></title>
            <link>https://medium.com/@mark_31534/scale-your-research-influence-include-listen-and-share-broadly-d2f8df5f0b4f?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2f8df5f0b4f</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Tue, 07 Jun 2022 17:08:42 GMT</pubDate>
            <atom:updated>2025-02-06T19:05:21.857Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*2n4IIhTbQoZrGV3aoajMtA.jpeg" /><figcaption>“Important People” by Simon Wehner</figcaption></figure><p>If you see your research role as a <a href="https://medium.com/@mark_31534/my-evolution-as-a-user-experience-researcher-632e7cc3d129">Catalyst</a>, it’s a logical conclusion that this means focusing on people high up on the org chart — those with acronyms in their titles. This makes a lot of sense as they are important decision-makers and hold a lot of weight in an organization. Not to mention that impressing these people can be good for your career. However, if I take a close and honest look at my career and the actual tangible outcomes from my research, most of this came from people outside of this small sphere of high-up organizational influence. Here are 3 stories of how my work influenced others unexpectedly.</p><h4><strong>Include Broadly: Great ideas come from anyone</strong></h4><p>When it comes to research observation, whether it be in a lab, remote, or in the field, I always try to err on the side that it is better to invite more people to observe than less. So, I always invite as many people as I can — many of whom I’d never met before. I believed in the power of <a href="https://medium.com/@mark_31534/mantras-for-an-influencer-in-user-experience-research-1b7183ea0b5a">observation </a>and this always proved to lead to interesting outcomes.</p><p>I was once working on a search engine for buying products locally in your neighborhood. My team was engaged in a RITE process, and we tested multiple iterations over the course of a month. A lot of people came in and out of the lab, I really couldn’t keep track. It ended up being a great project, even earning me praise from the product VP. Fast forward five months, I noticed a poster displayed outside the desk of an engineer on my team. It was his “hack-a-thon” project that won him a prize and even better — the green light to implement his idea. Curious, I asked him to explain it to me, to which he replied, “Well it’s your idea”. I was puzzled. It didn’t look like any idea I ever proposed, and I was not involved in this hack-a-thon. He then clarified and said the inspiration for the idea came from observing a RITE study months earlier. He observed a user problem in search, unrelated to what we were studying, and he set off to go solve the problem, unbeknownst to me. I was touched. Not because he was giving me credit for the idea, which I did not deserve, but because my work had inspired him and led him to success. To me, this was as important as the praise from the VP.</p><p>Problem solvers are everywhere in our industry. And everyone has their own unique gifts as to what they are equipped to solve. My acronym colleagues high up the org chart have unique powers to solve the broader big picture problems as does the staff engineer who is solving the problems of actually “painting that picture”. Practically speaking, it means being broad with who you include. Even if it is simply inviting a broad swath of stakeholders to research sessions, report readouts, and ideation sessions. Try to be as inclusive as possible and see where it may lead.</p><h4><strong>Listen Broadly: Great questions come from anyone</strong></h4><p>Throughout my career I often find myself working on new and emerging products. In big companies, where I’ve spent a lot of my work, these initiatives usually start with a small team and grow in size as the product grows and gains traction. In such situations, it’s usually hard to know who to involve and include — often people would just sort of appear along the journey of building a product.</p><p>I was working on such an emerging product when a new team member just showed up out of the blue one day to the research lab, observing our research on the latest product ideas. After the session, I introduced myself and learned that his expertise was in marketing, and he recently got pulled into the project to figure out how to position this new product. He thus was interested in a lot of marketing questions, which were not aligned with my research marching orders to inspect the core functionality. Nevertheless, this team member intrigued me. You see the product wasn’t just new. The whole concept of the product was new to the world. Nothing like it had ever been proposed or seen before. So, the challenge my marketing colleague faced was how to introduce this new concept to people and a completely new mental model they did not yet have. I was beginning to see in our research that getting this right was quite critical as the core functionality hinged on users understanding this new product concept. In the end, his questions actually ended up being the more critical questions for us to test, even though it was off the radar of the original product creators.</p><p>Interesting research questions can come from anywhere. These are often the <em>your lens</em> questions I discussed in a previous <a href="https://medium.com/@mark_31534/the-3-lenses-of-user-experience-research-planning-2e3861d1176f">writing</a>. This is tough because often there is a logical tendency to listen to questions coming from “the top”. However, when I reflect back, some of the best questions have come from the most unlikely places, as was the case with my marketing colleague. Often it’s these individuals who see potential issues that others do not, and need research to help navigate these potential problems. Practically, this means just listening and engaging as broadly as possible. This doesn’t mean I have to answer everyone’s research questions. And I rely on my colleagues at “the top” to see the big picture and help prioritize questions. I simply open myself up to hearing what is worrying and concerning my teammates, as it often leads to very interesting areas of research.</p><h4><strong>Share Broadly: Great results can come from outside your team</strong></h4><p>One of the most fascinating research projects I have ever conducted centered around how people discover and attend local events in their neighborhood. This involved doing an extensive diary study and ethnography, tracking the journey of people as they discovered and attended things to do in their local area. The primary recipient of these insights was my immediate team who was tasked with showcasing local events across Yahoo! However, as I was conducting the research, I noticed interesting insights about how people schedule and coordinate events, which seemed quite relevant for the Yahoo! Calendar team. So I immediately reached out and involved that team in the research. At the end of the project, the insights were relevant, intriguing, and impactful. I worked hard with my team and these insights to try and lead our effort in displaying events across Yahoo! However, as I reflect back on the project, some of the best ideas and solutions from that research came from the calendar team — not my own team.</p><p>Working in big organizations, or even midsize organizations with several products, gives one the opportunity to scale their influence to many more people and products. When I find myself in such situations, I always do my best to keep up-to-date on what those other products are up to. That way, I can identify any relevant insights that might emerge from my own research that these other products might find helpful, as was the case with the calendar team. But even then, sometimes you simply don’t know if your insights might be useful for another team, in which case it is simply useful to share openly and broadly as much as possible.</p><p>In some cases, the influence I had on other products wasn’t even based on the insights I uncovered. Sometimes just sharing my work broadly sparked curiosity and questions in those other teams which inspired them to conduct their own similar research project.</p><h4><strong>Be Open</strong></h4><p>Focus is very important for research, otherwise questions and projects can get out of hand. From a very practical sense, a research project can’t be all things to all people, and it is important to <a href="https://medium.com/@mark_31534/the-3-lenses-of-user-experience-research-planning-2e3861d1176f">prioritize</a> your research focus. However, I don’t believe influence needs to be focused. Influence is not a scarce resource that needs to be bottled and shared with only a select few. I don’t believe influence is a zero-sum game or that influencing some comes at the cost of the ability to influence others. If you truly see your researcher role as a <a href="https://medium.com/@mark_31534/my-evolution-as-a-user-experience-researcher-632e7cc3d129">Catalyst</a>, you need to think about how to scale your influence broadly. Of course, when setting up a report readout, I’ll center it around the CPO’s schedule over the summer intern’s. But there is no reason why I can’t influence both and I truly believe in the value of influencing both. This is extremely easy to do. All it comes down to is opening yourself to broadly including, listening, and sharing. Don’t hide your work.</p><p><em>This writing is part of a series of contemplations in User Experience Research. </em><a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634"><em>Check out some of the other writings</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2f8df5f0b4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 3 Lenses of User Experience Research Planning]]></title>
            <link>https://medium.com/@mark_31534/the-3-lenses-of-user-experience-research-planning-2e3861d1176f?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e3861d1176f</guid>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Tue, 17 May 2022 17:43:18 GMT</pubDate>
            <atom:updated>2025-02-06T19:01:22.198Z</atom:updated>
            <content:encoded><![CDATA[<h3>The 3 Lenses of UX Research Planning</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qaPFm-5lGGHhxtEtxLKbRA.jpeg" /><figcaption>“Questions” by Simon Wehner</figcaption></figure><p>Along time ago, I went on a job interview that didn’t go well. One interviewer asked me how I go about deciding what research to conduct. The question seemed simple to me. I simply said, “You get everyone into the same room and discuss what questions we need to know, then go out and conduct the research”. But the interviewer kept pushing and pressuring me with variations of the same question, “but how do you know it is the right research?”. I was puzzled by this continued question because I thought the answer was really this simple, and so I kept repeating myself making for a very awkward and frustrating conversation.</p><p>Now as I look back, with a lot more experience under my belt, I realize that the question was not that simple. You can’t answer every question and do unlimited research — there isn’t enough time or resources. Priorities need to be put in place on what research we do and don’t do. If I were to answer that question today, I would describe the three lenses of questions that I believe go into research planning.</p><h3><strong>Our lens</strong></h3><p>So, I wasn’t completely wrong in the approach I described in the interview as research planning does start with listening to questions. The first set of questions falls under the broad lens of what we need to know as a business. I call it <em>our lens</em> because it should be a shared goal between all the stakeholders. These questions don’t just affect one person’s role (like marketing or design), but all of our roles. Often these are fundamental questions about the business or product. In fact, they are so fundamental that these questions can sometimes be challenging as they are stated quite broadly (e.g. how do we increase conversion by x%?) and technically aren’t even user research questions. So my role as a researcher is to help translate those broad questions into user research questions (e.g. what do we need to understand about our users that can help us understand how to increase conversion?). Because these are shared questions, everyone should be aligned that these are important questions. If not, then we have bigger problems as a team and we should not even think about the next lenses until we’re aligned.</p><h3><strong>Your lens</strong></h3><p>The next lens I call <em>your lens</em> because these are the questions of individual stakeholders. Each stakeholder has their own perspective and unique set of questions — often tied closely to their role (marketing, design, product management, etc). While these questions also can be broad, like <em>our lens</em>, they tend to be quite tactical. These are the questions that revolve around barriers and hurdles that are presented to individual stakeholders — often questions that keep individuals up at night as key problems to solve. Sometimes these are unobvious questions that emerge later in a project once individuals begin to work on their own project goals and find themselves challenged. It’s imperative to not underestimate the value of <em>your lens</em> questions. The most important questions I’ve encountered in my career often came from the most unlikely individuals.</p><p>Utilizing this lens well means being as inclusive as possible, expanding and reaching out to as many stakeholders as possible to gather these questions. For one, this helps ensure we’re not missing any of those unique, yet critical questions. Secondly, it helps bring people <a href="https://medium.com/@mark_31534/mantras-for-an-influencer-in-user-experience-research-1b7183ea0b5a">closer</a> and shares research ownership with a larger set of people.</p><h3><strong>My lens</strong></h3><p>After these first two lenses, I now have a ton of questions and not enough time to answer all of them. So just like any good planning process, we need to prioritize. Hopefully, I should see some alignment between stakeholders on what’s most important — especially within <em>our lens</em> questions. However, for whatever reason, when it comes to brainstorming research questions people seem to be really good at “Yes, and’ing”. The common phrase I hear is, “yes that’s a great question, which also makes me think about another question….”. I love people’s curiosity and enthusiasm and try my best to encourage them. But I’m also the only one in the room who understands the effort that is going to be needed to answer all these questions. So, this is where <em>my lens</em> comes in.</p><p><em>My lens</em> is myself and the researcher lens that I apply to the project. So first and foremost, there are my own questions. Usually, this comes with experience. If I’ve been on a project for a while there may be unanswered questions from the past that will be helpful to understand moving forward. But mainly <em>my lens</em> is about bringing practicality into the process and helping to prioritize work given that we most likely won’t be able to answer all the questions that my team has. <em>My lens</em> usually comes down to asking some variance of the following questions:</p><ul><li><strong>How much do we already know? Do we have any past research that helps address these questions? </strong>In my experience, it’s all too common that the same questions come up over and over again, especially as an organization ages. Are there any learnings we can already leverage? If so, how long has it been? Has the landscape changed enough that it is worth exploring these questions <a href="https://medium.com/@mark_31534/your-product-will-die-someday-7a7b82288f50">again</a>?</li><li><strong>Is this a new product or experience?</strong> Are the questions being asked leading us into uncharted territory as an organization? Or is this yet another iteration of something we’ve explored and tested again and again? There are times when I’ve had products go through lots of iterations with research along the way. There comes a point where it was best to stop researching the latest iteration so we can focus on early exploring the next phase of the project. Other times I’ve had products with a rich history within the organization and lots of past research. Even if there were new questions to explore, the institutional knowledge was built up in such a way that we had less to gain as a team for this established product, than if we used our time exploring questions for a new product or concept. Finally, there is also the familiarity and experience of the users. Is this something completely new and a first-time experience or just another familiar next step? In short, novelty, exploring new products, and projects that explore the proverbial “we don’t know what we don’t know” kind of questions, get priority.</li><li><strong>What is the risk if we don’t get it right? </strong>Risk is always involved when it comes to prioritizing and decision-making, and research planning is no different. Often this question is posed in terms of importance, as in “how important is this piece of the product experience?” However, I prefer to pose it in terms of risk. For one, I often find stakeholders have difficulty coming to a consensus if I ask what’s important. Second, I think discussing things in terms of risk helps focus the conversation on the actual experience and what we may learn. For example, in my experience, the “welcome” and first-time experiences are often deemed as the less important parts of an experience than the core product. The “welcome” experience is often treated as a side project and does not nearly get the most attention. However, from a risk perspective, getting this experience wrong can have catastrophic cascading effects on the experience. So <em>my lens</em> bumps this up in priority for research to make sure we get this right.</li><li><strong>How confident do we feel in our approach? </strong>Now, this is a tricky question because I’ve seen a lot of overconfidence regarding an idea or approach that failed — confidence is no barometer for success when it comes to a product. This question is more applicable towards the other end of the spectrum and for teams that often can’t make up their minds on an approach to an experience. In some cases, researching multiple design approaches can be useful for fundamentally exploring interesting questions about our users. In other cases, I’ve been given countless variations of an experience and asked to let the research help us decide. Notwithstanding that an A/B test might be more appropriate in some of these cases, I’m often surprised by how much team alignment there is already on these variations. If we all logically think it through and agree on variation A, then why are there versions B, C, D, E, F, etc. ? If all the other factors I described earlier <strong>don’t</strong> apply (there is a high risk if we get it wrong, it’s a new product, etc) then it might be a better use of our research resources to explore other foundational questions about our users than using research to help make up our indecisive minds.</li></ul><p>These questions are not an algorithm or map to follow on whether we do or don’t do research. <em>My lens</em> is simply about helping to prioritize. Asking these kinds of questions helps us navigate when we have too many questions and not enough time or resources, which I often find, unfortunately, to be often the case. They help us think beyond what is simply useful to know and instead think about how to maximize what we get out of our research efforts.</p><h3><strong>A more thoughtful approach to gathering questions</strong></h3><p>From here I suppose the next steps in prioritizing can come down to your favorite methods of using weights, scores, and spreadsheets. This I am not a master in and I am always on the lookout for ways to improve.</p><p>I have purposefully not been very prescriptive here in terms of the steps to take (i.e. step 1: discuss <em>our lens</em>, step 2: discuss <em>your lens</em>, etc), because I’m always constantly evolving my approach based on the context at hand. This is just a framework I work with to help guide my approach.</p><p>Planning research still comes down to questions. First <strong>listening to questions</strong> and the curiosity of others (<em>our lens</em>,<em> your lens</em>). Then <strong>asking questions</strong> to help us as a team prioritize our research questions (<em>my lens</em>). I suppose that is how I would answer that interview question posed to me ages ago. Still conceptually just as simple, but a more refined and thoughtful approach.</p><p><em>This writing is part of a series of contemplations in User Experience Research. </em><a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634"><em>Check out some of the other writings</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e3861d1176f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Greatest Lesson My Dad Taught Me as a UX Researcher]]></title>
            <link>https://medium.com/@mark_31534/the-greatest-lesson-my-dad-taught-me-as-a-ux-researcher-194fff990acf?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/194fff990acf</guid>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Tue, 26 Apr 2022 14:50:49 GMT</pubDate>
            <atom:updated>2024-02-20T22:42:03.879Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cknw25JVN7CzdVzS_rJeNQ.jpeg" /><figcaption>Collage of Harvey Wehner created by Michael Wehner</figcaption></figure><p>My dad was a high school teacher for 31 years teaching English and Journalism. When Dad passed away in 2019 from a fatal lung disease, many of his former students threw their own party celebrating his life and the influence he had on them. I visited this gathering with my brother. It was interesting to see a side of his life that I had never seen before as we listened to stories of what an inspiring teacher and mentor he was. On our way home from the party, my brother revealed how odd the experience was as he never saw Dad as a teacher. This struck me as I had felt like this for years always seeing Dad as a father, but never a teacher. I was surprised to learn my brother, who followed in his footsteps becoming a teacher himself, also had this experience. We further discussed our childhood, knowing Dad was a teacher, but never seeing him actively taking a “teaching” role in our lives. He never instructed us or taught us lessons — at least no more or less than other fathers I had known. He was never in “teacher” mode at home. Perhaps it was conscious parental style, or perhaps he had enough of playing that role at work and did not want to “bring his work” home with him. When I look back at my life with my Father, he was a role model, but never a teacher. Yet, he probably taught me one of the most important lessons in my career.</p><p>Years ago I conducted a fascinating ethnographic field study. I put a lot of effort and passion into the project. I traveled to homes across the greater Bay Area and created what I thought was an insightful summary. I felt great. But when it came down to presenting the project and insights, I didn’t feel too great. There wasn’t a lot of interaction or questions from the stakeholders. Just a lot of nodding heads. Some in agreement, some in understanding, and one nodding to try and keep from lulling into a nap. I left the meeting/presentation feeling horrible. Was I wrong about the project? Were the insights not as impactful as I thought or was I just a horrible presenter?</p><p>After that presentation, I visited my dad for dinner. The presentation was at the end of the day, right before I left, so I joined the dinner still feeling distressed. Dad, sensing my stress, asked how things were going at work. Having no time to process the event, I unleashed my thoughts. I informed him how I conducted this fascinating project but gave a horrible presentation with a lack of any feedback or enthusiasm from stakeholders. Dad quietly listened. He too silently nodded as my stakeholders did, making me wonder if he truly understood. We came from such opposite worlds, UX and teaching English, and I was not sure if he could relate.</p><p>I finished my rant, Dad paused, then told his own story:</p><blockquote>“When I first started teaching English, I loved poetry and I really wanted to teach it to my students. So one year I built a fabulous curriculum around all my favorite poets and poems I loved. Well as I began teaching, I noticed the students seemed disinterested. I remember one student falling asleep in class and I had never had that happen to me before. I can still see that student today snoring away. So after finishing the poetry section I decided ‘I’ll never teach this again — and I didn’t.”</blockquote><blockquote>“So, 5 or 6 years pass by and I reconnected with a former student. As it turned out she was getting her graduate degree in English. When I asked her what inspired her to go into English and she said, ‘well Mr. Wehner, actually it was those classes you taught on poetry.”</blockquote><blockquote>Dad briefly laughed and smiled at himself.</blockquote><blockquote>“I cursed myself for the years I wasted not teaching what I loved based on my wrong impressions. I started teaching poetry from then on and never stopped”.</blockquote><p>Dad ended it there. No further lesson or summary. But I got it. Judging the success or failure of something, especially a presentation, simply based on perceiving others’ reactions can be misleading. As a researcher, I know that people’s reactions can be very telling and useful for prompting a question. But a presentation is not a research project and one’s own nerves can arise and perhaps cloud one’s perceptions. Perhaps that stakeholder could have fallen asleep because they were disinterested, but there are plenty of other reasons (poor sleep, missing lunch, meeting at the end of the day, etc.). Do you know what would have been more accurate? Simply asking. Why rely on my feelings about how things went when I could get more accurate and unbiased feedback by just asking my stakeholders. Had either my father or myself done this, we could have saved ourselves a lot of unnecessary frustration. Because as it turned out, like my father, that research became pivotal for another project 6 months later. It was my first lesson in learning about the <a href="https://medium.com/cheggux/if-time-travel-were-possible-what-would-i-tell-myself-as-a-junior-ux-researcher-30c5dfd7dc70">longevity of research</a>. The real reason why the passion didn’t show during that meeting was that the team wasn’t ready to act on those presented insights at that moment. But the passion for my work certainly showed later.</p><p>So I pass this lesson on to you as perhaps another <a href="https://medium.com/@mark_31534/tips-for-user-experience-research-presentations-2f19c49c9dd1">presentation tip</a>. When thinking about how a presentation went, or any work for that matter, don’t rely too heavily on how you feel in the moment and certainly don’t use your perceptions as your criteria for success. There are much better assessments and in some cases, as the saying goes, only time will tell.</p><p>That was the greatest lesson my father ever taught me as a UX researcher and I bring it with me to every presentation. It’s an interesting lesson because it never came as a lesson he “taught” me, but just through his story. Sometimes the most important insights can be conveyed through a simple story and letting the other draw their own conclusion. I know I’ve experienced that with my own work as a researcher and use <a href="https://medium.com/@mark_31534/mantras-for-an-influencer-in-user-experience-research-1b7183ea0b5a">storytelling</a> to convey points. Hmm. I guess Dad taught me more lessons as a UX researcher than I thought!</p><p><em>This writing is part of a series of contemplations in User Experience Research. </em><a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634"><em>Check out some of the other writings</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=194fff990acf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips for User Experience Research Presentations]]></title>
            <link>https://medium.com/@mark_31534/tips-for-user-experience-research-presentations-2f19c49c9dd1?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f19c49c9dd1</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Tue, 05 Apr 2022 21:04:57 GMT</pubDate>
            <atom:updated>2025-02-06T18:58:36.963Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tips for UX Research Presentations</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8-hvLr6KdXzSEzMy4dTxWA.jpeg" /><figcaption>“Listening and Talking” by Simon Wehner</figcaption></figure><p>In a <a href="https://medium.com/@mark_31534/how-to-be-a-better-presentation-audience-member-5b83def9d280">previous writing</a>, I shared tips for how to be a better audience member. I started there because quite frankly we’ll spend more of our time being audience members than presenters and there is little information out there on how to be a good audience member. But I’d be remiss without sharing the other side which we all struggle with: presenting.</p><p>A few years ago, my manager asked me to think about how to improve the presentation quality of the UX research team. She enjoyed my presentations and wanted my presentation style to rub off on others on the team. At first I felt a little bit out of sorts because I’ve never really considered myself a good presenter or, more accurately, I have always been a bit self-conscious presenting. However, as I reflected further, I realized that it was this self-conscious feeling that made me more aware over the years of my presentation style and developed me into a better presenter. So I forged ahead thinking of what I have learned over the years and developed a curriculum of presentation best practices specifically for researchers. I supplemented my thinking by reading two presentation books recommended by UX peers: “<a href="https://www.amazon.com/Show-Tell-Everybody-Extraordinary-Presentations/dp/1591848024/">Show and Tell</a>” by Dan Roam and <a href="https://www.amazon.com/Presentation-Zen-Simple-Design-Delivery/dp/0135800919">“Presentation Zen”</a> by Garr Reynolds.</p><p>I thought I would share a taste of what came out of that curriculum. There are a lot of great and more robust resources, such as the books I just mentioned, so this is by no means an exhaustive list. Just some of my top tips and advice specifically relevant to User Experience Research presentations.</p><h3><strong>Tell a story</strong></h3><blockquote>Storytelling makes ideas more memorable</blockquote><p>In both “See what I mean” and “Presentation Zen” the authors stress using storytelling to convey your points. The rationale is that storytelling makes ideas more memorable. In User Experience Research presentations storytelling helps to bring emotion and customer empathy which further connects the stakeholders to their customers.</p><p>Storytelling can mean many things. There is the high level of arrangement of your presentation narrative such that it tells a cohesive story and not just a barrage of slides. But there is also the simple act of using actual stories to convey a point, which is how I find myself using storytelling effectively. As I described in a <a href="https://medium.com/@mark_31534/mantras-for-an-influencer-in-user-experience-research-1b7183ea0b5a">previous writing</a>, I try as much as possible to intersperse my presentations with participant stories. I take a pause from the presentation to tell a story of a user that highlights a key insight I want to stress. Not only does it bring stakeholders closer to the user and make the insights more memorable, it also helps to illustrate an insight.</p><p>As a User Experience Researcher, I am blessed with access to lots of great stories at my fingertips. It would be a shame to not use and share them.</p><h3><strong>Create a presentation and written version</strong></h3><blockquote>Researchers struggle to make a great presentation <strong>or </strong>a great written report. I just create both.</blockquote><p>Every presentation book or class I’ve ever taken always preaches the same theme: less is more. Less slides, less bullets, less words — less.</p><p>However, in User Experience Research there is a conflict. When you create a presentation deck it must dually serve the purpose as something to be presented as well as read later. There is a conflict here because as we’re taught in presentation classes we don’t want our audience to read the slides, but rather listen to us the presenters. But for a written report those details need to be described and written down. So this leads to conflict as researchers struggle to make a great presentation <strong>or </strong>a great written report. Should they try walking a tightrope creating something in between? What’s a researcher to do?</p><p>I just create both and avoid the conflict. It surprisingly doesn’t take much more extra time for me. I first create a written report meant to be read either in the near future or archived for future inspiration. When it comes time to present, I prune it down to a lighter version — speaking towards those details I’ve just removed. When I present, I print out my written version as a guide which I have on hand when I present. Printing may be old fashion, but paper is an elegant “2nd screen”.</p><p>Just remember that “less is more” applies to your written version as well and taking this approach doesn’t leave room to dump <a href="https://medium.com/cheggux/if-time-travel-were-possible-what-would-i-tell-myself-as-a-junior-ux-researcher-30c5dfd7dc70"><strong>everything</strong></a> into the written report.</p><h3><strong>Triangulate data</strong></h3><blockquote>Simple triangulation can go a long way in strengthening your insights</blockquote><p>Academic research constantly builds off one another. You’ll never find a journal article without dozens of references. For some reason, this gets lost when it comes to research conducted in industries such as User Experience Research. Perhaps it’s the fast-paced nature of research, the desire to have a simple message, or just the lack of prior research given the specificity of the project.</p><p>Whatever the reason, I’ve found my message to be more effective when I’ve been able to reference related research as much as I can. First, it helps me tell a much richer story of our users by tying the threads of multiple insights. This is especially true when I have been able to mix quantitative data and qualitative data together as they <a href="https://medium.com/@mark_31534/missing-the-point-of-qualitative-research-edc5433fbfc">dance beautifully together</a> by answering the questions of both how and why. Second triangulating data helps bring creditability to the insights. For better or worse, I’ve noticed that people tend to find your story more credible when they see multiple studies referenced.</p><p>The beauty of this is that it does not need to be heavy-handed. While I’ve created very thorough synthesis reports that triangulate multiple research projects together, the concept of triangulating data can be impactful in the simplest forms. I’ve found that simply referencing other research as a footnote, presenting a supporting graph for an insight, or even just verbally saying, “We’ve heard similar insights before……” can be impactful. Simplicity in a presentation is still important and simple triangulation can go a long way in strengthening your insights.</p><h3><strong>Focus on time management</strong></h3><blockquote>There is the delicate moderation of allowing conversations to happen, but also making sure there is time to get through all the insights.</blockquote><p>The consistent feedback that I’ve been given and had to work on is managing my presentation time. It seems I’m always at odds with trying to get through content at a pace that allows me to avoid rushing through insights at the end. I’m certain this is true for lots of types of presentations, but this is especially true for User Experience Research presentations because interesting insights seed interesting conversations. If I am truly embracing my <a href="https://medium.com/@mark_31534/my-evolution-as-a-user-experience-researcher-632e7cc3d129">Catalyst role</a> I need to hear my stakeholders’ interpretations and begin the discussion on what to do with this data. This takes time. So there is the delicate moderation of allowing conversations to happen, but also making sure there is time to get through all the insights.</p><p>I admit haven’t mastered this and it is still a struggle. The best thing that I’ve found is to first plan conversations as part of the presentation. I usually plan a third of my time for conversations. If I have 1 hour, I plan for 20 minutes of conversations and 40 minutes of presenting. To do this I need to prioritize. I prioritize first what to keep in the presentation based on which insights I really want to focus on. And among those insights, I think about what the key takeaways are and where I expect to have the most conversation or controversy. I keep an eye on the clock at all times and cut out insights on the fly. Better to discuss these additional insights later than to rush through and have the insights not come across clearly in the moment.</p><h3><strong>Credible, Curious, and Conversational</strong></h3><p>Different presentation contexts require different tones and styles. When I reflect on the style I’m aiming for in research presentations, it would come down to three C’s.</p><p>1. <strong>Credible:</strong> First and foremost, you want an audience to believe your research. While credibility is built in many ways, when it comes to presentation style I’ve found credibility is achieved by making myself come across as unbiased as possible. I’ve noticed that people are naturally on guard when they feel someone is “selling” something to them. And there is a place and time for salesmanship within a presentation, but for the most part I don’t think a research presentation is the place. When the focus is on data and insights, I want to disconnect myself from the data as much as possible — the data is what it is without my bias determining it. Of course, I have my expert interpretation when discussing the next steps/recommendations which is where salesmanship comes in. But when talking about data, as part of my <a href="https://medium.com/@mark_31534/my-evolution-as-a-user-experience-researcher-632e7cc3d129">Catalyst role</a>, I want to make my stakeholders feel like this is <strong>our</strong> research, not <strong>my</strong> research.</p><p>2. <strong>Curious: </strong>If you are not a salesman, then how do you add energy and enthusiasm? For me, I generate enthusiasm from my curiosity. I’m a naturally curious person and curiosity is core to research. Curiosity is also infectious. Stand in a crowd of strangers, look up, and say “isn’t that fascinating”. I bet you’ll spark several strangers’ interest who can’t help but look up. Using a curious tone not only grabs attention but focuses that energy on the insights.</p><p>3. <strong>Conversational:</strong> I try my best to aim to make the presentation feel as much as possible like a conversation rather than a presentation. This is not always easy, and the best approach I’ve found is a mindset shift. I try to put myself in the mind space that I’m leading a discussion and not necessarily presenting, shifting the context around in my head and letting my tone and style follow. And if this mental jujitsu doesn’t work, simply leaving time for questions and literally having a conversation helps to achieve a conversational tone.</p><p>I realize that reading about tone/style is difficult– you really have to see it in action. So here is an analogy that spoke to me from “Show and Tell”. As Dan Roam wrote that “report” presentations are the most frequent presentations and yet they are also the most likely to fail. Why? As he put it, they usually just present the facts with little surprise, drama, and hence are not very memorable. The analogy he gave was to imagine watching a sports game with no ticking clock, halftime, no surprises — just the facts. It wouldn’t be very memorable. Enter the announcers whose emphasis and commentary turn the facts into a lively story. This really hit home for me as the role of the “announcer” felt exactly like the kind of tone that hits on the 3 C’s and achieves the tone I am aiming for. They turn the facts into a conversation, bring enthusiasm to draw you into the action, and at the same time are not taking sides — giving them credibility in their interpretation. They’re announcers, not cheerleaders. When I think about trying to be credible, curious, and conversational in a research readout I try and channel my inner sports announcer.</p><h3><strong>Prepare for pushback</strong></h3><blockquote>There is a delicate balance of how to deliver bad news in a way in which people will still listen and accept what you are saying.</blockquote><p>In all presentations, there is a risk of pushback or negative response to what you are delivering. I believe the risk is even higher in UX research presentations as you are often in the position of delivering negative feedback — basically telling someone their baby is ugly. So, there is a delicate balance of how to deliver bad news in a way in which people will still listen and accept what you are saying. Here are a few tips I found helpful for User Experience Research projects specifically.</p><p>First, when stakeholders are faced with results that challenge their preexisting ideas, the first thing they often do is attack the method or project setup. To prepare for this, I usually do my best to poke holes in my own research. When I was a graduate student, I ran my thesis research project using the psychology department’s resources. As I described my project to the lead psychology professor, whom I just met, I couldn’t help vent out all the aspects that I was concerned with that could confound the study. After he patiently listened, I quickly apologized for venting, to which he replied, “No that’s good. It sounds like you’ve really thought this through. Good researchers know their project flaws.”. That really stuck with me, and now I feel comfortable deeply critiquing my research. You’re the best person to poke holes through your project, so poke away! By doing so, you’ll be prepared for those difficult questions.</p><p>Second, you’ll no doubt get questions you don’t have answers for. New insights tend to pose new questions. When this happens, I fight the urge to make a guess. I spoke about the importance of researchers admitting “I don’t know” in a <a href="https://medium.com/cheggux/if-time-travel-were-possible-what-would-i-tell-myself-as-a-junior-ux-researcher-30c5dfd7dc70">previous writing</a>, and in the context of a presentation it goes back to credibility. If you’re just making a guess at a question, how are your stakeholders supposed to believe the insights you do know and are presenting? Of course, I do give opinions, but I always preface that there is no research to support these ideas. However, there is an exciting opportunity to get out there and learn more!</p><p>Finally, the last tip comes from my previous manager. She taught me that if I ever have a sense that research is going to be delivering news people don’t want to hear, to begin “pre-selling” before the presentation. There are lots of ways to do this, but my favorite comes in the form of starting to expose the bad news early on during the study. This is not hard because I’m always trying to bring stakeholders <a href="https://medium.com/@mark_31534/mantras-for-an-influencer-in-user-experience-research-1b7183ea0b5a">closer</a> to the research. Not to mention that people are always asking for the results as early as possible. Of course, I have to be certain in the result before previewing but doing so does take a bit of the “shock” away and allows me to also get a preview of how stakeholders are taking it. It also gives stakeholders time to process the information before the larger share-out.</p><h3><strong>It’s not about you</strong></h3><blockquote>It’s not about impressing people with the depths of my knowledge, but sharing or teaching something of lasting value.</blockquote><p>As mentioned earlier, I’ve always been self-conscious about presenting. It seems to me that no matter how great a presenter you are or how confident you seem, everyone deals with some element of anxiety when it comes to public speaking. While this applies to any presentation, the need to deliver bad news at times in User Experience Research presentations is not fun and can make anyone nervous.</p><p>The most helpful tip for myself was inspired directly from “Show and Tell”. Dan Roam ends his book by talking about how presenting is a gift. As a presenter, you are given the gift of an audience’s time and in return, the best gift you can give back is an extraordinary presentation. As he puts it, “Enjoy your idea. Enjoy yourself. Enjoy your audience. This is going to be fun.”.</p><p>For me thinking this way completely changed my approach and mentality when giving presentations. I now see presentations not about me, but about my audience and giving them insights that might change their thinking in some way. It’s not about impressing people with the depths of my knowledge, but sharing or teaching something of lasting value. When I have this mentality, I feel a little less anxious because I’m not focused on myself and how I look or sound. Instead, I’m inspired because I’m focused on others and trying my best to give them insights to help them understand their customers.</p><p>I’ve taken plenty of presentation classes over my career, and they were all helpful in one way or another. But they were also general and often in the context of a general presentation like a TED talk. And while that is helpful for setting a foundation of presentation skills, I was always looking for the nuances in specific advice for my industry or within my context of research presentations. I hope these tips provide a slice of those nuances for <em>User Experience Research presentations.</em></p><p><em>This writing is part of a series of contemplations in User Experience Research. </em><a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634"><em>Check out some of the other writings</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f19c49c9dd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to be a better presentation audience member]]></title>
            <link>https://medium.com/@mark_31534/how-to-be-a-better-presentation-audience-member-5b83def9d280?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b83def9d280</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Tue, 22 Mar 2022 21:12:15 GMT</pubDate>
            <atom:updated>2024-02-20T22:41:28.934Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How to be a better audience member during presentations</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cLY8gUOfXHrmiERSw69EVA.jpeg" /><figcaption>“Listening and Talking” by Simon Wehner</figcaption></figure><p>Last year I had the opportunity to take a presentation class. I have taken 4 classes on presenting in my career. They were all great in their own way, each teaching me something new about how to communicate effectively in front of an audience. No doubt presenting and communicating effectively is a valuable skill or at least valuable enough that my company was willing to spend resources to train us in this skill. While companies spend a lot of money training and critiquing presentation skills, I’ve never seen any training programs on how to be a good listener and audience member. The flip side to this communication equation. As a researcher, I’ve always thought of myself as a good listener, and I’ve brought that skill to be good at absorbing and engaging presentations. So here are some of my simple tricks that I’ve learned on how to be a good audience member.</p><h4><strong>Shut everything else down. Be present to the presentation.</strong></h4><blockquote>If the information presented didn’t require my attention, then why was I there?</blockquote><p>This is probably the most intuitive tip yet seems the hardest to do. It’s not rocket science that the more focused you are on a presentation, the better you’ll understand it. Yet we all consider multitasking easy to do and have our eyes on multiple threads (email, Slack, social media). We leave it up to the presenter to grab our attention and convince us what they have to share is more worthwhile than our other tasks. We often are not present and keep one ear open for sound bites or key takeaways.</p><p>In the days of in-office working and in-person presentations, I made it a point to not bring my laptop to most meetings and definitely not presentations. The act was to force me to pay attention and remove any unnecessary distractions. My thinking was that if I can’t be in two places at once and if I needed my attention on something else, then maybe I shouldn’t be at that meeting/presentation. I still had my phone handy if an emergency ever came up, although one rarely ever did. If the information presented didn’t require my attention, then why was I there?</p><p>But what about using a laptop to take notes? Sure, I use my laptop to take notes. But I also take written notes. I’ve developed a system where I use electronic notes during planning meetings as electronic notes work well for creating bulleted lists, great for capturing the “brass tacks” of project work, and are easily accessible later. But presentations are more about absorbing and learning new ideas. This is where I use written notes. There is something about the visceral nature of writing and drawing which makes it useful when learning new information.</p><p>Of course, this has become harder for me in the days of working remotely as my laptop is always there beckoning to distract me. I simply make the remote video application as large as I can and focus on the presentation. Being present to the presentation not only helps me absorb the information but makes it more enjoyable for me as I focus on just one thing.</p><h4><strong>Show your attention</strong></h4><blockquote>The more you are engaged the more it engages the presenter.</blockquote><p>No presenter in the history of presenting wants an unengaged audience. There is a relationship between the presenter and the audience. The more you are engaged, the more it engages the presenter. The more engaged the presenter, the more confident they become. The more confident they become, the better the presentation.</p><p>There are lots of some small tricks to showing your engagement (eye contact, nodding, etc), but if you follow the first point of being present to the presentation, you’ll show your attention naturally and it will show to the presenter. However, I will share with you one trick I learned for being an actively engaged audience member during remote presentations. Remote meetings naturally put everyone in eye contact, whether they are listening to you or ordering food delivery for lunch. So, it is hard for the presenter to know if you are actually engaged. But here’s the trick: <strong>show your hands.</strong> Bringing at least one hand into the camera view shows that you’re not browsing, typing, or doing anything but listening. I have a thinking gesture of resting my face on the palm of my hand, which naturally brings my hand into view and shows my attention. I’ve noticed that when I engage in this gesture as much as I can I receive a better interaction my remote speaker.</p><h4><strong>Ask “we” questions first</strong></h4><blockquote>“We” questions fit within the narrative and are helpful for everyone. They naturally make the presentation more of a conversation.</blockquote><p>Another way to engage is by asking questions and asking the right questions. As an audience member, there are 2 basic types of questions: “Me” questions and “We” questions. “We” questions are those that fit within the narrative of the speaker’s presentation. They could be clarifying a key point or context. Generally, these are questions that are going to be helpful for everyone there to know. All other questions are “Me” questions, and only relevant only to you. “We” questions are the questions I try to ask.</p><p>Now most speakers love all types of questions. After all, that’s why they’re there and they prefer an engaged audience. But here is the thing about “me” questions, while the speaker is happy to answer them, it is likely a tangent from the story the speaker is trying to tell. Although interesting, it most likely takes time away from other material the presenter hopes to discuss.</p><p>“We” questions fit within the narrative and are helpful for everyone. They naturally make the presentation more of a conversation which helps engage others and makes the presentation better.</p><p>I usually write down all the questions I have. It slows down my thinking, gives me pause, and helps me prioritize my questions. I then look for the “We” questions and ask these during the presentation. “Me” questions I save towards the end if there is time or simply engage the presenter with these questions at another time. I find “Me” questions tend to lead towards more interesting conversations in a 1-on-1 discussion format anyways.</p><p>Sure, this seems simple, but you wouldn’t believe how many people ask more “Me” questions than “We” questions.</p><h4><strong>Show up on time and know your speaker</strong></h4><blockquote>The first 10 minutes of a presentation are the most important.</blockquote><p>In presentation classes, we are taught to know your audience and craft your message to that audience. The same goes for an audience member. Who is the speaker, why are they here and what is their goal? Context of course is important for learning, but context also sets the stage for everything to come in the presentation. Luckily most speakers, even the most poorly trained, will do their best to give context at the beginning of the presentation. This is why the first 10 minutes of a presentation are the most important and the part that I try to give my most focus. If this isn’t clear at the beginning, ask — preferably earlier than later.</p><p>But here is the #1 audience sin: showing up late to a presentation. If you show up late to a presentation, you miss the context and a chance to know your speaker. You then spend the whole presentation playing catch up or worse make the presenter catch you up and waste everyone else’s time. Don’t show up late. If you show up late, then the onus is on you to elevate your listening skills and not on the speaker to be miraculous and make up for your tardiness.</p><h4><strong>If the slides are confusing, then don’t look at them</strong></h4><blockquote>Who says you have to read the slides?</blockquote><p>In presentation classes, there is a lot of focus on how to improve slides. Some give heuristics on the ratio of words to bullets, bullets to slides, slides to presentation, etc. Some push presenters to try presenting without slides at all. Slide creation is truly an art.</p><p>But what’s an audience member to do when confronted with horrible and illegible slides? Here’s what I do: I don’t look at them. Who says you have to read the slides? Whenever I just focus on the speaker, I’m often surprised at how much I can grasp and gain just from listening. If it is confusing or unreadable, why waste time trying to parse those slides? For remote presentations, most systems allow me to easily minimize the slides and maximize the person’s face. Essentially, I’ve turned their presentation into a no slides presentation. As a bonus, ignoring the slides and focusing on the speaker show attention.</p><h4><strong>What are YOUR main takeaways? What action are YOU going to take?</strong></h4><blockquote>Actively think about what are the main 3 points that stand out to you and what your next steps might be.</blockquote><p>To be a good presenter we’re taught to serve up and spoon feed our audience the main takeaways. Don’t make the audience hunt and piece this together. Give the audience clear action!</p><p>As an audience member, you may very well be given this clearly and concisely. But I think as an audience member you should make an effort to piece together your own takeaways and action items. Actively think about what are the main 3 points that stand out to <strong>you</strong> and what <strong>your</strong> next steps might be.</p><p>I know myself as a presenter I’m always interested in how others perceive my data. Often the best interpretations of the data are not my own and I’m always grateful when others bring that interpretation to the conversation. You are unique and have a unique perspective, so bring it!</p><p>If the speaker gives you clear takeaways, then respect and digest them. From there, compare that to your takeaway and action items. If you see something unique from your interpretation that stands out, ask about it. If the speaker doesn’t give you clear takeaways, well then you’ll be doing the speaker and everyone a service by asking and clarifying the takeaways.</p><h4><strong>We can all be better speakers AND audience members</strong></h4><blockquote>Let’s get out of the mindset that our role is to just show up — expecting to be wowed, threatening to take our attention elsewhere.</blockquote><p>Don’t get me wrong, we should all strive to be better presenters. As a presenter, you have the gift of someone’s time and attention and you should strive and work on how best to give back to the audience.</p><p>A presentation is just another form of communication and communication is a two-way street. I know presentations don’t seem that way, but there is a role for you to play as a receiver of information and you should do your best to play that role well.</p><p>Many of these tips seem just obvious acts of being polite, respectful, and attentive to a speaker. They absolutely are and simple things to do. Maybe the reason why there are no classes on being a great audience member is because we should have all learned these skills in primary school. Yet you would be surprised at how often I notice colleagues NOT doing this — myself included at times. Let’s get out of the mindset that our role is to just show up — expecting to be wowed, threatening to take our attention elsewhere.</p><p>Of course, if everyone was a great presenter and stellar at grabbing your attention, creating awesome slides, and giving you clear takeaways, then you wouldn’t have to be mindful of any of this. However, it seems terribly less efficient to turn everyone into rockstar presenters, when just a few simple acts can make us all into better listeners.</p><p><em>This writing is part of a series of contemplations in User Experience Research. </em><a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634"><em>Check out some of the other writings</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b83def9d280" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your product will die someday]]></title>
            <link>https://medium.com/@mark_31534/your-product-will-die-someday-7a7b82288f50?source=rss-34e658f2c153------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a7b82288f50</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <dc:creator><![CDATA[Mark Wehner]]></dc:creator>
            <pubDate>Tue, 08 Mar 2022 22:42:28 GMT</pubDate>
            <atom:updated>2025-02-06T18:53:39.262Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Your Product Will Die Someday</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UbYaxdfA2B_1ls_d1UORTg.jpeg" /><figcaption>“Dead” by guest artist Simon Wehner</figcaption></figure><p>I’ve been very grateful to work on a lot of unique products, and each project has taught me a valuable lesson. However, there was one product in particular that really changed my outlook on my work.</p><h3><strong>The passion for a product</strong></h3><p>Immediately after graduate school, I had the opportunity to work on Yahoo!’s mapping product. It was an exciting time in the industry as Google Maps had just come onto the scene changing the local space forever. It was special for me personally as well because I love maps. In fact, as I write this I can see two decorative maps framed on my home wall from where I’m sitting. I love the aesthetic and technical aspects of maps and I love the connection to my human factors training in such topics as wayfinding and data visualization. I was very proud of landing this role.</p><p>Working on Yahoo! Maps was a great experience and ended up being everything I wanted and more. Mostly because I got to work with other amazing mapping nerds who were as passionate about maps as I was. At the time we explored some really amazing new concepts, many of which are standard in today’s mapping products. I personally had the freedom to conduct and explore fascinating research topics. I can say without hesitation and with all modesty that I had amassed a larger research portfolio around online maps than anyone else at the time.</p><p>I threw myself happily and passionately into the product. I remember flying down to the Hewlett-Packard office in San Diego where we tested our driving directions in cars with users. I was not impressed with the research consultant HP hired, and we got into some heated arguments on how best to run the research. I was still a fairly junior researcher and took a lot of tactful persuasion on my part to convince the more seasoned consultant to take my recommendations seriously. However, when you work on a product you love, those conversations are more thrilling than stressful.</p><p>You may be wondering, why would Yahoo! partner with HP in our research? Well, HP had a special interest in innovating around printable information, and at the time we were testing printable maps. That’s right, this was at a time when maps were not yet in everyone’s cars or phones and people still printed out maps. Those passionate conversations, that hard effort, those exploratory concepts, innovative research techniques, and insights, all of this was for printable maps. Something that is completely dead now.</p><h3><strong>The death of a product</strong></h3><p>The important lesson I gained from that project is this: your product will someday die.</p><p>Change will come in one form or another. The landscape will change, technology will change, or user behaviors will change. For some products, it may be a slow evolution. Sure a similar product may still exist, but it will evolve and eventually only resemble the product you once worked on. For other products, like printable maps, it will become obsolete right before your eyes. Given enough time the product you are working on now will no longer exist as you know it.</p><p>When it comes to research this makes it very important to develop insights that have a longer <a href="https://medium.com/cheggux/if-time-travel-were-possible-what-would-i-tell-myself-as-a-junior-ux-researcher-30c5dfd7dc70">shelf life</a>. This is why I often try to generate insights that reveal core user needs and behaviors rather than only focusing on short-term recommendations. For example, for the in-car research, we learned a lot about the attention-starved environment and what information was most important to display while navigating. These insights could easily apply to in-car dashboard displays as much as they could to printable directions.</p><p>But let’s be honest, even those insights will also die and fade away. As much as I try to make a longer shelf life for my UX research, there is a shelf life. I don’t have the exact formula, but my guess is that even the most exploratory and generative research project has a shelf life of around 5 years, and for tactical research it is much shorter. While a researcher working on a mapping product today could blow off the dust of one of my old reports for guidance, so much has changed that surely they would do their own foundational research. Even if it were 5 years past a project it would be prudent to validate whether the core needs have changed over time given that the technology has changed.</p><h3><strong>Why is this important?</strong></h3><p>Although I always intuitively understood that working in technology meant playing in a rapidly evolving space, I didn’t completely understand this lesson until I had the benefit of hindsight and actually saw my products die.</p><p>So, what is so valuable about seeing a product die? It lessens any feelings I may have around petty arguments, insecurity, ownership, politics, and other baggage that comes from working in corporate culture. It relaxes me and helps me see the more long-term and big-picture perspective on my work.</p><p>It doesn’t cause a depressing, “what’s the point” mindset. On the contrary, I still see today’s work as critical and I am passionate about the products I work on now as I was back then. I still create great data looking towards long-term value, and I’m enthusiastic about what we are building today to both serve today’s user and as a stepping stone for tomorrow’s. But I do so with the humility of knowing that we are creating something that will die someday.</p><p>Perhaps more importantly, understanding my work/product will die someday has helped me embrace my role as a <a href="https://medium.com/@mark_31534/my-evolution-as-a-user-experience-researcher-632e7cc3d129">Catalyst</a>. While the products will evolve or fade away and the insights will someday become stale and obsolete, the relationships I create with others will last much longer. I know the influence others have had on me has lasted much longer than those dead products. I hope that perhaps the influence I’ve had on others may still resonate long after our product has died and we’ve gone our separate ways.</p><p><em>This writing is part of a series of contemplations in User Experience Research. </em><a href="https://medium.com/@mark_31534/contemplations-in-user-experience-research-1c2aed4e8634"><em>Check out some of the other writings</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a7b82288f50" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>