<?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 Helen Arvanitopoulos on Medium]]></title>
        <description><![CDATA[Stories by Helen Arvanitopoulos on Medium]]></description>
        <link>https://medium.com/@helenarvan?source=rss-720fb3cdf7c9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0AKLIsxJy2R5_1ptlcX5KA.png</url>
            <title>Stories by Helen Arvanitopoulos on Medium</title>
            <link>https://medium.com/@helenarvan?source=rss-720fb3cdf7c9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:12:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@helenarvan/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 Squad is the Strategy]]></title>
            <link>https://helenarvan.medium.com/the-squad-is-the-strategy-ce8e32882249?source=rss-720fb3cdf7c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce8e32882249</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Helen Arvanitopoulos]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 17:44:15 GMT</pubDate>
            <atom:updated>2026-10-11T17:47:51.861Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*h3obVJGtZAa3dr3SFisUmA.png" /></figure><h3>I think in elevens</h3><p>Every time I build a team, I end up talking about football.</p><p>It happens in hiring conversations, in planning sessions, in one-to-ones. Someone asks what the team needs and I start describing a squad: who plays where, who covers whom, where we’re thin, where we’re carrying someone. Eleven core players. A bench. A manager trying to make it all work on a Saturday afternoon.</p><p>I’m a Manchester United supporter, the travelling kind. Sir Alex Ferguson is my idol, not for the trophies, but for how he built teams that won them. I’ve read his books and listened to him talk about leadership more times than I can count. He’s the kind of leader I want to be.</p><p>I’m a design director at a large, long-established company. I love building teams. And the longer I do it, the more convinced I am of something football fans know instinctively: <strong>great players aren’t enough. The environment decides whether talent performs.</strong></p><p>This piece is about both halves of that — how I build a squad, and what it takes for a squad to thrive.</p><h3>Know your players</h3><p>Ferguson’s philosophy started with people, not tactics. He made it his business to know his players properly — where they came from, their families, what drove them, what rattled them. Not as a nice-to-have, but because it told him how to get the best out of each one. Some needed an arm around the shoulder. Some needed the hairdryer.</p><p>I bring that into hiring. When I meet a candidate, the portfolio tells me what they’ve done. The conversation needs to tell me who they are: their roots, what shaped them, what they’re proud of, what they’re running from, what kind of week makes them come alive.</p><p>That isn’t about being nosy. It’s about fit, in both directions. A brilliant designer in the wrong role, with the wrong manager, in the wrong rhythm, will look average. The same person in the right setup will look like a signing of the season.</p><p>The best team I’ve ever built was at Decathlon Digital. I ran the hiring from scratch: eight roles across senior product design and research, from screening through hiring manager interviews to portfolio walkthroughs.</p><p>What made the difference wasn’t the process. It was time and context. I’d had time to learn the business and see what it actually needed, so I knew what I was building. And I had time with the candidates — two or three conversations each, enough to understand their personalities and expertise, where they’d fit, and how they’d work with each other. I wasn’t hiring eight individuals. I was picking a squad.</p><p>To this day, people from that team tell me it’s one of the best they’ve ever worked in. They ask how I managed to get them together, because they worked as one. They had each other’s backs. It was a safe space, built on trust and real relationships. Not a group of designers — a team.</p><h3>Walking into a new club</h3><p>A new manager doesn’t get to pick the squad on day one. They inherit one.</p><p>The same is true when you join as a director. In the first few weeks you start to see the gaps: where design maturity is high and where it barely exists, which capabilities are missing entirely, which positions are overloaded, who is quietly holding everything together, who is coasting.</p><p>The temptation is to judge fast. The better move is to watch a few matches first. Some of the players you inherit are better than their results suggest — they’ve just been playing out of position, or under a system that didn’t suit them. Before you go to the market, find out who you already have.</p><p>This is also where the academy question comes in. Ferguson’s Class of ’92 showed what developing from within can do; the transfer market shows what money can buy. Most of us need both. The real skill is knowing which gap needs a new signing and which needs coaching, time and a clearer role.</p><h3>The transfer window</h3><p>Then comes the market. You’ve mapped the gaps, made the case, and now you’re spending the club’s money.</p><p>That last part matters. Every hire is an investment someone else signed off on, and every one is a bet on the future shape of the team. A good transfer window isn’t about collecting the most famous names. It’s about buying the players the system needs — the holding midfielder nobody notices until they’re gone, not just another number ten.</p><p>I treat hiring like scouting. I want to see people in their natural habitat, hear how they talk about their teammates, understand what they’d need from me to play their best football. The CV is the highlight reel. The interview is the full ninety minutes.</p><p>And sometimes the window means letting people go. Ferguson’s rule was simple: no player is bigger than the club. He moved on stars when they started to erode the dressing room. It’s the hardest part of the job, and the part that protects everyone else.</p><h3>The suits problem</h3><p>Here’s where it gets uncomfortable for a United fan.</p><p>Since Ferguson left, we’ve watched what happens when the people in the suits get it wrong. Unclear ownership. Strategy that changes with every season. Transfer decisions made far from the pitch. Results suffer, morale drops, and you can see the manager — Michael Carrick, right now — start to show the strain. A manager can only be as good as the squad and the structure around him. If he isn’t surrounded by high performers, and the club above him isn’t aligned, he can’t do his job.</p><p>Legacy companies can feel similar. Not because the people are bad, but because the systems are old. Governance built for a different era. Approval chains that outlast the people who designed them. Processes you can’t work around, only through. You can have a strong squad and still lose matches because the club is set up to play a game that no longer exists.</p><p>The lesson I take from United isn’t cynicism. It’s that <strong>leadership above the pitch is part of the team.</strong> As a director, I’m in the middle: I’m the manager to my team and a player to the people above me. Part of my job is to absorb the noise, translate it, and protect the dressing room from it — and part of it is to keep pushing the club to change.</p><h3>The coaching staff you inherit</h3><p>When a manager takes over a club, they usually bring their own staff. Ferguson brought his assistant with him from Aberdeen. It isn’t sentiment. A manager’s philosophy only reaches the pitch through the coaches who run training every day, and those coaches need to speak the same language.</p><p>Directors don’t always get that luxury. Sometimes you inherit your leadership layer: people who were hired for a different manager, a different strategy, a different game. They may be good at what they do. They may also see the work completely differently from you.</p><p>Is that a fit problem? Eventually, it can be. Your direct reports carry your philosophy to everyone else, and if they can’t, the team hears two managers. But I’ve learned to ask a harder question first: have I actually taught them the language? A philosophy that lives only in my head isn’t a philosophy yet. It’s a preference. Ferguson didn’t expect his staff to guess; they lived his standards every day because he made them visible every day.</p><p>So with inherited staff, I’m doing two jobs at once. I’m making the way I work explicit enough that a good leader can pick it up and run with it. And I’m giving them a fair, defined window to do that. If it still doesn’t click after that, it’s a fit conversation, and an honest one is kinder than a slow one.</p><h3>Buying time, not waiting for it</h3><p>Ferguson went years without a league title at United and was reportedly close to the sack before it turned. The club gave him time, and the rest is history.</p><p>But time on its own isn’t the point. Nobody gets the slowest possible version of patience, and nobody should ask for it. What a new manager needs is a window and the tools: a clear period to show progress, and the signings, budget and decisions that make progress possible.</p><p>I’ve come to think part of the job is negotiating both, out loud. Here’s what you’ll see by when. Here’s what I need unlocked to get there. Here’s how we’ll both know it’s working. A manager who asks for time without a plan sounds like an excuse. A manager who asks for time with a plan sounds like a strategy.</p><h3>Same player, different club</h3><p>Football is full of players who looked ordinary at one club and world-class at the next. Ángel Di María struggled at United and then thrived at PSG. Same legs, same touch. Different system, different manager, different role, different week-to-week life.</p><p>That’s the clearest argument I know for taking environment seriously. When a designer isn’t performing, the first question shouldn’t be “what’s wrong with them?” It should be “what’s wrong with the pitch they’re playing on?”</p><p>In my experience, people thrive when a few things are true:</p><ul><li><strong>They know their position.</strong> A clear role, clear ownership, and a clear sense of what good looks like.</li><li><strong>They trust the manager.</strong> Someone who knows them as a person and backs them in public.</li><li><strong>They play with good players.</strong> High performers raise each other; isolation drags everyone down.</li><li><strong>They have room to play.</strong> Freedom to make decisions without five layers of sign-off.</li><li><strong>The club believes in the game plan.</strong> Leadership that is aligned, consistent, and patient.</li></ul><p>I love building teams most when I have the freedom to build them properly. Some organisations give you that. Others make you fight for every inch. Either way, the job is the same: create a place where good people can do their best work, and then go and find more of them.</p><h3>Picking the formation</h3><p>A formation isn’t a template. It’s a decision about how you want to play, shaped by the players you have. Org design for a design team works the same way: the structure should follow the strategy, not the other way round.</p><p>Here’s one way I map it:</p><p><strong>Position / In a design team / What they protect</strong></p><p>Goalkeeper / Design system and quality / Consistency; the last line before a bad experience ships</p><p>Defence / Research and insight / The team from building on assumptions</p><p>Midfield / Product designers embedded in journeys / The flow between strategy and delivery</p><p>Attack / Senior and principal designers on the big bets / The moments that change outcomes</p><p>Captain / Heads of design / The dressing room, when the manager isn’t in it</p><p>Backroom staff / Design ops, content, accessibility / Fitness, set pieces, the details that win tight games</p><p>The exact mapping matters less than the habit: before you hire anyone, know the shape you’re building towards, where the gaps sit in it, and which positions you’ll develop rather than buy.</p><h3>The manager I want to be</h3><p>The hardest lesson from United since 2013 is this: a system that lives in one person doesn’t survive that person leaving. Ferguson built a dynasty, and when he walked out, a lot of what made it work walked out with him.</p><p>So the real test of a team I build isn’t whether it wins while I’m there. It’s whether the people in it have grown, the culture holds, and the next manager inherits a squad rather than a rebuild.</p><p>Know your players. Build the squad the strategy needs. Fight for the environment they need to thrive. And leave the club stronger than you found it.</p><p><em>“What’s the best team you’ve ever played in, and what made it work?”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce8e32882249" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Balancing businesses with people]]></title>
            <link>https://uxdesign.cc/balancing-businesses-with-people-ec66c131e4b4?source=rss-720fb3cdf7c9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec66c131e4b4</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[ideate]]></category>
            <dc:creator><![CDATA[Helen Arvanitopoulos]]></dc:creator>
            <pubDate>Tue, 10 Dec 2019 10:05:40 GMT</pubDate>
            <atom:updated>2019-12-12T00:44:08.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t1g3r9PLtPrFmXd76B84bA.jpeg" /><figcaption>Collaborating with the business you’re designing for is just as important as creating product and services for the people you’re designing for.</figcaption></figure><p>Every problem is different, every organisation has its challenges and people react differently in various scenarios, so how can we tackle the challenges businesses have and create experiences that delight humans? By using a framework that helps us in understanding the problems.</p><p>It’s bringing together collaborative minds, across various disciplines. <br>It’s developing unstructured ideas. It’s learning and understanding from our why’s and continuously being curious from what we’ve observed and heard.</p><p><strong><em>It’s Design Thinking.</em></strong></p><p>Often I’m asked, especially within my organisation, ‘…what are the benefits and why should we implement Design Thinking?’ My response is usually with a big exhale of breath whilst trying to gather all the thoughts, words, quotes and reasons that are circulating at the top of my head into an explanation that can best answer these questions.</p><p>However I end up responding with, “…why not?”</p><p>Let me first explain what Design Thinking means to me. Yes, there is a design thinking methodology that a Google search returns, but to everyone that has used Design Thinking, they’ll have a different explanation (to a point). <br>This is due to experiences, what works well, what doesn’t and how we’ve best achieved outcomes that answers the problems we are trying to solve.</p><p><strong><em>Design Thinking focuses on people, it’s human centred.</em></strong></p><p>If there is one thing that we can probably all agree on regarding Design Thinking, it would be that we have to have empathy. It isn’t just empathy to the people we’re trying to solve for, it’s also something that I feel a lot of us as preachers tend to miss when we’re beginning our process. We need to be a bit more empathetic towards businesses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wVPf9EVs_AneH5uKjuIfCA.png" /><figcaption>Bringing empathy to both Businesses and People — with Design Thinking</figcaption></figure><p>It’s easy to want to disregard organisational heads, or top level managers in our processes as designers — because realistically practicing what we preach, we are already 100% convinced we know what to do, because we live by design. However, sometimes you’d be surprised by taking the time to listen, understand and empathise with their situation, we really don’t know that much.</p><p>So, should the often asked question be changed to: How do you balance business needs with the people you’re designing for? Yes, by using Design Thinking. Let me explain how this is a great framework that balances businesses with people.</p><p><strong>Empathy</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*TW7tYwISfhtgX4TLQO6j6g.png" /><figcaption>Empathy is about listening, understanding and being present with unbiased.</figcaption></figure><p>As earlier mentioned, Design Thinking begins with empathy. It’s the stage of the process where we are able to get a better understanding of the problem we’re trying to solve — and more importantly is there actually a problem here at all to be solved? It’s the stage where we should be setting aside our own assumptions about everything and to just sit, watch, listen and observe. It’s the most important stage in my opinion.</p><p>Being able to work for some large organisations where CEO’s, managers and leaders often say I don’t have time to sit down and have a chat, you will be surprised that when you give them the opportunity and also the time to talk, they actually do have a lot of time, and a lot to say.</p><p>Being able to create an environment where you would like to hear, understand and just flat out know — what really are the problems and struggles that these people are facing. Then when you flip the coin and take the time to do the same to people we’re trying to design for, you start resonating with both tribes and you realise that you are wanting to create a happy medium in achieving outcomes for the business and creating something great for people. By being empathetic to both businesses and people (product and users) it creates unbiased opinions and breaks down any assumptions you had before.</p><p><strong>Define</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*63sWsyHMmMxjv-8iovG9yg.png" /><figcaption>Define is about bringing together all our learnings and observations.</figcaption></figure><p>Depending on how much time you gave yourself to empathise with both groups you’re trying to work with, the define stage follows and this is gathering all the information you heard, observed and found informative. What I love to do is take all these insights — synthesise them, then relay back to everyone in the organisation. This for me creates transparency, collaboration and connection — and a sense of ownership if you’re ‘managing up’. You will be surprised what conversations start to come out of this and further questions that arise from this activity. From these insights common factors will appear and together with your team you should be able to clearly define the problem in a statement that is human centred.</p><p><strong>Ideate</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*nVADQW0SsDUEkIgauzc2Cw.png" /><figcaption>Go wild. Sketch, doodle — ideate.</figcaption></figure><p>Thinking outside the box.<br>As designers, we often think differently, often challenging ourselves. The challenge here is trying to work with businesses to think differently and to remove their tunnel vision. Businesses are so focused on their day to day, they forget to look outside of it. We as designers need to guide each other in making sure we don’t get caught up in the current state and come up with some radical ideas, views and alternative ways to look at the problem. It’s about creating a collaborative environment where we can use techniques like “how might we” or “crazy eights”, to name a few, to be explorative. It’s about leaving everything at the door and coming inside with an open mindset. <br>Be wild.</p><p><strong>Prototype</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*wTEg3axFhSow9AEubVz8CA.png" /><figcaption>Collaborating and building a product or service together as a team — prototyping.</figcaption></figure><p>By this point, let’s hope businesses, designers, teams, individuals, groups — are what… working together? Yep, you better believe it. The majority of times, I see the friendly arguments and disagreements on how an inexpensive version of a product is created to be shared and tested within the business and of course with people who will be using the product. This stage gives us a clearer view on how people will behave, think and feel when engaging with the product.</p><p><strong>Test</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*tdRSHReeW4glI6o2H4MW_w.png" /><figcaption>Sit, observe, watch, listen, note — test.</figcaption></figure><p>My favourite stage to be honest. To hear, to see, to make notes and capture insights on what we’ve worked on in all the stages before to understand. Observing all the thoughts and assumptions we had in real life. This stage allows us to derive a deeper understanding of people and the product, work with the business and to redefine our problem. Design never ends. It’s continuous.</p><p>Overall, Design Thinking may look linear but in practise it’s quite flexible and loops. You don’t need to always do every single stage. It’s just a framework and dependant on where you are with certain problems, it’s easy to carry out various stages of the process in order to solve something.</p><p>The reason I wanted to highlight these stages specifically is because for me, it’s a framework I’ve used that balances pretty well business problems and people problems. It’s collaborative, it’s challenging, it’s rewarding and it works.</p><p><strong><em>Design Thinking ensures we’re creating something that solves a real problem and makes people’s lives better.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec66c131e4b4" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/balancing-businesses-with-people-ec66c131e4b4">Balancing businesses with people</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>