Work
How I Lead
I'm Brian, a Design Manager at PayPay, based in Tokyo, Japan. I've been a designer since 2015, and since 2023 I've been leading design teams, which means my job now is helping other designers get better.
My path has taken me through many kinds of companies. I started in e-commerce, then joined a design agency, moved into travel, then a ride hailing and delivery super app, and now finance. Along the way I've worked in teams of every size, from a design team of three to one of 200 designers.
This page starts with how I think about leadership, then shows it in practice through three cases: growing designers who were stuck (People), earning trust for a new way of working (Process), and giving designers a say in what gets built (Culture).
1My leadership philosophy
- Lead by example.
- To inspire my team, I have to be a manager they can look up to. For a design manager, that means staying good at three things: designing, turning complicated information into simple insights, and building trust with stakeholders, leadership, and my own team.
- Guide, don't spoon-feed.
- I build trust by giving my team the transparency they need to do their best work. Designers learn by trying things and making mistakes, so I let them choose their own path and step in when they head the wrong way. I let them swim freely, but I don't let them drown.
- Every designer gets a clear path.
- Every designer is different, so I build a career plan with each one. That way they know what the next level looks like and how to get there. I also match their personal goals with what the company can offer.
- AI for efficiency, not taste.
- I encourage my team to use AI to work faster and raise the quality of our output. But AI doesn't replace designers. They still need to explore and keep building their craft, because AI can't replace taste.
2People: Growing designers who were stuck
Two designers on my team had stopped progressing, each for a different reason. I worked with each of them on the specific issue that was holding them back, and both were promoted within a year.
2.1Designer A
The problem
- Influence: Designer A had a lot of good ideas, but they rarely went anywhere. He would raise a proposal but not follow through, so nobody else backed it either.
- Career progression: He was a mid-level designer who wanted to become a senior, but nobody had ever shown him what that looked like in practice, or what it would take to get there.
What I did
Influence starts with trust. People back ideas from designers they trust, and that trust comes from finishing work consistently and presenting it clearly. So his first goal was to earn his stakeholders' trust, knowing it would take time.
I then coached him on how to work with stakeholders, including how to align people in small conversations before a formal meeting. That way, by the time a decision is made, most people in the room already support the idea.
I also held him to following through on his own initiatives, because people won't believe in ideas he doesn't act on himself.
Finally, we made a career plan together. I showed him what we look for in a senior designer and where he stood. We wrote down what the senior role requires, listed his strengths and where he got stuck, and broke the goal into smaller projects to work through one by one.
The outcome
Within six months, he was promoted to Senior Designer, and six months after that, to Lead Designer. He went from a designer who lacked confidence and influence to one that stakeholders trust and junior designers rely on.
2.2Designer B
The problem
- Motivation: When I took over his team, Designer B had received low performance ratings for five review cycles in a row, and his motivation and confidence were very low.
- Independence & Initiative: He tended to wait for step-by-step instructions instead of starting work on his own. His design skills were actually great, so capability wasn't the issue. He was just afraid of making mistakes.
- Confidence & Communication: At the same time, he agreed to every request and rarely challenged stakeholders' ideas. He worried about looking like he didn't know enough, so he needed the confidence to speak up and explain his design thinking.
What I did
I asked him to propose his own initiatives and lead them from start to finish, next steps included, and made it clear I would back him if things went wrong. I told him that "mistakes are the path to wisdom," and encouraged him to experiment freely.
We also worked on why speaking up in meetings felt risky to him. He usually brought ideas without any evidence, so every question felt like a personal attack. I told him to always have a "strong why" behind his ideas. That could be a simple list of pros and cons, supporting data or research, or even an honest "I don't know yet, I'm assuming here."
And as with Designer A, we built a career plan together.
The outcome
Within about six months, he had become more confident, motivated, and independent. By the end of the review cycle, he received a top rating and was promoted to Senior Designer.
3Process: Earning stakeholder trust
At Wego, I introduced a new design process that the head of product, the engineers and the designers all adopted. My first attempt failed, and what I learned from it changed how I bring new ideas to a team.
The problem
- Missing process: When I joined Wego, the team had three designers and very little process. A request came in and a design file went out, with no quality checks, design reviews, design system or user testing. The head of product also approved every piece of work herself, on top of her other responsibilities.
- Trust & Influence: Soon after I joined, I told the head of product that the process needed to change. The problems were real, but I was new and she didn't know my work yet, so she had no reason to trust my recommendation. Nothing changed.
What I did
As a new joiner, I couldn't push change from the top. Instead, I asked the designers what they wanted to improve. Together we listed what was broken, how to fix it, and what to fix first, which made it the team's initiative, not just mine.
We then tested the new process on a live project, because a good result from real work is much harder to argue with than a proposal in a meeting.
The main change was a layered design review. Designers reviewed each other's work in rounds, and engineers joined early, so technical limits came up while changes were still easy to make. The head of product then needed only one final review instead of approving every step.
I also built the company's first design system, so designers and engineers could build from the same components and work together more efficiently.
The outcome
The project was a success, and we walked the wider team through what we had changed and why. The stakeholders backed the new process, and it earned me their trust.
4Culture: Giving designers a say in what gets built
Designers in my team now help decide what the product should build, not only how it should look.
The problem
- No say in the work: The team followed a fixed routine: a product manager sent a brief, and a designer designed it, applied feedback and shipped it. Designers rarely asked what the work was for. When a project's scope grew, they simply took on the extra work, which led to burnout and low motivation and left less time for the work that mattered.
- Fear of speaking up: The designers cared about quality, but they were afraid to turn down requests, speak up in meetings, or look unprepared in front of product managers and stakeholders. Some felt they didn't know enough to have an opinion.
What I did
I made "saying no" part of the job. I taught it, practiced it with each designer, and did it myself when stakeholders kept adding to the team's workload. That showed the team that disagreeing is fine when you have a strong reason, and that I would back them when they did.
I also made it safer to share ideas in meetings, with the same "strong why" I gave Designer B: bring data if you have it, and if you don't, say so openly. Not having every answer is fine, because we find it together as a team.
Finally, I coached them to pitch ideas as stories, so they are memorable and believable, and brought them into my conversations with stakeholders before big meetings so they could see how to align people early. After a few of these, they did it on their own and started proposing ideas for the roadmap.
The outcome
Designers now ask questions about a brief before they start designing: what the work is for, who it is for, what success looks like, and which business metric it should improve.
They bring their own proposals to roadmap planning, backed by real problems and data, and a few are accepted every season. They also start their own initiatives: one designer built a plugin that lets marketing, business, and design create illustrations from the same set of assets.
The clearest example: after receiving a brief, one designer researched and interviewed users before designing anything. He found they had no real need for the feature and presented his findings. The project was cancelled, saving hundreds of hours across product, engineering, and design.
































