<?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 Eduardo Ulrich on Medium]]></title>
        <description><![CDATA[Stories by Eduardo Ulrich on Medium]]></description>
        <link>https://medium.com/@eduardo.ulrich?source=rss-a57329c89dcb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*55DG2qYDEpe2hzG4mYdXYQ.png</url>
            <title>Stories by Eduardo Ulrich on Medium</title>
            <link>https://medium.com/@eduardo.ulrich?source=rss-a57329c89dcb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:42:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eduardo.ulrich/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[AI as Your Research Sidekick]]></title>
            <link>https://medium.com/design-bootcamp/ai-as-your-research-sidekick-0ca5e1e09f9d?source=rss-a57329c89dcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ca5e1e09f9d</guid>
            <category><![CDATA[customer-centricity]]></category>
            <category><![CDATA[notebooklm]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[research-democratization]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Eduardo Ulrich]]></dc:creator>
            <pubDate>Sat, 28 Mar 2026 12:56:00 GMT</pubDate>
            <atom:updated>2026-03-29T13:09:00.732Z</atom:updated>
            <content:encoded><![CDATA[<p>Adventures in research part 2</p><figure><img alt="A human with glasses sitting at a desk, writing on a computer from which cryptic symbols rise (it’s trying to symbolize AI in an artistic manner but it might be failing completely…who knows?)" src="https://cdn-images-1.medium.com/max/928/1*fHCbMYajL65n6PfwTwWtnQ.png" /></figure><p>Ah…Researchers. We have a calm and collected life, where everything is planned, meetings are booked weeks in advance, users show up on time, and we never get any surprises. It’s the most Swiss job of jobs… right? So this is why we try new things, why we get a little adventurous, we throw some chaos in there, not because we need to figure out how on earth to get through an everest of discovery and validation while being a solo band, but because we have the time…heh.</p><p>So Democratization had started, every 2 weeks I was reaching out to people to get questions, editing scripts, fine tuning the screener to get relevant users, calling them, being called a scammer, or just being rudely treated on the phone (call center workers, you have a place in heaven I swear), and then hunting down moderators. This while simply running my other projects and interviews. I was the picture of sanity in a burning house. So I needed to figure how to optimize, the pressure was there, so time to turn the coal into a diamond.</p><p>We were getting insights, I had participants, Moderators and expanded to 3 markets. I didn’t have time to write a report every 2 weeks (I tried…unsustainable). Also tried an actionable report, but it was also a bit meh…it shared conclusions but the users weren’t coming through. Luckily, we live in the future, and at work we had an internal AI that had a new beta feature called Spaces.</p><h3>The first attempt (Or: Vibe coding my way out of a pain in the b…ehind)</h3><p>The company had an internal AI tool that was honestly a great start. It had a clean way to create patterns from qualitative data and the interface made sense. I used it as a repository for the democratized sessions, it allowed us to read insights, though in it’s early days it was a tad slow and prone to hallucinate (1 casual mention of an issue magically turns into the biggest issue a user faces).</p><p>Then we hit 20 sessions. The tool had a limit of 15 files. Not being one to give up without a fight I did what any non-technical researcher with a deadline and a ChatGPT subscription does: I vibe coded my way out of the problem. With ChatGPT’s help, I cobbled together a mini workflow that went through all the audio files in a folder, transcribed them using Whisper, and wrote everything to a single file , always adding a header with the date, a unique user’s name (GDPR compliant), and the country they participated from.</p><p>It worked. It was held together with digital duct tape, but it worked.</p><p>Until I changed computers.</p><p><em>(OK…let me make this clear…I did not migrate it properly. I know. Totally my bad.)</em></p><p>Adding newer sessions was a pain, it broke, and remembering how I created the “cataloguer” while drowning in a work tsunami left me with no motivation to fix it quickly nor did I have the time. I needed something that wasn’t too hacky and was sharable without a mountain of instructions to get it up and running.</p><h3>Notebooklm to the rescue!</h3><p>I had been testing NotebookLM in beta. It was interesting , you could upload documents and ask questions, which helped with analysis, it made documents dynamic and allowed me to think of things from different angles. But when they released the “Audio Overview” I could hear angels sing.</p><p>When I listened to that first AI-generated podcast about our own research I had a laughing fit. It genuinely felt like the world took a step in the right direction. I mean…</p><p>Two hosts. Chitchatting. About our customers. The exact pain points we had just covered the day before. For 10 minutes.</p><p>I had been wanting to make something like this for ages, heck, creating a podcast was one of my personal goals for that quarter. I saw it as a way to get research findings to people who would never open a report, and we make pretty ones with images. But between running sessions, onboarding moderators, writing scripts, and babysitting Murphy’s law, I had never found the time or sanity.</p><p>And here it was. Done. In minutes.</p><h3>Reaching the unreachable</h3><p>The first few podcasts took about an afternoon to get right. In the early days, you could only write a short prompt, so I had to iterate a few times and it took a while , hallucinations, misinterpretations, weird tangents (leather car seats…3 minutes about those amazing leather car seats????). I redid them three, four, sometimes 5 times. It was a miracle it existed but it still took time and triple checking.</p><p>But then, as all things AI do, it evolved, new features were added, the prompt context expanded, NotebookLM got better.</p><p>When I shared the first podcast, everyone was asking where on earth was this coming from, so it got the conversation started (yes even with the lovely humans keeping our platforms safe).</p><p>Everyone was blown away.</p><p>Then the PMs started chiming in. One had listened on the way home from work. Another had played it while walking their dog. People I had no idea would ever click on a research output were suddenly talking about customer problems in the hallways based on fresh research..</p><p>This was the ROI I had been struggling to find. Not a metric or a slide…A medium that people actually paid attention to because it didn’t feel like work.</p><blockquote><strong><em>Research findings were reaching people I had never managed to reach before. And they were doing it on the commute home.</em></strong></blockquote><h3>The actual workflow (no magic, just process)</h3><p>Once I discovered NotebookLM could handle up to 300 documents in our enterprise account, I migrated everything , all the transcripts from Userzoom, organized with headers for date, name, and country. No more broken scripts. No more manual stitching.</p><p>The setup now works like this:</p><p>I maintain a main User Days repository in NotebookLM with all sessions accumulated over time. Every new session, I upload the fresh transcripts and create a separate focused notebook just for that session , this is where moderators can go in and ask their own questions directly, immediately after the session while it’s still fresh, saving on notetaking and helping keep hallucinations in check.</p><p>For each session, I ask NotebookLM to answer the main research questions we had , which I know well, since I wrote the script. I check the answers against my own observations from watching the sessions live, which is where the human part still matters enormously. I know what sounded right in the room. I know what was a one-off comment versus a recurring theme.</p><p>Then I ask it to generate the podcast. I always include one specific instruction: thank the moderators by name. And it does , beautifully, naturally, in a way that makes people feel genuinely seen. These days I also ask it to generate a short video as a teaser, which has become its own little moment of anticipation after each session.</p><h3>The Surprise: Segmentation at Scale</h3><p>The moment that genuinely surprised me was when we started looking at user segmentation.</p><p>With around 100 sessions loaded into the repository, I asked NotebookLM to suggest user segments. It didn’t give me demographics. It gave me segments anchored in actual use cases , how people were using the platform, what they were trying to achieve, where they kept hitting the same walls.</p><p>Patterns I would have needed weeks to surface manually were sitting there, organized and cross-referenced, in minutes.</p><p>Now, full transparency: this data has bias baked in. Our users are recruited with specific profiles that we are looking to learn from and how they interact with the platform based on their context. There are blindspots, and I know where they are. But as a foundation for segmentation thinking, as a way to generate hypotheses and challenge assumptions , it was remarkable.</p><h3>PM’S and dog walks</h3><p>The democratization effort from Part 1 had a hidden cost: the more people participated, the more data we generated, and the harder it became for one researcher to make sense of all of it.</p><p>AI didn’t solve the human problem of getting people to care about users. We solved that with popcorn and persistence and PM’s who walked their dog while listening to a podcast about customer pain points.</p><p>What AI solved was the scale problem. The 2-hour synthesis sessions were gone. The erratic observer notes mattered less because the transcript was the ground truth. The insights reached people I couldn’t have reached manually , a data analyst on their lunch break, a PM on the evening commute, a FE magician who would never dream of opening a 20-slide report now can happily listen to 10 minutes of two hosts talking about real users, and the insights are not frozen in time, they are clustered to detect patterns over time, evolution of challenges, they stay relevant.</p><p>And because analysis got faster, we ran more sessions. More sessions meant more data. More data meant better segmentation, richer patterns, faster answers to questions that used to take quarters to answer.</p><blockquote><strong>It compounded. In a good way.</strong></blockquote><h3>A Note on Tools and Trust</h3><p>If you’re a researcher considering this: the tool will fail you sometimes. The hallucinations will be frustrating (though they have gotten wayyy better). The first attempts will take longer than you expect. The prompts will take some time to get right for your use case.</p><p>But the moment someone from a team you’d never reached before mentions something a user said , something they heard on a podcast, on their walk home, that you generated in an afternoon , you’ll understand why it’s worth the learning curve.</p><p>Over time you will rack up an imense amount of insights that will allow you to be quicker to answer what are the core issues plaguing customers, as well as understand where you lack information, and this allows you to be proactive in your research. You can look at the areas least understood and enrich your product, solve an invisible customer issue, help others understand what wasn’t adding up and, at the end of the day help people.</p><p>You’re not being replaced. You’re being amplified.</p><blockquote><strong>The insights were always there. Now they travel further, and you can look deeper and broader.</strong></blockquote><h3>TL;DR: A little recipe for you to try</h3><p><strong>Step 0</strong>: Run good sessions and record them (AI amplify’s what’s there, it can’t invent what isn’t)<br><strong>Step 1</strong>: Grab the transcripts from the session and upload them to Notebooklm<br><strong>Step 2</strong> : Click on Audio<br><strong>Step 3</strong> : Write down the main focus of the research, the main questions you wanted to answer, the surprises, a few quotes, and if it was a democratized initiative, ask it to thank each of the moderators by name (it does it very well and it makes it much more personal).<br><strong>Step 4</strong> : Listen, iterate, perfect the prompt, triple check that it lines up with what you heard (there is enough slop out there)<br><strong>Step 5</strong>: Share and enjoy</p><p>• • •</p><p><strong>Up Next: Part 3 , Ghost in the Machine</strong></p><p><em>So as research democratizes, and AI complements research, I started thinking (and digressing), where will research fit in this future ?<br> So Join me when I (eventually) share my 2 cents on what I believe research can look like in a world that is ever increasing it’s speed (to be fair, it will probably be outdated as soon as I share it, but I’m still going to give it a shot anyway).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ca5e1e09f9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ai-as-your-research-sidekick-0ca5e1e09f9d">AI as Your Research Sidekick</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Learned to Stop Worrying and Trust the Chaos (or just “Democratizing Research”)]]></title>
            <link>https://medium.com/design-bootcamp/how-i-learned-to-stop-worrying-and-trust-the-chaos-or-just-democratizing-research-3f138ccc1164?source=rss-a57329c89dcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f138ccc1164</guid>
            <category><![CDATA[research-democratization]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Eduardo Ulrich]]></dc:creator>
            <pubDate>Sat, 14 Mar 2026 12:23:05 GMT</pubDate>
            <atom:updated>2026-03-22T17:05:32.242Z</atom:updated>
            <content:encoded><![CDATA[<h4>Adventures in Research, part 1 of 4 (err…maybe)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MRbw47Kk0EJ3Jckef8n0jw.png" /><figcaption>Image <em>obviously</em> made with nano banana 2 (there is a sentence I didn’t think I would write today)</figcaption></figure><p><em>Imagine you walk into an office and there’s a schedule on a table next to a TV. There’s popcorn. Free popcorn. And if you sit down, you get to watch real people struggle with your product in real-time.</em></p><p>This was not a team-building exercise. This was not ‘fun Friday.’ This was my colleague’s solution to a problem we faced at the time. Back then research was something stakeholders asked for, not participated in. The users existed in reports and data but nobody in the company actually talked to customers, even though (as it turned out)they desperately wanted to, even if they didn’t know it yet.</p><p>J. had been experimenting with different formats, popcorn sessions, card sorting exercises,trying to get people to listen instead of just reading reports.</p><p>When he became my manager, I inherited the popcorn initiative. I also inherited the skeleton of something that would make me dig deep, wear many hats, redefine what sanity means to me and spend many hours thinking how can I get people to show up??</p><p>Then out of nowhere the layoffs happened, my manager was gone, and I inherited a lot more than popcorn.</p><h3>The First Volunteer (sort of)</h3><p>The early sessions were… let’s call them ‘character-building.’</p><p>I’d recruit the participants myself, screener on the platform, call the people who signed up, be accused of being a scammer, repeat the explanation 7.5 times to get 3 amazing participants. I’d beg Product teams to send questions. I’d cram a 30-minute crash course in ‘please don’t ask leading questions/have you met usezoom’ before we went live. Fun times.</p><p>And then I’d moderate two of the three sessions myself, only one person would volunteer.</p><h3>It Just Takes One (and a hell of a lot of luck)</h3><p>In the first sessions I had 1 Project Manager that had just joined my side of the track in motors, and she volunteered as she thought it was a great way to get to know the customers (yes these people exist). She was nervous, she sped through the session, but she made it, and had fun. She spread the word, and slowly I started to get regulars.</p><p>That’s when I knew something was shifting. It wasn’t immediate love. It was more like: Oh. This is actually hard. And relevant/worth my time.</p><p>The momentum didn’t flood in…it trickled. Slowly, PMs started asking if they could moderate. Designers started showing up without being reminded. Someone suggested a leaderboard (gamification ftw!!). We started doing shout-outs in all-hands meetings, which was quite surprising how it actually worked, people like being recognized for doing hard things…who knew?</p><p>And then one day, I was in a meeting with Markets and PM’s and a PM just… casually quoted a user. Not me. Not the research report. The user they’d personally talked to three weeks earlier.</p><p>Other PMs chimed in. They referenced specific flows. They talked about pain points like they’d been there.</p><p>I just sat there grinning like an idiot. It had been roughly a year since we started, and this, was the thing I’d been hoping for without knowing how to ask for it.</p><h3>From Portugal with love</h3><p>Once the format stabilized in Portugal, we began expanding to our other markets. Sessions started running in English. Different markets. Different cultural contexts. More complexity. More risk.</p><p>We also expanded from 3 sessions to 5 sessions in 1 day every 2 weeks, rotating between markets, and of course we did it gradually and not from one month to the next…yup…totally like that…no rush in product…ever…</p><p>The reality is that by then, something fundamental had shifted: research wasn’t something stakeholders read about in a report, they were an active part of it.</p><p>Empathy and respect for our craft grew, moderators had to deal with people in less than happy moods, with no-shows, with people who said they were one type of customer but in the end it was their second cousin’s mother’s aunt who was buying a car but they couldn’t attend. They also understood why when we do 5 interviews in one day we couldn’t tackle that survey and be in 4 other meetings.</p><h3>The Beautiful Chaos</h3><p>It wasn’t a sea of roses. Juggling this with other projects was at times insane. I’d ask everyone for questions, add them to the script, onboard first-time moderators, and be there in the sessions to support them. I’d help them with their nerves, deal with the cranky user who pops up in his bathrobe and forgot about the session, mitigate biased questions, and make sure they get through it.</p><p><em>(Murphy’s law, I can now confirm, is one of the governing forces of the universe.)</em></p><p>I look back at the chaos of these times, happy they have passed but also amazed how it grew in these almost 3 years (and counting). The reality is that if it wasn’t for having these sessions I wouldn’t have been able to run so many projects. Since the research team became smaller, and later just me, we trained our own in-house researchers.</p><p>Having the head of consumers seeing the need for this initiative, pushing me to expand as well as supporting me by reaching out to his team and giving me a spot at certain all hands made all the difference, and very likely determined the success of this initiative.</p><p>At the end of the day, from the user sessions, we gained something far more valuable than insights alone: shared language, shared context, and a growing sense of ownership over customer problems across Product.</p><blockquote><strong>Democratization didn’t make research weaker. It made it inevitable.</strong></blockquote><h3>A Note for Researchers in Tough Moments</h3><p>If you’re a researcher reading this while your team is shrinking, budgets are tightening, or expectations are rising, this part is for you.</p><p>Since I started user days there were 2 rounds of lay-offs (the latest turning me into the sole Researcher in Motors). This system allowed me to keep the ball moving, keep our customers at the center and keep moving fast, but like I said, I am lucky because I don’t have to convince anyone that research is important, just need to remove as much entropy as possible so it can flow and focus on getting insights fast.</p><p>Invite. Share. Trust. Let go (a little) and try to <strong>enjoy it</strong>.</p><p>We are researchers, we are by nature people who love to learn from others, who listen to their struggles and are good at converting needs to product road map items, making sure the product is human centered.</p><blockquote><strong>We are not the source of truth, we make sure it gets to the right people</strong></blockquote><h3>TL;DR: How to Democratize Without Losing Your Mind</h3><ul><li><strong>Broadcast the Chaos:</strong> Don’t just run sessions; make them an event. Set a schedule, grab the popcorn, and invite the whole office to watch the “beautiful chaos” of real user struggles in real-time.</li><li><strong>End-to-End Visibility:</strong> Structure interviews so every department (from Engineering to Marketing) can see a piece of their world reflected in the session.</li><li><strong>Crowdsource the Script:</strong> Beg (or professionally nudge) Product teams to submit their own questions. When they see their specific curiosity addressed, they stop being observers and start being stakeholders.</li><li><strong>The “Nudge” to Moderate:</strong> Challenge PMs and Designers to take the mic. Even if they’re nervous or speed through it, the firsthand experience of a “cranky user in a bathrobe” builds more empathy than any 50-page report ever could.</li><li><strong>Find a High-Level Champion:</strong> Getting a “Head of” to push the initiative and grant you “All-Hands” stage time is often the literal difference between success and a quiet rollout.</li><li><strong>Publicity is the Best Reward:</strong> Use leaderboards, shout-outs, and public recognition. People are surprisingly motivated by being seen doing “hard things”.</li><li><strong>Breathe and Let Go:</strong> You aren’t the sole source of truth; you are the facilitator. Remove the entropy, trust the process, and try to actually enjoy the ride.</li></ul><p><strong>Up next</strong></p><p>So, great…a Lot of interviews are happening, pm’s and designers are talking to our customers, but how on earth do we keep track of this?</p><p>How can we keep it relevant? What on earth do we do with all the information we’re capturing?</p><p>Join me in the next iteration of <strong>Adventures in Research </strong>to hear how AI came to our rescue in the Information avalanche</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f138ccc1164" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-i-learned-to-stop-worrying-and-trust-the-chaos-or-just-democratizing-research-3f138ccc1164">How I Learned to Stop Worrying and Trust the Chaos (or just “Democratizing Research”)</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Projective techniques in design research]]></title>
            <link>https://uxdesign.cc/projective-techniques-in-design-research-c41e630c8338?source=rss-a57329c89dcb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c41e630c8338</guid>
            <category><![CDATA[projective-techniques]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Eduardo Ulrich]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 16:00:12 GMT</pubDate>
            <atom:updated>2021-02-06T10:28:16.445Z</atom:updated>
            <content:encoded><![CDATA[<h4>Brief context, definition and how to use them.</h4><p><em>This article was co-written with </em><a href="https://medium.com/u/fae6f7fa7758"><em>Heitor Pagliari</em></a></p><p>Before we start talking about how fun projective techniques are and how to use them to get into your participants most hidden thoughts, let’s start with a crash course on basic psychology:</p><figure><img alt="Classic black and white image of Sigmund Freud smoking a cigar looking very serious at the camera" src="https://cdn-images-1.medium.com/max/1024/1*HfEz4Q3t3bPaABKRpg8KMQ.jpeg" /><figcaption>Halberstadt, Max (c. 1921)</figcaption></figure><h3><strong>FREUD IN 5 MINUTES</strong></h3><p>So it all started* with Sigmund Freud (I bet his friends called him Ziggy) father of psychology and everyone’s angry uncle.</p><p>Besides all the creepy scandals and making us think that our dreams are all about weird sex, he gave us a new way to think about who we are and how we feel.</p><p><em>*Yes, there were others before him and many after, but for today’s purposes let’s just call this “the beginning” or otherwise we will never get to the main part.</em></p><p>He told us that our minds are composed of 3 levels: The Conscious, the Preconscious and the Unconscious.</p><p>You can read more about it <a href="https://www.simplypsychology.org/unconscious-mind.html">here</a>, but the key message is that the Conscious mind is the one that processes all the thoughts and feelings that we are aware of.</p><p>The Preconscious is where our memory resides, where we keep the information that we need quick access to.</p><p>And the Unconscious mind is a storage for all the thoughts, feelings and memories that we are not aware of — usually things that we try to hide without realising it, like unpleasant or unacceptable thoughts.</p><p>Making it more visual, the Conscious mind is the tip of the iceberg and the Unconscious mind is everything hidden in that cold dark water.</p><p>Freud also divided our personalities in 3: the ID, the Ego and the Superego.</p><p>The ID, is our raw brutal selves, where all our natural urges live — like hunger, anger, excitement and desire (it’s Freud, so there’s obviously sex involved).</p><p>Just imagine all of these without any control…</p><p>Then we have the Ego. This is the part of our personality that interacts with society, grows and adapts based on morality and conventions.</p><p>Now to balance these two out we have the Superego that dilutes the raw impulses that come through, but only enough so that the Ego can control it.</p><p>This is simplifying the crap out of this, but you got the idea, right?</p><h3><strong>Theory is fine, but how does this work in practice?</strong></h3><p>Imagine someone pisses you off tremendously at work. Later that night you’re falling asleep on your comfortable bed and start to dream.</p><p>On the ID level, you feel like destroying the person that pissed you off. But since this is not good for you or society, your Superego will create a more acceptable scene in your mind.</p><p>So instead of the image of you hurting this person, you’ll repress this urge and instead you might dream of your office enemy surrounded by angry farting cats.</p><p>Too specific, we know, we will handle this in therapy later.</p><p>When you wake up, you only remember that you had a pretty crazy dream about cats for no apparent reason. This happened because your Superego blocked those unacceptable thoughts from your mind and hid them in a place that you can’t reach (your Subconscious).</p><p>So recapping to make sure we got it: your ID had an urge to do something that was not acceptable for your moral standards. In response to that, the Superego repressed this thought and hid it into your Subconscious so you don’t have to face this unpleasant side of yourself.</p><p>Of course this isn’t always perfect, and even Freud recognized some flaws in this process. But the key point is that our minds always seek balance to protect ourselves, and they have mechanisms to help them with this.</p><p>And one of those mechanisms is Projection (ta-da, we finally got here)!</p><figure><img alt="An image of a colourful inkblot with pink, blue and orange  that may look like a butterfly" src="https://cdn-images-1.medium.com/max/689/1*tvRAdKPDJO-eOqgPlk3rCw.jpeg" /></figure><h3><strong>FANCY STUFF, BUT CAN YOU PLEASE TELL ME NOW WHAT THE HECK IS A PROJECTIVE TECHNIQUE AND WHAT TO DO WITH IT?</strong></h3><p>Psychology found out that certain human behaviours could be better understood by accessing those thoughts and emotions hidden in our Subconscious.</p><p>And Projective Techniques helps us with exactly that:</p><p>By exposing a person to a neutral stimulus (an image, a sound, a word, an object), we can invite them to make associations between their thoughts and that stimulus. This provides us a way to interpret and better understand what’s going on in their heads and why they behave in a certain way.<br>It’s about giving people a tool that they can use to give shape to their thoughts and emotions!</p><p>Actually, we do this Projection stuff all the time without realising it.</p><p>Remember your office enemy from the previous example? The whole situation might have started because they gave you feedback on your work and you misinterpreted it as an insult just by the tone they used.</p><p>In reality, what happened is that you usually use that kind of tone when you’re mad at someone, so when it was used on you, you just assumed it meant the same thing.</p><p>Projective Techniques can be a wonderful tool to have in your design &amp; research toolkit, especially if you’re working on some deep or delicate topics.</p><p>Experiences involve emotions, and it’s not always easy to talk about the emotions that an experience makes you feel.</p><p>Imagine the situation: you walk into a room, or connect through zoom to a perfect stranger that wants to interview you. They start asking you questions about what you think about a product, how was your day, what you do in your life and your dreams for the future.</p><p>If you had a bad experience with the product and are afraid to offend who built it or are just having a bad day, you’re probably feeling tense by now and not painting a real picture of your feelings — and this is not an ideal scenario for any kind of research.</p><p>What usually happens in these situations is that we lose our capacity to elaborate emotions comfortably since we don’t like to be vulnerable in front of strangers.</p><p>By using projective techniques we help people to lower their guard and open themselves to us without feeling threatened.</p><h3><strong>COMMON TYPES OF PROJECTIVE TECHNIQUES IN DESIGN RESEARCH:</strong></h3><h3><strong>Word Association</strong></h3><p><strong>What it is</strong>: A simple enabling exercise where we suggest words participants can associate in any way with topics relevant to the research, such as a brand or activity.</p><p><strong>What to expect from it: </strong>Finding the right words in a research interview can be hard, this technique gives participants vocabulary to better express themselves.<br><strong>A real example:<br></strong>A startup incubator wanted to identify the challenges that small entrepreneurs faced when starting this new path in their lives and how to better support them.</p><p>This was an overwhelming moment in those people’s lives: they had to learn a lot of different things, they were full of doubts and insecurities, they had a hurricane of feelings and emotions going through their minds. And it was extremely difficult for them to rationalize all of this.</p><p>So to help them articulate their thoughts in a more organized way, we presented a list of words — feelings like fear, joy, excitement and regret but also events like lack of money, family support and issues with bureaucracy — and asked them to choose the ones that best reflected their current moment.</p><p>Those words were then used as conversation prompts to guide the rest of the interview and deep-dive into specific topics.</p><h3><strong>Picture sorting</strong></h3><p><strong>What it is: </strong>The participant sorts through images (ideally neutral images) and identifies the ones that best represent an emotion or thought around a specific topic.</p><p><strong>What to expect from it</strong>: By giving participants a non verbal stimulus it helps them to verbalize their thoughts in a more abstract (and oftentimes easier) way.</p><p><strong>A real example:<br></strong>The journey of buying a car is an emotional rollercoaster full of ups and downs. But when we were interviewing people on that topic and asked them about it, they were always very focused on the rational part of the process: “I felt happy because I found a good car” or “I felt angry because the price was too high”.</p><p>To go deeper into their feelings and understand all those emotional nuances, we gave participants a set of Dixit cards (a card game where you need to match surrealist images with words) and asked them to choose the card that best represented how they felt in some specific situations.</p><p>This allowed us to understand what were the moments with the heaviest emotional burden (both positive and negative) and what we could do to minimize or potencialize them.</p><h3><strong>Third Person</strong></h3><p><strong>What it is:</strong> A technique where participants are asked to suggest how they think other people would feel and behave in a certain situation.</p><p><strong>What to expect from it:</strong> By explaining the problem from another point of view, the participant feels less guilty about pointing out potential problems and oportunities</p><p><strong>A real example:<br></strong>A new product recommendation feature for a fashion e-commerce was implemented but the number of users trying it was lower than expected. We decided to run some usability tests and, at the end of the session, asked the participants how they thought other users would use/feel about this new tool.</p><p>When they were testing it, most participants kept praising the feature and complimenting how practical and accurate the recommendations were for their personal style.</p><p>But when they started talking about a third person (the supposed “other users”, a.k.a. a projection of themselves) that’s when we learned something quite interesting:</p><p>In their point of view, “other users” like to use fashion e-commerce as a tool to fantasise about new styles and explore possibilities, and the recommendation tool didn’t allow this behaviour.</p><h3><strong>Brand Personification</strong></h3><p><strong>What it is: </strong>In this technique we ask people to think about inanimate things (products or brands, for example) as if they were people and describe how those things would act, think and feel in certain situations.</p><p><strong>What to expect from it:</strong> A description of how participant actually perceive this product or brand.<br><strong>A real example:<br></strong>When working on a project for a bank, we were trying to understand how people with money debts handled their personal finances. It was a very delicate topic and most of the research participants were feeling ashamed/not comfortable to talk about it.</p><p>So after a couple sessions we chose a different approach and, instead of asking about their situation directly, we changed it to: “If your bank account could talk, what would it tell us about you?”</p><p>The result was a way more lighter conversation about the topic where people shared funny anecdotes and some deep struggles that they faced to manage their finances.</p><p>This happened because we changed the focus of the conversation to an object (in this case, the bank account) and people were projecting their feelings and behaviours to it.</p><h3><strong>Drawing</strong></h3><p><strong>What it is:</strong> Drawing is an amazing technique as it usually gets participants out of their comfort zone. We ask people to draw something (a situation, an object, a feeling) and then use the drawing to explore it in more depth — it’s not about the drawing itself but what it represents to the participant.</p><p><strong>What to expect from it: </strong>When we draw we use other parts of our brain (and yes everyone says they can’t draw) that allows us to express things that we are not always aware of.</p><p><strong>A real example:<br></strong>When doing some research on urban mobility, we asked people to draw four words: Living, Transportation, Working and Recreation.</p><p>This allowed us to better understand the context of each participant and how they subconsciously perceived these moments of their day.</p><p>For example, one participant drew a packed bus on the Transportation part, while the other drew a car sharing app.</p><p>There are other projective techniques out there and we really encourage you to try them out to get better insights from your research.</p><p><strong>But here are some words of advice:</strong></p><ul><li>When using a Projective technique that requires a predefined set of stimulus (images or words, for example) be careful to not choose things that are too specific or that can be leading.</li><li>Projective techniques are great for in-depth interviews, especially on complex topics. But they can be an overkill for simple stuff. Assess the value that it can bring to your project before deciding to use it.</li><li>Some people can get VERY uncomfortable with this type of activity. Always have a plan B or be prepared to skip it if you feel that it’s getting awkward (read the room, people)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*Qwqw8BkFeeTOqT0e" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c41e630c8338" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/projective-techniques-in-design-research-c41e630c8338">Projective techniques in design research</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>