Three layoffs, five new managers, three reorgs: chaos is the normal job
Over two to three years, one engineering leader lived through roughly three layoffs, two strategy shifts, five new managers and three reorgs, each pushing her team a step backwards while the business still needed results. Swathi Sundar, Head of Scientific Modalities Engineering at Benchling and formerly of Uber and Microsoft, has kept teams delivering through all of it. So how does a leader keep executing when there are no clear answers?
Get a four-step playbook for leading a team through layoffs, reorgs and strategy shifts
Swathi Sundar, Head of Scientific Modalities Engineering at Benchling, argues that layoffs, reorgs and strategy shifts are a normal part of engineering leadership rather than rare events. She offers a four-step approach to keep teams delivering through change: check your pulse, communicate openly, strategize and pivot, and execute effectively, with practical tactics such as confidence-rated estimates and process-led status tracking.
“I did want to echo this quote, which is lead from the heart, not from the hurt. This is because as a leader, you have a multiplier effect on your team.”
“But talking about deadlines, talking about timelines, the key thing is, all deadlines and timelines are set up by humans. So everything is negotiable.”
What you will learn
Assess your own reaction to a change and gather context from your manager, skip-level, peers and an outside network before asking your team to align.
Run post-change team meetings as safe spaces for emotion, and close them with agreement on what can be controlled next.
Replace implicit assumptions about delays with explicit, written agreements and reset expectations with stakeholders.
Share estimates and decisions with a confidence percentage and say what it would take to reach higher confidence.
Negotiate scope, staffing or timelines early, and use a lightweight daily process to track progress without adding stress.
Key takeaways from the speaker
How to support your teams through changes
What strategies can you deploy as a leader to execute towards your goals when there is so much chaos
Taking care of yourself and your team during uncertainties
Details
Level
Intermediate
Format
Talk
Technical depth
Non-technical
For
People manager, Executive
Length
20:26
Published
June 2023
Questions this talk answers
What should a leader do when she does not agree with a company decision she must roll out?
Gather context from her manager, skip-level, peers and an outside network, then take a stance. If she still cannot credibly deliver the message, as with a remote leader enforcing return to office, she can lean on her manager or HR to set the tone.
How much context should a manager share with her team during a period of change?
As much as possible, with transparency. Sundar found that withholding context to shield people led to anxiety, gossip and outside narratives on forums like Blind.
What is the real purpose of the team meeting right after a change?
It is a psychologically safe space for people to share reactions and emotions, not a forum to answer every question. It should end with a clear focus on what can be controlled next and agreement on the path forward, not consensus.
How can a leader give estimates when she lacks full information after a layoff or strategy change?
Use Jeff Bezos' 70% rule and share the decision with a confidence percentage, explaining the reasons and what it would take to reach 90% confidence.
How can a manager ask for status after layoffs without signalling performance concerns?
She does not ask directly; she leans on a process, such as a 15-minute daily meeting to review items, assign owners and follow up.
About this talk
From recent layoffs, recessions, covid, to leadership/ management/ roadmap/ people changes, there is so much that happens in the life of an engineering leader . These are "unprecedented changes", or are they? As a leader, you face a lot of changes that are preceded by other changes. It's your job to not only manage yourself, but also your team members. How can you continue to execute when there is so much noise? What can you do to make sure your team is not only surviving but thriving through the chaos? Come hear about strategies that you can apply to help your team to march forward towards their goals while taking care of themselves.
Why the post-change team meeting is a safe space (72 s)
Share decisions with a confidence percentage (80 s)
Every deadline is set by humans and negotiable (67 s)
Speaker 1: Hello, everyone. Thank you for coming to my session, Executing in Times of Chaos. Speaker 1: I'm Swathi. I'm currently an engineering leader at BenchLink. Before that, I used to be at Uber and Microsoft. Let's dive right in. Chaos. There is so much that happens in the life of an engineering leader. Changes are not actually as uncommon or unprecedented as people think it is. Personally, for me, these are the subset of changes I've been through over the last two to three years. Been through roughly about three layoffs, two strategy shifts, five new managers, and three reorgs over the course of two to three years. Every change affects me and my team. And I'm sure you all have gone through your fair share of chaos in
the last couple of years too. So if you are comfortable sharing, how has your journey been? How have you been navigating chaos in the chat? Definitely go for it. But something that's common about chaos is each of these changes has an effect on me and my team. It basically takes a step backwards from where we are and what we are doing and makes us pause and figure out what do we do next.
So chaos by definition means it's going to be ambiguous, it's going to be unpredictable, it is going to be out of control. It also means there are no clear answers. There are no known outcomes that you can just follow the rulebook for. But what can you do in that case to not only support yourself, but also to support your team, not only to help them survive, but actually thrive through the chaos.
How can you continue to execute when there is so much noise that's happening? Let me share four steps to follow as a leader to cut through the noise and to continue to deliver value for the business. One is check your pulse. That's the first and foremost. You have to wear your oxygen mask before you can help others. If not, the entire team is going to be drowning.
Second, communicate openly. Communication is key. What you say needs to come out with conviction and clarity. And main thing here is transparency. Third, strategize and pivot. Things have drastically changed. What used to work even days or weeks before might not work anymore. So you need new ideas, you need new approach, and you definitely need a new attitude to face that. And finally, execute effectively.
At the end of the day, people of your team needs to feel that they've both accomplished and appreciated and that there is a clear goal for them to absolutely need the results. So let's dive in, go through each of these steps individually and talk through what can you do as a leader. First of all, check your pulse. Self-care is important. You need to assess how you're feeling, what your reactions to the change are. And mainly, are you bought into the change? Are you aligned? You need to take a stance.
You cannot bring your team forward if you're not aligned on the changes. So I would say gather as much context as you can. Talk to your manager, talk to your skip, talk to your peers in the company. All of those networks that you've built within your company or your organization. You'll be surprised to find out the different kinds of context that all of them have.
And just chatting with them, you can actually gain a lot more just other than from what you get from the top-down narrative. Next one, I would say, lean in on your personal and professional network. I personally have a group of like engineering managers, directors, senior managers that I go to who are my friends, but they are also part of like different companies, not just my own.
The reason for leaning on them is they provide different perspectives. Those different perspectives helps to figure out what to do next, but they also helps me to validate. Does it resonate with what I'm hearing internally? Is there a dissonance? Is this how companies go through? Just understanding what people have gone through before, figuring out, does that align with what I'm looking at my company?
I think that is definitely helpful. Apart from that, you need a place to rent, you need a place to rent, you need to let it out too. And it's always better to do that with somebody outside the organization rather than with somebody inside the organization. So once you've kind of gone through the process of gathering the context, the next thing is taking a stance, you need to be aligned to march forward.
There might be cases, I'm sure, when you don't feel aligned towards the overall decision. I have an example. I'm a remote employee. For me, it doesn't feel right to enforce a three-day return to office policy with my team. That would be ridiculous. Like, I'm not going to be in the office. And then how can I enforce somebody to come into the office?
In those situations, what I do is I lean in on my manager or the HR to help convey the message across. I can lean in on them to set the tone. I can lean in on them to navigate these special situations. Once you're aligned, once you've taken a stance of like, yes, this change makes sense or what is happening across the company, I understand the meaning behind it.
Then the next thing that I have historically made a mistake on is not sharing that enough context with people on the team. Generally, I do that with a good internet because I'm trying to balance between how much context to share with people versus how much they want to protect and shield them from the trash. As a leader, I'm always watching out for them and I don't want them to go through noise.
But then what I realized is if I don't share a lot of context, if I'm not transparent with my team, with the half-baked information that they get, there's anxiety built up. People reach out on like different forums like blind, read their own things, and they end up making a judgment which is very different from the narrative. Sometimes, innocent things come out as like, oh, this is politics or things where there's a clear reason behind why your organization made a decision, it leads to gossip.
So, personally for me, I've leaned in on sharing as much context as I can with as much transparency as I can with my team, knowing, understanding that they have a similar or a higher level of maturity or EQ compared to me. So, if I can be trusted with the context, more often than not, they can be as well.
I did want to echo this quote, which is lead from the heart, not from the hurt. This is because as a leader, you have a multiplier effect on your team. If you are hurt, your team will be hurt and that will actually affect the overall execution. Second, communicate. Communicate openly. Communicate transparently. Most of this should be fairly obvious to folks, but there are a couple of things that I wanted to highlight here.
Whenever there is a change, what I used to do is I set up an immediate team meeting to get people together, to give them context. Also, using that forum as an opportunity to shape the narrative of the situation. In those meetings earlier, I used to feel pressure to answer every single question or every single comment that came up in the meeting.
I used to think incorrectly, of course, that that's a forum for cascading the message or to reinforce the message. But then I realized the purpose of the meeting is not that. It is to provide a safe space within a smaller group of people where there is psychological safety, where people can share their reactions, be open with their emotions.
It's a place to go to share their perspectives. It's okay if things get heated. It's okay if it gets emotional. There have been times where I have become emotional, I've teared up. That's okay because at the end of the day, your team, your organization have gone through a change or a chaos. It's okay to be human and to react in unpleasant, unexpected ways, whichever that suits for you.
But the main key part is, once the emotions is out of the way, always, always end the meeting with a clear focus on what can be controlled next. You need not try to strive to reach for a consensus-based decision here. All you are aiming for is an agreement on the path forward and a willingness to engage in the next days or months or weeks to follow.
It's natural that any time when your team or organization goes through a chaotic period, it has an impact on the culture. But instead of trying to shape it, I'd say let the chaos shape the culture. People are going to think differently. New processes are going to emerge. That is expected. So let the chaos shape the culture rather than you trying to shape it during the time of chaos.
Third one, strategize and pivot. Any time, any time when there's a chaos, it needs some kind of a re-plan. It could be changes to your product. It could be changes to your process. It could be changes to people. It doesn't matter. At the end of the day, there's a re-plan which is needed and you need to refocus.
As a leader, you should have clarity and justification behind every investment that your team is working on. Be it short-term or long-term. One thing I see people making mistakes here is, as much as you want people to align and march forward in the new direction, most immediately. The truth is, it takes a while for people to align and account for that buffer.
Account for people's time to come up with the new idea, do some research. Probably, if they are engineers, do some spikes. Figure out what needs to be done next. There is going to be a buffer time or amount of period where there's going to be ambiguity. And that's okay. Just account for the time when you're planning for the next steps.
You need to be fully brought into the new plan before you can expect them to execute, which makes sense. The key thing here is, do not just rely on top-down narrative and top-down directions. Engage with the team for coming up with new modes of operation. Brainstorm with them. Include them in discussions. Get their suggestions. Prioritize their suggestions.
And create a plan. When you're creating a plan, also explain to them why you selected some parts of the suggestions and not. The other mistake that I've seen people do, I've made this in my past, is to make implicit assumptions. You see you are going through chaos. You kind of assume that, oh yeah, either folks are bought into the new plan or your leadership or your stakeholder team or your product team, people understand that there's going to be delays.
You kind of assume that, yeah, people are not going to be 100% effective. Let's say, maybe you lost an engineer. So it's obvious that project is going to slip. Or you lost the product manager. Obviously, there's not going to be enough clarity on the product. You assume a lot of those things. But unfortunately, all those assumptions, if you have not explicitly built agreements with people or reset expectations with them, people are going to assume that everything is normal.
So key thing here is avoiding implicit assumptions and explicitly building agreements with stakeholders and folks. And also, maybe even writing it down, explicitly writing down the reset new expectations on what's going to happen to the things that you're driving. I'd say be flexible, be adaptable, be open to new ideas. It's not going to be easy. It's not going to be easy to, let's say, shut down a project that people have been working on.
It's not going to be easy to move people from one team to another, from one project to another. Especially in terms of chaos, it's also going to be harder as leaders to give feedback to folks. Because there's always a fear that they might interpret it differently or you're going to add more anxiety or stress for them. It's natural to want to stay in your comfort zone when situations become uncomfortable, but please don't.
I think that is just a trap that people fall into. Just be flexible, be adaptable, be explicit, and be open to new ideas. And when you're making decisions, trust your instincts, be decisive. You are not going to have a lot of time after a big change has happened in your company to figure out everything at the same time.
So you might not have 100% clarity yourself before you were asked to come up with, let's say, estimations or something for your project. At those times, what I do is follow Jeff Bezos' 70% rule. That is making a decision with 70% information and the rest 30% rely on your instinct, your judgment, and your experience. In that, I would call out that there's a possibility that I could be wrong or you could be wrong in that judgment.
So one tip I have for folks there is when you are sharing a decision or a judgment, share it with the confidence percentage. So for example, let's say somebody is asking me for a long range planning or estimate for my team right after the layoff or right after they have changed the product direction. I basically go to them and say, hey, I'm 50% or 60% confident we will ship this project.
Here are the X, Y, Z reasons for it. And also, I'll say, if you would like me to build a 90% confidence on this judgment or decision, this is how long it's going to take. And here are the next steps. Kind of just laying out your confidence level, laying out what you're going to do next. And just checking with your leadership, your stakeholders, people around you in terms of, do they want you to have full clarity before you make the next step?
I think that's helpful. Goes back to the point of just explicitly building agreements and resetting expectations with people. And finally, executing effectively. This technically should be straightforward if you have been doing step one, step two, and step three. But regardless, you should continue to follow good execution practices, your processes that you have with your team. But there are a couple of things that I wanted to call out here.
Similar to what we talked before, every time there's a change or a chaos, you need to revisit your timeline. Do not assume that things are going to go the same way before. You might have lost folks to layoffs, or people might have left due to attrition. New leader came in, they introduced a new process, or there's a change in strategy, which might mean you completely need to go back to the scratch, go back to your dying boat starting from scratch.
But the real effect is, it is going to affect the timelines that you previously communicated, and that's going to matter. But talking about deadlines, talking about timelines, the key thing is, all deadlines and timelines are set up by humans. So everything is negotiable. There are multiple ways to negotiate or de-risk a project. You can negotiate with your product for a smaller scope.
You can negotiate with your manager for adding more people to project or team. You can negotiate with your customers, ask for additional time or extended timelines. Or if none of that is possible, just reset expectations with the people that you're working on. Maybe you might want them to work more hours or extra hours than you initially expected.
Just set an expectation of how long or how temporary that is going to be. One thing I noticed is the leadership team always, always appreciates early heads-up. When things are going to go south, it's always better to communicate it earlier than to surprise or shock it at the later time. Let's say in a chaotic situation, layoffs, which is pretty common these days.
People are in higher stress. One thing that leaders find it hard is, how do I ask for status? How do I ask for progress without inducing more stress or negatively signaling performance to people? You completely understand as a leader, the team just went through a tumultuous period. And now you feel hesitant to ask them for updates, which is totally fair.
The key point is you don't. You as a manager, you are not going to go ask for deadlines or estimates or whatever it is. What you want to do is lean on the process, which will help you get the answers to those. For example, a 15-minute meeting every day to review through the list of items. Assigning owners, following up on that the next day for the next 15 minutes.
Just leveraging on that process. You do that until you get to the end goal of what you want to achieve. That would be more helpful because at that point, it is seen as, hey, this process is going to help me and my manager figure things out. Rather than my manager is asking me for what needs to be done.
The other point here is your relationship with stakeholders is key. This is something you build early on from your time at your company. Those coffee chats, those one-on-ones, they all should come in handy. When now you go and say, hey, things are changing, people will have that empathy and understanding for what's happening. Finally, celebrate the small wins.
This adds to the motivation and encouragement for folks who are doing and just celebrate, taking time to celebrate even the smallest progress helps for folks. Another quote that I truly resonate with, wartime CEO violates protocol in order to win. It's tempting to follow all the processes that you used to do before, but it's a different time. It needs you to do things differently.
So there might be tradeoffs that you can make. So for example, in my past, I've said, oh, let's not do the end-to-end test right now. Let's just get into beta testing, but parallelly do the end-to-end test, which obviously is going to break the definition of done rules for my team. But that is what is needed when I've already lost an engineer or so.
But that's just an example. Be judicious in terms of what rules you're breaking, how that will impact you and the team. But do not hold back if that's the right move to deliver results. So finally, here's the four steps. Definitely check your pulse. You want to be aligned before you get your team aligned. Communicate openly and transparently.
Strategize and pivot. And finally, execute effectively. Hopefully this was helpful. I just want to leave you with this quote. In the midst of every crisis lies great opportunity. I hope all of you find that for your team and for yourself. All the best. If you have any questions, leave it in the chat. If you have any comments, do share it.
I'm happy to connect with folks offline as well. If not, have a great evening, night and take care. Thank you.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
How do engineering leaders keep teams delivering through layoffs and reorgs?
Swathi Sundar of Benchling offers four steps for leaders who must execute while the ground keeps shifting.
In short
Swathi Sundar argues that change is a normal condition of engineering leadership, not a rare exception, and that leaders can keep delivering through it with four steps: check your pulse, communicate openly, strategize and pivot, and execute effectively. Her advice pairs self-care and transparency with practical tactics such as confidence-rated estimates, explicit written agreements and process-led status tracking.
Key takeaways
How to support your teams through changes
What strategies you can deploy as a leader to execute towards your goals when there is so much chaos
Taking care of yourself and your team during uncertainties
Chaos is the job, not the exception
Sundar opens by challenging the idea that organizational upheaval is "unprecedented." She shares her own record from recent years: "Been through roughly about three layoffs, two strategy shifts, five new managers, and three reorgs over the course of two to three years." (0:00)
Each of those changes, she explains, pushes a team a step backwards and forces a pause to work out what comes next. By definition, chaos is ambiguous and unpredictable, with no rulebook and no known outcomes. The question she sets out to answer is how a leader helps her team not only survive that, but thrive and keep delivering value. Her answer is four steps, starting with the leader herself: "You have to wear your oxygen mask before you can help others. If not, the entire team is going to be drowning." (2:08)
Check your pulse before you lead others
The first step is self-assessment. Sundar asks leaders to notice how they feel about a change and, above all, whether they are aligned with it, because a leader cannot bring a team forward from a position of doubt. She recommends gathering context from a manager, skip-level and peers, and leaning on a personal network of managers and directors at other companies who can offer different perspectives, help validate what is heard internally and provide a safe place to vent outside the organization.
When alignment is not possible, she is candid. As a remote employee, enforcing a three-day return-to-office policy would not feel right to her, so in such cases she leans on her manager or HR to convey the message and set the tone.
She also names a mistake she made: withholding context to shield her team. Half-baked information produced anxiety, gossip and outside narratives on forums like Blind. Her conclusion is to trust people with the full picture: "So, if I can be trusted with the context, more often than not, they can be as well." (6:48) She closes the step with a line she wants every leader to carry: "I did want to echo this quote, which is lead from the heart, not from the hurt. This is because as a leader, you have a multiplier effect on your team." (7:12)
Communicate to create safety, then focus
After any change, Sundar convenes an immediate team meeting. She once felt she had to answer every question there, but came to see its real purpose as a psychologically safe space where people can share reactions and emotions, including her own. Emotion is allowed, but the meeting has a firm ending: "But the main key part is, once the emotions is out of the way, always, always end the meeting with a clear focus on what can be controlled next." (8:49)
The goal is not consensus but agreement on the path forward and a willingness to engage. She also advises leaders to stop trying to control culture in these moments: "So let the chaos shape the culture rather than you trying to shape it during the time of chaos." (9:15)
Strategize and pivot without hidden assumptions
Every disruption, whether to product, process or people, needs a re-plan. Sundar urges leaders to have clear justification for every investment, to build buffer time for people to research, run spikes and align, and to involve the team in shaping the new plan rather than relying only on top-down direction, explaining why some suggestions were chosen and others were not.
Her sharpest warning is about implicit assumptions. Leaders often assume stakeholders understand that losing an engineer or a product manager means delays. Unless agreements are made explicit, and ideally written down, people assume everything is normal.
For decisions made under uncertainty, she follows Jeff Bezos' 70% rule and adds her own tip: "So one tip I have for folks there is when you are sharing a decision or a judgment, share it with the confidence percentage." (13:54) She might tell leadership she is 50% or 60% confident a project will ship, give her reasons and explain what it would take to reach 90% confidence.
Execute effectively when the rules change
The final step builds on the first three. Every change means revisiting timelines, and Sundar reminds leaders that these are not fixed: "But talking about deadlines, talking about timelines, the key thing is, all deadlines and timelines are set up by humans. So everything is negotiable." (15:38) Leaders can negotiate smaller scope, more people or extra time, or reset expectations with the team about temporary extra hours. Leadership, she notes, always appreciates an early heads-up rather than a late surprise.
To track progress after a layoff without adding stress, she suggests leaning on process, such as a 15-minute daily review of items with clear owners, so updates feel like shared problem-solving rather than a manager chasing deadlines. Strong stakeholder relationships built earlier through coffee chats and one-on-ones pay off now, and celebrating small wins keeps motivation up. She ends with permission to break rules judiciously: "Another quote that I truly resonate with, wartime CEO violates protocol in order to win." (18:13) Her example was moving to beta testing while running end-to-end tests in parallel after losing an engineer.
Watch the talk
"Executing in times of chaos" by Swathi Sundar (20 minutes): https://www.womentech.net/video/executing-in-times-chaos
About the speaker
Swathi Sundar is Head of Scientific Modalities Engineering at Benchling, where she leads software development teams building next-generation SaaS platforms for the life sciences industry. She previously worked as an Engineering Manager at Uber and a Senior Software Engineer at Microsoft, and is passionate about mentorship, teaching and recruiting.
Questions this talk answers
What should a leader do when she does not agree with a company decision she must roll out?
How much context should a manager share with her team during a period of change?
What is the real purpose of the team meeting right after a change?
How can a leader give estimates when she lacks full information after a layoff or strategy change?
How can a manager ask for status after layoffs without signalling performance concerns?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Jeff Bezos' 70% rule
Definition of done
Cite this talk
Swathi Sundar. "Executing in times of chaos." WomenTech Network, 2023. https://www.womentech.net/video/executing-in-times-chaos