<?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 Joren Devocht on Medium]]></title>
        <description><![CDATA[Stories by Joren Devocht on Medium]]></description>
        <link>https://medium.com/@jorendevocht?source=rss-33946e37f726------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_h0BxmDeMoAyS_8cJ2C2-A.png</url>
            <title>Stories by Joren Devocht on Medium</title>
            <link>https://medium.com/@jorendevocht?source=rss-33946e37f726------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:38:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jorendevocht/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[The five stages of being the first UX designer at a product company]]></title>
            <link>https://medium.com/tl-eng/the-five-stages-of-being-the-first-ux-designer-at-a-product-company-df694f232bb4?source=rss-33946e37f726------2</link>
            <guid isPermaLink="false">https://medium.com/p/df694f232bb4</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Joren Devocht]]></dc:creator>
            <pubDate>Wed, 01 Dec 2021 13:34:55 GMT</pubDate>
            <atom:updated>2021-12-01T18:08:39.060Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is the story of my own personal experiences at Teamleader, how I found my way and figured out the position of ‘UX’ in the organisation. I first brought this story as a talk at </em><a href="https://www.meetup.com/nl-NL/UX-Ghent/"><em>UX Ghent</em></a><em>.</em></p><figure><img alt="Title" src="https://cdn-images-1.medium.com/max/1024/1*8ioItQz4iTp9yRxSQsdekA.png" /></figure><p>I can tell you about the perfect, theoretical way to do user research in a product company, but believe me… you’ll have read it all before. If not, I can point you to dozens of books and courses that are more than willing to walk you through it for the first time.<br>I can tell you about how we do it at Teamleader, and I will in a later blogpost, but in all honesty: what works for us won’t necessarily be the best approach for you.</p><p>So instead, here is a story about our path to where we are now in the hope that it will help you to avoid the same mistakes and get you there on your own with an approach that works for you, your customers and your company.</p><p>I think you’ve all heard about the five stages of dealing with grief? Bargaining, acceptance etc. This is like that, but totally different. It’s called ‘<em>the five stages of being the first UX designer at a product company</em>’.</p><p>And just like grief, it also starts with denial.</p><h3>1. Denial</h3><p>A bit of personal information to frame this story: when I joined Teamleader I came from an agency. As a consultant I did not fully realise this, but when you come in to ‘fix the problem’, the red carpet is being rolled out for you. You can follow that ideal process you sold in your pitch.</p><figure><img alt="Red carpet" src="https://cdn-images-1.medium.com/max/1024/1*Jx1XjPzjyjKvRspMRDoeLQ.png" /></figure><p>When you go work for a company as a consultant the problem has already been well established (or it should be) and the budget has been allocated for you to come and change things: you pitched a solution and they bought into that.</p><p>Joining a product company on the payroll is different. They hire you for long-term engagement, but not really to uproot the current way of working from day one and you’ll have to figure stuff out as you go along.</p><p>So when I joined Teamleader I was still thinking in that ‘consultancy mindset’, trying to come up with the perfect slide deck to deliver. Thinking I would instil that user-centred design process throughout the organisation in a matter of weeks. This was <em>not</em> the case.</p><h4>So what then?</h4><p>Actually it’s quite simple: just do the design work, sneaking in quick-fire research when possible. I realised quickly that things were moving a lot faster when we were just asking the right questions, rather than trying to get the perfect research track off the ground.<br>If you can do this with a customer, perfect! If not, talk to your customer-facing colleagues. There’s a wealth of information there already. But be patient, don’t try to change the world overnight.</p><h3>2. Existential crisis</h3><p>When you come to the realisation that doing things the way you’ve been used to won’t cut it, you start questioning yourself: What is my role here exactly? What do people expect me to do?<br>Things get especially tricky when there’s an overlap between the role you’re trying to carve out for yourself and already established responsibilities. Most common case: product designers vs product managers.</p><figure><img alt="Product design vs product management" src="https://cdn-images-1.medium.com/max/1024/1*6taJVC1TPBWYwM2K2QUiaA.png" /></figure><p>This is where my ‘survival instinct’ kicked in: I was trying to take as much control as I possibly could over everything even remotely related to user research.<br>Obviously this wasn’t very productive, on the contrary: you’re bound to create friction instead of building trust.</p><blockquote>You’re bound to create friction instead of building trust.</blockquote><h4>What we ended up doing</h4><p>A better person than me would have taken the time to take stock of current practices and leverage those instead swooping in and taking over, but that wasn’t me. Through trial and error I learnt to take a more supportive role: propose to do things together and pair up. That way you can introduce some user-centred methodologies along the way, and learn a thing or two yourself.</p><p>Together we started conducting customer interviews, put together customer journey maps and organised workshops. All great things, but it wasn’t scalable. I still tried following up or facilitating every research track myself. And that kept snowballing until I had no other choice than… <em>letting go</em>.</p><h3>3. Letting go</h3><p>You can only stretch yourself so far before something has to give. There’s no such thing as the ‘<em>super hero designer</em>’, you’re just human like everyone else.</p><blockquote>There’s no such thing as the <strong><em>super hero designer</em></strong><em>,</em> you’re just human like everyone else.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MPjfhTK4mYVVCZhL-4CG6A.png" /></figure><p>Once that realisation sinks in, I did what you read in every management book, hear in every design talk and get told by everyone around you but still manage to forget in the moment (read: purposefully ignore because you think you can make it work).</p><p><em>I focused.</em><br>I chose my ‘favourites’: I put the majority of my time into the projects that I believed would provide the most value to our organisation, the projects where I could make the difference as a designer. Not the projects where the only design contribution would be applying our component library to a technical refactor, but the projects were we changed entire flows and we had yet to better understand our customers.</p><h4>There’s more</h4><p>Start by working on the most impactful projects, but don’t stop there. Because I documented my approach and shared it with stakeholders, they started to develop a user-centred mindset of their own. This not only gave the design team some visibility and created understanding for our way of working, it also spread some of the weight of the process because as you know: many hands make light work.</p><p>Alright! I was building momentum. People, even outside of the product, engineering and design team, were starting to grasp the fundamentals of user-centred design. I introduced methodologies, tools and processes. Awesome, right?<br>Well, yes… but also sometimes, no. UX evolved to be no longer property of the product design team. Now everyone had an opinion about design and people started throwing around phrases they heard designers use. All of sudden you heard people throughout the organisation talk about ‘<em>expected behaviour</em>’, the customer’s ‘<em>mental model</em>’ and ‘<em>too many clicks</em>’.</p><p>This meant we were entering the ‘Spartacus’ stage.</p><h3>4. Spartacus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dQaGIVcaG6abWtDVK7CFDg.png" /></figure><p>Because everyone now had an opinion about design, I was no longer fighting to get recognition for a user-centred approach. Now I had to manage multiple cooks in the kitchen and more often than not it felt like ‘too many cooks’.</p><p>Instinctively I felt like tackling this in one of two ways:</p><p><strong>1.</strong> Do nothing and let people think about user research and user-centred design in their own way ,while we would continue doing our own thing. <strong>Problem:</strong> In the long-term this would have eroded the value(s) of UX design and we would have to prove ourselves again as people would get burned out on ‘<em>doing UX</em>’.</p><p><strong>2.</strong> Start correcting everyone. We could have meddled in every track that uses one of ‘our’ user research techniques. <strong>Problem:</strong> Before you know it we would have been back at stage 2, but at an even larger scale.</p><h4>But instead</h4><p>Luckily, what we did is: involve them (sounds familiar?).<br> Don’t try to prove them wrong or correct them. You’ll spend all your time doing that, you won’t make yourself popular and you definitely won’t have the impact you’d like to have. Invite your colleagues to interviews so they can see what you see, take their feedback to heart so you can find a common goal to use as a ‘shared language’ and work on solutions together.</p><p>We introduced ‘project teams’ at Teamleader to do exactly that. They’re groups of representatives of all departments within Teamleader that follow along (and partake in) the product delivery process: from research all the way to release. By doing this, those internal stakeholders are aware of what drives our decisions and they have the opportunity to weigh in on the decision making process.</p><h3>5. Trust</h3><p>That brings us to the fifth and final stage. The one that we’re in now at Teamleader. The one we’re still figuring out… <em>trust</em>. Kind of self-explanatory, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s9OShumUq31WB0swCPp6pQ.png" /></figure><p>Allow me to elaborate one last time. Because it’s important to note that we definitely haven’t figured everything out, our process isn’t perfect and we’re still regularly faced with challenges. This is a dynamic, continuous process. As I write this down, I’m already thinking about adding a new step… but that’s for another blogpost.</p><p>For now, we’ve reached a place that works for us. A healthy foundation to build upon. People understand what user-centred design means and appreciate the value it brings, we’ve found a way to involve colleagues from the entire organisation and we’re learning as we go…</p><p>Now go on, make your own mistakes, learn from them and please share your insights with the rest of us!</p><p><em>Intrigued by our journey towards a more user-centred culture at Teamleader? Curious how things are now? Don’t hesitate and reach out to </em><a href="/service/mailto:joren@teamleader.eu"><em>joren@teamleader.eu</em></a><em>, we’re hiring!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df694f232bb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tl-eng/the-five-stages-of-being-the-first-ux-designer-at-a-product-company-df694f232bb4">The five stages of being the first UX designer at a product company</a> was originally published in <a href="https://medium.com/tl-eng">Teamleader PED</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>