Post-AI Enterprise Division of Labor - Operating and Changing Automated Systems

C1. In a deeply automated enterprise, essentially all enterprise work reduces to operating automated systems ("run") or changing them ("change"), even though individual people and agents may split their time and context across both and day-to-day job titles remain more varied.

G1.1: Core business capabilities (sales, underwriting, fulfillment, HR, finance) increasingly execute through software systems, cloud platforms, and AI agents, with humans supervising, interpreting, or intervening rather than performing every step manually. G1.2: Traditional IT and operations already distinguish between "run" work (keeping systems and processes operating within agreed SLAs) and "change" work (projects and initiatives that modify systems or processes), even if the language is informal. G1.3: McKinsey's run-versus-change research quantifies this distinction: they classify run as mandatory "keep the lights on" activities (maintaining infrastructure and existing applications, cybersecurity, regulatory compliance, cloud platforms) and change as upgrades that create new value (modernization, application development, data and analytics, AI). G1.4: In their sample of 17 global companies, McKinsey maps each firm on a 2x2 using run intensity (IT run spend as a share of revenue, normalized to industry medians) and change investments (share of the technology budget spent on change), producing four distinct archetypes - deliberate modernizers, strained transformers, lean operators, and heavy IT sustainers - with different performance patterns and technical-debt trajectories. G1.5: The same analysis shows that AI and agentic automation increasingly consume change budget while also affecting run costs, pushing CIOs to modernize architectures so that new capabilities replace legacy systems rather than accumulate on top of them. G1.6: In practice, many roles and agents already span both domains: the same product manager, SRE, or transformation lead may participate in operating a system (monitoring performance, tuning processes, addressing incidents) and in changing it (shaping requirements, prioritizing backlog, validating new behaviors). G1.7: Strategic Operations Governance frameworks naturally distinguish between (a) operating existing capabilities for efficiency and yield against strategic objectives, and (b) changing capabilities to better actualize strategy under future conditions, while ensuring new capabilities will themselves be operable within targeted efficiency and yield constraints.

W1.1: When most value-creating activities are executed by systems, the meaningful distinction in enterprise work becomes whether the work is keeping those systems operating safely and efficiently in service of current strategic commitments (run) or altering those systems to add or reshape capabilities so the strategy can be better realized in the future (change). W1.2: If external benchmarks and internal planning already distinguish run versus change as budget categories, then aligning Strategic Operations Governance, architecture, and role design to the same division clarifies how much capacity is going to operating for efficiency and yield versus changing for strategic capability, and enables better portfolio decisions.

A1.1: Automation and agentic AI continue to advance such that a growing share of routine and even complex tasks are executed by systems rather than people. A1.2: Organizations are willing to reframe planning and governance around system-centric concepts - how much work goes to operating versus changing systems - while still allowing individual people and agents to play mixed or specialized roles across both. A1.3: The run/change distinction remains useful even as some activities blur the boundary (for example, continuous delivery, A/B testing, and online learning systems).

Q1.1: The claim is most relevant for medium-to-large enterprises with significant automation and a meaningful technology budget; very small or low-automation organizations may not see as sharp a division. Q1.2: "All work" is an intentional overstatement for clarity; there will be edge activities (relationship-building, sense-making, culture work) that do not map neatly to run or change, but they are often in service of those missions.

R1: Rebuttal: Some roles (for example, strategy, compliance, people leadership) are not just operating or changing systems. Response: These roles mostly set direction, constraints, or culture for systems and for the portfolios of run and change work; their tasks still support either operating existing capabilities within strategic guardrails or changing capabilities to better realize strategy over time. R2: Rebuttal: Agile and DevOps blur run and change into continuous delivery; the distinction is outdated. Response: The delivery cadence changes, but the semantics do not: some capacity is spent ensuring current behaviors continue to work as expected (run), and some is spent modifying behaviors or adding new capabilities (change). R3: Rebuttal: Over-simplifying work into two buckets risks ignoring important nuances. Response: The hypothesis is a guidepoint, not a job taxonomy. It is meant to sharpen architectural, budgeting, and governance thinking - especially how we allocate budgets, agents, and attention - rather than to flatten human roles or ignore necessary nuance.