Skip to main content

The Way Forward: Choosing Our Operating System on Purpose

Graphic: The Way Forward. Choosing our operating system on purpose. Part 8 of The Inherited Operating System by Dana Houston Jackson. Choosing an organizational operating system on purpose.

By Dana Houston Jackson, Founder and Principal Change Architect, Change – With a Coach Approach, LLC

The Inherited Operating System for Organizations – Expired Assumptions | Part 8

Five thinkers, one century and a choice in front of us. Here's how to update your organizational operating system without throwing out what still works.

In a nutshell – what we learned (right or wrong)

The big idea: Choose on purpose what to keep, what to retire and what to build instead.

What’s expired: Running an organization on habits nobody chose.

What replaces it: Five shifts, built with people across every career stage, a little at a time.

Over this series we’ve looked at five thinkers whose ideas still run inside most organizations. Three of them, Taylor, Weber and Fayol, solved real problems of their time, and parts of their thinking have expired. Two of them, Follett and McGregor, offered alternatives the mainstream mostly passed over. None of them were fools, and neither were the managers who learned from them. We all inherited an operating system we never chose.

Parts 6 and 7 added two more lenses. Adaptive leadership, from Ronald Heifetz, Marty Linsky and Alexander Grashow to practitioners like Dr. Ross Wirth, explains why AI adoption stalls when we treat it as a technical fix instead of the learning it really is. And today’s thinkers, from Amy Edmondson to Ethan Mollick, are already writing the new code, while some of the newer management ideas of the last 30 years turned out to be the old code with a spreadsheet.

If AI feels like it’s grinding against your organization, it is, and now you can see why. This last article pulls it together: where AI clashes with the inherited code, what to keep, what to retire and what to build instead. It ends with five questions and one small step for the whole organization.

The world we're solving for now

Taylor, Weber and Fayol built for a world of scarce information, a workforce with little formal schooling and work that could be standardized. Ours looks different. Information moves instantly. People are educated, connected and spread across five generations, often in the same team. AI is taking over much of the standardized, measurable work the old system was designed to manage. Travis Hahler calls this the Great Scramble: technology advancement and social evolution colliding to create a perfect storm for transformation.

An operating system built for 1910 can still run in that world. It just runs slowly, burns energy and throws away much of what people know.

How they overlap and where they split

Most of us learned these thinkers as one blended package, usually from a first boss or an MBA program. Pulling them apart is the first step to unlearning what’s expired. Here’s the short version.

What Taylor, Weber and Fayol share: the system comes before the person, work is divided into specialties, authority runs down a hierarchy and control keeps it all on track. That shared core is the operating system most of us inherited.

Looked at Main question View of people
Taylor The task How do we do this job most efficiently? Hands to be trained and paid for output.
Weber The structure Why do people obey, and what does it cost? Office-holders, protected by rules and confined by them.
Fayol The manager What does management do, and can it be taught? Capable of initiative, inside a clear chain of command.
Follett The relationships How do people create power together? Co-creators who see the facts of the situation.
McGregor The assumptions What do we believe about people, and how does it shape them? Whatever our assumptions make them, so check the assumptions.

Read down the last column and you’ll see the whole series in one line. The first three built systems around a limited view of people. The last two asked what happens if we start with a bigger one.

Why your AI rollout feels like friction

Most organizations are trying to plug a new technology into an operating system that was designed for something else. The friction isn’t a sign that your people are resisting or that the tool is bad. It’s the old code doing exactly what it was built to do. Here are the five clashes in one place.

Inherited idea Where AI clashes What to redesign
Taylor: thinking at the top AI takes over the routine doing, and the value moves to judgment at the front line, where the old design gave people no say. People design and improve their own work, with AI handling the routine.
Weber: send it up the chain Decisions that AI speeds up to hours wait weeks for approvals and “who owns this?” Decision rights near the work, guardrails instead of approval chains.
Fayol: manager as checker AI does the tracking and reporting, so managers built on checking feel replaced and slow things down. Managers as coaches and connectors, trained before AI arrives.
Missing Follett: power over Tools picked at the top and mandated get complied with on paper and worked around in practice. AI adoption co-designed with the people who do the work.
McGregor: Theory X AI makes surveillance cheap, so people hide mistakes and avoid the experiments adoption needs. AI used to remove drudgery, with clear promises and safety to say “this didn’t work.”

Read across any row and you’ll see the light bulb. The fix is rarely more training on the tool. It’s redesigning the structure the tool lands in.

Why AI forces a redesign, not a tune-up

It’s tempting to bolt AI onto the old operating system and call it transformation. That’s putting the cart before the horse. AI changes the work itself, and when the work changes, the structure built around it has to change too.

  • Paul Cheek’s No One Works Here (2026) describes organizations as networks of people and AI agents, where decision cycles shrink from quarters to hours. People shift from carrying out tasks to setting goals and overseeing systems. A structure built to route every decision up a hierarchy can’t keep that pace.
  • 10X ORG, by Alexey Krivitsky, Craig Larman and Roland Flemm, treats organization design as a lever for capability, with AI raising organizational intelligence from doing and delivering to directing and driving.
  • Nick Bostrom’s Superintelligence (2014) is a reminder of the stakes. As machines grow more capable, the hard part is being clear about what we want them to do. That’s a leadership and design question, not a technology one.

Put simply, the expired assumptions in this series aren’t just slowing us down. They’re in the way of the redesign AI makes necessary. You can’t make room for new ways of working while the old ones still occupy every chair.

What do we do with the people?

This is the question everyone’s asking and few are answering out loud. AI agents are already taking over tasks that used to be whole jobs: drafting, reconciling, scheduling, first-line analysis and much of what specialists spent years learning to do. The old operating system has an answer ready, and it’s the wrong one: if the specialty is gone, so is the person.

That answer comes straight from the default code. Taylor narrowed jobs to single tasks. Weber drew firm edges around each role. Fayol divided the work into fixed functions. Generations of us learned to introduce ourselves by our specialty and to believe it was the limit of what we could do. So when the specialty goes, people don’t just lose a job. They lose the story of who they are at work.

Here’s the better news. People can learn and do far more than their job description says, and growth mindset research backs that up. The work now is to free that capacity:

  • Treat roles as bundles of skills, not boxes. Map what people can do and are learning, not just their title, and let them move toward work that needs doing.
  • Make learning part of the job. Give people time and safe places to experiment with AI and new work, not just a course catalog.
  • Redesign work with the people whose work is changing. They know which tasks agents should take and where human judgment matters most. Built with people, not handed to them.
  • Change the question managers ask. Not “what’s your role?” but “what are you curious about, and what could you take on next?”
  • Protect people’s dignity on the way through. Someone whose specialty is being automated didn’t fail. The work changed. Say so plainly, and invest in the next step with them.

Your specialty was never the limit of what you can do. It’s where you started.

Keep, retire, replace

Every one of these thinkers left us something worth keeping. The point isn’t to tear it all down. It’s to choose on purpose.

Thinker Keep Retire Replace with
Frederick Taylor Studying the work. Measuring what matters. Thinking at the top, doing at the bottom. Measuring activity. People who do the work improve it (kaizen). Measure and reward outcomes, not motion.
Max Weber Fairness, merit and equal treatment. Rules as a substitute for judgment. Rules nobody can explain. Minimum rules with a purpose, an owner and a review date.
Henri Fayol Management as a skill you can learn. Equity, initiative, esprit de corps. The manager as checker-in-chief. The single chain of command. Managers as coaches who build capability and connect teams.
Mary Parker Follett All of it. Nothing. Power with, integration, the law of the situation, put into daily practice.
Douglas McGregor The habit of checking your assumptions. X and Y as labels. Psychological safety, growth mindset and conditions where people can do their best work.

Five shifts for a new organizational operating system

Put the series together and five shifts stand out.

  • From “thinking belongs at the top” to “thinking belongs everywhere.” The people closest to the work see problems first. Give them the time, data and permission to fix them.
  • From “the rule is safer than your judgment” to “rules serve judgment.” Keep the rules that protect fairness and safety. Retire the ones that only protect someone from blame.
  • From “management means control” to “management means capability.” A manager’s best work is coaching, clearing obstacles and connecting people across the chart.
  • From “power over” to “power with.” Treat disagreement as information. Look for the answer that meets both sides’ real needs.
  • From labels to assumptions. Before reacting to someone’s behavior, ask what you’d have to believe for it to make sense, and then ask them.

These shifts point toward what Krivitsky, Larman and Flemm call the 10x org: not ten times more activity, but ten times more capability to learn, adapt, create value and stay aligned. That’s the future this series has been pointing toward: people and technology working in harmony, with structure serving the work instead of the other way around.

How to hand it down differently

The old operating system didn’t spread because people read Taylor or Weber. It spread because each generation taught the next one the way it had been taught. That means the fix spreads the same way. Every manager is a teacher, whether they mean to be or not.

In the upcoming book Leading a Five-Generation Workforce, we ask a question that applies to every generation’s inheritance: “How could an organization preserve composure, reliability, stewardship and anti-waste discipline without preserving unnecessary bureaucracy?” That’s the right question. Seasoned leaders carry hard-won judgment about what controls are for. Early-career people often see most clearly which ones no longer make sense. Neither group has the whole picture alone. Put them in the same room, ask them to trace an old practice back to its purpose and decide together what to keep.

This isn’t a one-time overhaul. It’s continuous improvement: adopt, adapt and keep improving. And it doesn’t have to happen fast. Small changes that people help design last longer than big ones handed down from above. Built with people, not handed to them.

What to watch out for

Change theater, a term from 10X ORG, is the trap: plenty of motion that looks like transformation and builds no real capability. New titles, new frameworks and new org charts can all be the old operating system with fresh paint. Renaming the annual review a “growth conversation” and keeping the same form doesn’t count. That’s all hat and no cattle. The test is simple. Can people closest to the work make better decisions faster than they could last quarter? If not, the code hasn’t changed.

Check your own organization

Picture an engineering and construction firm trying to roll out AI across the company. The first attempt follows the old code: a committee at the top picks the tools, a policy says what’s allowed, managers track usage and everyone gets the same training. A year later there’s plenty of activity and very little change. The second attempt starts small. A 30-year superintendent, a mid-career project engineer and a second-year field engineer get one inherited practice to redesign: the weekly progress report. Together they decide which parts AI should draft, which parts need human judgment and which approvals can go. The superintendent’s experience keeps the safety checks in. The field engineer knows the tools. Within a quarter the report takes an hour instead of a day, and other teams start asking to try the same approach. That’s what choosing your operating system on purpose looks like: small, built with people and spreading because it works.

  • Which of the five shifts would make the biggest difference for your team right now?
  • What’s one inherited practice your team would retire tomorrow if you asked them?
  • Where do seasoned and early-career people already work together to improve how things get done?
  • How would you know, in 90 days, whether your operating system has actually changed?
  • What will the managers you’re developing today pass on to the next generation?

One small first step: Bring together three people from different career stages. Give them one inherited practice (a report, an approval, a standing meeting) and 30 minutes. Ask them to trace it back to its purpose and recommend keep, change or retire. Act on their recommendation and tell everyone where it came from. Then do it again next month.

Inherited isn’t the same as chosen. We get to choose again.

Quick Answers

What is an organizational operating system?

It’s the set of assumptions, habits and structures that decide how work gets managed: who thinks, who decides, how rules work and how people are treated. Most organizations inherited theirs rather than choosing it.

What should organizations keep and what should they retire?

Keep the rules that protect fairness and safety. Retire the ones that only protect someone from blame, and move thinking from the top to everywhere.

How do you choose an operating system on purpose?

Start with the shifts the series points to. Thinking belongs everywhere, so give the people closest to the work the time, data and permission to fix problems, and let rules serve judgment instead of replacing it.

Sources

Bostrom, Nick. Superintelligence: Paths, Dangers, Strategies. Oxford: Oxford University Press, 2014.

Cheek, Paul. No One Works Here: How AI-Driven Enterprises Are Raising the Bar for Business, Leadership, and Competition. Hoboken, NJ: Wiley, 2026.

Dweck, Carol S. Mindset: The New Psychology of Success. New York: Random House, 2006.

Edmondson, Amy. “Psychological Safety and Learning Behavior in Work Teams.” Administrative Science Quarterly 44, no. 2 (1999): 350–383.

Fayol, Henri. General and Industrial Management. Translated by Constance Storrs. London: Sir Isaac Pitman & Sons, 1949.

Follett, Mary Parker. Dynamic Administration: The Collected Papers of Mary Parker Follett. Edited by Henry C. Metcalf and L. Urwick. New York: Harper & Brothers, 1942.

Hahler, Travis D. Rethink Resistance: Embracing Neuroscience to Lead Transformational Change. Fast Company Press, 2026.

Hamel, Gary, and Michele Zanini. Humanocracy: Creating Organizations as Amazing as the People Inside Them. Boston: Harvard Business Review Press, 2020.

Houston Jackson, Dana, et al. Leading a Five-Generation Workforce. Forthcoming, April 2027.

Krivitsky, Alexey, Craig Larman, and Roland Flemm. 10X ORG – Powered by Org Topologies. Org Topologies, 2026.

Laloux, Frederic. Reinventing Organizations. Brussels: Nelson Parker, 2014.

Liker, Jeffrey K. The Toyota Way. New York: McGraw-Hill, 2004.

McGregor, Douglas. The Human Side of Enterprise. New York: McGraw-Hill, 1960.

Taylor, Frederick Winslow. The Principles of Scientific Management. New York: Harper & Brothers, 1911.

Weber, Max. Economy and Society. Edited by Guenther Roth and Claus Wittich. Berkeley: University of California Press, 1978.

Dana Houston Jackson

Dana Houston Jackson is Founder and Principal Change Architect of Change – With a Coach Approach, LLC, author of The AI Adoption Traps and co-author of the upcoming Leading a Five-Generation Workforce (April 2027). A straight-talking Texan with 30 years of experience, she helps leaders make change less confusing, less painful and far more useful. She holds a master’s degree in Organizational Change Leadership and is a PMP, CCMP, Prosci trainer and ICF Professional Certified Coach. Visit changewithacoachapproach.com or connect on LinkedIn at linkedin.com/in/danahoustonjackson.

    Leave a Reply

    Your email address will not be published. Required fields are marked *