Impact / Beyond the product
Building and growing teams
Designing the organization itself, the one product where I am the user.
How I approach it
When leaders grow a design team, most of them follow the budget. They're behind schedule or facing a big build, so they ask for more people. It's a reasonable move, but it turns into a chase with finance instead of designing the organization around the people in it.
I start from the North Star and the year's objectives, meaning where each product is and what it needs to improve. Then I look at the kind of change each product needs, and who on the team is best at that kind of work. If they aren't on it, I move them and their team. Whatever gaps are left tell me who to hire.
Leaders also don't move people often enough. Designers on the same product for too long get tired and stale, and the fear of the ramp-up keeps them there. Lower-quality work costs more than the time it takes a new designer to get up to speed.
And don't hire for sameness. Some people are best at new ideas, some at starting from zero, some at cleaning up debt, and some at turning abstract concepts into execution. Know your team by its strengths, not its titles.
Right people in the right seats, then hire for the holes.
Lead story
One example of the approach in action.
Growing Infobip's design organization
Infobip · Agency work, then in-house · VP, Product Design and Research
- SituationWhen I joined Infobip in-house, the design organization had about 20 people.
- What I didGrew it to 70 across six disciplines, reporting to the Chief Product Officer. Stood up research and analytics as wholly new departments, together called Customer and Product Research, covering both buyer and user personas. Set up a product leadership panel that held teams accountable for release decisions, assumptions, and results after launch.
- ResultDesign, research, and experience expertise reached across the company. Teams got clearer, craft quality rose, and the panel created a stronger feedback loop between what we shipped and what we learned.
Where I've faced it
The same kind of problem, at other companies.
- InfobipAgency, then in-houseGrew the design org from about 20 to 70, and stood up research and analytics
- TelepathyAgency leadershipGrew the agency from about 10 to 65 people
- Arthur UXAgency leadershipLed a 10-person team, and built a 1,000+ designer community with skills training
Related thinking
What I've learned from this work.
The quietest person in the room often has the sharpest insight
Most meetings reward whoever speaks first, fastest, and most confidently. But charisma isn't a strategy.
Building and growing teamsYou don't have an execution problem. You have a rhythm problem.
If every sprint feels like a five-alarm fire, the team isn't failing. The pacing is.
LeadershipDesign isn't the bottleneck. Leaving it out of decisions is.
When design looks like the bottleneck, it usually comes down to misaligned expectations and a missing seat at the table.
LeadershipYour design team isn't slow. Your decisions are.
The slowest decision is the one you have to make twice.