FIELD ENTRIES
By Rafa Munaro
Part I of a three-part series exploring how organizations survive, adapt and endure.
The Question
Have you ever wondered why some organizations adapt and compound over time, while others slowly decay?
Not necessarily through one catastrophic event.
But gradually.
Sometimes despite having:
- more resources
- more talent
- stronger brands
- larger market share
- or seemingly dominant positions
Over time, this question kept resurfacing across many of the environments that shaped the thinking behind SRV.
And eventually, it started feeling surprisingly similar to something we observe constantly in nature.
Across evolutionary history, species rarely disappear overnight.
Most decline gradually.
Environmental conditions shift. Resources become constrained. Previously useful traits become liabilities. Adaptation slows. Complexity increases.
Some species evolve and survive.
Others slowly disappear.
Organizations often behave in similar ways.
Like biological organisms, companies exist within external environments they do not fully control.
Markets shift. Competitors emerge. Technologies evolve. Customer behavior changes.
And just as natural selection acts as a filtering mechanism in biology, markets often play a similar role in business.
Organizations that adapt effectively tend to survive and compound.
Others slowly fall out of alignment with reality.
Over time, one thing became increasingly difficult to ignore:
there was no single explanation.
A Simplified Model
Of course, reality is far more complex than any simplified model could ever fully capture.
Organizations are messy, multi-causal, adaptive systems interacting with constantly changing environments.
But simplification is still useful.
Not because it perfectly explains reality.
But because it helps us understand the system at a higher level before diving deeper into the details.
At the broadest possible level, organizations can almost be thought of as systems that:
- exist within an external environment
- interpret that environment
- make strategic decisions
- and then configure themselves internally to execute against those decisions
In other words:
organizations respond to the outside world by aligning themselves internally around a chosen strategy.
The external world continuously creates pressure:
- markets evolve
- technologies shift
- competitors react
- customer behavior changes
- regulation emerges
- economic conditions fluctuate
Organizations then respond to those conditions by making strategic choices:
- where to compete
- how to compete
- what capabilities matter most
- and what kind of organization must exist to support those capabilities
And this is often where things start breaking down.
Because success rarely depends on strategy alone.
It depends on whether the organization can continuously align:
- people
- structure
- culture
- systems
- incentives
- and execution
with the reality of the environment it operates in.
Small misalignments rarely look dangerous at first. But over time, they compound.
A plane that deviates by a single degree early in a long flight may initially appear perfectly on course.
Twelve hours later, it ends up hundreds of kilometers away from its intended destination.
Organizations often drift in similar ways.
The outside world changes.
But internally:
- incentives remain frozen
- structures calcify
- processes optimize for yesterday’s conditions
- and capabilities that once created advantage slowly become rigidities
In many cases, organizations do not collapse because of one catastrophic decision.
They slowly drift out of alignment with reality.
The Outside Game
Strategic Management
Once you start looking outside the organization, another layer of complexity appears.
Markets evolve. Competitors adapt. Technologies shift. Customer expectations change.
At its core, strategy attempts to answer a deceptively simple question:
how do organizations create value and establish a favorable position in a changing environment?
Thinkers like:
- Michael Porter
- Igor Ansoff
- Clayton Christensen
- W. Chan Kim & Renée Mauborgne
all explored different dimensions of that question.
And one of the most humbling aspects of strategy is that:
there is no universal playbook.
A strategy only makes sense relative to:
- the environment
- the competition
- the customer
- and the moment in time
In many ways, strategy is ultimately about understanding:
what game you want to play, and how you intend to compete.
Or put differently:
how an organization chooses to respond to the external world around it.
The Inside Game
Organizational Alignment
Eventually, another question starts to emerge:
what must the organization become good at for that strategy to actually work?
One of the most useful ideas from organizational design is that strategy alone is rarely enough.
A strategy is only as good as its execution.
Execution depends on whether the organization is aligned around the capabilities that matter most.
In other words:
strategy determines which capabilities become critical
And then:
the organization must align itself to develop those capabilities
One useful simplification is to think about organizations through four core elements:
People
talent, leadership, incentives
Structure
roles, coordination, hierarchy
Culture
values, norms, behaviors
Systems
processes, workflows, governance
Much like a biological organism, an organization only functions effectively when its core systems operate in alignment.
The core idea is surprisingly simple:
all four elements must reinforce the capabilities required by the strategy.
Otherwise, organizations slowly drift into misalignment.
Different strategies require different organizational capabilities.
And different capabilities require different combinations of:
- people
- structures
- cultures
- and systems
Because ultimately:
strategy defines what matters,
organizational alignment determines whether it can happen.
Misalignment & Slow Decline
One pattern appears repeatedly across business history.
Organizations often remain optimized for environments that no longer exist.
Processes continue reinforcing outdated assumptions.
Incentives reward behaviors that once created advantage, but no longer fit current conditions.
Capabilities that once differentiated the organization slowly become rigidities.
Companies like:
- Kodak
- Nokia
- BlackBerry
- Blockbuster
clearly did not fail because they lacked intelligence, talent, or resources.
In many cases, they simply remained optimized for a game that was already changing.
And the longer that misalignment persists, the harder adaptation becomes.
Which means the challenge is rarely finding permanent answers.
More often, the challenge is continuously realigning the organization as reality changes.
Frameworks As Lenses
The deeper we explored these questions, the more another challenge started becoming visible.
Different disciplines seemed to illuminate different parts of the problem:
- strategy
- organizational architecture
- systems thinking
- behavioral psychology
- leadership
- competitive dynamics
- execution
- etc.
Each framework captured something real.
But none seemed capable of fully explaining organizational survival or decline on its own.
It started feeling a bit like the old parable of the blind men and the elephant.
Several blind men encounter an elephant for the first time.
One touches the trunk and concludes the elephant is like a snake.
Another touches a leg and believes it is like a tree.
Another feels the side and describes a wall.
Each perspective captures something real.
But none fully explains the whole system.
Organizations often feel similar.
Different theories illuminate different dimensions of reality, but reality itself is usually far messier, more interconnected, and more multi-causal than any single framework can fully capture.
That does not make frameworks useless. Far from it.
If anything, frameworks become useful precisely because reality is so complex.
They help simplify, organize, and interpret parts of systems that would otherwise be almost impossible to fully reason about.
Not as universal answers. But as lenses.
Ways of observing different dimensions of a much larger system.
Why Field Notes?
These Field Notes are simply an ongoing collection of observations, reflections, frameworks, and first-principles thinking around:
- organizations
- systems
- strategy
- adaptation
- incentives
- leadership
- and human behavior
All explored through the lens of trying to better understand how complex systems evolve, survive, fail, and endure over time.
Always somewhere at the intersection between:
- academic theory
- practice
- and real-world complexity
In many ways, these notes are less about finding certainty, and more about:
building better lenses for navigating complexity, making better decisions, and understanding the systems that increasingly shape the world around us.
Download Resources
Field Note 001 — Full Essay (PDF)
Long-form archival version of this essay.
Organizational Alignment Model
A simplified visual framework exploring the relationship between external reality, strategy, capabilities, and organizational alignment.
Field Sheet 001 — The Organizational Alignment Model
A one-page operational synthesis of the core principles, dynamics, and systems explored throughout this Field Note.
Selected References & Influences
Selected influences behind many of the ideas explored throughout these notes include:
- Michael Porter
- Igor Ansoff
- Clayton Christensen
- W. Chan Kim & Renée Mauborgne
- Richard Rumelt
- Henry Mintzberg
- Peter Senge
- Edgar Schein
- Daniel Kahneman
- Richard Thaler
- Johnson, Scholes & Whittington — Exploring Strategy
along with broader work in:
- systems thinking
- organizational behavior
- complexity science
- evolutionary theory
- and behavioral psychology
By Rafa Munaro
Part II of a three-part series exploring how organizations survive, adapt and endure.
Questions Worth Asking
Why do some organizations seem capable of anticipating change while others spend years reacting to it?
Why do industry leaders sometimes disappear despite having talented people, strong brands and abundant resources?
And why do two organizations facing the same market conditions often make completely different strategic choices?
These questions appear different on the surface, but they all point toward the same underlying challenge.
Organizations do not operate in isolation. They exist within environments that are constantly changing. Customers evolve. Competitors adapt. Technologies emerge. Entire industries can be reshaped by forces that initially appear small or insignificant.
The organizations that endure are rarely those that predict the future perfectly. More often, they are the organizations that develop a better understanding of the present and continuously update that understanding as reality changes around them.
Before organizations can adapt, they must first learn to see.
And that is where strategy begins.
Looking Back
In the previous Field Note (Field Note 001 – Why Some Organizations Endure While Others Slowly Fail), we introduced a simple but powerful idea.
Organizations exist between two worlds:
- An external world they cannot control
- And an internal world they can design
The external world consists of markets, competitors, technological shifts, customer behaviour, regulation and broader industry dynamics.
The internal world consists of people, structures, systems, culture, incentives and capabilities.
Long-term performance depends on maintaining alignment between the two.
When organizations remain aligned with reality, adaptation becomes possible. When small misalignments begin to accumulate, decline often starts long before anyone notices.
One of the central arguments of the previous note was that failure is rarely sudden. More often, it emerges from a long series of small misalignments between what is happening outside the organization and how the organization continues to operate inside it.
This note focuses on the first half of that equation. The outside world.
Why Start Outside?
When people think about organizational performance, they often focus on what happens inside the organization.
- Leadership
- Culture
- Talent
- Execution
- Structure
- Systems
These factors are undoubtedly important, but they are only part of the story.
A highly capable organization can still fail if it is responding to a version of reality that no longer exists.
History provides no shortage of examples. Kodak possessed extraordinary capabilities in film manufacturing. Nokia employed some of the world’s most talented engineers. Blockbuster dominated its industry for years. None of these organizations lacked intelligence, resources or operational expertise.
Their challenge was different.
The environment changed faster than their understanding of it.
The lesson is subtle but important.Organizations rarely fail because they stop executing. They often fail because they continue executing against assumptions that no longer reflect reality.
This is why strategy begins outside.
Before deciding how to organize ourselves, we must first understand the environment in which we are operating. Before deciding how to compete, we must first understand the game itself.
What Is Strategy?
Few words have become as overused in modern business as strategy.
Projects become strategic. Meetings become strategic. Priorities become strategic. Roadmaps become strategic. At times, the word seems to function less as a precise concept and more as a signal that something is important.
The result is that strategy gradually loses meaning.
Michael Porter offered a much more demanding interpretation:
“The essence of strategy is choosing what not to do.”
This idea is deceptively simple.
Most organizations spend considerable time discussing what they should pursue. Far fewer spend time discussing what they should deliberately ignore.
Yet meaningful strategy requires trade-offs.
An organization cannot pursue every opportunity, serve every customer, enter every market and maintain every possible source of competitive advantage simultaneously. Resources are finite. Attention is finite. Time is finite.
Strategy therefore becomes the process of making choices.
Choices about where to play.
Choices about how to compete.
Choices about which opportunities deserve commitment and which should be left behind.
Before those choices can be made, however, organizations must first understand the environment within which those choices exist.
The Strategy Pyramid
One useful way to think about strategy is through three interconnected layers.
The first layer is Strategy Context.
This concerns understanding the environment surrounding the organization.
The second layer is Strategy Content.
This concerns deciding how the organization intends to compete within that environment.
The third layer is Strategy Process.
This concerns implementation and organizational alignment.
In simple terms:
- First we observe
- Then we choose
- Then we execute
This framework also serves as the roadmap for the broader Field Notes series.
This note focuses on Strategy Context and Strategy Content.
The next note will focus on Strategy Process and the organizational architecture required to bring strategic choices to life.
ACT I
Strategy Context
Reading Reality
The first responsibility of strategy is not action.
It is interpretation.
Organizations operate within environments that are constantly evolving. Customers change their preferences. Competitors launch new products. Technologies reshape industries. Regulations alter market dynamics. Economic conditions create both opportunities and threats.
The challenge is rarely a lack of information.
The challenge is determining which information matters.
Over time, strategists developed a variety of frameworks designed to help organizations interpret the environment more systematically. While these frameworks differ in form, they are ultimately trying to answer the same question:
What is happening outside the organization that deserves our attention?
- Some frameworks focus on customers
- Some focus on competitors
- Some focus on industries
- Others focus on broader environmental forces
Together, they help organizations construct a more complete picture of reality.
Understanding Customers
Organizations exist to create value for specific groups of people. Understanding who those people are, what they value and how those preferences evolve over time is therefore one of the foundational responsibilities of strategy.
Some of the classic frameworks used to explore this layer include Customer Segmentation, Customer Analysis, Targeting and Market Mapping, many of which may become future Field Notes in their own right.
Understanding Competitors
No organization operates alone. Every strategic choice is made within a competitive landscape that includes direct competitors, indirect competitors and substitutes.
Frameworks such as Competitor Analysis (direct + indirect), Strategic Groups and Substitute Analysis attempt to help organizations understand not only who they compete against today, but who they may be competing against tomorrow.
Understanding Industries
Beyond individual competitors lies the broader structure of the industry itself.
Some industries are naturally attractive. Others are structurally difficult. Some reward scale. Others reward specialization.
Classic frameworks such as Industry Analysis, Value Chain Analysis and Porter’s Five Forces help explain why profitability varies so dramatically across industries and why some competitive environments are far more challenging than others.
Understanding the Broader Environment
Organizations are also shaped by forces that exist beyond customers, competitors and industries.
- Technological shifts
- Regulation
- Political change
- Social movements
- Economic conditions
- Environmental pressures
Frameworks such as PESTEL, Environmental Scanning and Scenario Analysis attempt to capture these broader forces and help organizations identify emerging trends before they become obvious.
The goal is not prediction.
The goal is awareness.
Because organizations rarely fail because change occurs. More often, they fail because they fail to notice it.
Act I Summary – Seeing The Pattern
Up to this point we have explored customers, competitors, industries and broader environmental forces as separate lenses. The diagram below brings those pieces together into a simplified view of how organizations interpret reality before making strategic choices.
Reflection From The Field
Most strategic surprises are visible long before they become obvious.
The challenge is rarely access to information.
The challenge is attention.
What assumptions about your customers, competitors or industry are you currently treating as permanent?
And what happens if those assumptions are already changing?
ACT II
Strategy Content
Choosing How To Compete
Understanding reality is necessary.
It is not sufficient.
At some point every organization must decide what it intends to do with what it has learned.
This is where strategy moves from observation to choice.
If Strategy Context asks:
“What is happening?”
Strategy Content asks:
“What should we do about it?”
Two organizations can observe the same environment and reach completely different conclusions. The same customers, competitors, technologies and industry dynamics can lead to radically different strategic choices.
This is the domain of Competitive Strategy.
At its simplest, Competitive Strategy can be understood as:
Value Creation + Establishing a Favourable Competitive Position in the Market
In other words, it concerns both the value an organization creates and the position it seeks to establish within its chosen market.
The challenge is not simply creating value.
Many organizations create value.
The challenge is creating value in a way that allows the organization to occupy a distinctive and sustainable position relative to competitors.
Everything that follows can be understood as different dimensions of that challenge.
Understanding Competitive Strategy
Value Creation & Business Models
The first question any strategy must answer is deceptively simple:
What value are we creating, and for whom?
Organizations exist because they create value for customers, employees, investors or communities. Without value creation there is no reason for the organization to exist. Without value capture there is no reason for the organization to survive.
This is why many strategic frameworks begin with concepts such as Value Creation, Value Capture and Business Models. They help organizations understand not only how value is generated, but also how it can be sustained over time.
Know Your Competitive Options
Strategic Positioning
Creating value is only part of the equation.
Organizations must also decide how they intend to compete.
- Will they compete through lower costs?
- Through differentiation?
- Through specialization?
- Through focus?
This is the domain of Strategic Positioning.
Classic frameworks such as Generic Strategies, Cost Leadership, Differentiation and Focus attempt to answer a central question:
Given the environment we face, what kind of position are we trying to establish?
Different positions require different choices.
And different choices inevitably create different trade-offs.
Strategic Fit
Capabilities & Resources
Even the most attractive opportunity can become dangerous if an organization lacks the capabilities required to pursue it.
This is why strategy cannot be separated from capabilities.
- An organization may wish to compete through innovation, but does it possess innovative capabilities?
- It may wish to compete through operational excellence, but does it possess operational excellence?
Frameworks such as the Resource-Based View, VRIO, Key Capabilities and Strategic Fit attempt to answer a critical question:
Do our ambitions actually match our capabilities?
The strongest strategies are rarely those that chase every opportunity. They are the ones that align opportunities with capabilities.
Strategic Choice, Growth & Renewal
Organizations rarely face a shortage of options.
The challenge is deciding which options deserve commitment.
- Some opportunities appear attractive but are strategically inconsistent.
- Others fit the organization’s capabilities but offer limited long-term potential.
This is why strategic choice ultimately becomes an exercise in judgment.
Frameworks such as SAF, BCG Matrix, Ansoff Matrix, Blue Ocean Strategy and Strategic Ambidexterity provide different lenses for evaluating opportunities, balancing risk and deciding where future resources should be allocated.
Their purpose is not to provide answers. Their purpose is to improve decisions.
Act II Summary – Choosing How To Compete
Understanding reality is only half of the challenge. Once an organization has a clearer picture of its environment, it must decide what to do with that understanding. This is the domain of strategy content: transforming observations into choices about where to play, how to compete and what capabilities deserve investment.
The diagram below summarizes the core logic explored throughout this section, from value creation and value capture to competitive positioning, strategic fit and sustainable advantage.
Reflection From The Field
Organizations rarely struggle because they lack options.
Most industries offer more opportunities than any organization could realistically pursue.
The challenge is deciding which opportunities deserve commitment and which should be deliberately ignored.
Competitive Strategy is ultimately less about maximizing possibilities and more about making choices.
The Organizational Alignment Model
Bringing The Pieces Together
Up to this point we have focused primarily on the outside world and on the choices organizations make in response to it.
But strategy only creates value when it can be translated into execution.
The model below reconnects the pieces discussed so far and shows how context, content and process interact as a single system.
Looking Ahead
At this point we have explored the two halves of the outside world.
- Understanding reality.
- And deciding how to respond to it.
Yet even the most insightful strategy eventually encounters a second challenge.
Execution.
A strategy can identify the right opportunity, define a compelling position and establish a clear direction. Yet it can still fail.
Because organizations do not execute strategies. People do.
Which raises a different question.
How should an organization be designed to support the strategy it has chosen?
That question takes us inside the organization.
In the next Field Note, we will explore the second half of the equation:
- People.
- Structure.
- Culture.
- Systems.
The elements that determine whether strategy remains an intention, or becomes reality.
Download Resources
Field Note 002 — Full Essay (PDF)
Long-form archival version of this essay.
Field Sheet 002 — Understanding The Outside World (PDF)
A one-page operational synthesis of the core ideas, frameworks and strategic questions explored throughout this Field Note.
The Organizational Alignment Model (Enhanced) (PDF)
A visual framework illustrating how organizations interpret their environment, make strategic choices, develop capabilities and continuously realign themselves in response to change.
Selected References & Influences
Selected influences behind many of the ideas explored throughout these notes include:
- Michael Porter
- Richard Rumelt
- Henry Mintzberg
- Igor Ansoff
- Johnson, Scholes & Whittington
- W. Chan Kim & Renée Mauborgne
- Clayton Christensen
- Jay Barney
- Gary Hamel
- C.K. Prahalad
along with broader work in:
- competitive strategy
- strategic management
- industrial economics
- systems thinking
- organizational theory
- behavioral psychology
- complexity science
By Rafa Munaro
Part III of a three-part series exploring how organizations survive, adapt and endure.
Strategic Alignment and the Capabilities That Matter Most
One of the ideas introduced in the first Field Note was that organizations exist between two worlds: an external world they cannot control, but must continuously observe, interpret, and respond to, and an internal world they can deliberately design and shape. Long-term performance depends on maintaining alignment between the two.
The second Field Note focused on the first half of that equation. It explored how organizations make sense of the world around them, how they interpret changes in customers, competitors, industries, technologies, and broader environmental forces, and ultimately how they translate those observations into strategic choices about how they intend to compete and the position they hope to occupy within that environment.
ACT I
The Alignment Challenge
The How
Understanding the environment is important. Choosing how to compete is equally important. Yet neither, by itself, is enough.
Two organizations can observe the same environment, face the same competitors, and even pursue similar strategic objectives, yet achieve dramatically different outcomes. The difference often lies in what happens next.
Once an organization has interpreted the world around it and decided how it intends to compete within that world, it faces a new challenge. It must decide how to configure itself to support that choice.
In some ways, the challenge is similar to preparing a vessel for a journey. Understanding the waters you are navigating is important. Deciding where you want to go, and the route you intend to follow, is equally important. But the vessel itself must still be configured for the voyage ahead. Its structure, crew, instruments, supplies, operating procedures, and the way responsibilities and resources are distributed must all work together in support of the journey.
Organizations face a remarkably similar challenge. There are countless ways to structure teams, distribute authority, shape culture, design systems, develop talent, allocate resources, and measure performance. Some organizations operate through rigid hierarchies, while others rely on decentralized decision-making. Some emphasize discipline, consistency, and control, while others prioritize experimentation, autonomy, and innovation. Some reward efficiency, while others reward learning.
None of these choices are inherently right or wrong. At least not in isolation. Not in absolute terms.
Yet some configurations will move an organization closer to its strategic objectives than others.
Which raises an important question:
How should an organization be configured?
It Depends
So, how should an organization be configured?
The answer is: it depends.
At first, this can feel frustrating, almost like a non-answer. Yet the deeper one goes into organizations, the more difficult it becomes to answer management questions in absolute terms.
Is a flat organization better than a hierarchical one? Should decisions be centralized or decentralized? Is culture more important than structure? Should organizations prioritize specialists or generalists?
The answer to all of these is usually the same.
It depends.
Not because these questions are impossible to answer, but because they are incomplete.
Relative to What?
Better according to whom?
Better for what?
Better relative to what?
Before a strategy has been chosen, there are many ways an organization could be configured. Different structures. Different cultures. Different systems. Different approaches to managing people.
But strategy changes the nature of the problem.
Once an organization decides how it intends to compete, some choices begin to make more sense than others because the strategy becomes the reference point. Many possibilities remain, yet the range of good answers begins to narrow.
Just like there may be many types of vessels to choose from, and countless ways to configure them, before a destination has been set, there are endless ways an organization could be configured before a strategy has been chosen.
None is inherently better than the others.
But once a destination and course are clear, some begin to make more sense than others.
You wouldn’t want to cross an ocean on a kayak, nor navigate a river on a cruise ship. Not because either vessel is inherently better, but because some configurations are simply better suited to the journey ahead.
But then again, what makes certain configurations better suited to the journey than others?
What exactly should these configurations be designed to enable?
ACT II
The Capabilities That Matter Most
Key Capabilities
The answer lies in what many organizations overlook when discussing strategy, structure, culture, or execution: key capabilities.
Once an organization has interpreted its environment and decided how it intends to compete, the next challenge is understanding what it needs to become exceptionally good at in order to successfully execute that strategy.
This may sound like a subtle distinction, but it changes the nature of the problem entirely.
The Logic Runs the Other Way
Many organizations begin by looking inward. They examine their existing strengths, resources, expertise, and assets, then attempt to build a strategy around them.
The logic often sounds something like this:
“We are good at X, therefore we should pursue Y.”
Yet strategic thinking typically works in the opposite direction. The starting point is not what the organization is currently good at. The starting point is what the organization is trying to achieve.
The question changes.
Not:
“What are we good at?”
But:
“What must we become exceptionally good at in order to succeed?”
Those capabilities may already exist within the organization. They may need to be strengthened. Or they may need to be built almost from scratch.
Either way, the logic runs from strategy to capabilities, not the other way around.
The strategy determines which capabilities matter most.
And those capabilities, in turn, begin to shape how the organization should be configured.
- The way people are selected, developed, and deployed (People).
- The way work is organized and responsibilities are distributed (Structure).
- The behaviors, norms, and values that are encouraged and reinforced (Culture).
- The systems used to coordinate, measure, and manage performance (Systems).
In other words, the capabilities an organization seeks to develop eventually influence every major element of its internal design.
At a high level, the relationship looks something like this:
Choosing the Game
The relationship between strategy and capabilities becomes easier to understand when viewed through a different lens.
Consider an athlete.
A marathon runner, a sprinter, a weightlifter, and a sumo wrestler may all share the same objective: winning. Yet each must develop a very different set of capabilities if they hope to succeed in their chosen sport.
A marathon runner must prioritize endurance. A sprinter must prioritize explosive speed. A weightlifter must develop strength and power. A sumo wrestler must develop mass, balance, leverage, and technique.
Each athlete trains differently because each athlete is trying to achieve something different.
Organizations face a remarkably similar challenge.
A company competing primarily on price requires different capabilities than one competing on premium service. A luxury hotel requires different capabilities than a low-cost airline. A business built around customized solutions requires different capabilities than one built around standardization and scale.
So which capabilities matter most?
It depends.
But we now understand why.
The capabilities that matter most depend on the game being played.
And the game being played is determined by strategy.
- The strategy determines the game.
- The game determines the key capabilities.
- And those key capabilities begin to shape every major aspect of the organization.
Once that relationship becomes clear, many organizational choices that previously seemed subjective begin to make more sense. The capabilities required to compete successfully start to reveal what the organization should prioritize, where resources should be allocated, which trade-offs must be accepted, and ultimately how the organization should be configured.
In that sense, strategy does more than define a destination.
It also determines what the organization must become exceptionally good at along the way.
Focus
Why Focus Matters
Not all capabilities matter equally.
Every organization possesses dozens, sometimes hundreds, of competencies, processes, resources, and strengths. Yet only a small number typically play a decisive role in determining whether its strategy succeeds or fails.
This is what makes identifying key capabilities so important.
When organizations correctly identify and develop the capabilities most closely linked to their strategy, resources tend to reinforce one another. Investments become more coherent. Priorities become clearer. Trade-offs become easier to make.
When they do not, the opposite often occurs.
Resources become fragmented. Effort gets spread across too many initiatives. Attention drifts away from the capabilities that matter most. The organization remains busy, but gradually becomes less effective.
The challenge, therefore, is not developing every capability.
It is identifying and strengthening the few capabilities that matter most.
Too Broad. Too Narrow.
One of the challenges highlighted by Chris Zook is that organizations often struggle to define their capabilities at the right level.
Some define them too broadly.
Others define them too narrowly.
- Capabilities that are too broad become difficult to translate into decisions and actions. They provide little guidance when allocating resources, making trade-offs, or deciding where to invest.
- Capabilities that are too narrow create a different problem. They may be highly relevant to a specific product, process, or market, yet become obsolete as the organization evolves or the environment changes.
The goal is not simply to identify capabilities.
It is to identify the right capabilities at the right level of abstraction.
Capabilities that are specific enough to guide decisions, yet broad enough to remain strategically relevant over time.
Lessons from the Field
One of the examples Chris Zook frequently uses to illustrate this idea is Domino’s.
Most people would not consider Domino’s the best pizza chain in the world. Yet it has consistently outperformed many competitors that arguably offer a better product.
According to Zook, the company’s success comes from understanding something deceptively simple: competitive advantage rarely comes from being good at everything. More often, it comes from becoming exceptional at a small number of capabilities that matter most. In Domino’s case, those capabilities include delivery, packaging, franchising, convenience, and technology-enabled customer experience.
The challenge, however, is that identifying those capabilities is far harder than it sounds.
Organizations frequently misidentify their core capabilities or misunderstand where those capabilities should be applied.
Zook highlights four common traps.
MySpace (Too Broad)
As MySpace grew, it expanded across an increasingly wide range of initiatives and priorities. Rather than deepening the capabilities that had originally created its advantage, the company became involved in too many things at once. In the process, focus eroded and competitive advantage weakened.
Blockbuster (Too Narrow)
Organizations can also define their core too narrowly. Blockbuster saw itself primarily as a network of physical video rental stores. As the industry evolved, this definition constrained its ability to recognize and invest in adjacent opportunities. By remaining anchored to a shrinking definition of its business, it struggled to adapt to a changing environment.
LEGO (Wrong Shifting)
LEGO’s challenge was different. In the 1990s, the company expanded into a broad range of initiatives that moved it away from the capabilities that had historically defined its success. Over time, complexity increased while performance deteriorated. Its recovery began only after refocusing on the capabilities that sat at the heart of the business.
US Concrete (Multiple Battlefronts)
Another common trap emerges when organizations attempt to compete across too many products, segments, geographies, or customer groups simultaneously. As resources become dispersed, maintaining excellence becomes increasingly difficult. US Concrete eventually reversed this pattern by narrowing its focus and concentrating resources on the areas where it could compete most effectively.
The specific circumstances differ from case to case, yet the underlying lesson remains remarkably consistent.
The challenge is not simply identifying a core capability.
The challenge is defining that core accurately, protecting it from dilution, and continuing to invest in it as the organization grows.
The patterns described above appear so frequently that Zook summarizes them into four recurring ways organizations misidentify or lose sight of their core.
Which raises another question:
How do organizations identify the capabilities that matter most?
Finding the Few That Matter
No Universal Formula
There is no universal formula for identifying key capabilities.
Different industries require different capabilities. Different strategies create different requirements. And capabilities that matter today may become less important as technologies, markets, and customer expectations evolve.
Yet despite these differences, there are a few useful ways to begin.
Checklists
One approach is to start with existing capability frameworks and use them as a checklist.
Researchers such as Chris Zook, Dave Ulrich, and Norm Smallwood have spent years studying the capabilities that frequently underpin competitive advantage.
Some of the capabilities that appear repeatedly across their work include:
- Talent and Leadership
- Speed and Adaptability
- Innovation and Learning
- Customer Connectivity
- Operational Excellence
- Collaboration across Boundaries
Their frameworks are not intended to provide the answer, but they can help narrow the search and stimulate thinking.
Following the Value
A second approach is to examine how value is actually created inside the business.
Tools such as Porter’s Value Chain encourage leaders to look beyond products and outcomes and focus instead on the activities that generate value.
Often, key capabilities emerge not from a single activity but from clusters of interconnected activities that reinforce one another.
Business Judgment
The third approach is simpler, though no less important.
Leaders can ask a straightforward question:
If this capability disappeared tomorrow, would our ability to execute the strategy be fundamentally compromised?
Capabilities that consistently survive this test tend to reveal themselves rather quickly.
Triangulation
None of these approaches is perfect in isolation.
Capability frameworks help broaden the search. Value chain analysis helps reveal where value is actually being created. Business judgment helps determine which capabilities are truly essential.
Together, they create a useful form of triangulation. And when all three begin pointing toward the same capabilities, leaders are often getting close to the answer.
ACT III
Aligning the Organization
At this point, it is worth acknowledging that each of the topics that follow could easily justify a Field Note of its own.
People, structure, culture, and systems are enormous subjects. Entire careers have been built studying each of them.
The goal here is not to explore them in depth, but to step back and look at the bigger picture.
Across these three Field Notes, the objective has been to understand how organizations survive, adapt, and endure. Field Note 001 introduced the idea that organizations exist between two worlds: an external world they must continuously observe, interpret, and respond to, and an internal world they can deliberately design and shape. Field Note 002 focused primarily on the external world and the strategic choices that emerge from it. This note has focused on the capabilities required to successfully execute those choices.
What remains is the final piece of the puzzle.
How organizations translate capabilities into reality.
How strategy becomes something people actually do every day.
While different authors use different terminology, most discussions of organizational design eventually converge around four fundamental elements:
- People
- Structure
- Culture
- Systems
Together, these elements shape an organization’s ability to develop, strengthen, and sustain the capabilities that matter most.
What follows is a deliberately simplified overview. The goal is not to explore each element in depth, but to understand how they work together to translate strategy into capabilities, and capabilities into performance.
People
Many organizations proudly claim that people are their most important asset.
The statement sounds appealing, yet from a strategic perspective it is incomplete.
The challenge is not simply having talented people. The challenge is having the right people in the right roles, developing the capabilities that matter most to the strategy.
Once an organization has identified its key capabilities, a new question emerges:
Which roles contribute most directly to building, strengthening, and sustaining those capabilities?
Not all roles contribute equally.
Some sit much closer to the capabilities that create competitive advantage. Others play important supporting functions. Still others exist primarily to ensure reliability, compliance, or operational continuity.
This is not a statement about the value of people.
It is a statement about the strategic importance of roles.
Relative to the Strategy
Consider two airlines.
One competes primarily through low prices, operational efficiency, and fast turnaround times. The other competes through premium service, customer experience, and hospitality.
Which role is more important?
The pilot?
If there is one idea I hope readers take away from this series, it is that the answer should immediately feel familiar.
It depends.
In the first airline, ground crews, operations teams, and scheduling functions may sit closest to the capabilities that create competitive advantage. In the second, flight attendants and customer-facing staff may play a far more central role because they directly shape the experience the company is using to differentiate itself.
The question is not which role is more important in absolute terms.
The question is which role is most important relative to the strategy being pursued and the capabilities required to execute it successfully.
The Same Role, Different Strategies
Perhaps the most interesting implication of all this is that the very same role can occupy different positions depending on the strategy being pursued.
A flight attendant in a premium airline may sit much closer to the capabilities that create competitive advantage than a flight attendant in a low-cost carrier. Likewise, a pilot may be strategically central in one business model and far less central in another.
The individuals may possess similar credentials, training, and experience.
What changes is the strategy.
And once again, the answer turns out to be the same one that has appeared repeatedly throughout these Field Notes:
It depends.
More specifically, it depends on the capabilities required to successfully execute the strategy.
Strategic Priorities
Once key capabilities have been identified, organizations face a practical reality.
Resources are limited. Time is limited. Attention is limited. Development budgets are limited.
As a result, choices must be made.
Which roles should receive the greatest development?
Which positions require the strongest retention efforts?
Where will additional investment create the greatest impact on the capabilities the organization is trying to build?
One way to think about the problem is through a simple thought experiment.
If a particular role disappeared tomorrow, how significantly would the organization’s ability to execute its strategy be affected?
Some absences would be disruptive.
Others would fundamentally undermine capabilities that sit at the core of the business.
This is not a statement about the importance of people.
It is a statement about the importance of capabilities.
Just as organizations cannot invest equally in every market, every product, or every capability, they cannot invest equally across every role.
Strategic alignment requires prioritization.
The objective is not to determine who matters most.
The objective is to ensure that investments in people are aligned with the capabilities the strategy requires.
Structure
Once organizations have identified the capabilities they need and the people required to develop them, another question emerges:
How should those people be organized?
- Should decisions be centralized or decentralized?
- Should organizations be organized by functions, products, customers, or geographies?
- Should authority sit at the center or closer to the front line?
As with many of the questions explored throughout these Field Notes, the answer is familiar:
It depends.
Different structures enable different capabilities.
Organizations have developed many ways of organizing themselves over time, including functional, divisional, geographic, matrix, networked, and more recently agile designs. Entire books have been written comparing the strengths and weaknesses of each.
Fortunately, understanding every structural model is not necessary for our purposes.
What matters is a simpler observation:
Different strategies require different capabilities, and different capabilities often require different structures.
A company competing through operational efficiency will typically organize itself differently than one competing through innovation, customer experience, or local responsiveness.
A useful way to think about this is to imagine two very different organizations.
The first operates a nuclear power plant.
The second is a startup searching for a breakthrough innovation.
Would we expect them to have the same structure?
Probably not.
A nuclear facility may benefit from clear hierarchies, tightly defined responsibilities, standardized procedures, and carefully controlled decision-making. Reliability, consistency, and risk reduction sit at the heart of its mission.
An innovative startup often faces a very different challenge. Experimentation, rapid learning, adaptability, and speed may matter far more than consistency. Decision-making is frequently pushed closer to the front line, communication becomes more fluid, and structures tend to be less formal.
Neither approach is inherently better.
Each simply reflects a different set of strategic priorities and the capabilities required to support them.
As with people, the question is not which structure is best in absolute terms.
The question is which structure best supports the capabilities the strategy requires.
The Trade-Offs
One reason organizational design is so challenging is that every structure involves trade-offs.
Organizations often seek efficiency, responsiveness, and coordination simultaneously. Unfortunately, structure rarely allows all three to be maximized at the same time.
- Improving efficiency frequently reduces responsiveness.
- Increasing responsiveness can create duplication and reduce efficiency.
- Strengthening coordination often introduces additional complexity and slows decision-making.
The challenge, therefore, is not finding the perfect structure. The challenge is deciding which trade-offs are worth making.
- A low-cost airline may willingly sacrifice some local flexibility in exchange for consistency and efficiency.
- A luxury hotel chain may accept higher costs in exchange for greater responsiveness to guest needs.
- A global consulting firm may tolerate additional complexity in order to coordinate expertise across industries, regions, and client segments.
Different strategies require different capabilities. And different capabilities inevitably lead to different trade-offs.
Simplicity Matters
Perhaps the most consistent lesson from organizational design is that complexity tends to arrive faster than value.
As organizations grow, layers, committees, processes, and reporting lines tend to accumulate. Some are necessary. Many are not.
For that reason, organizational design experts often arrive at remarkably similar advice:
Keep it simple.
Structure should help people execute the strategy more effectively. When it becomes an obstacle to execution, it is often a sign that the organization has drifted away from what matters most.
Ultimately, structure is not an end in itself. It is simply another mechanism for developing and sustaining the capabilities that create competitive advantage.
Culture
Even with the right people and the right structure, another question remains:
How do organizations influence behavior?
Every organization has goals, priorities, and capabilities it is trying to develop. Yet capabilities do not emerge simply because leaders announce them.
People ultimately decide how to spend their time, what to prioritize, which risks to take, and how to behave when unexpected situations arise.
In other words, capabilities are expressed through behavior.
Which raises a new challenge:
How do organizations encourage the behaviors that support the capabilities they are trying to build?
More Than Words
Organizational culture is often described as “the way we do things around here.“
While simple, the definition captures something important.
Culture is often compared to an iceberg.
A small portion is visible above the surface: mission statements, values posters, office layouts, dress codes, company slogans, and other visible artifacts.
Yet most of culture sits below the surface.
It exists in the norms people follow, the stories they tell, the symbols they recognize, the rituals they repeat, and the assumptions they rarely question.
Like a fish unaware of the water surrounding it, people inside organizations often struggle to see the culture that shapes their behavior every day.
Most importantly, culture influences behavior.
And behavior ultimately determines whether capabilities are strengthened or weakened over time.
Different Cultures Encourage Different Behaviors
Researchers have proposed many ways of understanding organizational culture. One of the most widely used frameworks is Cameron and Quinn’s Competing Values Framework, which identifies four broad cultural archetypes:
- Clan cultures emphasize collaboration, belonging, and people development.
- Adhocracy cultures emphasize innovation, experimentation, and risk-taking.
- Market cultures emphasize competition, achievement, and results.
- Hierarchy cultures emphasize stability, control, consistency, and risk management.
Most organizations contain elements of all four, although one or two typically dominate.
As with many of the themes explored throughout these Field Notes, the goal is not to determine which culture is best.
The goal is to understand which behaviors a particular culture encourages and whether those behaviors support the capabilities the strategy requires.
Relative to the Strategy
Consider the same two organizations introduced earlier.
A nuclear power plant and an innovative startup.
Would we want them to share the same culture?
Probably not.
A nuclear facility may benefit from a culture that emphasizes discipline, consistency, compliance, and risk avoidance. The consequences of experimentation in the wrong place can be catastrophic.
An innovative startup faces a very different challenge. Learning, experimentation, adaptability, and intelligent risk-taking may be essential to survival.
In Cameron and Quinn’s language, the first organization may naturally lean toward a hierarchy culture, while the second may lean toward an adhocracy culture.
Neither is inherently better.
Each simply supports a different set of capabilities.
Once again, the answer depends on the strategy.
What Gets Reinforced Gets Repeated
One of the most common mistakes leaders make is assuming that culture is determined by what organizations say.
In practice, culture is shaped far more by what organizations consistently reinforce.
- An organization may claim to value innovation, yet punish every failed experiment.
- It may claim to value collaboration, yet reward only individual achievement.
- It may claim to put customers first, yet promote efficiency above all else.
Over time, employees learn which behaviors are genuinely valued and which exist only in mission statements and presentations.
Culture is therefore not defined by slogans.
It is defined by repeated signals.
What gets rewarded gets repeated.
What gets tolerated persists.
And what leaders consistently reinforce gradually becomes part of the culture itself.
An interesting implication follows from this observation.
The same mechanisms that reveal a culture can often be used to change it.
- If culture is shaped by what gets rewarded, leaders can redesign incentives.
- If culture is reinforced through stories, leaders can change which stories are celebrated and repeated.
- If culture is reflected in symbols and rituals, those symbols and rituals can be redesigned.
In other words, culture rarely changes because people are told to behave differently.
More often, it changes because the signals surrounding behavior begin to change.
Over time, new behaviors become new habits, and new habits gradually become part of the culture itself.
Culture as an Enabler
Perhaps the most important point is that culture should not be viewed as an end in itself.
Many organizations become fascinated with particular culture types. Process-driven organizations often admire innovative startups. Startups frequently wish they were more structured. Results-driven organizations sometimes envy highly collaborative cultures.
The temptation is understandable.
Yet the objective is not to build the most innovative culture, the most collaborative culture, or the most disciplined culture.
The objective is to build a culture that supports the capabilities required by the strategy.
Just as there is no universally superior structure, there is no universally superior culture.
There are only cultures that are more or less aligned with what the organization is trying to achieve.
Ultimately, culture is valuable not because it feels good, but because it helps people consistently behave in ways that strengthen the capabilities required for long-term success.
Systems
If culture influences behavior through informal norms, stories, rituals, and shared assumptions, systems influence behavior through formal mechanisms. They determine what gets measured, discussed, rewarded, and reviewed, ultimately shaping where people focus their attention and how they behave.
While often associated with software, dashboards, and reporting tools, organizational systems are much broader than technology alone. At their core, systems exist to help organizations reinforce priorities, monitor performance, manage risk, and ensure that day-to-day decisions remain aligned with strategic objectives.
What Gets Measured Gets Managed
A long-standing principle in management suggests that what gets measured gets managed. While the phrase is often attributed to Peter Drucker, its exact origins are less clear. Regardless of authorship, the underlying idea remains highly influential.
The logic is straightforward. People naturally pay attention to what is tracked, discussed, and reviewed. One of the broader lessons associated with the Hawthorne studies was that observation itself can influence behavior. While the experiments and their interpretations remain debated, the central insight remains relevant: attention changes behavior.
In organizations, measurement is one of the primary mechanisms through which attention is directed.
This creates an important challenge: what exactly should be measured?
One of the most useful distinctions is the difference between lagging and leading indicators.
Lagging indicators measure outcomes that have already occurred. Revenue, profit, market share, and customer retention are common examples because they help organizations understand how they performed in the past.
Leading indicators, by contrast, focus on the activities and conditions that influence future outcomes. Employee development, customer engagement, product quality, innovation activity, and sales pipeline strength are all examples of factors that may provide early signals about future performance.
A useful analogy is weight loss. Body weight is a lagging indicator; it reflects the cumulative result of past behaviors. Calories consumed and physical activity, on the other hand, are leading indicators because they influence future outcomes. One reflects the result. The others influence the result.
Organizations need both. Lagging indicators reveal whether objectives were achieved, while leading indicators help leaders understand whether the capabilities required to achieve those objectives are actually being developed.
Beyond Financial Metrics
Recognizing both the limitations of purely financial measures and their inherently lagging nature, Robert Kaplan and David Norton introduced the Balanced Scorecard in the early 1990s.
Their central insight was simple.
Financial performance matters.
But financial metrics alone rarely tell the full story.
Most financial indicators describe outcomes that have already occurred. They provide valuable information about where an organization has been, but often provide limited visibility into the capabilities, processes, and relationships that will shape future performance.
To address this limitation, the Balanced Scorecard encourages organizations to monitor performance from four complementary perspectives:
- Financial
- Customer
- Internal Processes
- Learning & Growth
The framework’s deeper contribution, however, is not the scorecard itself but the logic that sits behind it.
Strategy maps extend this logic by making explicit the cause-and-effect relationships between capabilities, processes, customer outcomes, and financial results. Capabilities influence processes. Processes create value for customers. Customer value drives financial performance.
In other words, strategy maps help organizations visualize how today’s actions are expected to produce tomorrow’s results.
The objective is not to measure everything, but rather to identify the relatively small number of indicators that best reflect whether the organization is building the capabilities required by its strategy.
As with capabilities themselves, focus matters.
Too many metrics often create confusion rather than insight.
Systems as an Enabler
Measurement is important, but it is only one part of a broader system of organizational control. Researchers such as Robert Simons have argued that organizations require a combination of
- belief systems
- boundary systems
- diagnostic controls
- and interactive controls
to remain aligned with their strategy and adapt as circumstances change.
The details of these frameworks are beyond the scope of this note. What matters for our purposes is a simpler observation.
Systems do far more than monitor results. They help reinforce culture, guide behavior, manage risk, and support adaptation over time.
Perhaps the most important lesson is that systems should not be viewed as an end in themselves. Organizations sometimes become obsessed with reports, dashboards, scorecards, and KPIs, mistaking measurement for management.
Yet the objective is not to produce more information.
The objective is to create clarity.
Well-designed systems help leaders focus attention on what matters most. They reinforce the behaviors that strengthen key capabilities, provide early warning signals when performance begins to drift, and help ensure that everyday decisions remain aligned with strategic priorities.
Ultimately, systems are valuable not because they generate data, but because they help organizations translate strategy into consistent action.
ACT IV
Bringing It All Together
At this point, it is worth stepping back and looking at the complete picture.
Across these three Field Notes, we have explored a deceptively simple question: Why do some organizations survive, adapt, and endure while others struggle to do so?
The answer, of course, is far more complex than any single framework can fully capture. Yet a recurring pattern appears throughout much of the strategy and organizational design literature.
Organizations operate between two worlds: an external world they cannot control and an internal world they can deliberately design.
Field Note 001 introduced this idea and explored why alignment between these two worlds matters.
Field Note 002 focused primarily on the external world: understanding the environment, interpreting reality, and making strategic choices about where and how to compete.
This note focused on the internal world: the capabilities required to execute those choices and the organizational elements that help develop and sustain them.
Taken together, the logic can be summarized in a relatively simple way.
The external environment influences strategy. Strategy determines the capabilities required for success. And those capabilities, in turn, must be supported by the organization’s people, structure, culture, and systems.
The important point is that none of these elements exists in isolation. Changes in strategy often require new capabilities, and new capabilities frequently require changes in people, structure, culture, or systems. As the external environment evolves, the entire process begins again.
Alignment is therefore not a one-time exercise.
It is an ongoing process of adaptation.
No Perfect Answers
One final observation is worth emphasizing.
Throughout these three notes, a familiar phrase has appeared again and again:
It depends.
There is no universally superior strategy, capability, structure, culture, or system. Every organizational choice involves trade-offs, and every design enables certain capabilities while making others more difficult.
This is one of the reasons leadership is so challenging. The objective is not to find a perfect answer, but to make deliberate choices, understand their consequences, and continuously realign the organization as circumstances change.
The organizations that endure are rarely those that predict the future perfectly.
More often, they are the organizations that remain attentive to reality, willing to challenge their assumptions, and capable of adapting when circumstances change.
Organizations survive not because they find permanent answers.
They survive because they remain capable of adapting when the answers change.
Download Resources
Field Note 003 — Full Essay (PDF)
Long-form downloadable version of this essay.
Field Sheet 003 — Aligning the Organization (PDF)
A one-page synthesis of the key concepts explored throughout this note, including capabilities, organizational alignment, and the role of people, structure, culture, and systems in strategy execution.
The Organizational Alignment Model (Complete Version) (PDF)
An expanded visual framework connecting environment, strategy, capabilities, people, structure, culture, systems, performance, and continuous adaptation.
Selected References & Influences
Selected influences behind many of the ideas explored throughout these notes include:
- Michael Porter
- Richard Rumelt
- Henry Mintzberg
- Jay Barney
- David Teece
- C.K. Prahalad
- Gary Hamel
- Chris Zook
- Robert Kaplan
- David Norton
- Robert Simons
- Edgar Schein
- Cameron & Quinn
- Lepak & Snell
Along with broader work in:
- strategic management
- organizational design
- organizational behavior
- performance management
- systems thinking
- behavioral psychology