Why Leadership Teams Fail

Illustration of the Weavers – Two reports in 5 mins

Can you write a paper for the British Computer Society Leadership Team who are looking at the question of leadership. Answer the following question without using the Weavers Framework and again using the Weavers Framework. What new insights does the Weavers bring. The paper should cover the differences: Why do leadership teams fail to meet their own and stakeholders expectations, identify problems in advance, innovate or spot future trends.

A PAPER FOR THE BCS LEADERSHIP TEAM

Why Leadership Teams Fail

Meeting expectations, anticipating problems, driving innovation and spotting future trends

Two analyses: without the Weavers framework, and with it. What does the Weavers lens add?

Author: David Sutton CITP MBCS Framework: The Weavers and the Web

Audience: BCS Leadership Team Year: 2026

Abstract Leadership teams across public, private and voluntary sectors consistently fail in three related ways: they fail to meet their own and their stakeholders’ expectations; they fail to identify problems before those problems become crises; and they fail to innovate or recognise the future trends that will reshape their environment. These failures are widely studied, extensively theorised, and persistently repeated. This paper addresses the question in two parts. Part One applies the best available conventional analysis — drawing on established leadership research, organisational theory, and current practice — to answer why these failures occur. Part Two applies the Weavers and the Web framework to the same question. Part Three identifies what the Weavers analysis adds: the insights it surfaces that conventional approaches consistently miss, and why those particular insights matter for the BCS and for the profession it serves. The central finding: Conventional leadership analysis correctly describes what goes wrong. The Weavers framework explains why the correct descriptions do not produce the changes they recommend — and provides instruments for addressing the structural reasons why good analysis does not become better practice.

PART ONE

Why leadership teams fail: the conventional analysis

The literature on leadership failure is extensive, the diagnoses are often correct, and the pattern of failure is remarkably consistent across organisations of every type and size. Understanding this pattern is the starting point for both analyses.

1.1 Failing to meet expectations

The expectation gap

Leadership teams fail to meet expectations primarily because the expectations themselves are poorly defined, inconsistently held, and inadequately connected to the decisions that are actually made. Research by Keil and Zangrillo (Harvard Business Review, 2024) identifies the health of the leadership team itself as a critical and consistently overlooked factor in organisational performance. A dysfunctional team can be a serious drag on strategy execution even when individual members are competent and motivated.

The expectation gap operates at three levels simultaneously. At the board level, trustees and non-executives hold expectations about strategic direction and risk management that are often not explicitly shared with the executive team. At the executive level, the team collectively holds expectations about each member’s contribution that are rarely made explicit in formal governance processes. At the organisational level, staff and stakeholders hold expectations about culture, responsiveness, and accountability that leadership teams typically discover they have failed to meet rather than proactively managing.

Why this produces persistent failure

The persistence of expectation failure is not explained by incompetence. Most leadership teams contain highly capable individuals. It is explained by four structural features of how leadership teams operate.

First, leadership teams spend most of their time on the operational and tactical, even when their formal mandate is strategic. The urgent displaces the important, not through laziness but through the legitimate pressure of accountability for immediate performance.

Second, the information that reaches leadership teams is filtered through organisational hierarchies that systematically present successes and suppress failures. Leaders receive the version of reality that the organisation has determined they should receive, which is rarely identical to the version that exists at the frontline.

Third, the criteria by which leadership performance is assessed are typically lagging indicators: financial results, customer satisfaction scores, staff turnover. By the time these measures reflect a failure, the conditions that produced it have been operating for months or years.

Fourth, and most importantly: leadership teams are typically constituted on the basis of functional expertise rather than collective capability. The team that is excellent at managing individual domains is not automatically excellent at managing the interactions between those domains, which is where the most significant risks and opportunities typically reside.

1.2 Failing to identify problems in advance

The anticipation failure

The consistent finding from post-crisis analysis is that the information needed to anticipate most crises was available before the crisis occurred. What was missing was not the information but the mechanism for that information to reach the people who could act on it, and the institutional permission to act on it before it became urgent.

This is described in the literature as ‘organisational silence’: the systematic suppression of dissenting information that might challenge prevailing assumptions or create discomfort for those in authority. Studies of major institutional failures — from the NHS Mid Staffordshire scandal to the 2008 financial crisis to numerous technology programme failures — consistently find that frontline workers knew what was going wrong, had communicated their concerns, and had not been heard.

The structural causes of anticipation failure include: the absence of formal mechanisms for escalating concerns across organisational boundaries; the social cost of being the person who raises uncomfortable information; the professional culture of many technical organisations that treats early problem identification as criticism rather than contribution; and the tendency of leadership teams to interpret the absence of reported problems as evidence that no problems exist.

The horizon problem

Leadership teams also consistently fail to look far enough ahead. The planning horizon of most organisations — even those with formal strategy functions — is dominated by the annual budget cycle and the quarterly review. Structural trends that operate over five to ten years — demographic shifts, technology transitions, regulatory change, geopolitical realignment — are acknowledged in strategy documents but rarely translated into current decisions.

The reason is structural rather than attitudinal. Leaders who make decisions today based on conditions that will not fully materialise for five years face an accountability problem: they cannot demonstrate the return on that decision within the reporting cycles that govern their performance assessment. Rational actors in a system of short-term accountability make short-term decisions. Changing the decisions requires changing the accountability system, not the individuals.

1.3 Failing to innovate and spot future trends

The innovation paradox

Organisations that need to innovate most urgently are typically the least able to do so. Innovation requires slack: time, cognitive space, and permission to pursue things that might fail. Organisations under performance pressure have less of all three. The result is that innovation is consistently sacrificed for optimisation precisely when the environment is changing fastest and optimisation of the existing model is least sufficient.

The BCS itself illustrates this tension directly. The organisation retains many characteristics of its 1950s origins, functioning in many ways like a club from that era, despite having grown into a large chartered charity with over 250 staff and annual income consistently over £20 million. The governance structures that were appropriate for a small community of scientists are not necessarily appropriate for an institution attempting to lead professional development in one of the most rapidly changing fields in human history.

Why innovation is structurally suppressed

The conventional analysis identifies several mechanisms through which innovation is suppressed in leadership teams. Conformity pressure within senior teams means that members self-censor ideas that might be perceived as impractical or disruptive. Expertise hierarchies mean that innovation in one domain is blocked by authority holders in adjacent domains even when the innovation is well-evidenced. The ‘not invented here’ dynamic means that innovations from outside the organisation are resisted by internal functions whose authority they implicitly challenge.

Most significantly, the criteria used to evaluate leadership performance systematically disadvantage innovation. An innovation that fails visibly is recorded as a leadership failure. A failure to innovate — the slow-motion organisational irrelevance that results from not changing when the environment demands it — is typically not recorded at all until it becomes a crisis, at which point the individuals responsible for the failure to innovate have usually moved on.

The trend-spotting failure

The research on trend identification in leadership teams reveals a consistent pattern: trends are spotted by people who are closest to the environment where they are emerging, which is usually not the leadership team. The challenge is not identification but translation: moving the insight from where it exists to where it can be acted upon. This translation fails for the same reasons that problem escalation fails — the information does not have a formal route, the social cost of carrying it is high, and the leadership team’s existing mental model creates resistance to information that contradicts it.

There is an additional factor specific to technology-facing organisations: the pace of change creates a competence gap at the top that did not exist in previous generations. Leaders who were technically current fifteen years ago may not be technically current today, and the rate at which technical knowledge becomes obsolete is accelerating. This creates a specific failure mode in which leadership teams cannot evaluate the trends that their technical staff are identifying, because they lack the conceptual vocabulary to assess the significance of what is being presented to them.

Part One summary: what conventional analysis tells us Conventional analysis correctly identifies six root causes of leadership failure: expectation gaps that are structural rather than attitudinal; filtered information flows that systematically hide reality from decision-makers; short-term accountability systems that punish long-term thinking; team composition based on individual expertise rather than collective capability; innovation-suppressing conformity and authority dynamics; and a widening competence gap between the pace of environmental change and the currency of leadership knowledge. The analysis is well-evidenced, widely accepted, and has been available for decades. And yet the failures it describes continue to recur. Which suggests that the conventional analysis, however correct, is not sufficient. Something is missing.

PART TWO

Why leadership teams fail: the Weavers analysis

The Weavers and the Web is a strategic framework developed through practice in complex organisational settings. It uses a symbolic image — a richly detailed painting — as an analytical bridge: a device for surfacing the structural problems in a system that conventional analytical methods consistently miss. It is applied here to the same question: why do leadership teams fail to meet expectations, identify problems in advance, and innovate?

The Weavers analysis does not contradict the conventional analysis. It extends it by naming the mechanism that explains why correct diagnoses do not produce sustained improvements.

2.1 The vine: barriers that hide in plain sight

The Weavers framework identifies a structural feature it calls the vine: the barriers that grow through an organisation’s normal processes, severing connections that appear to be intact. The vine is not a single dramatic failure. It is the accumulated effect of decisions that each seemed reasonable in isolation but collectively produce a system in which critical information does not flow, cooperation does not happen, and the people who hold power do not hold the knowledge they need to exercise it intelligently.

In leadership teams, the vine manifests as the gap between the formal governance structure and how decisions are actually made. The allocated map — the organisational chart, the terms of reference, the governance framework — shows a structure in which authority and accountability are clearly assigned. The actual map shows where decisions are really made, by whom, on the basis of what information, and subject to what constraints. These two maps are rarely identical. The vine grows in the gap between them.

The critical insight the Weavers analysis adds: the vine cannot be removed by improving the formal governance structure, because the vine is not in the formal structure. It is in the informal relationships, the social dynamics, the professional cultures, and the unspoken assumptions that determine how the formal structure actually operates. Leadership teams that have excellent governance documents and poor actual governance are not failing to implement their governance framework. They are operating a second governance system that runs alongside the first, in the gap between the allocated and the actual map.

Applied to expectation failure: the Weavers analysis identifies the expectation gap not as a communication failure but as a vine. The real expectations of boards, staff, and stakeholders are not communicated through formal channels because formal channels are not where those expectations actually live. They live in the informal conversations, the unstated assumptions, the things everyone knows but nobody says. A leadership team that improves its formal communication without identifying and addressing the vine will improve its allocated map without changing its actual practice.

2.2 The two maps of governance

The Weavers framework distinguishes consistently between the allocated map and the actual map. This is not simply the observation that formal structures and informal practices differ — that observation is common in the literature. The distinctive contribution of the Weavers analysis is the instrument it provides for making this gap visible before it produces a failure.

The inversion instrument is a pre-strategy analytical tool. Applied to a leadership team, it asks: what does our current governance structure make it impossible for us to see? What does compliance with our own framework allow us to avoid doing? What are the things that everyone in this team knows are true but that our governance structures prevent us from naming?

These questions surface the actual map. They produce the answers that the formal governance process is designed — not deliberately, but structurally — to suppress. A leadership team that can answer these questions honestly, before it is forced to answer them by a crisis, has a fundamentally different relationship with its own governance than one that waits for external events to reveal the gap.

The reason this matters specifically for the BCS is that the organisation has its own documented experience of the gap between allocated and actual governance. The BCS has retained many characteristics of a 1950s club despite growing into a large chartered charity, with governance structures where trustees also hold quasi-executive positions, creating a situation where the best practices of trusteeship — a separation between trustees, functional leadership, and oversight — are compromised. The Weavers inversion instrument applied to the BCS would ask: what does this structure make it impossible for the organisation to see about itself?

2.3 The dependency cascade: how capability leaves invisibly

The Weavers framework identifies a five-phase cascade through which organisations progressively lose the capability to govern what they have built. Phase one: operational capability is outsourced or delegated. Phase two: the capability to direct and transform is lost. Phase three: the organisation can no longer audit or inspect what it has produced. Phase four: strategy itself becomes dependent on the framing provided by whoever holds the operational capability. Phase five: the capability to see what has been lost is gone.

Applied to leadership team failure, the dependency cascade describes the specific mechanism through which leadership teams lose the ability to anticipate problems. It is not that the information is absent. It is that the leadership team has progressively lost the capability to understand, evaluate, and act on the information it receives. The team is given a dashboard showing everything is green. It cannot tell whether the dashboard is accurate, because the knowledge required to evaluate the dashboard has been contracted out to the people who built the dashboard.

This is the specific failure mode that produces the pattern identified in the conventional analysis: frontline workers who knew what was going wrong, raised concerns, and were not heard. The Weavers analysis adds precision: they were not heard not because leadership was indifferent, but because leadership had lost the capability to evaluate what it was being told. The cascade had reached the point where the organisation could not distinguish between a genuine early warning and an operational complaint.

For the BCS and for the organisations it serves, the cascade is directly visible in AI governance. The challenge is finding new ways to facilitate engagement when the world is speeding up its desire for change, ensuring that business planning is tailored for the unique organisation and not just following generic templates, and that governance is not just a formality but the foundation for real engagement and lasting impact. The cascade begins the moment governance becomes a formality — the moment the allocated map is treated as the actual map.

2.4 The smaller tower: institutional knowledge that does not pass forward

The Weavers framework uses the image of the smaller tower to describe the specific and consistent pattern in which institutional knowledge that could prevent future failures is held inside individuals rather than embedded in the organisation. When those individuals leave — through retirement, role change, or the simple passage of time — the knowledge leaves with them. The next generation rebuilds what was already built, without knowing it already existed.

This is the mechanism that explains why the correct diagnoses of the conventional analysis do not produce sustained improvements. Each generation of leadership researchers identifies the same failures. Each generation of leaders reads the analysis, agrees with it, and does not change what they do. This is not because the analysis is wrong. It is because the analysis is held by individuals — researchers, consultants, practitioners — and is not embedded in the institutional practices that would make it persistent.

The Weavers analysis asks a specific question about any organisational practice: if the people who currently hold this knowledge were to leave simultaneously, what would survive? If the answer is ‘the documents they produced,’ the knowledge is in the smaller tower. If the answer is ‘the network of practitioners who have adopted and extended the practice,’ the knowledge is in the golden network.

Applied to leadership development: most leadership development programmes produce documents, frameworks, and trained individuals. The individuals carry the knowledge. When they move on, the documents remain but the tacit understanding of why the framework works, what it is protecting against, and how to apply it in difficult edge cases — that tacit knowledge goes with them. This is why organisations repeatedly commission leadership development programmes that produce the same insights, and why those insights do not accumulate across generations of leaders.

2.5 The blue flower: designing from the right constraint

The Weavers framework uses the image of the blue flower — a small, plain flower with no resources of its own, growing in the same soil as the elaborate gardens — to identify the principle that should govern system design. The system should be designed for the person with the most need and the least power to navigate it. If the system works for that person, it works. If it does not, the adequacy it provides for everyone with more resources is provisional and fragile.

Applied to leadership team failure, the blue flower principle identifies the specific population whose experience reveals whether the system is working: the member of staff at the most junior level who has seen something going wrong, has tried to communicate it, and has not been heard. The new joiner who has noticed that the organisation’s stated values and its actual behaviour are not the same. The part-time volunteer who has a genuine insight but no formal channel through which it can be received.

Leadership teams that design their governance for the person with the most power — the senior stakeholder whose satisfaction is most visible, the customer whose complaint will make the news — systematically miss the information that would allow them to anticipate failures. That information is held by people whose voices are structural quiet: not because they are timid, but because the system does not have the mechanisms to hear them.

The blue flower test applied to BCS governance asks: does the governance system work for the most junior member, the volunteer who is giving time without institutional backing, the student who has not yet joined the professional network? If the answer is no — if those people cannot effectively raise concerns, contribute insights, or receive acknowledgement for what they offer — then the organisation is losing precisely the information and energy that would allow it to see its future before that future arrives.

2.6 The AI multiplier and the innovation question

The Weavers framework identifies AI as a multiplier: a force that amplifies what it is shown. Show it good governance and it produces better governance faster. Show it poor governance — fragmented information, siloed decision-making, historical bias, a system calibrated for a world that no longer exists — and it amplifies those failures at speed and at scale.

This is the missing insight in the conventional analysis of innovation failure. Leadership teams are not failing to innovate because they lack ideas. They are failing to innovate because they are adopting AI tools into governance systems that have not been designed to use AI well. The speed advantage AI provides is real. But speed applied to a broken process produces faster broken outcomes. The innovation that matters is not the adoption of AI tools. It is the redesign of governance systems to be worthy of AI amplification.

The trend-spotting failure identified in the conventional analysis takes on a different character through the Weavers lens. The trends that leadership teams fail to spot are not the ones that no one has seen — they are the ones that have been seen by people whose voices the governance system is not designed to hear. The junior analyst who has read the research. The frontline worker who is living the consequence of the trend that leadership has not yet noticed. The part-time member who has a perspective from outside the organisation’s primary operating environment.

AI tools can surface these voices. They can aggregate patterns across large numbers of weak signals. They can make visible the connections between events that appear unrelated from inside a single department. But they can only do this if the governance system is designed to receive and act on what they produce. A leadership team that adopts AI tools without redesigning its governance system will get faster versions of the information it was already receiving, and miss the information it was already missing — faster.

Part Two summary: what the Weavers analysis adds The Weavers analysis extends the conventional analysis by identifying the structural mechanisms that explain why correct diagnoses do not produce sustained improvements. The vine explains why formal governance and actual governance are always different and how to make the gap visible. The two maps and the inversion instrument provide a specific tool for surfacing what the governance structure is preventing leadership from seeing. The dependency cascade explains the specific mechanism through which the capability to anticipate problems is progressively lost. The smaller tower explains why institutional learning does not accumulate across generations of leaders. The blue flower identifies the specific population whose experience reveals whether the system is working. And the AI multiplier reframes the innovation question from ‘how do we adopt new tools’ to ‘how do we design governance systems worthy of what those tools can amplify.’

PART THREE

What new insights does the Weavers framework bring?

The Weavers framework is not an alternative to conventional leadership analysis. It is an extension of it. The new insights it brings are not new observations about what goes wrong. They are new instruments for addressing the structural reasons why correct observations do not change practice. There are five distinct insights, each of which produces a different practical response.

New insight 1: the diagnosis is not the problem

The conventional analysis has diagnosed leadership team failure correctly for decades. The Weavers framework’s first new insight is the observation that this diagnosis is itself insufficient and sometimes counterproductive. Organisations that produce accurate diagnoses of their failures — and then do not change — are not failing to understand the problem. They are failing to change the structural conditions that produce the problem, while believing that the diagnosis itself constitutes progress.

The Weavers inversion instrument asks: what does this diagnosis make it easier to ignore? Applied to leadership failure, the answer is often: the informal governance system that the formal diagnosis is implicitly ratifying by describing only the formal system. A leadership review that produces a report about communication failures, expectation gaps, and innovation deficits — and then asks the same team to implement the recommendations — has not changed anything. It has produced a document that will sit on the shelf alongside the previous leadership review that made the same recommendations.

The practical implication: before any leadership development intervention, apply the inversion test. Ask what the proposed solution makes it easier to ignore. Design the intervention to address that thing first.

New insight 2: the actual map must be drawn before the allocated map can be improved

The conventional analysis recommends improving formal governance: clearer expectations, better communication structures, improved accountability mechanisms. The Weavers framework’s second new insight is that these improvements will be absorbed by the actual governance system — the informal practices, unspoken assumptions, and social dynamics that determine how the formal structure really operates — and will produce less change than expected.

The specific practical contribution of the Weavers framework here is the method for drawing the actual map. This requires asking the people at the bottom of the organisation what they know, what they have tried to communicate, and what happened when they did. It requires asking what the governance system makes it difficult to say, who benefits from that difficulty, and what would have to change for the truth to flow freely. These questions are not comfortable. They are also not optional if the organisation is serious about understanding what is actually happening rather than what its governance structure says should be happening.

New insight 3: capability loss is invisible until it is catastrophic

The conventional analysis identifies the anticipation failure: leadership teams do not see problems coming. The Weavers framework’s dependency cascade provides the specific mechanism that the conventional analysis does not: capability loss. The reason leadership teams cannot anticipate problems is not primarily attitudinal or informational. It is operational. They have progressively lost the capability to evaluate the information they receive, because the capability to evaluate has been delegated, outsourced, or left to atrophy through disuse.

The specific insight this produces: the first question any leadership team should ask about any area of its governance is not ‘are we receiving the right information?’ but ‘do we have the capability to evaluate the information we receive?’ In the context of technology governance — which is the BCS’s specific domain — this is the question that distinguishes intelligent commissioning from dependent commissioning. A leadership team that cannot evaluate a technical audit finding, cannot read a software architecture diagram, or cannot assess the significance of a data governance failure, is already in the dependency cascade. The question is which phase.

New insight 4: the golden thread must be traceable in both directions

The conventional analysis recommends establishing clear strategic direction and communicating it effectively. The Weavers golden thread adds a specific and underappreciated requirement: the thread must be traceable not just from strategy to action, but from action back to strategy. It must be possible to look at any current operational decision and trace the line from that decision back through policy, through principle, through vision, to mission.

This bidirectional traceability is what the conventional analysis means by alignment, but rarely specifies in terms precise enough to be operationalised. The Weavers framework makes it precise: the golden thread is broken if the person making the operational decision cannot explain how it connects to the organisation’s stated mission. It is broken if the board cannot explain how its strategic choices will manifest in the specific operational decisions that will be made in the next quarter. And it is broken if the distance between strategy and action is so great that the strategy is effectively invisible from the operational layer.

For leadership teams, the golden thread test produces a specific discipline: before any strategic decision, test whether it is traceable to current operational practice. Before any operational decision, test whether it is traceable to current strategy. The gap between these two tests is where leadership failures live.

New insight 5: the image holds what language cannot

The fifth and perhaps most distinctive new insight the Weavers framework brings is methodological rather than analytical. The framework uses a symbolic image — a complex painting with a richly layered symbolic register — as an analytical bridge. This is not a presentational flourish. It is a response to a specific limitation of language-based analysis.

Language-based analysis — strategy documents, governance frameworks, leadership reviews — is processed through the same cognitive system that produced the practices it is trying to change. It is evaluated by the people whose assumptions it is implicitly challenging. It is filtered through the same social dynamics that produce the failures it is diagnosing. It is very good at being agreed with and very poor at changing behaviour.

The image works differently. It creates a shared field of perception that does not trigger the same defensive responses as propositional language. When a leadership team is asked to describe what they see in a complex symbolic image — and the image has been designed to carry the structural tensions of their situation — they articulate things they would not articulate in a meeting. The storm and the calm are both visible in the image simultaneously. The closed tower and the open network are both present. The vine growing through what appears to be normal landscape is visible to everyone.

The practical application for the BCS Leadership Team: the Weavers image is not a metaphor to be explained. It is an instrument to be used. Presenting the image to a leadership team at the beginning of a governance discussion, and asking each member to describe what they see, surfaces assumptions and concerns that a conventional agenda would not reach. It is a rapid, non-threatening method for drawing the actual map before the meeting begins.

Comparative summary: conventional vs Weavers analysis

The following table summarises the key differences between the conventional and Weavers analyses across the three failure modes. The Weavers column does not replace the conventional analysis — it adds to it.

Failure mode	Conventional analysis	Weavers analysis adds
Meeting expectations	Expectation gaps, poor communication, lagging accountability measures, team composition based on individual rather than collective capability	The vine in formal governance: the actual map of how expectations are held and how decisions are made is never the same as the allocated map. The inversion instrument surfaces what the governance structure is preventing leadership from seeing.
Anticipating problems	Organisational silence, filtered information flows, short planning horizons, accountability systems that penalise long-term thinking	The dependency cascade: leadership teams lose the capability to evaluate information before they lose access to it. Phase 3 of the cascade — cannot audit or inspect — is reached invisibly and irreversibly without the cascade diagnostic.
Innovation and trends	Conformity pressure, expertise hierarchies, innovation-penalising accountability, widening technical competence gap	The smaller tower: innovation and trend insight is held in individuals who move on, not in networks that accumulate. The AI multiplier reframes innovation from tool adoption to governance redesign worthy of amplification.
Why analysis does not produce change	(Not addressed — assumes implementation follows diagnosis)	The smaller tower explains why correct analysis does not compound across generations. The image as analytical bridge provides a method for surfacing what language-based analysis cannot reach.
Who the system is designed for	(Assumes stakeholder-centric design)	The blue flower test: design from the person with the most need and least power. If the system works for them, it works. If not, its adequacy for everyone else is provisional.

Recommendations for the BCS Leadership Team

The following recommendations draw on both analyses. They are practical, sequenced, and designed to be implemented incrementally. None require wholesale transformation. All require honest engagement with the gap between the allocated and the actual map.

1. Apply the inversion instrument to this paper

Before any other action: apply the inversion test to this paper itself. Ask: what does this analysis make it easier for the Leadership Team to ignore? The answer will surface the most important thing the analysis has not said.

2. Draw the actual map

Commission a structured process for drawing the actual governance map: how decisions are really made, what information really reaches leadership, and what the most junior members of the BCS community have tried to communicate and not been heard. This is different from a stakeholder survey. It requires specifically asking the people whose voices the current system is least designed to hear.

3. Apply the dependency cascade diagnostic to AI governance

The BCS is the Chartered Institute for IT. Its leadership team should be able to answer the dependency cascade question about its own AI governance: at which phase of the cascade is the organisation’s relationship with AI systems currently operating? The answer determines the priority of capability-building over tool adoption.

4. Apply the blue flower test to BCS governance

Does the BCS governance system work for the most junior member, the part-time volunteer, the student not yet in the professional network? If not, the organisation is losing the information and energy that would allow it to see its future before it arrives. Design one specific change in governance that makes the blue flower more visible.

5. Use the image as an instrument in one leadership session

Before the next major governance decision, use the Weavers image as an opening instrument. Ask each member of the Leadership Team to describe what they see. Do not interpret the answers. Record them. The divergence between what different people see in the same image is the actual map of the leadership team’s assumptions. That divergence is more useful than any governance document.

Conclusion Leadership teams fail to meet expectations, anticipate problems, and innovate for reasons that are well understood and persistently repeated. The conventional analysis describes what goes wrong with clarity and accuracy. The Weavers framework adds the structural explanation for why correct descriptions do not produce lasting change. The five new insights the Weavers analysis brings — that the diagnosis is not the problem; that the actual map must be drawn before the allocated map can be improved; that capability loss is invisible until it is catastrophic; that the golden thread must be traceable in both directions; and that the image holds what language cannot — are not insights about leadership in general. They are instruments for a specific kind of leadership team: one that is serious about the gap between what it says it does and what it actually does, and is willing to look at that gap directly. The BCS is exactly that kind of organisation, in exactly that kind of moment. The profession it serves is being reshaped by AI at a pace that makes conventional anticipation timelines obsolete. The members it represents are looking to it for guidance in conditions of genuine uncertainty. The governance challenges it faces are structural rather than attitudinal, and the structural challenges are the ones that conventional analysis alone cannot resolve. The network grows stronger with each connection. The flame burns brighter with each honest encounter. The BCS Leadership Team is the network. The question is whether it is building itself to carry the flame forward, or holding it inside a structure that will not outlast the people who built it.

Google:

Structural Blindness in Strategic Leadership: A Diagnostic Comparison

Prepared for: The British Computer Society (BCS) Leadership Team
Focus Area: Executive Decision-Making, Systemic Risk, and the Mechanics of Institutional Failure

Executive Summary

This paper addresses a foundational paradox in modern organizational governance: why well-resourced leadership teams, equipped with sophisticated diagnostic tools and explicit stakeholder mandates, systematically fail to meet expectations, anticipate catastrophic risks, or drive meaningful innovation.

To isolate the root causes of this phenomenon, the paper performs a comparative analysis. It first addresses these failures through standard institutional lenses (Enterprise Architecture, corporate risk theory, and traditional KPI design). It then analyzes the exact same systemic issues using the Weavers and the Web framework. Finally, it outlines the net-new strategic insights uncovered by transitioning to the Weavers model.

Part 1: The Standard Institutional Analysis

The traditional corporate governance and technology management view attributes leadership shortfalls to operational execution gaps, information filtering, and capital allocation constraints.

[ Traditional Management Model ]

Strategic Roadmap (KPIs/SLAs) ➔ Operational Processes ➔ Frontline Delivery

▲

Filtered Upward Reporting (RACI)

1. Failure to Meet Stakeholder Expectations

Traditional management theory views the gap between executive intent and actual delivery as a structural breakdown in the alignment of strategy, process, and performance metrics.

The Disconnect of Abstract Metrics: Strategies are frequently designed around aggregated financial indices or high-level Key Performance Indicators (KPIs). These abstractions mask the ground-level friction points, technical debt, and resource deficiencies that directly inhibit delivery.
Asymmetric and Filtered Reporting: Performance governance mechanisms, such as RAG (Red-Amber-Green) status trackers and RACI matrices, incentivise delivery teams to suppress bad news. Mid-level management filters data to show superficial project compliance, leaving executives blind to underlying delivery failures until they reach a breaking point.
Misaligned Incentive Frameworks: Executive tenure and reward cycles prioritize short-term milestones over multi-year systemic resilience. This decoupling encourages temporary patches over permanent fixes, leading to an inevitable collapse in long-term stakeholder value.

2. Failure to Identify Problems in Advance

Standard risk management paradigms attribute predictive blindness to isolated data silos, static compliance models, and a lack of true operational oversight.

Compartmentalised Risk Management: Corporate risk registers treat vulnerabilities as discrete events limited to individual departments (e.g., isolated IT, HR, or Legal risks). They fail to model risk as a dynamic web of dependencies where a minor failure in one node triggers a compounding cascade across the enterprise.
The Tick-Box Compliance Bias: Leadership frequently conflates regulatory compliance (e.g., passing a security audit, meeting a statutory guideline) with genuine operational resilience. This creates a false sense of security while leaving the actual, lived practices of the workforce unmonitored.
Optimism Bias in Program Assurance: Internal governance reviews are commonly compromised by a lack of independent verification. Project boards routinely accept optimistic completion schedules without conducting rigorous, code-level or ground-level technical assurance.

3. Failure to Innovate or Spot Future Trends

Legacy institutions struggle to navigate market and technology transitions due to institutional inertia, rigid budgeting models, and vendor dependency.

Capital Stifled by Technical Debt: The vast majority of corporate capital and technical talent is consumed by the continuous maintenance of fragile, legacy systems. This leaves minimal funding or cognitive capacity for disruptive research and development.
Predictive Extrapolation Errors: Market research and horizon-scanning teams rely heavily on historical trend data. This linear approach leaves leadership completely blind to sudden, non-linear technological shifts—such as rapid transitions in foundational AI architectures or cloud-delivery paradigms.
Vendor Lock-In and Roadmap Capture: Long-term, rigid procurement contracts link an enterprise’s technical trajectory to the commercial roadmaps of external suppliers. Leadership becomes incapable of adopting agile, open-source, or cutting-edge innovations because their architectural core is legally and technically bound to an incumbent vendor.

Part 2: The Weavers and the Web Analysis

The Weavers and the Web framework discards process-oriented explanations. It treats leadership failure as a deeper Sovereign Capability Crisis born from Ontological Enclosure and the decoupling of authority from frontline truth.

[ THE INCUMBENT TOWER ] (Proprietary / Closed System)

========= [ THE BROKEN CLOCK ] (Static Policy / Fixed Roadmap)

| || |

| [THE VINE] | (Protective Silos / Compliance Barriers)

| || |

==========================

[ THE SOIL / WEB ] (Tacit Knowledge / Real-World Context)

[THE BLUE FLOWER] (Fragile, Resource-Strained Practitioner)

1. Failure to Meet Stakeholder Expectations: The Dependency Cascade

Through the Weavers lens, expectations are missed because leadership relies entirely on Allocated Governance (the paper map) while remaining completely oblivious to Actual Governance (the reality map).

The Separation of Torch and Fire: The executive body holds the Torch (legitimate institutional authority) but lacks the Fire (the technical and practitioner knowledge required to govern the system). Consequently, major strategic decisions are outsourced to external contractors or vendors who step into this executive knowledge vacuum.
The Trajectory Commit: At the moment of system launch, a critical trajectory is locked in. If data logic is handed over to a proprietary third-party platform, the organisation surrenders its internal understanding.
The Dependency Cascade: The institution progresses through a fatal cascade: first outsourcing the doing (operations), then the understanding (data logic), and finally the direction (strategy). The leadership team can no longer meet stakeholder expectations because they no longer possess the internal capability to alter their own trajectory.

2. Failure to Identify Problems in Advance: The Proliferation of Vines

The framework demonstrates that predictive blindness is a structural product of information starvation caused by the unchecked growth of systemic barriers.

The Protectionism of the Vine: Horizontal and vertical silos (Vines) are intentionally grown within an organisation. They are planted by middle tiers for self-protection, compliance, or to hide operational strain. These vines sever the Golden Thread—the raw, unfiltered feedback loop that connects executive oversight to frontline reality.
The Suppression of the Signal: Impending failure is always felt first by the Blue Flower—the practitioner or participant with the fewest resources and the highest exposure to reality. Because the Vines block the Blue Flower’s voice from reaching the Torch, leadership receives only polished “success reports” generated by teams whose interests are served by maintaining executive confidence.
The Governance Default: When the system eventually fractures, leadership treats the failure as a structural anomaly. They re-arrange the boxes on the org chart (pruning the leaves) while leaving the underlying culture, incentives, and information blockages (the roots) completely untouched. The vine returns, stronger and better adapted to survive the next audit.

3. Failure to Innovate or Spot Future Trends: The Broken Clock of the Tower

Innovation and horizon scanning fail because centralized leadership structures are structurally built to repeat past assumptions rather than compound live learning.

The Architecture of Enclosure (The Tower): Closed, vendor-led software ecosystems represent an I-aligned Tower. These architectures are highly optimized for a static world but are entirely incapable of learning from external environments. They do not pass on or compound institutional memory.
The Small Tower Effect: When a closed strategic cycle ends or a proprietary contract terminates, the internal logic collapses because no native Network was built to sustain it. The organization is forced to clear the site and build a Small Tower right next to the old one—custom-rebuilding core competencies from scratch, trapped in an expensive cycle of perpetual duplication.
The Broken Clock: The executive strategy becomes a Broken Clock, permanently frozen at the specific moment the project requirements were defined. It remains blind to emerging “realistic futures.” The institution cannot innovate because its data layer is enclosed within an ontological moat; it must pay continuous Inference Rent to global technology providers just to analyze and interact with its own historical operational records.

Part 3: What New Insights Does the Weavers Framework Bring?

The value of shifting from a traditional management analysis to the Weavers and the Web framework lies in the diagnostic transitions outlined below:

1. Shifting Data from an “Asset” to “Soil”

Traditional models treat corporate data as a static commodity to be stored in data lakes and queried for optimization. The Weavers framework reveals that data is dynamic Soil. The data itself is useless unless the organization retains the native, sovereign capability to model, define, and interpret the semantic relationships (the ontology) within that soil. If a vendor owns the ontology, they own the soil, rendering the institution a tenant on its own land.

2. Redefining Silos as Active Organisms (“Vines”)

Standard Enterprise Architecture sees silos as passive design flaws or communication gaps to be solved with more meetings or software integrations. The Weavers framework identifies silos as Vines—active, self-reinforcing defensive structures that grow to block transparency. This insight alters the leadership action: you cannot “integrate” a silo away; you must deploy Independent Programme Assurance (IPA) as a structural vine-cutter to actively sever these information blocks and protect the feedback loop.

3. Re-Anchoring Strategy through the “Blue Flower”

Corporate planning usually focuses on the “Red Flowers”—the high-performing, well-funded departments that look excellent on board presentations. The Weavers framework introduces the Blue Flower Test as a core debugger of strategy. It dictates that the health of an entire enterprise system is determined by the participant with the fewest resources. If the digital architecture does not immediately ease the cognitive and operational load of the frontline worker, the strategy is failing, regardless of what the executive KPIs claim.

4. Exposing the Myth of the “Clean Slate” (The Small Tower)

Traditional project management treats a new transformation program as a fresh start, independent of past failures. The Weavers framework surfaces the hidden “elephant”: without an A-aligned (cooperative) network architecture, organizations are doomed to repeat the Small Tower cycle. They will continually spend massive capital to build temporary structures that collapse when the vendor contract expires, failing to build any compounding, sovereign institutional memory.

Conclusion: The Mandate for BCS Leaders

For the British Computer Society Leadership Team, the transition to the Weavers framework provides a vital diagnostic vocabulary for the modern technology landscape. It proves that traditional leadership failures are not caused by a lack of data, poor planning tools, or insufficient funding. They are caused by the loss of strategic sovereignty.

An organisation that systematically outsources its technical understanding and surrenders its operational logic to closed, proprietary towers completely loses the capability to govern its own future. The leadership mandate for the next decade must shift from the management of static corporate structures to the active cultivation of open, learning networks that protect the sovereign soil of our national institutions.

Proactive Next Steps

To advance your leadership strategy, consider exploring these critical areas:

Formulating the specific Sovereign Exit Protocols required to protect public sector data layers from long-term vendor enclosure.
Designing an Independent Programme Assurance (IPA) framework engineered to identify and cut information “vines” before major project delivery dates.
Deploying the Blue Flower Test within your current technology portfolio to map the exact discrepancy between board-level KPIs and frontline reality.