Eryk Orłowski
CV · ContactCV and contact

Eryk Orłowski · hretheumhretheum.com/questions/lead-my-team

Question P1 of 8

All questions1

Can they lead my team?

Has led design teams since 2006. At ING Bank Śląski, built a UX chapter from scratch and recruited the whole team personally: 15 designers in 6–9 squads, led for 5.5 years. At Sportradar, moved the team from mostly UI work to a full UX and UI craft, with research with traders and a share in discovery. Today at Efigence, leads a team of about 10 people in 3 teams, each with its own lead.source sources: om-01, ing-02, ing-03, ing-19, sr-13, sr-15, ef-01

Evidence

  1. The chapter grew from nothing to 15 designers working across 6–9 squads.”

    projekt · me · to be confirmedING Bank Śląski, 2017–2022sourcesource: ing-02case study →case study: hretheum.com/work/ing-ux-chapter

  2. I lead a team of about 10 people in 3 teams, each with its own lead.”

    employment, todayEfigence S.A., from 11.2025sourcesource: ef-01

  3. I hired the entire chapter team myself.”

    projekt · me · to be confirmedING Bank Śląski, 2017–2022sourcesource: ing-03case study →case study: hretheum.com/work/ing-ux-chapter

  4. First, by talking to people regularly, one to one, and reacting as soon as the first signals show up. […]First, by talking to people regularly, one to one, and reacting as soon as the first signals show up. Burnout rarely arrives without warning; it's usually visible weeks earlier in small things. Second, by protecting the team from priority chaos coming from outside. Designers don't burn out from hard problems as much as from priorities that change every week. Filtering that is a big part of my job. Third, by planning workload on data, with a reserve, so the team isn't running at a hundred percent all the time. A team that's always full has no room to recover, and no room to get better either.”

    answersourcesource: ko-c8-1

  5. I redefined the designers' work in the team: from mainly UI design to the full UX and UI toolkit.”

    projekt · me · to be confirmedSportradar, 2022–2025sourcesource: sr-13case study →case study: hretheum.com/work/sportradar-odds-tools

  6. At Deloitte Digital CE I built and led a UX team delivering projects for clients in the United Kingdom and Switzerland.”

    employmentAgencies, 2000–2016sourcesource: wr-01

  7. I have been designing digital products since 2003 and leading design teams since 2006.”

    profilesourcesource: om-01

  8. At Efigence I lead a design team and bring AI tools into its work.”

    profilesourcesource: om-04

  9. From 2007 to 2009 I was managing director and co-owner of K2 Internet (komitywa.com), leading a team of usability and UX specialists.”

    employmentAgencies, 2000–2016sourcesource: wr-03

  10. As UX Director at MRM Worldwide I managed the team and the full user-centred design cycle.”

    employmentAgencies, 2000–2016sourcesource: wr-04

  11. At K2 Internet I led a team of up to 5 people.”

    employmentAgencies, 2000–2016sourcesource: wr-08

  12. At MRM Worldwide I managed a team of up to 5 people.”

    employmentAgencies, 2000–2016sourcesource: wr-09

  13. I led the chapter for 5.5 years.”

    employmentING Bank Śląski, 2017–2022sourcesource: ing-19

  14. I led a team of designers in the Odds tribe that designed tools for internal traders.”

    employmentSportradar, 2022–2025sourcesource: sr-02

  15. My team was 2 seniors and 1 junior retraining from QA to UX design.”

    employmentSportradar, 2022–2025sourcesource: sr-03

  16. I managed to extend my people's skills towards the full UX and UI toolkit.”

    projekt · me · to be confirmedSportradar, 2022–2025sourcesource: sr-14case study →case study: hretheum.com/work/sportradar-odds-tools

  17. I extended the team's craft through research with traders, workshops, mentoring, changing the scope of tasks and taking part in discovery.”

    projekt · me · to be confirmedSportradar, 2022–2025sourcesource: sr-15case study →case study: hretheum.com/work/sportradar-odds-tools

  18. I shifted the team's mindset to ownership of the process from discovery to workshops in product teams, working cross-functionally with product managers, analysts, architects, engineers and end users.”

    projekt · me · to be confirmedSportradar, 2022–2025sourcesource: sr-16case study →case study: hretheum.com/work/sportradar-odds-tools

  19. The compliment I've heard most often in the last five years, and more than once, wasn't about my skills at all. […]The compliment I've heard most often in the last five years, and more than once, wasn't about my skills at all. People said they like working with me. Peers said it, and so did people in my teams. It still surprises me every time. The only sensible explanation I have is that it works both ways: I look after the people I work with, and they end up looking after me. Karma comes back.”

    answersourcesource: ko-a10-1

  20. Any conversation that ends with letting someone go. […]Any conversation that ends with letting someone go. Even when it's clearly the person's own doing, and even after an improvement plan that didn't work, it's still the hardest conversation a manager has. In my whole career I've had two or three of them. I don't want to get used to them, and I think the day a manager finds them easy is the day they should stop managing people.”

    answersourcesource: ko-c5-1

  21. Yes, two or three times in my career, each time after an improvement plan that didn't work. […]Yes, two or three times in my career, each time after an improvement plan that didn't work. I always do it face to face. I keep it short and I don't wrap the message in so much padding that the person has to guess what's happening, because that only drags it out, however kind it's meant to be. Being direct and being respectful aren't in conflict. The person deserves a clear answer and a conversation that treats them as an adult.”

    answersourcesource: ko-c6-1

  22. I start by looking for the cause. […]I start by looking for the cause. In my experience what looks like a toxic person is often a frustrated one: someone who sees problems nobody fixes, carries more than their share, or feels their judgement isn't trusted. Strong designers tend to react to that loudly. So before I treat it as a character problem, I sit down with them and find out what's behind it. Quite often there's something concrete I can change, and once it's fixed the behaviour changes too. The talent stays, and the team gets a calmer colleague.”

    answersourcesource: ko-c9-1

  23. I don't let the team sort that out on their own. […]I don't let the team sort that out on their own. When everything is urgent, the real problem is usually that several people are asking for different things at once, and designers end up negotiating priorities instead of designing. So I agree the order with product, and the team gets one sequence, from one place, with no conflicting requests on the side. If someone wants to jump the queue, that conversation happens with me and the product lead, not with the designer doing the work.”

    answersourcesource: ko-d7-1

  24. I think they'd say I should delegate more, and they'd be right. […]I think they'd say I should delegate more, and they'd be right. It's the same weakness I'd name myself: when something matters, I tend to pick it up and do it, because I know how. It gets the task done and leaves the team with less room to grow. I'm working on it, and I'd rather a manager point it out early than watch me become a bottleneck.”

    answersourcesource: ko-k4-1

  25. I have a firm rule about this: I don't tell stories in public in which someone could recognise themselves in a bad light. […]I have a firm rule about this: I don't tell stories in public in which someone could recognise themselves in a bad light. That applies here even more, because a wrong hire is often my mistake rather than the candidate's. I may have misjudged the role, the fit or what the person needed to succeed. I'm happy to talk about what I've learned about hiring, and in a direct conversation I can go into more detail without putting anyone on display.”

    answersourcesource: ko-k5-1

  26. I wouldn't answer that without looking at the team first, because each of them solves a different problem. […]I wouldn't answer that without looking at the team first, because each of them solves a different problem. I'd check where the bottleneck is. If decisions are being made on guesses because nobody has time to talk to users, it's a researcher. If designers spend their days on tooling, handovers and process instead of design, it's design ops. If the work is moving but the quality isn't there, or juniors have nobody to learn from, it's a senior designer. The worst choice is the one made by habit, hiring whatever role you hired last time.”

    answersourcesource: ko-m6-1

Limit

I take too much on myself instead of delegating. […]I take too much on myself instead of delegating. When something matters and I know how to do it, the fastest route always looks like doing it myself, and for a single task it often is. Over time it's the wrong trade: I become the bottleneck, and people in the team don't get the chance to grow into the work I'm holding on to. I've learned to catch the moment I reach for something, and to ask whether it really has to be me or whether I'm just faster at it today. Most of the time the honest answer is the second one.”

answer from a conversationsourcesource: ko-k3-1

E-mail: [email protected] (kt-01) · LinkedIn: linkedin.com/in/eofek (kt-02)

Contact · #contact

I work on AI in 3 areas: AI in the design process, a product or tool with AI, and design systems with AI.

sourcekt-03

Three ways · no form
E-maileof@offline.plkt-01
LinkedInlinkedin.com/in/eofekkt-02
CVDownload CV (PDF, 84 KB)

Built on a 12-column grid. Every fact leads to its source; where there is none, the page says so.