by
Ritika Vijay
Fri 22 May 2026
Marcus has been in this role for six months now. He leads a variety of cross-functional initiatives. He is in charge of a team that is dependent on product, engineering, and operations. They all have clear timelines, with each production depending on the other. Every team knew what they needed to do and when they needed to deliver.
There was agreement in the room, but progress stalled. Marcus depended on other team managers to handle their tasks, yet the work stopped. Deadlines slipped, and Marcus lacked direct authority over those teams. He watched the project he was responsible for begin to crumble.
When Authority Doesn't Follow Accountability
Cross-functional leadership is among the most challenging roles in any organization. They are responsible for outcomes, but cannot influence the inputs. Most leaders facing this challenge either escalate issues, risking relationships, or absorb dysfunction, risking burnout.
Neither of these solutions are durable; they both fail for the same reason. They are trying to solve an accountability problem with tools, but the real issue is a structural issue.
- Why does cross-functional accountability break down when everyone says they are aligned?
Marcus’s situation is built on layers of complications. The CEO was a public supporter of this initiative. In every situation, like meetings and one-on-ones, the message was clear: everything was going to get done. But privately, when the other managers came to the CEO, he didn’t think the team needed to prioritize these goals, and the CEO would let it go. He would tell the managers it was okay to deprioritize it. As a result, it caused a ripple effect in Marcus’s team, where he had a mandate but no backing to enforce it, and the other team had already learned they didn't have to move.
The Root of the Problem
The problem isn’t the other managers, and it is easy to frame someone who isn’t delivering. But in this situation, they are just listening to their CEO, and teams adjust to the behavior of what they see is happening. If there are no follow-ups with missed deadlines, then they file that way.
If employees learn that nothing will happen if they miss deadlines and avoid work, they will keep doing it. They see if leadership avoids those difficult conversations and does not enforce rules, they have no reason to change.
- How do teams learn what is actually expected of them versus what is said out loud?
The issue is not solely with the underperforming manager. The bigger issue is the culture of the workplace, where accountability does not exist because leadership is not willing to step up and address these problems.
In Marcus’s company, this problem grew over time. The previous leader hadn’t avoided conflict. He would foster an environment built on fear. The new CEO who stepped in wanted to change that. But in the process, a lot of things got lost. The CEO confused not being toxic with not holding the line. Without anyone willing to enforce these commitments, people learned they could opt out without consequences.
CEO Ripple Effect
When a senior leader publicly embraces an idea, but they privately undermine it, not one project is affected. On the outside, the company looks strong and buoyant, but on the inside, accountability is being negotiated.
- What does it signal to an organization when public commitments and private decisions don't match?
The CEO was trying to avoid being someone who creates fear and pressure. Sometimes, there are situations where a previous leader has created an environment fostering fear, and the new leader doesn’t want to replicate it. But this situation has fostered kindness and dysfunction.
How to Lead When the Ceiling Has Holes In It
- Structural Problem That Needs To Be Solved:
Rather than escalating to frustration, it is imperative to question whether cross-functional accountability works in the organization. The conversation with leadership should focus less on blaming individuals and more on understanding the process itself. That means asking questions such as who is responsible when two teams disagree, how decisions are made across departments, and what happens when an important dependency gets dropped. The goal should be to identify weaknesses in the system and improve the process so similar problems do not continue to happen in the future.
- Cost of Inaction:
It is important that everyone becomes aware of the cost of poor teamwork. With leaders brushing it off and excusing delays, it can create real damage. For example, identify which customer deliverable will be delayed, how long the delay will last, and who will ultimately be affected by it. When people can clearly see the direct outcome of inaction, the issue feels more real and urgent, which often encourages faster collaboration and problem-solving.
- Building Systems Fostering Teamwork:
Creating initiatives that can foster teamwork is one of the most effective ways to mitigate such problems. Setting up peer reviews, shared goals, and cross-team meetings where problems are discussed. The most important part is making problems aware to everyone in the room, not just the individuals who are directly impacted by them. When things are openly acknowledged in front of multiple teams, social accountability often motivates people to act more quickly.
The Deeper Issue
The goal is to build a culture where agreements mean something, where yes in the room translates to action in the work, and where the gap between public alignment and private behavior doesn’t exist.