Eryk Orłowski · hretheumhretheum.com/questions/build-a-design-org
Question P2 of 8
All questions2Can they build and sustain a design organization?
At ING Bank Śląski, built from scratch the UX chapter of the Business Banking unit, which served 3 tribes. Gave it a career ladder with about 6 levels, design review as a regular rhythm of work, and a measure that the same problem is not solved by more than one team. The rituals, standards, career ladders and people in roles kept working after leaving in 2022. At Sportradar, together with the organization, moved designers from a service model to product teams, because in a difficult domain moving them between projects got in the way of the work.source sources: ing-01, ing-04, ing-10, ing-15, ing-11, ing-12, sr-05, sr-07
Evidence
I built the UX chapter for ING's Business Banking division from scratch.”
I created a career ladder for designers with about 6 levels, from junior up to Principal Expert UX and Chief Expert UX.”
I have had a budget in every leadership role.”
Mostly not alone, and not ad hoc. […]Mostly not alone, and not ad hoc. At ING I made design reviews and knowledge sharing between teams part of the regular rhythm of work, and I still work that way. Designers show their work to each other regularly, so feedback also comes from peers who know the context. That has two effects. People get used to showing unfinished work early, when changing direction is still cheap. And my opinion stops being the only filter, which is healthier for the team and for the work.”
Rituals, standards, career ladders and people in their roles kept working after I left in 2022.”
The designers first worked in a service model central to the tribe, and after a change of concept were embedded in product squads.”
At ING Bank Śląski I built a UX chapter for business banking from scratch, up to 15 designers across 6–9 squads.”
I hired the entire chapter team myself.”
The Business Banking division had 3 tribes: cash management, financing and digital platforms, and the chapter served all 3.”
The chapter worked in a distributed but not fully embedded model, with designers hired by tribes according to the needs of their squads.”
As UX chapter lead I took part in the obeya room where the division's epic roadmap was discussed.”
In hiring I assessed hard skills, soft skills and experience, while tribe management assessed cultural fit.”
Goals and reviews were run by line managers in the tribes; my contribution was defining goals that fit design roles and helping to assess them.”
The measure of the chapter working was that the same problem was not being solved by more than one team.”
I was the UX Chapter Lead and a UX Principal Expert.”
I introduced design reviews and knowledge sharing between squads as a steady rhythm of work.”
From the start I wanted the chapter not to depend on one person.”
At ING Bank Śląski the chapter's designers worked in squads using Scrum (planning, review, retro), and I organised their work around the sprints.”
I took part in the agile transformation that covered the whole bank, and I was responsible for my part of it.”
Sportradar was a very flexible organisation: if something did not work, we changed the concept together, including the designers' working model.”
The designers moved into product squads because the domain is very demanding and moving them between projects made it hard to get up to speed.”
I took part in launching AI Sagres, the group that leads AI projects at Efigence.”
I proposed the idea and the name of AI Sagres: designers, business analysts and technology people at one table.”
I proposed the strategy of the centre of excellence and identified the business problems it can solve.”
In October 2025 I co-founded TalentCanvas, a company that hires for product and design teams.”
TalentCanvas talks to candidates and companies in designers' language, understanding the product context instead of keywords.”
It's easier than it was fifteen years ago, when I had to explain what a UX designer was for. […]It's easier than it was fifteen years ago, when I had to explain what a UX designer was for. In product organisations people usually come to me: they already know they need more hands, so the conversation is about what kind of person and where. Where product design is a service, as in an agency, nobody questions the need either, but the headcount has to come from the data. I size the team on its current and forecast workload, and I keep a sensible reserve for work nobody invoices: developing the offer, R&D, strategic work and new business. Without that reserve the team is busy, but it stops getting better.”
Most of a design budget is people, then tools, then research. […]Most of a design budget is people, then tools, then research. I go through it with finance on a regular cycle, more often than once a year, so nothing surprises either of us. I always keep a reserve for development work, the same way I plan headcount: time for R&D, for improving how we work and for things nobody invoices. Without it the budget looks efficient on paper and the team slowly falls behind. AI tools I track as a separate line. They're cheap individually and add up quickly, so every few months I check which ones people really use and whether they pay for themselves, and I cut the rest.”
I try never to make it my opinion against theirs, because that's a contest of rank and I'll usually lose it. […]I try never to make it my opinion against theirs, because that's a contest of rank and I'll usually lose it. I bring data and research instead: what users actually do, where they get stuck, what it costs. Then I connect it to the goal we share. At Kokos.pl, a peer-to-peer lending platform, I persuaded the client to reorder the flows around what the user was trying to achieve rather than around how the business was organised, and it shipped that way. The "no" becomes "here's what gets us to your goal faster". A senior person can say yes to that without losing face.”
The same way they read any other proposal: the problem, my recommendation, what it costs and what the risks are. […]The same way they read any other proposal: the problem, my recommendation, what it costs and what the risks are. If we have evidence from data or from research with users, it goes right next to the recommendation, because one number or one short clip of a user struggling does more than any argument of mine. That fits on a few slides. The design process, the full research and the alternatives we rejected go into an appendix, and I bring it to the meeting in case someone wants to dig in. A board doesn't need to see how we got there to make a good decision. It needs to understand what it's deciding and what happens if it doesn't.”
If what you need is a cheaper pair of hands, you shouldn't, and I'd rather say that honestly than pretend I compete on price. […]If what you need is a cheaper pair of hands, you shouldn't, and I'd rather say that honestly than pretend I compete on price. I'm worth it when you need someone to build and lead a design team, set standards and make AI work inside it without breaking things. And you don't really have to choose. A good team needs both: younger designers who bring energy and fresh habits, and someone who has seen enough to help them grow. I've spent most of my career doing exactly that, hiring and developing designers, not competing with them.”
Limit
I decided which competences a role required; the tribe lead decided on the need and the headcount.”
E-mail: [email protected] (kt-01) · LinkedIn: linkedin.com/in/eofek (kt-02)