Good output alone says little about whether an engineering team is healthy
In her first engineering class, she was the only woman among 40 men; today, 45% of the engineering leadership on the team she helped grow are women. Madeline Carson, Engineering Director at MetaLab, argues that output is a poor long-term measure of a team's health and that old management tactics no longer fit today's tech world. So what should a new leader of engineers build first?
Learn five habits that build trust and the checklist that shows your team is truly healthy
Madeline Carson, Engineering Director at MetaLab Design, argues that successful leadership of engineers rests on trust earned through consistent actions, especially as the tech world changes. She shares five trust-building habits, a checklist for judging team health beyond output, and candid lessons from her own journey as a woman moving from developer to department leader.
“Every interaction that you have is casting a vote towards the type of relationship that you want to have with your team. So make them count.”
“The hardest part in leadership is going to be learning how to offer support without just jumping in and actively doing something yourself to fix their problem.”
What you will learn
Build trust with engineers through five consistent actions: knowing them beyond the code, listening and following up, being kind rather than nice, helping hands-on and owning your mistakes.
Open coaching sessions by asking what someone is most proud of and most frustrated by in their past week.
Deliver feedback that lands by listening first, pairing a conversation with a written summary and giving specific positive feedback.
Judge team health with a litmus test of early risk reporting, regular feedback, delegation, quality work and balanced lives rather than output alone.
Plan a personal support network of three to four people who can advise, direct, encourage and challenge you as a leader.
Key takeaways from the speaker
The skills and actions to successfully deliver projects as a leader
How to leverage your own natural skills and abilities to lead
The wholistic aspects of engineering leadership including project delivery, stakeholder management, and team management.
How to lead the growth your engineers on and off project.
Details
Level
Intermediate
Format
Talk
Technical depth
Non-technical
For
Senior individual contributor, People manager, Mid-career
Length
20:51
Published
August 2022
Questions this talk answers
What foundation does a new engineering leader need before making changes?
Trust, which Carson says is earned through actions and time. Without it, rushing into asks and changes with a new team will not go well.
How should a leader open a one-to-one coaching session with a developer?
Carson asks two questions about the past week: what they are most proud of and what was most frustrating. This pushes introspection and stops frustrations from silently festering.
How can a leader give feedback that is clear and kind?
Listen first and gather input from others involved, then deliver feedback by video or in person and follow up with a written summary. Include specific positive feedback, because people keep doing what is recognized.
When should an engineering leader roll up their sleeves and help?
When a team member needs extra support and a push. Carson spent 30 minutes on a screen share starting a milestone document with a lead, who then finished it without her taking over.
How do you know if an engineering team is healthy?
You hear about risks and mistakes early, feedback is regular, you are not necessary day to day, the team delivers high-quality work, and everyone lives balanced lives. Output alone is not a good long-term indicator.
About this talk
In this talk I will discuss:
- How to make the career progression from engineer to engineering leadership
- Key responsibilities of successful engineering leadership
- The traits and skills of an effective leader that you can learn and perform while being your authentic self.
- What good engineering leadership means - what you can give to your project, stakeholders, and team.
- Reflections on my own journey and learnings from individual contributor software developer to leading teams to leading departments.
Two questions to open every coaching session (74 s)
Helping without taking over: the 30-minute milestone doc (61 s)
Why owning mistakes is hard and powerful (54 s)
Awesome. I think it's time. So we'll jump right in. Yeah. Thank you all for coming and I'll start by introducing myself. I'm Madeline. I'm Madeline Carson. And we're going to dig into what it means to be a successful leader of engineers. And I'll share my stories of my personal journey as I grew into engineering leadership. If you're a new or an experienced leader, this is meant to help you to develop a new leader.
How do you navigate your leadership responsibilities in relation to that new climate that we're experiencing, and especially in our tech industry. So who am I and why should I attempt to give you any advice? Well, no journey goes smoothly, let alone one where you have responsibility for other complex multifaceted humans. I'll do my very best over the next 20 minutes to share some of my hard earned lessons to save yourself some energy.
How do you even validate some of the great things that you're doing already? A little info about me that might help provide some context into everything else that I'll be sharing. Firstly, I was born in the West Coast of BC, and I can confirm that Canadians really do have their own special brand of authenticity and niceness. I grew up as a woman in a patriarchal world, which taught me to be creative in a world that isn't designed for me. The data is clear. Women are underrepresented in medical studies, city planning research, and tech. To get what we need in this world, we often need to find creative solutions to make things work for us.
And I took my electrical engineering degree at uni. Maybe it's a cliche, but I really did excel at science and math. And without really knowing why, I enrolled in engineering. I actually had no idea about the gender gap in the program until I went to my first class where I was the only woman out of 40 men.
I had naively assumed that it would be a 50-50 split. I definitely had feelings of being out of place and being different, which has its own cognitive load and struggles to work through. But you keep going. I've worked in tech for the last 15 years. From my university internship program, I was lucky enough to get some programming jobs where I learned that I could excel.
But that I wasn't going to be given the benefit of the doubt and had to work on my skills and believe in myself enough to make up for that. A moment of honesty. When I was preparing for this and reflecting on my career so far and my journey into leadership, a lot of challenges came up with being a woman in a largely male industry.
I started to weave this into my notes because it was part of my lived experiences. But then I got scared. What if this sounds like complaining? What if this is off-putting for people to hear? I had to sit back and think on why it was that I was afraid of being judged for talking about feminist experiences in a conference called Woman Tech and why I wanted to tone it down to be more palatable.
I've decided not to shy away from talking about my real experiences as a woman in tech. And although these might be different from your own, I appreciate you all being part of this discussion with me. A large part of my experience has been -- a large part of my leadership experience has been here at Metalab. They were the ones to support my growth even when I wasn't sure I was ready for it.
I started out as a developer. I was then promoted to engineering lead and then engineering director, which is the position that I've held now for over four years. So it's worthwhile sharing a little context into the work that I've done at Metalab to put my learnings and advice into perspective. So although we're based on the west coast of Canada, we follow talent all over the world, so I've mentored and worked with folks globally.
We're a digital product accelerator who takes founders' ideas and with our teams of research, product, and engineering, in just a handful of months, we'll launch a gorgeous, highly functioning app into market for real users. We do this again and again. We launch, repeat, and learn. We're a true partner for our clients and we've put hundreds of products into market and delighted billions of users.
We've shipped from many of our friends out there on the internet, probably many that you've heard of and used before. A few of my favorite examples include Slack. We got Slack off the ground and developed their differentiated user experience that's so ubiquitous today. Notarize. We were the entire product design and tech team to launch a beta V1 and V2 into market for this now unicorn product company.
And this one's near and dear to my heart because I am so proud to have made the very first commit on their backend code base. And Calvin Klein. I personally had so much fun working collaboratively with design to bring this beautiful e-commerce redesign to life. So let's jump into the tech team in particular since that's where I work and that's why we're all here.
So I'm pretty proud of our meta lab engineering team that I've helped grow. Another honesty moment. I struggle to properly acknowledge my achievements and let alone celebrate them. But this is my first lesson learned. If you're genuine in your pride and your outcomes, it isn't bragging. These are some pretty darn cool growth and retention stats that are the result of a great deal of work by myself and the team.
And I believe made possible by strong and caring leadership. My favorite highlight here is that 45% of our engineering leadership are women, and that includes our CTO and me. All right. Let's take a quick level set for where the world is right now. We've had an unprecedented worldwide pandemic. We've just seen the great resignation, which particularly affected the tech industry.
World politics are heated and divisive, and we might be moving towards a global recession. The world is changing. And with it, the humans who live in it and work with us. The same old management tactics that we grew up with aren't going to cut it. I have different expectations and needs from my employer than I used to, and so do the folks on my team.
The folks on my team are learning how to balance burnout, working on their mental health, growing their skills in this new tech talent market, delivering on work to clients who are also trying to navigate growing their own organizations in this new world. Tensions are high, things are tough, and we need that whole balance. We need more care, kindness, and technical strength and output than ever before.
All right. Now that we've established that things are not business as usual, how do you ensure that you're successful in leadership with your team? Having highly functioning and happy, healthy teams and individuals doesn't just happen by accident. And if it does, it certainly won't stay that way for long. There's work required from you and your teams. You can't just go rushing into that new coaching relationship or team leadership and start making asks and changes.
It's not going to go well. You need to build that right foundation for these relationships. And how do we do that? It starts with trust. If you think back to any good manager that you've had, there'll be trust there. The ones who could ask you favors and you'd be happy to help out because you knew that they would have your back.
I've experienced this from many leaders, but I feel so lucky to work with our CTO, Jonah. When she asks me to work on a project that I'm initially not keen on, I will work on it regardless. Regardless, I have trust that if she's making that ask of me, it's beneficial for my growth, is needed for the organization.
If things get tough, I have her as a safe space to talk things through without repercussions. And if things get really tough, I have her for help and support, I know that she'll jump right in. I have this trust because of the relationship that we've built since she started. She's shared context into her life, experiences and current role.
And in return, she's asked me questions and listens to understand what's important to me, including my strengths and my struggles. Trust doesn't just happen. It's earned through actions and time. Every interaction that you have is casting a vote towards the type of relationship that you want to have with your team. So make them count. But with taking these actions, you can't help but build a better relationship with your team.
I'm actually really curious if any of these surprise you or if they're things that you found to be particularly effective. You can feel free to post in the chat if you like or just think to yourself. I personally have found number five, taking ownership over your mistakes, is the one that's felt most uncomfortable to me. But it's the one that resonates with me most in my own leaders.
So let's jump in. First, getting to know your team beyond the code. By really getting to know your own team as humans, you'll better understand how they bring up issues to you and how you can more effectively give them feedback. When I have coaching sessions with my devs, I don't let them get away with saying things are good.
This is not useful information to me and it's not how folks grow themselves. I always start by asking two questions about their past week. What are you the most proud of? And what has been the most frustrating thing in your past week? This really pushes them to be more introspective about their work, to showcase some cool things that they've done, and to not let frustrations silently fester without us working it through.
By truly caring about your folks, you'll learn when they need a break or if they just need that strong push and held to a high standard to get it done. And then you celebrate those wins together. Next, listen, take action, and follow up. In those coaching conversations that we talked about in that last slide, make sure you really leave space to let them talk.
We listen, not just to the words that they say, but all of their cues. The most important part here is to help your dev dig deeper into that root of the challenge and what can and should be done about it. Supporting your folks through their challenges doesn't mean that you need to take all the action and solve all the problems that your team brings to you.
The hardest part in leadership is going to be learning how to offer support without just jumping in and actively doing something yourself to fix their problem. But by consistently doing these steps, you're signaling that it's worth it to bring up issues and questions to you. Number three, be kind, not nice. This means being willing to have those tough, real conversations.
I have a few guidelines that I follow to make sure that I'm collating and sharing useful feedback. First, I listen to understand why the situation is happening. And I get information from others involved as well to ensure that I have that full picture. This one's tough. It's not what you say, but it's what they hear. To help with this, whenever I give feedback, I'll give it in two ways.
I'll start by talking to them over a video call or in person if I can. But I'll also send over a written summary that I've made. This is more clear and therefore more kind. And this is the best one. It's not just constructive feedback that helps folks grow, but positive feedback. Positive feedback is not only just plain nice to talk about, but it's genuinely useful.
I'm guilty of this for myself. I don't treat the things that I do well as important. Instead, I focus on the things that I need to change. But if you do focus on the specific things that you do well that bring value, you'll keep doing them. And you'll even improve on them, which adds to that value. Number four.
Roll up your sleeves when they need help. Remembering that as you move into leadership, you spend less time in the work. So ensuring that you have a good foundation of the work before transitioning into that leadership. And then when you're there, doing what you can to gain insight into the day to day work will really help us out.
I'll give a particular example of when it's useful to jump in and how. On a particular project recently, I realized that we were missing milestones mapped out for the project. And not having this info was causing a lot of stress that I was hearing from our lead. Although the lead was well experienced enough to do this task, they needed a little extra support and a push.
So on one of our coaching calls one day when I heard this challenge again, I grabbed an old milestone doc as a template. I cleared it out and together we did a screen share and started filling it in. It was a super busy day for me that day, but I was able to make 30 minutes for us to make that start.
And that's the hardest part. The lead was able to finish it up after I dropped off the call. In this situation, it didn't mean that I took over and did all of that work for them. And it didn't even mean a large chunk out of my day. But it did mean offering that hands on support based on my own experience and my knowledge of that project situation.
And that made all the difference. All right, that tough one. Number five, taking ownership over your mistakes. To be completely honest, I've personally felt this challenging as a woman. When I feel like I've spent so much time in my career proving that I'm smart enough. I'm capable enough. And admitting a mistake at times has felt like proving them right.
But taking ownership over your mistakes is really powerful. Done properly, it can gain a lot of trust and respect. When you have an environment of learning from your mistakes and sharing these learnings, you'll actually have a higher quality work output. And you'll get to promote people faster because they're making more measurable growth. When you have these trusting relationships, you're able to have these useful, real coaching conversations.
It means that you hear about problems right away when they're still easier to solve. Problems that are ignored lead to projects falling behind, interpersonal issues becoming irreparable. And the absolute worst part about leadership is people ultimately quitting. Having these open, honest conversations right away is just plain easier and makes your job a lot faster. All of these are real examples of conversations that I've had with my team over the past few months because of these trusting, solid relationships.
I found there are two different ways that these often come up. The folks that I've known for a long time will often slack me or if we hop into a call, we'll jump in right away into their frustrations or challenges. But other folks, when we sit down to our coaching calls, I need to really listen to know where to gently prod a little bit more to get all this information that I need.
So it's really good as a leader to know how to get all that information that you're going to need and how to support folks in both types of these situations. Whether they're ones that they're willing to bring up their problems directly or more indirectly and they need that little push. All right, a litmus test. Have you built that foundation of trust and are you having these honest and useful coaching conversations?
I'll give you the checklist that I use. And honestly, I get really proud when I can tick off these boxes. A bonus random learning. Take moments of pride for yourself where you can. Because these are some good signs that you're doing some darn good leadership. From my experience, these are signals that your team is healthy and highly functioning.
You can't just measure the output because it isn't a good long term indicator. If you have good output, but these items aren't being checked off, you won't have good output for long. It'll taper off at best or at worst, your team will crash and burn. So first, you hear about risks or mistakes early. Because they're going to happen, you need to know about it.
And if regular feedback is happening, there are always ways for everyone to improve. If you're not talking about it, it doesn't mean that it doesn't exist. It just means that you're not working on it. And then, if you've made it so that you aren't actually necessary in the day to day. If you've grown others and given them those opportunities to replace yourself in many small areas, it frees up time for you.
And it gives them those growth opportunities to do even better in their career. It's a win-win. And then, true, if teams are delivering on that high quality work. No matter how good they are, that superstar developer is not going to be as effective long term as that well-oiled machine of a highly functioning team. And then, the team and yourself are living healthy, balanced lives.
This means that hobbies and vacations aren't burnout necessities. If teams and projects are running smoothly, there is time for these things. If they aren't, it's a pretty good litmus that it's not an effective team and more leadership is needed. And that's where you can jump in and help. All right, let me practice that piece that I find so tough and own up to my own learnings.
So, here's a highlight reel of my own mistakes. As a leader, you spend so much of your time giving support to those around you, but you need support yourself. You need someone to bounce ideas off. Someone to give you direction when you're stuck. Someone to pump you up when things get tough. And someone to tell you like it is when you need to change something.
This may not all be from one person. So, build yourself a strong support network. I now have about three to four people in my life to provide this for me. Make sure you know how to feel good about your own value in your work. Remember those team stats of my own engineering team that I shared at the beginning, and the super cool work that teams have done at MetaLab.
When I'm feeling imposter syndrome or I'm not even sure what I've accomplished in the week, I look back to that and consider how my leadership has contributed. And I think this is the most hard earned lesson myself, being more direct about feedback. Especially earlier on in my leadership journey, I would be ready to be clear. But when faced with that team member who I cared about so much, I would default to wanting to soften the blow.
And this would result in me often being misunderstood and that team member wasn't able to make those necessary changes and that growth that we needed from them. And that wasn't fair. And something that I still struggle with every week that I'm working on. So, post in the chat if you have any ideas for this. How? How do you balance all the things in the week that are important to do for your job with that logistical constraint of a reasonable work day and a balanced life?
Still struggling through that one, but I think many people do. All right. Thank you so much for coming on that journey with me. I really appreciate it. Thank you again. That was really kind of you to follow through. All right. I'll talk to you all later. I'll connect with you soon. Thanks.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
What does it take to lead engineers well when the old playbook no longer works?
Madeline Carson of MetaLab explains why trust comes first, how to earn it, and how to tell whether your engineering team is really healthy.
In short
Madeline Carson, Engineering Director at MetaLab Design, argues that successful leadership of engineers starts with trust, and that trust is earned through small, consistent actions rather than granted by a title. Drawing on 15 years in tech and her path from developer to department leader, she offers five trust-building habits, a litmus test for spotting a healthy team, and an honest look at her own mistakes.
Key takeaways
The skills and actions to successfully deliver projects as a leader.
How to leverage your own natural skills and abilities to lead.
The holistic aspects of engineering leadership, including project delivery, stakeholder management and team management.
How to lead the growth of your engineers on and off project.
From the only woman in class to engineering director
Carson studied electrical engineering and only discovered the gender gap at her first class, where she was the only woman out of 40 men. Early programming jobs showed her she could excel, but also that she would not be given the benefit of the doubt. While preparing the talk, she worried that describing these experiences might sound like complaining, then chose otherwise: "I've decided not to shy away from talking about my real experiences as a woman in tech." (3:17)
At MetaLab, a digital product accelerator, she grew from developer to engineering lead to engineering director, a role she has held for over four years. She describes making the first commit on Notarize's back end and working with design on Calvin Klein's e-commerce redesign. Her first lesson is about recognising her own work: "If you're genuine in your pride and your outcomes, it isn't bragging." (5:23) As she cited, 45% of MetaLab's engineering leadership are women, including the CTO and herself.
Why the old playbook no longer works
Carson sets the scene with a pandemic, the great resignation, divisive politics and the prospect of a global recession. People's expectations of their employers have shifted, and hers have too. "The same old management tactics that we grew up with aren't going to cut it." (6:20)
Engineers are balancing burnout and mental health while growing skills in a new talent market and delivering for clients who face their own pressures. Her conclusion is that leaders now have to offer both care and rigour: "We need more care, kindness, and technical strength and output than ever before." (6:44)
Trust first, then five habits that earn it
Healthy, high-functioning teams do not happen by accident, Carson says, and leaders cannot rush into a new team making asks and changes. The foundation is trust. She points to her own CTO: because they have shared context and listened to each other, Carson takes on projects she is not keen on, confident the request serves her growth or the organisation. "Trust doesn't just happen. It's earned through actions and time." (8:46)
She then walks through five actions:
Get to know your team beyond the code. In coaching sessions she does not accept "things are good" and instead asks what each developer is most proud of and most frustrated by that week.
Listen, take action and follow up. Help people dig into the root of a challenge without solving every problem for them.
Be kind, not nice. Have the tough conversations, gather the full picture first, and remember that "It's not what you say, but it's what they hear." (11:44) She delivers feedback live, then sends a written summary, and gives positive feedback as deliberately as constructive feedback.
Roll up your sleeves when they need help. When a lead was stressed by missing project milestones, she spent 30 minutes on a screen share starting the document from an old template, and the lead finished it.
Take ownership of your mistakes. She finds this one hardest as a woman who has spent years proving she is capable, yet it builds trust and respect and creates a learning culture where people grow and get promoted faster.
The payoff is honest coaching conversations in which problems surface early, before projects fall behind or people quit.
A litmus test for a healthy team
Carson shares the checklist she uses to tell whether her leadership is working. Her starting point is a warning: "You can't just measure the output because it isn't a good long term indicator." (16:57) Good output without the right signals will taper off, or the team will crash and burn.
Her signals are that you hear about risks and mistakes early, regular feedback is happening, you are not necessary in the day-to-day because others have grown into your areas, teams deliver high-quality work, and everyone, including the leader, lives a balanced life where hobbies and vacations are not burnout necessities. On team strength she is direct: "No matter how good they are, that superstar developer is not going to be as effective long term as that well-oiled machine of a highly functioning team." (17:47)
Owning her own mistakes
Carson closes by applying her fifth habit to herself. Leaders spend so much time supporting others that they forget they need support too, so she now relies on three to four people who give her ideas, direction, encouragement and honest challenge. When imposter syndrome hits, she looks back at her team's results to remember her contribution.
Her hardest lesson is about directness. Early on, she softened feedback for team members she cared about. "And this would result in me often being misunderstood and that team member wasn't able to make those necessary changes and that growth that we needed from them. And that wasn't fair." (19:51) She admits she is still working out how to fit everything important into a reasonable workday and a balanced life.
Watch the talk
"How to become a successful leader of engineers" by Madeline Carson, 21 minutes: https://www.womentech.net/video/how-become-successful-leader-engineers-madeline-carson
About the speaker
Madeline Carson is Engineering Director at MetaLab Design, where she co-leads the Engineering Department and supports the growth of engineers in web, full-stack, iOS and Android. She was recognised in 2017 with a national Canadian 30 software developers under 30 award and has contributed to shipping products such as Notarize, Walmart and Tempest.
Questions this talk answers
What foundation does a new engineering leader need before making changes?
How should a leader open a one-to-one coaching session with a developer?
How can a leader give feedback that is clear and kind?
When should an engineering leader roll up their sleeves and help?
How do you know if an engineering team is healthy?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Five trust-building actions
Healthy team litmus test checklist
Kind, not nice
Cite this talk
Madeline Carson. "How to become a successful leader of engineers." WomenTech Network, 2022. https://www.womentech.net/video/how-become-successful-leader-engineers-madeline-carson