September 2026

Map the Whole System  The meeting that looked like a decision A few years ago I sat in a boardroom while a company approved a major technology investment. The strategy deck was polished. The business case showed a healthy return. The vendor demo had gone well. The vote was unanimous, and everyone left the room feeling like leaders. Eighteen months later, the program was late, the budget had nearly doubled, and the COO was quietly asking why operations had never been consulted about the rollout sequence. Nobody in that room had made a bad decision in isolation. Every individual pillar – strategy, architecture, economics, operations, suppliers, risk – had an owner, and every owner had done their job. But nobody owned the system. And that is where executive decisions actually live or die. That pattern is not rare. McKinsey surveyed 2,207 executives and found that only about a third believed the quality of decision-making in their organizations was very good – and 60% thought bad decisions were about as frequent as good ones. In a later large-scale study on CEO blind spots, McKinsey compared how CEOs rated themselves against how their boards and direct reports rated them across the six core responsibilities of the role – including aligning the organization – and found meaningful perception gaps: “unconsciously unskilled” zones where leaders don’t know what they don’t know. Organizational alignment sits precisely at the fault line between a decision and its consequences. Decision-quality gap – McKinsey survey of 2,207 executives The uncomfortable truth: most executive decisions are not wrong because leaders lack intelligence or information. They are wrong because the decision is made through a keyhole while the system around it stays invisible. The anatomy of an executive decision Over years of leading technology organizations – and advising boards and executive teams – I have come to map every significant decision as a system of six pillars orbiting one center: Strategy – Why are we doing this, and does it serve where we are going? Architecture – Can our systems, data, and organization actually carry it? Economics – What does it truly cost, and where does the value accrue? Operations – Can we run it, support it, and absorb the change? Suppliers – Who else holds our fate in their hands? Risk & Resilience – What happens when – not if – it goes wrong? Miss one pillar and you don’t get a slightly worse decision. You get a blind spot. And blind spots compound: a strategy-architecture gap becomes a budget overrun; an operations-supplier gap becomes an outage with no owner; an economics-risk gap becomes a breach you assumed was someone else’s problem. Alignment vs. decision outcome — illustrative model based on practitioner observation, not a statistical study Let’s walk the pillars the way I walk them with executive teams – with the questions, the data, and the stories that make each one concrete. The six pillars around the executive decision 1. Strategy: the decision must earn its place Every executive decision is a claim on finite resources, and strategy is the ledger that decides whether the claim is honored. The question is not “is this a good idea?” but “is this the best use of our next dollar, our next hundred people, our next year?” Here is what makes this pillar hard in practice: strategy is usually articulated at altitude, while decisions are made at ground level. The strategy says “customer-centric digital transformation.” The decision on the table is a $4M integration platform. Between those two statements lies an interpretive gap, and into that gap fall the most expensive misalignments I have seen. A composite example from my consulting work: a retail group approved a personalization engine because “personalization” appeared in its strategy deck. Nobody had asked the strategy-pillar question properly: which strategic outcome, measured how, and by when? Eight months in, marketing was optimizing click-through while the strategy actually prioritized basket size and retention. Same tool, same spend – different war. When we reframed the decision around the real strategic metric, the configuration, the data priorities, and even the vendor shortlist changed. The data: This gap between strategic intent and executional agility is measurable. In Gartner’s 2026 CIO and Technology Executive Survey – drawing on 2,500 participants – only 18% of CIOs said they can adjust technology investments and deployment plans at the pace their evolving business conditions require. Strategy that cannot be re-aimed is not strategy; it is a museum exhibit. Only 18% of CIOs can adjust technology investments at the required pace – Gartner 2026 CIO Survey The question I put to boards: If this decision succeeds completely, which line in the strategy document moves – and how will we know? 2. Architecture: the silent vote on everything Architecture is the only pillar that never attends the meeting and always determines the outcome. MIT’s Center for Information Systems Research (CISR) made this rigorous in Enterprise Architecture as Strategy (Ross, Weill & Robertson, 2006): companies that deliberately align their operating model – how standardized and how integrated their processes are – with their architecture outperform those that let architecture emerge by accident. The framework’s four operating models (Coordination, Unification, Diversification, Replication) are still the cleanest way I know to force the strategy-architecture conversation. Later MIT CISR research added a second, equally important lens: decision rights. Studying how organizations empower decentralized teams, CISR identified four guardrails that keep local decisions aligned with enterprise interests – guardrails built around purpose, data, policies, and resource allocation. In other words: architecture is not just systems. It is who is allowed to decide what, with which data, under which rules. The story I tell: In one organization, three business units each selected “best-of-breed” tools for the same function within the same year. Each decision was locally rational; each was defended in its own business case; each passed its own approval gate. The enterprise result: three contracts, three data models, three support models, and an integration bill that dwarfed any of the three