Running a design team, studio or agency changes the responsibility.
Other people's careers now depend partly on the environment you create.
You are responsible for more than the quality of your own work.
Build around a point of view
Why should the practice exist?
"Because we do good work" is not enough.
What do you understand unusually well?
What kind of problems should people come to you to solve?
What standards define the practice?
What work will you refuse?
A strong design organisation becomes recognisable through the consistency of its decisions, not simply through a visual style.
Hire people who improve the room
Do not hire people because they will agree with you.
Hire people who know things you do not.
Hire people capable of challenging you.
Hire curiosity.
Hire judgement.
Hire craft.
Hire responsibility.
Your authority is not weakened when someone on your team is better than you at something.
That is the point of having a team.
Do not create dependency
Do not make every decision travel through the most senior designer.
Set principles.
Make responsibilities clear.
Create strong critique.
Give people enough context.
Then let them work.
A design organisation that cannot produce excellent work without its leader touching every project has not scaled expertise.
It has scaled dependency.
Protect the team
Every client you accept becomes part of the working environment.
Every impossible deadline becomes somebody's evening.
Every badly scoped engagement becomes somebody's stress.
Every abusive client becomes your responsibility when you allow the behaviour to continue.
Revenue does not automatically justify the conditions required to earn it.
Choose clients carefully.
Preserve apprenticeship
AI can remove many of the tasks through which younger designers traditionally learned.
Do not respond by simply removing junior designers.
Give them real problems.
Bring them into research.
Let them present.
Let them prototype.
Let them work directly with engineers.
Let them use AI.
Then ask them to explain the decisions.
A profession that automates its apprenticeship eventually runs out of professionals.
Make AI organisational
Do not let AI adoption become hundreds of private experiments spread across personal accounts.
Define approved tools.
Define data policies.
Define review requirements.
Define disclosure expectations.
Define how generated assets are handled.
Define how AI accesses the design system.
Define where human accountability remains.
AI should become organisational capability rather than unmanaged individual behaviour.