In most organizations, senior leaders are expected to make important decisions without having all the information they would like. They identify problems, propose solutions, commit resources, and rely on their teams to help make those solutions successful. When the decision works, the leader is often praised for recognizing what needed to change. Things get more complicated when the decision doesn't work. At that point, leaders aren't just evaluating the results. They're also thinking about everything they've already invested in the effort. Time, money, employee hours, political capital, and personal credibility can all become part of the equation. The longer a project has been running, the harder it can be to step back and ask a simple question: Is this still the right path forward?

Take Lauren, for example. Lauren is an executive overseeing a department that has struggled with slow project completion and inconsistent communication. To solve the problem, she introduces a new project management platform that is supposed to improve accountability and make projects easier to track. The organization purchases new software and dedicates months to implementation and training. Lauren publicly supports the initiative and assures the rest of the leadership team that it will improve performance.

Six months after the rollout, the results aren’t what Lauren expected. Projects are still being delayed, employees are frustrated with the new process, and managers have begun creating their own workarounds to avoid using the system. Rather than making communication easier, the initiative has just added more steps to everyone’s work. Still, Lauren wants to continue defending it. In her mind, the organization has already invested too much to turn back now, and changing direction could make her look like she made the wrong decision. Instead of asking whether the initiative itself is working, she asks the team to work harder at making it work.

The core problem in this situation isn’t that Lauren made an unreasonable decision. The old process wasn’t working, and leadership had a responsibility to do something about it. The problem is that Lauren has started treating the initiative as something that needs to be protected instead of what it really is: one possible solution to a larger problem. Once a leader attaches their reputation to a particular plan, evidence against that plan can start to feel like evidence against them personally. This makes it harder to look at the results honestly and much easier to justify putting even more resources into something that isn’t working.

 How the Sunk Cost Fallacy Keeps Bad Initiatives Alive

Most organizations aren't held back by a lack of ideas. They're held back by an inability to let go of ideas that aren't producing results. This is where the sunk cost fallacy creeps in. The sunk cost fallacy happens when someone continues investing in a decision because of what has already been put into it, even when the current results suggest that continuing will cause more damage. For leaders, those sunk costs might include money, employee hours, training, software, and more. Because none of those resources can be recovered, leaders can feel like they have to prove that the investment was worth it.
By this stage, leaders often stop evaluating the quality of the decision itself. Their attention shifts toward justifying the investment that's already been made.  But what has already been spent shouldn’t determine whether the next dollar, hour, or month should be spent in the exact same direction. Those resources are gone no matter what leadership decides to do next. The more important question is whether continuing the initiative is still the best decision based on what the organization knows today.

The higher someone rises in an organization, the more visible their decisions become. An associate may be able to try a new approach and quietly adjust it when it doesn’t work, where an executive initiative, on the other hand, often requires budgets, presentations, and coordination between multiple teams. By the time it launches, the leader may feel like their credibility is tied directly to its success.

Because of this, changing direction can feel like much more than ending one unsuccessful initiative. It can feel like admitting the leader wasn’t qualified to make the decision in the first place. They may worry that their peers will question their judgment, or that employees will lose confidence in them. When a leader feels like their career is connected to making the initiative work, they may continue supporting it long after the results show that it isn’t working.

Unfortunately, waiting rarely protects the leader’s credibility. In fact, it does the opposite. Employees often recognize a failing initiative long before leadership does. When leadership continues defending it without acknowledging what is happening, employees begin to lose trust. The problem is no longer just that the initiative failed. The bigger problem becomes that leadership is unwilling to admit what everyone else can already see.

 How Leaders Should Respond When an Initiative Isn’t Working

When a new strategy fails to meet expectations, leaders must separate the problem they were trying to solve from the solution they chose. An initiative can fail without meaning that the organization should return to the old way of doing things. Here are 4 steps leaders can take to change direction while still taking accountability.

Changing direction isn’t the same as giving up. Sometimes, it is the most responsible decision a leader can make. By acknowledging the results, separating the problem from the plan, and involving employees in the next solution, leaders can turn an unsuccessful initiative into something useful. The sooner they do this, the sooner the organization can stop spending time trying to save an idea and start putting that time toward actually solving the problem.

 

 In many organizations, high performance can unintentionally hide the early warning signs of burnout. When a team consistently delivers, leaders often assume the system is healthy and the workload is manageable, even when the reality underneath tells a different story. This disconnect becomes especially dangerous for middle managers, who are responsible for translating executive expectations into day‑to‑day execution while also protecting their teams from burnout. Without clear communication about capacity, leaders begin to rely on output as the only indicator of what a team can handle, creating a cycle where strong performance is met with even more work, despite the health of the team behind it. 

Take Ben, for example. Ben has a high-performing team of 5 individuals. They meet deadlines, deliver quality work, and rarely fall behind. On the outside, everything is going perfectly. But behind the high-performing team are excessive overtime hours, burnout, and unsustainable workloads. Ben goes to his executive about expanding his team to meet demands, but after the team is expanded, they’re given another huge project. In the executive’s mind, Ben’s team can handle more work now that they have extra hands, but the reason Ben requested the extra hands in the first place was that his team was struggling with the work they already had. 

The core problem in this situation is executive misinterpretation of performance signals. Because Ben’s team consistently delivers, leadership assumes expanding the team will expand their capacity. They interpret the high performance as, “they aren’t struggling, and therefore they can handle more.” What leadership fails to see is that the team is being held together with unsustainable effort. Long hours might work well in the short term for meeting deadlines and major projects, but over time, this will lead to burnout, losing high performers, and damage trust in leadership.

Every time capacity increases, leadership fills in with more work. This results in a loop of the team constantly being overloaded, no matter how much the headcount is increased. The reason this happens isn’t unfair leaders trying to overload the teams they oversee; it is instead caused by the disconnect between the metrics viewed by leaders and the lived experience of the team. Executives look at the data, and when metrics are good, they have no reason to assume the system is unhealthy. Luckily, the solution to this disconnect is simpler than one might expect. First, the team needs immediate strategies to stop the issue currently at hand, then all parties must find structural changes to prevent this from happening in the future. 

Before focusing on any structural changes, the issue must first be brought to light. Here are 3 easy steps to stabilize the situation.

Step 1: Create a Capacity Report: One of the easiest ways to show your team would thrive with a lighter workload is to quantify that workload with a documented capacity report. This capacity report should show real data that can be used as evidence that the team is over capacity in the first place. This can include hidden overtime (weekends and evenings), tasks currently in backlog, tasks that have been delayed or dropped, and any impact on quality. This way, there is tangible evidence of a team being overworked, rather than having to go by someone’s word.

Step 2: Be Clear about Priorities: Understaffed teams must be very intentional with the work they prioritize, and be able to clearly communicate those priorities as well as their reasoning. Create a simple list of priorities, starting with what you must do (essential tasks), then what you should do (important but deferrable), and finally what would be nice to do. (only if the capacity exists) This way, if the CEO introduces a new task, the team can ask, “What can be deprioritized to make room for this new task?” This forces a conversation about trade-offs and acts as a gentle reminder that no one team can do it all.

Step 3: Make Boundaries Non-negotiable: For a team to be protected from burnout, clear boundaries need to be in place. Chronic overload as a result of skipping breaks and working outside of normal hours accelerates burnout and absenteeism. Having simple team norms, such as mandatory lunch breaks, no weekend work unless there's preapproval, and setting a hard stop time for evening hours, creates guardrails that protect capacity and prevent overextension. 

Leadership’s Job: Structural Fixes

Once the team has stabilized the immediate situation, the responsibility shifts upward. Executives must create the conditions where high performance doesn’t require burnout, hidden overtime, or constant crisis management. Here are some structural fixes to ensure that the organization starts managing work intentionally. 

This forces leadership to make intentional choices rather than unintentionally dealing out too much work.

These metrics give executives a more accurate picture of whether a team is operating sustainably or simply holding things together through overextension. 

This external perspective is often the catalyst leaders need to rethink outdated assumptions about capacity, productivity, and team health. When executives see how other organizations succeed without burning people out, they become far more willing to adopt sustainable practices. 

None of these issues are about blaming teams or leadership. They’re about recognizing that high performance can only last when the structure around it actually supports the people doing the work. When teams speak up early and leaders stay connected to what’s happening behind the metrics, it becomes much easier to catch problems before they turn into burnout or turnover. With clearer priorities, better systems, and honest conversations about capacity, organizations can keep delivering great work without running their people into the ground. 

 

In most organizations, managers are expected to deliver results. While it can often seem that all a manager needs to do to deliver these results is to delegate tasks, for a growth-oriented team to succeed, managers must also develop the people working for them. The position of leaders is to be the ones between the ultimate vision, and the work that actually needs to be done to achieve it, which puts a lot of weight into how they choose to delegate tasks. Delegating tasks in this case means much more than just telling their direct reports what to do. Managers must translate senior executive vision into actionable steps while also developing the team as a whole. This position comes with a unique responsibility: deciding how much control to retain and how much to give away. Many managers hesitate to hand off meaningful ownership because it feels risky. Delegating real responsibility requires trust and a willingness to let others make decisions that you could easily make yourself. But in reality, giving your direct reports something to own is one of the most essential functions of a manager. It helps to strengthen performance, build confidence, and transform employees from task‑takers into leaders. Autonomy is a developmental tool that elevates the entire team.

When managers fail to give their direct reports proper opportunities to share ownership over a project, it only makes it worse for themselves. Without autonomy, employees become overly dependent on direction, waiting for instructions instead of anticipating needs or solving problems proactively. Work slows down because every decision funnels back to the manager, creating bottlenecks that limit productivity and frustrate both sides. Over time, employees begin to disengage, feeling more like cogs in a machine than contributors to something meaningful. They lose the intrinsic motivation that comes from having a stake in the outcome. Meanwhile, managers become overwhelmed by the sheer volume of decisions they’ve kept for themselves, leaving little room for strategic and creative thinking. Because of this, holding on too tightly to control can be far riskier than learning to let go.

Why Managers Need to Give Away Ownership
 Because managers operate at the intersection of execution and development, one of the most critical leadership skills they must cultivate is the ability to delegate responsibility, which is different than just delegating tasks. Ownership is not about offloading work; it is about giving someone the authority, context, and trust to make decisions within a defined space. Some of the most important reasons to do this include:

How Managers Can Create Real Ownership
Some managers may think that creating ownership is simply assigning a project and stepping back, but this is not the case. Giving more autonomy to your direct reports does not mean handing over the entire project and saying, “figure it out!” It requires clarity, communication, and support throughout the process. Managers must define the scope of responsibility, this includes what decisions the employee owns, what success looks like, and where the boundaries are. This prevents confusion and will help the employee to act confidently, while still keeping a good eye on the situation. Instead of simply giving a step by step on how to do something, managers should explain the context of the situation and allow their people to exercise the skills that got them hired in the first place. Explain the “why” behind the work, the constraints, and the priorities, then allow the employee to determine how the work should get done. This should be done in combination with regular check‑ins that focus on guidance and alignment.  Here you can ask questions like “What decisions have you made so far?” or “What obstacles are you anticipating?” These questions encourage critical thinking without taking control. Ultimately, creating ownership is less about delegation and more about development. Ownership over projects helps employees build the skills, confidence, and judgment they need to succeed.

Giving your team something meaningful to own is essential for leadership that aims to grow and develop rather than just manage. Managers who hold too tightly limit their team’s growth and unintentionally create dependency. But managers who intentionally give away ownership build stronger, more capable teams who take pride in their work and contribute at a higher level. By trusting your direct reports with real responsibility, you reduce bottlenecks, strengthen collaboration, and create a culture where people feel empowered to lead. Ownership is the foundation of intrinsic motivation, accountability, and long‑term success for both the team and the organization.

 

In most organizations, middle managers are the essential link between big ideas and practical execution. Senior leaders set ambitious goals, and frontline teams bring those goals to life, but it’s the middle managers who must interpret and translate both sides. They have to have an understanding of the exact expectations, but also the limitations. This role as liaison between executives and frontline teams comes with an immense amount of pressure. You’re evaluated on your output, yet responsible for protecting your team. In this position, saying “no” feels like too much of a risk. There’s often a level of ambiguity about exactly what authority you have as a middle manager, making it feel like boundaries are a luxury reserved for those who run the organization, when in reality, setting boundaries is one of the most essential functions of a middle manager. Setting boundaries helps to not only protect your own peace but also to prevent team burnout, protect the quality of your work, and make you a better leader.

When middle managers fail to set boundaries, the consequences are felt by both the team and the organization. Without clear limits, teams become overwhelmed, and burnout begins to affect morale and performance. A middle manager who always says yes to taking on more than what is reasonable signals to others that their capacity is endless, causing the issue to worsen. Over time, saying yes to everything will lead to diminishing work quality, leading senior leadership to lose trust. This loss of trust is not due to a lack of effort from the manager's end, but rather because the workload was never sustainable to begin with. Never saying no or setting boundaries will lead people to start to expect constant availability and unquestioned compliance, making it even harder to push back in the future. In this way, saying yes to everything becomes far riskier than learning to say no.

Because middle managers sit at the intersection of competing demands, one of the most critical leadership skills they must develop is the ability to set boundaries. These boundaries are not about resistance; they are about creating the conditions for sustainable performance. Some of the most essential include:

Setting boundaries is about more than just knowing where the limits are; it’s about knowing how to communicate them. Middle managers can only do this effectively when they have a firm understanding of their team’s true capacity, which requires tracking workload patterns, noticing when performance dips or improves, and identifying the conditions under which the team does its best work. Using tools such as AIM insights can give you a better, more in-depth understanding of exactly how your team is performing and under what conditions. With that insight, boundaries become easier to articulate because they are grounded in evidence rather than emotion. Good communication from the start is essential; waiting until a deadline is slipping or a project is already off track makes boundary‑setting feel reactive instead of responsible. A good practice is framing conversations around trade‑offs rather than refusals. Be clear about your reservations, what can be done, and what support is needed. This will help to avoid the perception of refusal while still protecting your team. Practicing these conversations in low‑stakes environments builds confidence for the moments when the stakes are higher. Ultimately, setting boundaries is less about saying “no” outright and more about creating clarity, aligning expectations, and ensuring that the work you commit to is work you can deliver well.

 Boundary setting is a leadership requirement, not just a luxury for the higher-ups. The pressures of middle management make it easy to fall into patterns of overcommitment, blurred responsibilities, and constant availability, but these habits ultimately undermine both performance and credibility. By recognizing where limits must be drawn and communicating those limits frequently, middle managers protect their teams, strengthen organizational structure, and ensure that the work they take on is work they can deliver well.

When a team falls behind, it’s often tempting to blame individual members. Leaders often point to reasons like frequent dentist appointments or poor time management. However, slipping output usually doesn’t always stem from the people's lack of effort. It’s often due to a lack of standardized procedures that guide execution. Before you decide that the people on your team aren’t a good fit because you aren’t getting the results you want, you should make sure that the issue isn’t the system they’re operating under.

Effective leaders may have the same number of team members taking time off or stepping out of the office for appointments, but still manage to achieve better results. The key difference is not fewer interruptions. It’s a stronger focus on output and a clear plan for handling the predictable challenges. When teams know how to respond to obstacles, progress remains steady. Having standard operating procedures is a surefire way to protect the performance of your team and keep you on track. A clear procedure supports daily work and helps identify issues before they escalate into bigger problems.

Without standard procedures, it’s harder to measure progress and expectations are assumed rather than defined. Leaders lose visibility on where work struggles occur and often don’t realize there’s an issue until output has already dropped. At that point, individuals are blamed for failing within a poorly designed system, instead of examining the system that set them up to fail.

A strong team and its leaders should always have a standard process guided by these key questions to keep the team on track:

These questions keep the focus on output rather than individual behavior. They allow leaders to address performance without nitpicking and prevent distractions from diverting attention away from the goal. Instead of coaching individuals, leaders refine processes. 

A benefit of standard operating procedures is the clarity they provide to leaders. When SOPs are in place, leaders no longer guess whether someone is underperforming. They can see exactly where execution differs from the standard. This makes feedback factual instead of personal.

Without that clarity, feedback often comes too late. Leaders wait, hoping performance will improve on its own. This leads to the build up of frustration and resentment in a team, so by the time the issue is tackled, emotions are already involved. Even accurate feedback can feel unfair when the standard was never clearly set beforehand. SOPs prevent this by establishing expectations before problems arise. This way, it becomes easier for people to take accountability, because there is no excuse for not knowing the standards.

This delay in addressing issues is where many teams unknowingly create avoidable conflict. A team member falls slightly behind. Leadership notices but takes no action. As time passes, output will only continue to decline. Eventually, the conversation occurs under pressure. By then, the leader is frustrated, the employee feels blindsided, and both leave feeling dissatisfied. The problem wasn’t effort or intent. It was the absence of an early, objective standard to refer to.

Many leaders hesitate to implement more procedures fearing micromanagement. But micromanagement doesn’t come from added structure. It comes from emotion. It’s a reaction to missed deadlines, unexpected outcomes, and unclear expectations that leads to leaders becoming overly involved.

Well-implemented standard operating procedures do the opposite. They define standards early on, which reduces the need for reactive oversight. When leadership trusts the process, they’re less likely to micromanage. Issues can be identified sooner, addressed calmly, and corrected before they develop into larger problems that require significant intervention.

Strong SOPs also shift accountability from individuals to processes. Instead of asking why someone is always behind, leaders can investigate where execution diverged and whether the system supported the desired outcome. This doesn’t lower standards; it strengthens them. High standards become consistent rather than situational.

Teams without SOPs rely heavily on individual judgment. While that might work in low-pressure settings or with highly experienced contributors, when complexity rises, communication issues arise, people don’t get the guidance they need, and everyone is blaming someone else for the lack of output.

In contrast, teams with solid SOPs work with a shared understanding. Everyone knows what being “on track” looks like. Progress is visible. Deviations get caught early and adjusted smoothly. Work advances because expectations are clear, not because individuals are working harder or sacrificing more personal time.

In the end, standard operating procedures aren’t about control. They are about alignment. They align effort with results, expectations with execution, and accountability with fairness. When systems are clear, leaders spend less time reacting and more time leading. Teams work faster, frustration decreases, and performance becomes consistent rather than accidental.