The Leadership Umbrella: Protecting Teams Under Pressure
What a team loses when its protector leaves
When Tanu Tiwari moved on from the team of six she managed in London, the impact was immediate. Within months, every member of that team had resigned. She only understood why when she got them on a call and asked what had gone wrong. One of them told her plainly: she had been the team's umbrella, the one who kept the mess from above from landing on them. They hadn't realized how much she was absorbing until she was gone.
That story isn't unique to one manager or one industry. It points to a broad problem in how organizations develop and support their frontline leaders. Gallup's 2026 State of the Global Workplace report puts global employee engagement at 20 percent, the lowest level since 2020. Manager engagement has fallen further, from 31 percent to 22 percent since 2022.
Numbers like that tempt executives toward structural fixes. They restructure departments, roll out new software, or launch company-wide culture initiatives. Tiwari, who spent 18 years inside global technology and Fortune 500 companies before becoming a certified leadership coach, argues that these big-picture interventions keep missing. Gallup describes the engagement problem well, but a survey can't prescribe the fix. In her view, the fix happens one leader at a time.
When organizational pressure reaches the front line
A lot of what separates effective leaders from destructive ones comes down to how they handle pressure from above. Every leader under pressure deals with a steady stream of shifting directives, budget constraints, and executive anxiety. What matters is whether the leader acts as an umbrella or a funnel. We break down the two modes in more detail in the leader who absorbs pressure so their team doesn't.
A funnel takes the stress, ambiguity, and panic coming from the executive level and passes it straight to the team. In a meeting, that looks like a manager who shows up unprepared, leads with a sense of crisis, and demands immediate results without context or resources. The team sorts out the chaos while also carrying the weight of their manager's unmanaged anxiety. Focus suffers and errors become more likely, which is an unacceptable risk anywhere precision matters.
An umbrella absorbs the turbulence. They take the raw pressure from above and process it before it reaches the team. In a meeting, that leader gives clear direction, filters out irrelevant corporate noise, and defends the team's ability to do focused work. They turn executive panic into structured, actionable tasks. Protecting your team from distraction is a core part of the job, and most of it is work nobody sees, the kind that never shows up on a spreadsheet.
Three filters for management decisions
Protecting a team is simple in concept and hard to do when the pace is high. To make it practical, Tiwari uses three conditions: people stay engaged when they feel seen, significant, and safe. Any management decision, process change, or conversation can be run through those three filters to judge whether it will help or hurt the team.
Making people feel seen
Being seen at work takes more than basic recognition. It means the leader understands the specific daily friction their team deals with. Many teams work with complex equipment, strict regulatory requirements, and tight tolerances. A leader who sees their team works to remove the bureaucratic hurdles that make those jobs harder. They acknowledge how hard the work is and recognize specific achievements instead of offering generic praise.
That awareness builds trust between the manager and the front line. When people know their manager understands the realities of their role, they're far more likely to speak up about production issues or schedule slips. Specific recognition drives better decisions faster because it reinforces exactly the behaviors and standards the work requires.
Significance and psychological safety
Significance is knowing how your specific task connects to the larger mission. On many teams the mission is obvious in the final product. Leaders lose it when they let the daily grind of compliance and production targets bury that purpose. Significance means connecting the immediate technical requirement to the outcome it serves, again and again. An engineer who understands how their component protects the people who will depend on it cares more about the quality of that component.
Safety, in Tiwari's framework, means psychological safety as well as physical safety protocols. It's what lets an engineer or floor technician stop a line when they spot a defect without fear of reprisal. Without it, problems go underground and turn into much bigger failures later in production. Building that environment means rewarding people who report errors instead of punishing them. Without psychological safety, other leadership initiatives eventually stall.
The cost of merging identity with role
Failing to keep a boundary between the role and the person carries a serious physical and psychological cost. Tiwari lived it. Her dedication to her job had her working through labor while communicating on the company messaging platform. Five months later she was flying to a trade show and pumping in a stairwell. That was when she realized her identity and her job had fully merged.
This is common among high achievers in demanding industries. Leaders convince themselves that constant availability is what the organization needs. They give up sleep, health, and relationships in the name of commitment to the mission. That level of overextension degrades thinking, emotional regulation, and decision-making. Nobody sustains chronic stress without recovery.
When leaders run on empty, their teams pay for it. A sleep-deprived, burned-out manager can't be an umbrella. They lose the capacity to regulate their own emotions, which makes them more likely to funnel stress and anxiety downward. Burnout is a leadership problem, not a personal failure, and preventing it takes boundaries built into the system. Leaders who don't manage their own energy end up compromising the readiness of the teams they lead.
Technology shifts and corporate accountability
Many organizations are going through layoffs and restructuring. The common explanation from leadership is that AI and automation have made certain roles obsolete.
Tiwari pushes back on that story. Her assessment is that many companies blaming workforce reductions on AI had a business model problem long before the technology matured. AI gave them a convenient outside explanation for poor strategic planning, financial mismanagement, or a failure to adapt to the market.
That's a serious accountability problem. When executives use a technology shift to cover a business failure, they lose trust across the organization. It's the funnel at scale: the consequences of strategic mistakes get passed to the front line while responsibility at the top goes unclaimed. Leaders have to own the real business conditions instead of hiding behind abstractions and buzzwords. Once they see what abstraction hides, they can start rebuilding the credibility they'll need for real technology transitions. Whatever the tools, the job stays the same: communicate honestly, give clear direction, and protect the people doing the work.
Kestryl Edge works with leaders and teams to put ideas like this into practice. See how we work at Kestryl Edge.
Dan Korus, Kestryl Edge founder, publishes The Updraft, a weekly newsletter on leadership, trust, and how teams actually perform. Subscribe here.