Leadership

Leading design at Valor Software

From 2019 I led designers at Valor Software, and from November 2021 as Head of Design. This is how I hired and grew the team, gave feedback when work was not at the bar, led people through layoffs, and what I would tell a new Head of Design.

Role
Head of Design, 2021 – present
Team
Up to 6 designers reporting directly to me, up to 4 products at once
Scope
Hiring, yearly reviews and growth, feedback, layoffs, AI workflow
6designers reporting to me
4products at once
12designers hired
2designers grown to the next level

How I lead

Ten short chapters, from the daily rhythm of the team to the first three months in the role.

Six product designers, no layer of sub-leads, everyone worked directly with me. Each of them covered the full product cycle: user interviews and UX research, journey maps, information architecture, wireframes, prototyping and high-fidelity UI mockups.

We had daily design syncs, a weekly critique and regular workshops. I kept designing my own product and covered others during vacations and sick leave, so I knew every project from the inside.

I also made the case to management for an After Effects course for the team, and Valor paid for it. We did not finish the whole course, but everyone learned the basics. One designer went much further and built complex motion, so we brought her into every project that needed it.

I do not use take-home tests. Instead I worked with our recruiters on real examples of strong and weak candidates, and together we sharpened what we were looking for. At the start about 80% of the candidates were graphic designers, so we went through the reasons for each rejection together. After a few rounds the screening was sharp, and the recruiters became true partners in hiring.

I screened portfolios myself: real shipped work over showcase shots, and for shortlisted candidates I asked, where their NDAs allowed, to walk me through the source files in Figma to see components, structure and auto layout. In the interview I brought a designer from the team. We reviewed the portfolio, checked every claim on the CV, and asked how the person handles conflicting stakeholders and disagreements with PMs. English was checked too.

Result: about 12 designers hired.

Reviews. Every year I sat down with each designer to set goals: which way they wanted to grow and where the gaps were. To find the gaps I wrote my own tests, built on real work situations rather than theory, because past mid level theory tells you little. Each designer had a profile in Valor’s internal review tool, with past reviews and a chart of strengths and gaps. Later the designers started reviews themselves, and I stayed in daily contact with everyone.

Feedback when work is not at the bar. In my experience the designer usually knows something is wrong. What they lack is a way out. A designer early in her career, working on another UN WFP project, kept getting client requests she knew were bad for users, and it hit her hard. I stepped into her project to work alongside her. We named the problem together, I suggested ways to improve it, and we often stayed after work to go through the screens. The fixes usually worked. Anyone on the team who asked for my view got it, and we worked it through as colleagues.

Growth. She came from an art background and grew from junior to a solid mid-level designer. After I mentored her there, she took her first project on her own, and we learned Webflow together. A mid-level designer with good taste often came to me with context questions before trying himself. When the CEO handed him a presale on blockchain, then a new topic for all of us, he did not know where to start. I stepped in: we researched it together, talked to our developers and built the proof-of-concept presentation side by side, and the CEO was happy with it. Each time I showed him where I find things rather than giving the answer, and he grew into an independent senior.

We started by moving the team from a mix of tools to Figma as one standard. Today the handoff is a clickable prototype in code. A short brief comes first: states, data and a closed list of components, agreed by product, design, front-end and QA. Then Claude builds the prototype on a GitHub branch, and developers keep its front end and wire up data, auth and tests.

Figma stays where the team reviews, comments and annotates, and every generated screen is saved there too. Design artifacts live in both places, in code and in Figma.

The design system is built on tokens that mirror the system our developers ship, and it is the context our AI agents work in: they build only from components and tokens that already exist, never from raw values.

Our processes and documentation live in Notion. Design requests go through ClickUp, the task tracker used across Valor, so everyone knows how to ask for design work and where it stands.

Budget cuts hit Valor, and the team I had built shrank from six designers. These were people I had worked with for years, and it was the hardest part of the job.

I asked managers and HR to bring every layoff through me, and each time I offered to tell the person myself, before anyone else. Nobody heard it out of the blue. No one was let go for their work, it was always the company’s finances, and I said so plainly. When people asked me to warn them early, I did.

In those conversations I put the person first, not the handoff. Handoff was already a routine process. I told them to spend their notice period on themselves and their search, and I wrote a LinkedIn recommendation for everyone who asked.

One of the biggest blockers was not capacity but silence: feedback from a key stakeholder could take weeks. With the project managers we agreed on a one-week window. If no feedback arrives, the team decides and moves on.

We also settled design arguments with evidence instead of taste, using analytics, heatmaps and A/B tests. Decisions got faster, and silence stopped acting as a veto.

On Mabrook, Oleksandra, a designer I had worked with at Valor, was the only designer when the product started to grow. She asked for me to join. We saw that the product needed more designers, I ran two interviews and hired a senior product designer, and the team grew to three.

“He leads with trust rather than control, which is why people bring him with them from project to project.”Oleksandra Nadtochii, Product Designer

I built a Claude system for recurring internal work. The method: feed Claude real tasks, turn what works into skills, build agents from the skills, document everything in Notion and share it with the design team.

Each designer works with an agent on their project, and six shared agents cover requirements and documentation, presentations, social posts, articles and covers, the Valor site and designer portfolios. A B2C feature that took 5 to 7 working days now sometimes takes 3. Every designer became the lead of a two-person team: themselves and their agent.

Results on client work: Mabrook feature release from 10 to 4 days with AI-assisted design, and ASI Central brief to clickable prototype from 11 to 3.5 days. Figma stays alongside the code, for review and as a copy of every screen.

Together with a colleague I ran two internal masterclasses on AI for the company, mostly for developers: a talk of about two hours with Q&A. I covered Figma AI, and he showed working with Claude.

In November 2026 I ran a workshop for the product design team at Roomex, a Corpay company: how a team gets from a Figma library to working code with AI, together with developers. Read the article and see the slides.

I lead with authority, not control. I protect the team from outside pressure, and I do the work alongside them.

To a new Head of Design I would say three things:

  • Earn authority. Be useful before you demand anything: help with a real problem, give advice that works, stand up for your people.
  • Make the rules visible. Write down how work is requested, handed off and reviewed, so nobody has to guess.
  • Stay close to the work. A lead who designs is a lead the team trusts.

Need someone to lead
your
design team?

I’m looking for a Head of Design role, remote from Spain. English, Ukrainian and Russian, intermediate Spanish.