What People Actually Mean When They Talk About Andrew Stewart's Framework
You see the name Andrew Stewart come up in slides about organizational culture more often than you'd think, usually alongside concepts like adaptive leadership, collective responsibility, and the idea that leadership is a capability distributed across an organization rather than something tied to a job title. The academic work centers on how organizations learn and adapt, and how leaders create conditions where that learning can actually happen. It's not the same as transformational leadership theory from the 1980s. It's more grounded, less about charismatic figures and more about structural and cultural enablers.
The Transformative Influence Of Andrew Stewart On Modern Leadership And Organizational Culture
Stewart's central argument, if you strip away the academic phrasing, is that most organizations treat leadership as a position problem instead of a capacity problem. They hire or promote the right person and expect results to follow. His work suggests that approach consistently underperforms because the environment around that person either constrains them or actively works against the behaviors the organization claims to want. The framework pushes leaders to think about creating conditions — structural, social, and psychological — where adaptive work can happen across the entire organization.I ran into this directly when I was working with a mid-size company trying to implement a cross-functional agile transformation. We had the org charts, the ceremonies, the role descriptions. What we didn't have was any real mechanism for distributed decision-making. People kept escalating everything upward because the structure rewarded it implicitly. The workaround wasn't to change the org chart again. It was to create a simple escalation boundary — any decision under a certain budget or impact threshold could be made at the team level without approval, and the consequences of those decisions became visible to everyone within forty-eight hours. That visibility piece was critical. Without it, autonomy just becomes ambiguity and people retreat to the old patterns. Within three months, the escalation volume dropped significantly and the quality of decisions at the team level improved faster than anyone expected. The counter-intuitive part that people miss is that Stewart's framework doesn't actually solve the problem of unqualified leaders. It makes the problem more visible. When you distribute leadership capacity, you also distribute the consequences of poor judgment. An organization using this approach needs to get comfortable with the fact that more decisions will be made by people who haven't had traditional authority, and some of them will go wrong. The system is designed to surface those failures quickly so they can be treated as learning data rather than cover-up material. Another nuance that doesn't get enough attention: the framework assumes a baseline of psychological safety that most organizations don't actually have. You can read the material and nod along, but if your people are genuinely afraid of being held accountable for mistakes, adaptive leadership becomes performative. People will go through the motions of owning decisions while quietly waiting for someone with a title to rescue them. I've seen this play out in companies that adopted the language of distributed leadership without doing the harder work of changing their performance management and error-reporting systems. The result was worse, not better, because now there was more confusion about who was actually responsible.
How This Actually Works in Practice
The practical application tends to follow a few recognizable patterns, though no two implementations look identical. The first step is usually mapping where authority currently lives versus where it should live for the organization's stated goals. This is rarely a comfortable exercise because the gap between the two tends to be large. Most organizations discover that decision rights are concentrated in places that make strategic sense only if the organization operates exactly as it did three years ago. From there, the work involves redesigning the feedback loops. Stewart's emphasis on organizational learning means that information about decisions and outcomes needs to flow faster than it typically does in conventional hierarchies. This isn't about more meetings or better reporting templates. It's about restructuring what information is visible to whom and how quickly. A common implementation involves creating shared dashboards or regular cross-functional review sessions where teams present both their decisions and their results, including the ones that didn't work out. The inclusion of failures matters as much as the successes because it signals what the organization actually values.Get the Full Details
I found that the most effective organizations I worked with treated this as a series of small experiments rather than a full rollout. Pick one team, give them genuine decision autonomy in a bounded area, measure the outcomes honestly, and then decide whether to expand, adjust, or shut it down. This approach takes longer in the short term but avoids the catastrophic failure mode of implementing distributed leadership organization-wide and then scrambling to re-centralize when things go sideways. The re-centralization scramble is far more damaging to trust than a slow, iterative approach.
Where the Framework Breaks Down
This approach has real limitations that most presentations of Stewart's work don't emphasize enough. It works poorly in crisis situations where speed of decision matters more than quality of decision or organizational learning. A firefighting scenario — whether that's a product recall, a security breach, or a regulatory investigation — typically requires clear command structures and rapid unilateral action. Trying to apply adaptive leadership principles during an active crisis often produces paralysis because everyone is waiting for permission to act while the situation deteriorates.The framework also assumes that the organization has a sufficient density of capable people to sustain distributed leadership. If your talent pipeline is weak or your training investment is low, giving more people more authority amplifies problems rather than solving them. This isn't a flaw in the framework itself. It's a prerequisite that many organizations skip because it's harder to address than the structural changes the framework proposes. There's also a measurement problem. The outcomes of adaptive leadership — better organizational learning, higher engagement, improved decision quality — are real but difficult to attribute directly to the framework. This makes it easy for skeptical stakeholders to dismiss the approach as philosophical rather than practical. The best defense I've found is to track leading indicators like decision velocity, escalation rates, and the ratio of decisions made at different levels rather than waiting for lagging indicators like revenue or retention. These metrics respond faster and are harder to fudge.
A Practical Starting Point
If you're looking to engage with this material practically rather than academically, the most useful entry point is the concept of the leader's work as distinct from the manager's work. Leaders create conditions for adaptation. Managers ensure execution within those conditions. The confusion between these two roles is one of the primary sources of organizational dysfunction that Stewart's framework addresses. Most organizations conflate them, which means managers are asked to be adaptive while leaders are asked to be operational, and neither function gets done well. The concrete action most organizations can take immediately is to audit their escalation paths. List every decision type that routinely flows upward to senior leadership. For each one, ask whether the person making the decision has access to the information needed to make it well, whether they have the authority to act on it, and whether the consequences of being wrong are proportional to the stakes. Decisions that fail any of these tests should be reconsidered, not because the current system is perfect, but because the gap between current practice and effective practice is usually larger than leaders admit. One specific edge case I encountered involved a company where the engineering team had genuine technical expertise but systematically deferred to product management on prioritization decisions, even when those decisions clearly contradicted the engineering assessment. The framework would classify this as an adaptive challenge, but the real issue was simpler: the engineering team lacked the language and confidence to push back effectively. The fix wasn't structural. It was developmental. We spent six weeks running prioritization workshops where engineers practiced making and defending trade-off decisions in a low-stakes environment. By the time they were given real authority over roadmap decisions, they had the experience and the vocabulary to use it. Structural changes without this kind of capacity building tend to produce noise without signal.
The broader implication here is that Stewart's work is often cited as a blueprint for organizational change, but it's more accurately a diagnostic tool. It helps you see where authority, information, and accountability are misaligned. The actual work of closing those gaps requires whatever specific interventions the situation demands — some structural, some developmental, some cultural. No single framework replaces that judgment.
