Skip to main content
Paula Farrugia
  • Leading
  • Learning
  • Self-Awareness

Leading a Team on a Stack You Don't Know: How I Get Up to Speed

6 min read


How I get up to speed, and what carries over from other stacks.

I come from a front-end background, and front-end teams are the ones I've led the least. Most of the time I've led teams working in something else: back-end PHP teams, web3 and blockchain teams writing smart contracts, and WordPress teams. I'd used WordPress before, but it had been a while.

Every time I started with a team on a stack that was new to me, it was scary. The voice in my head said I didn't deserve to be there, and that my team was wondering why I was the one leading them if I didn't understand what they were doing. If you're leading a team on a stack you don't know, you may recognise the feeling. The first weeks usually go the same way: I go through the team's documentation, set up the projects myself, get onboarding sessions from the team and get familiar with the projects.

Over time I've collected a handful of habits and ways of thinking that help me get up to speed and make the fear quieter. They don't make the fear disappear, and I don't think they should. It's part of what pushes me to keep learning, and a leader who's sure they know better than everyone else is the one who stops growing. What these do is help me feel comfortable with what I don't know.

Being the expert isn't entirely the job anymore

You don't have to be the most technical person on the team. When I became a lead, I took on responsibilities that weren't part of my job before: team performance and tracking metrics, 1:1s, aligning team planning with business goals, cross-team communication, and stakeholder communication and management. They take the time and attention that used to go into technical depth.

So I don't beat myself up when I'm not the most technical person in the room. Time spent trying to match my team's technical knowledge is time taken from the other parts of leading them.

I also try to surround myself with people who know more than me. I want the team to be better than I am in their field. That lets me focus on what matters for my role. I learn what I need from them and trust them to get the job done.

Know what you need to know

Not knowing something is fine when you don't need it. Trying to know everything is a fast way to feel like an imposter, because on an unfamiliar stack there's always more you don't know.

Unless needed otherwise, I work on a need-to-know basis and look at things from a bird's-eye view. When a topic gets technical, I ask people to summarise what matters without going into every detail.

I go deeper only when I have a good reason, or when I'm interested and want to. When I catch myself wanting to learn something, I ask whether I want to know it or need to know it. If I need it to do my job, I learn it. If I only want it, that's fine, as long as I'm honest about the difference. If I find that most of what I want is technical depth I don't need, I should ask myself whether a leadership role is right for me.

In week one, tell the team where you stand

In my first week with a new team, I speak to each person individually. I ask what they think I should know, and I'm upfront about the areas where I have no experience. I tell them what I expect from them to help onboard me, and we start from there.

Being honest about it has gotten me empathy and less judgement from the team. Pretending to be better than everyone while not keeping up with them loses respect.

Ask the questions, out loud

I have a right to ask questions, and I use it. I don't have to know the answer, but when I need the information to do my job, I ask. The more insecure I feel about my technical knowledge, the more I try to ask. Staying quiet only makes the feeling worse, because the gaps stay where they are. Asking is how they close.

I ask openly, and I ask the "stupid" questions with confidence. People copy what a lead does, so when I ask, I'm showing the team that it's normal and useful to ask when you don't understand something. A team that asks questions learns faster than a team that pretends.

Questions also show what matters. When I ask about something, it signals that it's worth clarifying for everyone, not just me. Often someone else in the room was wondering the same thing.

What if I don't know what to ask? Then I ask what they think I should know about the topic, the same question I ask in week one. If I'm lost in a technical discussion, I ask what they think the problem is and what they think the solution should be. Those two questions work almost anywhere.

Everyone is an expert in something

When you're surrounded by people who know more than you about the stack, it's easy to feel like the only one who doesn't understand. I remind myself that everyone is confused by something. Someone who's an expert on one topic and explaining it in great detail is probably just as lost as I am on another person's topic. Everybody is an expert in something and a beginner in something else.

I keep the same mindset about myself. I believe nobody ends up leading a team without strengths the others don't have. You have yours too. Mine are how I communicate, how I see the bigger picture, and how I bring people together. I try to use them well and not hide them because I feel I should be somewhere else.

Bring what travels

I know more than I think, and so do you. My background is front-end, so at first I couldn't read a PHP codebase or a smart contract the way the people who write them can. But the principles I learned as an engineer don't belong to one language, and yours don't either.

  • How to structure components so each one has a clear job.
  • Keeping things simple, and being suspicious of anything clever.
  • Separating concerns so that changing one thing doesn't break another.
  • Choosing names and structure that the next person can read.
  • Knowing when to reuse code and when to leave it alone.
  • Keeping changes small and easy to review, and asking how we'll know a change works.

None of these depend on the syntax. They let me follow a conversation, spot when something sounds overly complicated, and ask a better question than I otherwise could.

They're also how I handle trust. I trust people to get the job done because they prove themselves, not because I constantly check their code and micromanage their work. But when something is risky, I verify, and I don't need the syntax for that either. I can ask whether it's as simple as it can be, whether the change can be smaller, how we'll know it works, and what success looks like.

The fear still shows up whenever I start with a stack I don't know, and I don't expect that to change. The first weeks aren't as scary as they used to be, though, because now I know what to do with it. I tell the team where I stand, I ask, and I lead from what I do know. And the syntax does get easier to read the longer I work with it.

Want to talk about this?