The Hidden Cost of Dysfunctional Senior Teams in an AI-First World

The pressure landed quietly at first. A line in a board presentation. A question from an investor call. Then, this year, it became unavoidable: 53% of investors now expect positive returns on AI within six months or less, and boards have stopped counting pilots and started counting dollars [1].

For senior teams, this represents a fundamental shift in the nature of accountability. AI is no longer a technology project owned by the CTO or a change programme delegated to a transformation director. It is a strategic bet, and the C-suite is now personally on the hook for the returns. 90% of financial services firms have already established C-suite or board-level accountability for AI outcomes [2]. The era of plausible deniability is over. 

Yet the most uncomfortable truth most organisations are not yet facing is this: the primary reason AI transformation fails at scale is not the technology. It is the senior team trying to lead it. And in an environment where top team effectiveness has never mattered more to the bottom line, most senior teams are operating without the foundations that make it possible. 

The Real Problem Is Not the Strategy. It Is the Room It Gets Made In. 

An MIT study reveals that up to 95% of firms investing in AI have yet to see tangible returns [3]. When analysts search for explanations, they reach for the familiar: poor data foundations, unclear use cases, insufficient investment. All true. But they miss the deeper structural failure. 

The proof gap in AI returns is, at its core, an accountability problem. Boards approved investments without setting governance expectations. Leadership deployed AI without defining who owns the outcomes [4]. 

Who owns the outcomes? That question lands squarely inside the senior team. And senior teams, at C, C-1, and C-2 level, are structurally ill-equipped to answer it. Not because they lack intelligence or ambition, but because of how senior teams actually function under conditions of strategic uncertainty. 

Lack of strategic clarity and ineffective decision-making remain the top constraints for senior leadership for the second consecutive year, with 1 in 4 senior leaders believing their current decision-making processes do not adequately support their organisation's needs [5]. Add the pressure of AI accountability to that already-fragile foundation, and what you get is not transformation. You get collective paralysis dressed up as governance. 

What Senior Team Dysfunction Actually Looks Like 

The dysfunction that kills transformation at the top is different from the kind found in middle management. It is more subtle, more political, and far more expensive. 

In a functional senior team, the CFO who argued against the AI investment throws her full weight behind it once the decision is made. The COO who favoured a different architecture actively champions the one the group chose. The CEO who privately doubts the timeline says so in the room, not to the Board afterwards. 

In a dysfunctional senior team, none of this happens. Instead, the decision gets made but never truly committed to. Each function pursues its own interpretation. Resource allocation quietly undermines the agreed strategy. Accountability conversations happen bilaterally, never collectively. And when results disappoint, as they will in any genuine transformation, the team retreats into positional defence rather than honest diagnosis. 

53% of CEOs openly acknowledge their teams struggle to align on strategies in a timely way, and confidence in AI strategies has fallen 11 percentage points since 2024 [6]. That is not a technology problem. It is a team problem, and it is happening at the most consequential level of the organisation. 

The Five Foundations of Top Team Effectiveness, Reframed for the Senior Level 

Patrick Lencioni's model of team dysfunction is well known. What is less often discussed is how each dysfunction manifests differently, and more dangerously, at senior level. The model identifies five behavioural foundations: trust, productive conflict, commitment, peer accountability, and collective results. Each plays out in a specific and high-stakes way at C, C-1, and C-2 level that generic team development approaches simply do not address. 

Trust at the top is not about liking each other. In a senior team, trust means being willing to admit, in front of peers who are also competitors for influence and future roles, that you do not know something. In an AI transformation context, this is not hypothetical. Only 44% of CIOs are considered genuinely AI-savvy by their own CEOs, and even fewer across other C-suite roles [7].

The capability gaps are real. The question is whether the team creates conditions where those gaps can be named openly, or whether individuals perform competence they do not yet have and make decisions based on partial understanding. Without this vulnerability-based trust, the difficult conversations about who needs support, which legacy assumptions need challenging, and where the strategy is genuinely at risk, go underground, where they fester and corrode the transformation from within. 

Productive conflict at senior level requires a specific kind of courage that most development programmes never build.

The higher the stakes and the more invested individuals are in their positions, the more conflict gets managed rather than had. Senior teams become expert at the language of alignment: broadly in agreement, more that unites us than divides us, let us take this offline. These phrases are often the sound of important disagreements being buried. An AI strategy that emerges from managed consensus is not a strategy. It is an averaging of competing agendas, and it will fail in implementation because no one truly owns it. 

Commitment means something harder at the top than it does anywhere else in the organisation. It means publicly staking your credibility on a collective decision you may privately disagree with, and protecting that decision when it comes under fire, including from the Board, from your own function, and sometimes from your own instincts. This is where most senior teams fail silently. The decision is announced. The commitment is never made. 

Peer accountability is perhaps the rarest capability in senior teams, and the most necessary. Most organisations have no mechanism for a Chief Marketing Officer to hold a Chief Financial Officer to account, and vice versa. Accountability flows upward, to the CEO, not across. This means that when one function's foot-dragging is endangering a transformation, the team watches it happen. The CEO is left managing individually what the team should be resolving collectively. Developing this capability requires, above all, the relational trust that makes a direct peer conversation feel safe rather than career-limiting, and that trust is only built through deliberate, sustained investment in the team's development, not through annual offsite retreats. 

Collective results over functional success is perhaps the tension most structurally built into senior teams. Every leader at this level is simultaneously a member of the enterprise leadership team and the head of a function with its own P&L, talent pool, and political constituency. In a transformation, these identities regularly conflict. The function that most needs to change is rarely the one that volunteers to go first. The capability that most needs to be shared is rarely the one that gets deployed where the enterprise needs it most. High-performing senior teams develop explicit norms for navigating this conflict. Most do not, and in an AI transformation context that gap becomes decisive. 

When the Problem Is the Structure, Not Just the People 

One of the most persistent blind spots in senior team development is the assumption that dysfunction is always behavioural. Sometimes it is. But senior teams leading AI transformation frequently find themselves operating inside structures that were not designed for the decisions they are now being asked to make. 

Who has the authority to approve an AI investment that cuts across three functions? When an algorithm surfaces a customer insight that contradicts the CMO's instinct, which process governs what happens next? When the CTO and the COO disagree on architecture, is there a decision-making mechanism that can resolve it without escalating to the CEO every time?

In most organisations, the answer to each of these questions is: not clearly. And when decision rights are unclear, even a cohesive team defaults to the path of least resistance, which is usually delay, workaround, or escalation. The behavioural dysfunction that surfaces in those moments is real, but the root cause is structural. Coaching the team around a broken governance model produces only limited results. The model itself needs to change alongside the behaviours. 

This matters particularly in the context of AI accountability. The organisations that are seeing returns from AI are not simply those with bolder or better-aligned leadership teams. They are the ones that have clarified who owns what, redesigned decision rights to match the speed at which AI insights are generated, and created escalation paths that do not bottleneck every consequential call at the CEO level. As our Top Team Effectiveness Handbook outlines, fixing the structure is not a precondition for behavioural development. It is part of it. Senior teams that are serious about transformation need to be willing to look at both. 

Why Development Must Start With Honest Diagnosis 

One of the most consistent mistakes organisations make when trying to improve top team effectiveness is jumping to solutions before understanding the problem. A team struggling with trust requires a fundamentally different intervention than one that has trust but lacks the commitment to follow through on collective decisions. A senior team that avoids conflict needs different work than one stuck in unproductive conflict. Cookie-cutter approaches, whether a two-day offsite or a single leadership assessment, waste time and money, and can actually deepen cynicism in teams that have seen these initiatives come and go before. 

Effective diagnosis at senior level typically begins with confidential individual conversations, not group workshops. These one-to-one discussions allow each team member to speak without political constraint, surfacing how they genuinely experience the team's purpose, what they see working and not working, and where the real tensions lie. When these insights are aggregated and fed back anonymously, they act as a mirror, often accelerating honest conversations that would never have happened organically.

The Moore Barlow leadership team, a post-merger group of senior leaders across a UK law firm with six offices, went through exactly this process. Psychometric assessments were run individually and then aggregated to show collective gaps, before an in-person facilitation session brought the team together to clarify vision, prioritise deliverables, and examine interdependencies for the first time as a group. Katherine Allison, the firm's CPO, described what that session made possible: "Each of us came to the session with a big list of things to do. It was overwhelming. Ines helped us focus on what mattered most, uncover blockers and enablers, and address interdependencies for the first time as a team." The result was not just clearer priorities. It was a team that left with stronger confidence in its collective role and meetings that had shifted from operational drift to strategic focus. You can read the full Moore Barlow case study on the Esendia website. 

Psychometric profiling and structured 360-degree feedback add additional layers of insight, helping team members understand both their own patterns and how they are experienced by others. This matters particularly at senior level, where individual blind spots tend to have outsized collective consequences. 

Also Read: The Complete Guide to Team Effectiveness: Building High-Performing Teams That Actually Work

Why the C-Suite Above Has to Be Part of This 

Here is where many well-intentioned development programmes quietly fail, and it deserves more directness than it usually receives. 

A C-1 team that goes through serious development work, building real trust, learning to have genuine conflict, committing to collective accountability, returns to an organisation in which the C-suite above them may be doing none of these things. What happens next is predictable. The C-1 team starts making bolder decisions. They start challenging each other. They escalate less to the CEO. And then the CEO, unused to this, starts stepping back in. The pattern is rarely malicious. It is usually anxiety. The CEO who built their career on being the decision-maker finds it uncomfortable when the room starts working without them. 

The result is that the trust the C-1 team spent months building erodes in weeks. Teams at C-1 and C-2 level that are expected to lead change are often conditioned to wait for permission, and shifting from a command-and-control dynamic to genuine empowerment requires deliberate work with the top team's leadership approach before the team below can deliver to expectations. The practical habits that make this shift possible, including how to build peer accountability across functions and how to move from managed consensus to genuine commitment, are explored in detail in When Top Teams Stumble: What You Can Do For Team Effectiveness. 

Effective senior team development is therefore never confined to a single team. It requires parallel work with the layer above: helping the CEO understand how their intervention style affects team confidence, working with the Board to recalibrate expectations around decision-making authority, and ensuring that the behaviours modelled at the very top are consistent with the behaviours being developed beneath them. Without this vertical alignment, the investment in C-1 and C-2 team effectiveness does not just plateau. It actively backfires. 

What the Stakes Actually Are 

Organisations leading in AI execution show 1.7 times higher revenue growth, 3.6 times three-year total shareholder return, and 2.7 times return on invested capital compared to laggards [8]. The gap between companies making AI work and those that are not is not a technology gap. It is an execution gap, and execution at enterprise level is a function of top team effectiveness. 

61% of senior business leaders now feel more pressure to prove AI ROI than a year ago [9]. That pressure is real, it is intensifying, and it is being felt most acutely by the people who sit in senior teams. The question is whether it becomes the catalyst for genuine investment in how those teams function, or whether it simply adds to the ambient stress of a team that was already not working well together. 

For most organisations, the answer is the latter. The team has the talent. It does not have the foundations. And in 2026, the distance between those two things is measured in shareholder value. 

If you are responsible for the effectiveness of a senior team navigating AI transformation, the Top Team Effectiveness Handbook is the starting point. It is built for leaders at C, C-1, and C-2 level who want to understand what top team effectiveness actually requires in practice, and what it takes to build those foundations under pressure. 

FAQ

Our executive team is under real pressure to show AI returns. Why would we invest time in team development right now rather than just pushing harder on execution? 

Because the execution problem is usually a team problem. When accountability is unclear, when commitments are announced but not held, and when peer-to-peer challenges get managed rather than had, execution slows down regardless of how hard individuals are working. The teams showing the strongest AI returns are not the ones with the most technical capability. They are the ones where accountability is clear, decisions stick, and the team resolves its own tensions rather than routing every difficult conversation through the CEO. Investing in team foundations is not a distraction from execution. In most cases, it is what makes execution possible. 

We have worked on trust and alignment before. What would be different about starting with a proper diagnostic? 

Most team development programmes start with a solution, usually a workshop or an assessment tool, rather than with an honest picture of what the specific team is actually struggling with. A team that has superficial harmony but avoids productive conflict needs different work than a team that has trust but cannot commit to collective decisions. Starting with confidential one-to-one discovery conversations, aggregated anonymously, surfaces the patterns that team members will not name in a group setting. That diagnosis is what makes the subsequent development land rather than wash off. Without it, even well-designed interventions produce workshop feedback scores rather than behaviour change. 

How do we know whether a governance or structural problem is making our team dysfunction worse? 

A useful signal is whether the same decisions keep resurfacing. If the team revisits calls it thought it had made, if escalation to the CEO is the default resolution mechanism for cross-functional disagreements, or if different functions are operating to different interpretations of an agreed strategy, these are often structural symptoms as much as behavioural ones. Unclear decision rights and misaligned accountability frameworks do not disappear through team coaching alone. Diagnosing whether the issue is structural, behavioural, or both is one of the most important functions of an initial discovery process. 

At what point in a senior team development programme should the layer above be brought in? 

Earlier than most organisations expect. If the C-suite above is not part of the development process, the progress made at C-1 and C-2 level can be actively undermined when the team starts operating differently. CEOs who are accustomed to centralised decision-making often step back in when the team below starts resolving things without them, not because they want to block progress but because the new dynamic is unfamiliar. Bringing the senior layer in early, at minimum to align on what different-looking behaviour from the layer below should be welcomed rather than corrected, is often the difference between a programme that sustains and one that quietly reverts. 

What does a team effectiveness programme look like in practice for a C-suite under AI accountability pressure? 

It starts with a diagnostic phase: individual discovery conversations with each team member, psychometric profiling, and 360-degree feedback where appropriate. That gives a precise picture of where the team's specific gaps lie. The development phase typically involves two to three structured workshops addressing who the team is, what it has committed to, and how it wants to make decisions together, combined with team coaching through live meetings, where a coach can prompt real-time reflection on the dynamics playing out. One-to-one coaching runs in parallel for individuals whose blind spots are affecting the collective. Structural changes to governance and decision rights are addressed alongside the behavioural work, not treated as a separate workstream. The goal is not a team that has attended development sessions. It is a team that operates differently when the next difficult decision lands. 

References 

[1] Jimenez, D. (2026) 2026: The Year AI ROI Gets Real and Forces a Strategic Fork in the Road. WNDYR. Available at: https://www.wndyr.com/blog/2026-the-year-ai-roi-gets-real-and-forces-a-strategic-fork-in-the-road

[2] EY (2026) Global Financial Services CEOs Upbeat on Revenue, Profitability and Productivity Growth in 2026, as ROI in AI Exceeds Expectations. EY-Parthenon CEO Outlook Survey. Available at: https://www.ey.com/en_gl/newsroom/2026/02/global-financial-services-ceos-upbeat-on-revenue-profitability-and-productivity-growth-in-2026-as-roi-in-ai-exceeds-expectations

[3] OriginTrail (2025) 5 Trends to Drive the AI ROI in 2026: Trust is Capital. Medium/OriginTrail. Available at: https://medium.com/origintrail/5-trends-to-drive-the-ai-roi-in-2026-trust-is-capital-372ac5dabc38

[4] Grant Thornton (2026) 2026 AI Impact Survey Report. Grant Thornton. Available at: https://www.grantthornton.com/services/advisory-services/artificial-intelligence/2026-ai-impact-survey

[5] LHH (2026) LHH 2026 C-Suite Research: Executive Turnover Falls Sharply as AI Accountability and Decision-Making Gaps Define Leadership Agenda. LHH. Available at: https://www.lhh.com/en-us/insights/pressroom/lhh-2026-c-suite-research

[6] Adecco Group (2025) Only 10% of C-Suite Leaders Say Their Companies Are Ready for AI Disruption. Adecco Group Press Release, 15 May. Available at: https://www.adeccogroup.com/our-group/media/press-releases/only-ten-percent-of-c-suite-leaders-say-their-companies-are-ready-for-ai-disruption

[7] Gartner (2025) Gartner Survey Reveals That CEOs Believe Their Executive Teams Lack AI Savviness. Gartner Newsroom, 6 May. Available at: https://www.gartner.com/en/newsroom/press-releases/2025-05-06-gartner-survey-reveals-that-ceos-believe-their-executive-teams-lack-ai-savviness

[8] Master of Code Global (2026) AI ROI: Why Only 5% of Enterprises See Real Returns in 2026. Master of Code Global. Available at: https://masterofcode.com/blog/ai-roi

[9] Kyndryl (2025) Kyndryl 2025 Readiness Report, cited in: Marko, K. (2026) '2026: The Year AI ROI Gets Real', CIO, 13 January. Available at: https://www.cio.com/article/4114010/2026-the-year-ai-roi-gets-real.html