How I lead
I build design teams that make every other team better.
- Level 01
Associate
Growing hard skills.
- Level 02
Mid-level
Becoming well-rounded, while mastering hard skills.
- Level 03
Senior
Mastering soft skills to strengthen influence and make decisions.
- Level 04
Principal
Driving product vision. Designing the best solutions from ideation through release.
- Hard skills
- Soft skills
- Influence + Drive
*A team performs as well as the individuals on it. Identity maps are my foundation for understanding each one.
In practice
How I do the job.
How we speak is how we behave
A shared language gives a team consistency, efficiency, and confidence in the work. It speeds up communication, comprehension, and delivery. I build a common language that makes the team unified and effective.
I stay focused on the objective
It's fun to jump in and start designing, but that's a quick way to get lost down the road. I root every task and project the same way. I restate the objective for everyone and keep it physically visible, so we test every idea with one question, "Can this achieve that?" If yes, then "Will this achieve that?"
Information architecture is everything to me
When we understand the hierarchy of what we're experiencing, whether we're navigating a product or having a conversation, we're better equipped to take part, and our chance of success goes up.
I don't hire for sameness
No competitive sports team plays with one position. They're all basketball players, but each has a different responsibility, and that's what makes it a team. They complement each other in the job they need to succeed at.
I aim for simple over complex
Simple is hard to achieve, but it's worth so much more in the long run. If I can't simplify it, I can't understand it, and then I can't communicate it well enough for you to be successful.
I strive for collaboration
Not just for the feels. It makes everyone in the room better, and it speeds up delivery while strengthening it.
Points of view
How I see leadership and teams.
- Your design team isn't slow. Your decisions are.The slowest decision is the one you have to make twice.
- Design 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.
- What will you do with the time AI saves?AI saved the team 20 hours a week. Too often, leadership just asked for 20 more hours of output.
- You 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.
- The quietest person in the room often has the sharpest insightMost meetings reward whoever speaks first, fastest, and most confidently. But charisma isn't a strategy.