There is a management philosophy that has quietly taken over large portions of American tech culture, and it goes roughly like this: the environment is chaotic, the pace is fast, priorities are shifting, resources are constrained, and the team needs to be resilient enough to absorb all of it and keep delivering. Adaptability is celebrated. Ambiguity tolerance is treated as a core competency. “We’re all figuring it out together” gets said with an energy that implies it is a feature, not a bug.

And then those same organizations are genuinely baffled when their best people leave, when engagement scores are low, when nobody can explain why a straightforward initiative is taking twice as long as planned, when the same problems keep resurfacing despite repeated attempts to fix them. The chaos has costs. We are just not accounting for them properly, because we have normalized expecting people to absorb them instead of leading in a way that reduces them.

This is a piece for leaders who are ready to stop doing that. Not because it is the nice thing to do, though it is. Because it is the high-performance thing to do, and the evidence is overwhelming that teams operating with appropriate support, clear structure, and genuine psychological safety outperform teams that are just grinding through chaos on sheer determination and fear of disappointing someone.

What “Absorbing Chaos” Actually Costs

The cost is rarely visible on any dashboard. It shows up in ways that get attributed to other causes. Decisions that take longer than they should because nobody is sure what the current priority actually is. Rework that happens because the requirements shifted and the team found out too late. Meetings that circle the same issues without resolution because the underlying ambiguity was never addressed. Brilliant people operating at 60% of their capacity because the other 40% is being spent on navigating unclear expectations, managing interpersonal friction that structure would prevent, and recovering from the cognitive load of chronic uncertainty.

The talent cost is the one that should alarm every technology leader. In a labor market where skilled technical people have real options, what keeps someone at an organization is not just compensation or interesting work. It is the quality of their day-to-day experience. Whether they know what is expected of them. Whether they have what they need to do the work. Whether they feel like their effort is channeled toward something meaningful rather than spent fighting organizational friction. Leaders who create that experience keep their people. Leaders who ask their people to absorb chaos lose their best ones first, because those are the people with the most options.

What Structure Actually Is

Structure is one of the most misunderstood concepts in organizational leadership. In tech culture especially, there is a persistent belief that structure and agility are opposites: that adding structure slows things down, creates bureaucracy, and reduces the team’s ability to respond to change. This belief is wrong, and it is costing organizations dearly.

Structure is not bureaucracy. Bureaucracy is process for its own sake, form over function, steps that exist to be completed rather than to add value. Structure is clarity. Clarity about who makes what decisions. Clarity about how work gets prioritized when there are more things to do than people to do them. Clarity about what “done” means for a given piece of work. Clarity about what to do when a blocker arises or a priority conflicts. Clarity about what is expected of each person in the organization and how their success will be assessed.

This kind of clarity does not slow teams down. It speeds them up. Because when people know what is expected of them, when they know how decisions get made, when they know what to do when something goes wrong, they can focus their energy on doing the work rather than on figuring out the rules of engagement every single time. Structure is the foundation that makes speed possible. Chaos is not a faster version of the same thing. It is a drag on performance that is wearing your team out quietly and consistently.

The Specific Structures That Matter Most

Decision rights are the single most powerful structural element a leader can clarify. In most technology organizations, it is genuinely unclear who has authority to make which decisions. People escalate things that should not need escalation. People make decisions that turn out to require buy-in they did not know they needed. Energy gets spent on politics and alignment conversations that would be unnecessary if the decision rights were explicit. Clarifying who can decide what, at which level, with what level of consultation required, is not exciting work. It is enormously valuable work, and it pays organizational dividends immediately.

Meeting structure is the second most impactful area. Not how many meetings, though that matters. How meetings work. Every recurring meeting should have a documented purpose, a clear agenda, an owner who is responsible for keeping it useful, and a regular review of whether it should continue. The absence of this structure means your calendar is an accumulation of historical commitments that nobody has reviewed since the circumstances that prompted them changed. That is not a schedule. It is an organizational artifact. Reclaiming it is an act of leadership.

Communication norms are third. When do people need to be informed versus consulted versus deciding? How are decisions documented and communicated so that the people who need to know actually know, without being copied on every email thread regardless of relevance? How does escalation work, and who is responsible for it? In the absence of explicit communication norms, the default is email overload, Slack anxiety, and a pervasive feeling that everyone is both over-communicated with and chronically under-informed. These are solvable problems. They require structure to solve.

What Support Actually Looks Like

Support does not mean protecting people from difficulty. Difficult work is where growth happens, and effective leaders create challenges deliberately because they want their teams to develop. Support means ensuring that the difficulty people face is the difficulty of interesting, important work, not the difficulty of navigating organizational dysfunction, compensating for inadequate resources, or managing unclear expectations while simultaneously trying to deliver on them.

Support looks like removing blockers. Not in theory, as something leaders say they do, but actually and specifically. When a team member tells you something is blocked, you work on unblocking it, and you follow up. You do not just note it and move on. You close the loop. The habit of following up on stated problems is one of the most powerful trust-building behaviors available to a leader, and it is one of the most commonly skipped.

Support looks like psychological safety that is genuine rather than performative. When you say “I want to hear the bad news early,” your team will believe you only if the first few times someone brings you bad news, you respond with genuine curiosity and gratitude rather than visible frustration or implicit blame. What you do with the first few hard truths determines whether your team brings you the rest of them. This matters more than almost any other leadership behavior during change initiatives, because change initiatives are full of things that are not going according to plan, and you need to know what they are.

Support also looks like paying attention to load. Not just deliverables and deadlines, but the overall cognitive and emotional demand on your team members. Women in tech often carry disproportionate loads beyond their formal responsibilities: mentoring others, sitting on diversity committees, managing the interpersonal dynamics of teams in ways that are never in any job description. Effective leaders see this invisible labor, name it, and account for it. Not with a token acknowledgment, but with actual consideration of capacity and an active effort to ensure that the invisible work is either resourced appropriately or redistributed more equitably.

Sanity as a Leadership Outcome

This is the part where I want to be very direct about something that often gets lost in the high-performance conversation. Sanity, the ability of your team members to do their best work without destroying their health, their relationships, or their sense of self in the process, is a leadership outcome. It is your responsibility. Not your team’s individual responsibility to manage through better self-care habits, and not a wellness program’s responsibility to address with yoga subsidies and mental health days.

When a team is consistently working unsustainable hours, it is almost never because the individuals on the team are managing their time poorly. It is because there is more work than can be sustainably done with the available resources and the current ways of working. That is a leadership problem. The solution is not to encourage everyone to take more breaks. It is to address the underlying mismatch, which means either adding resources, reducing scope, improving efficiency, or some combination of all three.

Leaders who create sane working environments do not do it by telling people to go home on time. They do it by making choices that ensure going home on time is possible. They make scope decisions. They make prioritization decisions. They say no to stakeholders on behalf of their teams. They are visible in protecting the team’s capacity from demands that are not worth the cost. This is what it means to lead people, not just to manage their output.

The Change You Can Start Today

If you are a leader reading this and recognizing your organization in what I have described, the change does not require a new initiative, a consulting engagement, or an all-hands meeting. It starts with a decision to take personal responsibility for the structural environment your team operates in. And then it continues with a series of specific, concrete actions: clarifying a decision right, removing a blocker, canceling a meeting that no longer serves its original purpose, asking a team member what would make their work more sustainable, and then actually doing something with the answer.

The chaos that your team is absorbing right now is not inevitable. It is, in most cases, a product of accumulated decisions that were each reasonable in isolation and collectively unsustainable. It is also, in most cases, a product of a leadership culture that has not yet decided that the experience of doing the work matters as much as the output of the work. You can decide that it does. Today. And every decision you make from that point forward, informed by that belief, is a vote for the kind of organization that actually sustains its people, retains its talent, and delivers results that do not require burning everyone out to achieve. That is not a soft goal. It is the highest-leverage leadership investment available to you right now. Please make it.