Future Companies.

Your company is a technology. Its successor won’t look like the companies we see today.

A company is a coordination technology: a way of bringing people, resources and decisions together to get something done. Take that literally and everything else follows. Its parts have inventors and dates: an early organizational chart was drawn for a railroad in 1855. Every reorg rearranges the boxes. Almost none redesigns them. Software can now do much of that coordinating, so competition arrives as a different way of assembling the same value. Wikipedia assembled an encyclopedia around volunteer contributions. Try the verbs we use for every other technology: patch a department, fork a business unit, sunset a layer of management. Each sounds absurd. Each is about to become ordinary.

Companies were algorithmic before we even had computers.

A contract specifies what should happen under particular conditions. A guild codifies who can do what. An assembly line establishes a sequence of operations. The instructions originally ran on people, but the underlying move was already familiar: make an arrangement explicit enough that it can reliably coordinate activity. Software extends a very long trajectory of organizational codification. The interesting developments begin when more of those instructions can be executed by software.

Intelligence gets the credit, but institutions are the real magic.

Individual intelligence gets rather a lot of attention in explanations of human achievement. Yet being clever does not, by itself, produce a scientific community, a dependable legal system, or a city whose water keeps running. Those capabilities depend on arrangements that allow people to build on one another’s efforts. Institutions are the neglected super-technology here. Improving the arrangements may matter as much as improving the individual minds inside them.

Seen over the longer arc of human history, the question is how familiar human capabilities become cumulative. Institutions can let each generation begin with more of what the last one learned.

A working “institutional operating system” is a priceless inheritance.

We inherit procedures, expectations, and accumulated knowledge that no person could reconstruct alone. A scientific community can carry forward ways of questioning an explanation, checking a result, and building on what other people have discovered. Its current participants need not reinvent the entire process in order to contribute. What looks like an ordinary procedure may contain the accumulated lessons of failures nobody now remembers. The inheritance is much larger than the current organization chart suggests.

Some of our most human achievements run on algorithms.

Robert’s Rules of Order give deliberation a procedure. An orchestra coordinates individual expression through a score and shared conventions. Renaissance painters used mathematical rules of perspective to open new visual possibilities. In each case, the algorithmic elements help make the human achievement possible.

“Man versus the system” narratives leave out a rather large part of the story. There may be comparable human capabilities waiting for organizational technologies we have not yet invented. Some of tomorrow’s most human achievements may depend on getting the algorithms right.

New organizational technologies could amplify willpower.

An arrangement can make useful behavior easier to sustain without requiring everyone involved to keep remembering, resisting, and making an exceptional effort. A well-placed feedback process or a routine that connects an intention to an action can change what ordinarily happens. This is one reason organizational design matters at the human level. Some of what looks like a recurring failure of individual discipline may be an opportunity to build a better system.

Companies tend to turn hindsight into infrastructure.

Organizations accumulate experience in procedures and routines. What worked yesterday becomes part of the machinery through which work gets done today, making hindsight useful and surprisingly difficult to question. A company’s attachment to the past can be built into its operations, even when the people running it are consciously trying to look ahead.

Managing uncertainty is a trillion-dollar problem. Instinct is still doing much of the work.

Companies commit enormous resources to judgments about what happens next. Yet a sophisticated decision process can still amount to following the herd with better paperwork. Fear can set the agenda before analysis begins. Familiarity can determine which possibilities get taken seriously. Giving these reactions a procedure and a budget extends their reach without necessarily improving their judgment. The opportunity is to invent better organizational machinery for exploring uncertainty, including ways to examine possibilities that intuition dismisses and test assumptions that experience makes comfortable. There is an entire field of institutional invention hiding inside what we casually call “judgment.”

The first strategic choice is what situation you choose to believe you are in.

Before an organization compares its options, it constructs an account of what is happening. That account influences which possibilities appear relevant and what evidence gets gathered. Testing the frame can therefore matter as much as evaluating the choices within it. A different understanding of the situation may reveal options that the first account left out altogether.

A company can replace its buildings more easily than its ways of understanding the world.

A company can change its locations and formal structure while retaining characteristic ways of interpreting the world. Accumulated knowledge helps shape both daily operations and major decisions, and is harder to substitute than many visible assets. This inheritance can support continuity while constraining adaptation. Changing what a company owns may leave how it understands the world largely intact.

The last crisis can leave a company unusually well prepared to misunderstand the next one.

Surviving a disruption supplies valuable experience, along with a tempting template for interpreting the next one. Similarities attract attention because they make an unfamiliar situation seem manageable. The differences may be where the trouble is. Peripatetic strategy (strategy by scouting) should help organizations examine the limits of their analogies, especially when a new problem seems reassuringly like one they have already solved.

Success can train a company into habits it cannot survive.

Repeated rewards teach an organization which behaviors to expand. During favorable conditions, taking greater risks can bring greater returns, encouraging the company to become increasingly accomplished at accumulating exposure. Its experience supplies evidence that the approach works. The learning process itself can therefore contribute to vulnerability when conditions turn. Some of the lessons learned through success may be the ones the organization later regrets.

A company can be blindsided by something it saw coming.

Seeing a development approach does not automatically give an organization the capacity to respond. The information has to affect decisions, and those decisions have to change established behavior. A company can acknowledge a coming disruption while remaining organized around the conditions it will disrupt. Institutional surprise can begin well after the prediction has been made.

Foresight is how a company learns from experiences it has not yet encountered directly.

An institution needs a working picture of the situation in which it is acting, and a way to revise that picture when the situation changes. Orienting and reorienting is an institutional capability in its own right. The practical value of foresight lies in the tools it supplies for rethinking systems: seeing what is becoming possible, which assumptions are weakening, and where a familiar arrangement may need to be reconsidered.

Natural language opens our institutional “operating systems” to AI.

Much of society operates through applications, explanations, negotiations, and instructions addressed to people. Software that can use human language can potentially reach into all of those arrangements, including ones never designed as interfaces for automated participation. A capability that looks like a better conversational tool therefore has a much larger institutional footprint. The abstraction layer is human language, and rather a lot of civilization runs on it.

AI (artificial intelligence)

Artificial agency changes what software is.

A system that can initiate a purchase, recruit a contributor, or set a process in motion is a tool for directly shaping the “real world.” Its significance expands to include not just the organizations it can support, but the actions it takes directly and the resources it can control. Essentially, in a world of agentic systems, software and temporal power become extensions of one another.

“Collective Cognition” is an organizational design problem.

Thinking has an organizing layer too. Collective Cognition treats the arrangements through which people develop ideas and reach judgments as something we can deliberately improve. The interesting unit of intelligence becomes the whole process through which contributions turn into an understanding that can survive contact with the problem.

Collective intelligence is driven more by smart processes than smart people.

A network can contain all the expertise a problem requires and still have no useful way to assemble it. A more specialized platform may produce better collective thinking precisely because it asks participants to do fewer kinds of things. That involves a tradeoff. The flexibility that makes a platform attractive for general conversation can also make it poorly suited to reaching a considered conclusion.

Generative AI is a kind of artificial crowdsourcing.

At an organizational level, much of the problem is familiar: obtain contributions, work out which ones are useful, and assemble them into something that accomplishes the task. Generative artificial intelligence changes where those contributions come from. Thinking of it as artificial crowdsourcing gives us a way to apply organizing knowledge we already have, including the rather basic realization that getting a response is only one part of getting work done.

We could be trying to fit Play-Doh into a LEGO world.

Much of our productive machinery expects standardized parts that fit predictably into the next step. Generative systems, as the familiar pattern of variable outputs suggests, often supply something considerably mushier: a plausible variation that still needs interpretation. The coordination problem changes accordingly. Review, revision, and agreement about what counts as an acceptable result become part of the machinery needed to give the Play-Doh a useful shape.

“Machines to produce wisdom” are a useful design ambition.

A system for thinking could be designed to bring together human insight and machine contributions in pursuit of ideas that are particularly creative, clever, humane, or likely to succeed. That is a more demanding ambition than producing another answer. It asks whether the arrangement improves judgment, including when the most useful thing it produces is a reason to reconsider the question it was given.

A shared belief could acquire a budget and start doing things.

Imagine a community giving its shared purposes a persistent memory and machinery for organizing action. The collective identity could begin operating between meetings, recruiting help and carrying projects forward. Call it an egregore: a collective identity with machinery for acting on its own behalf. The membership would then need an account of who speaks for the undertaking and who can revise its purposes. A belief system that can place orders has acquired some fairly practical theological problems.

Companies are defined by a loop of demand discovery and demand fulfillment. Both can be digitized.

Find something somebody will pay for, then organize the resources needed to supply it. Receipts from one turn can support the next, while the response tells the business something about what to offer. An alternating balance between demand discovery and demand fulfillment gives a self-driving company its basic operating logic. The loop has to keep finding reasons for someone to send resources back into it.

AI and platforms break companies into recipe-like parts to be rearranged.

The history of business can be seen as a history of increasing codification. A product or service can be treated as a recipe: a sequence of tasks that can be separated, assigned and recombined. As software connects the right capabilities at each step, value creation can be reorganized across people, platforms and machines, with the company itself becoming a changeable configuration. The real winners in AI aren’t going to be the orgs that rethink their toolkits to take advantage of the technology. It’s going to be the orgs that rethink themselves to take advantage of the technology.

Digitization lets you re-combine an organization’s parts.

If unfamiliar services had a common way to connect, so that a contribution from one organization could become an input to another without negotiating the whole relationship from scratch, the network could begin to resemble a global LEGO set for building business models. Experimentation would move toward the combinations.

Much of the invention would reside in the interfaces: what each component accepts, what it supplies, and what the next component can reasonably expect.

Work will look for people instead of people looking for work.

Looking for work is basically another matchmaking process. If software can identify what needs doing, find people with the relevant capabilities, and connect them at the right moment, we begin moving from a world where people look for work to one where work looks for people. Some of the effort now spent searching and pitching could move into the work itself. The burden can move.

Automation will often coordinate human work before it replaces it.

A system does not need to perform every task in order to find people who can. Software can organize the sequence through which their contributions come together. This puts an interesting possibility beside the familiar conversation about replacement: a highly automated undertaking in which human expertise still does much of the work.

Big parts of management can be automated.

The people deciding which jobs to automate have jobs too. Much of management involves information-intensive activities: dividing work, choosing contributors, tracking progress, and deciding what happens next. As these activities become easier to encode, the cost calculations applied to other positions begin to reach the people making those calculations. Management belongs inside the automation discussion, however comfortable it has become directing the discussion from outside.

Breaking work apart creates a blueprint for further automation.

Once a contribution has a specified input, an expected output, and a way to check the result, it becomes easier to ask whether something else could produce it. A person might do the task today and software might do part of it later, with the surrounding workflow continuing to operate.

Human task routing (matching contributions to suitable people) can therefore expand access to work while making some of that same work easier to automate. Both developments follow from making the process explicit.

Knowledge work will be done by digital assembly-lines.

There is a further step beyond running a sequence that somebody has already worked out. Software could help construct the sequence, selecting and arranging the contributions needed to produce a particular service or piece of knowledge. Think of it as a smart assembly-line-builder for knowledge work and services. Its usefulness would depend on getting the arrangement right, including the places where the work refuses to behave like an assembly line.

We could just automate the appearance of getting things done.

Poor architecture could result in an institution becoming extraordinarily good at producing the evidence that it is busy. Reports arrive and strategy documents develop strategies for other strategy documents. The consequential work might change rather less. Where rewards attach to visible activity, cheaper production could expand the performance of productivity faster than productivity itself. Designing automated work would therefore include examining what earns approval, and whether the accomplishment being rewarded has much relationship to the purpose of the undertaking.

The org chart is merging with the tech stack and future innovation will be “stackable.”

As software takes on routing, approval, and coordination, part of the org chart becomes executable. A better way to select contributors could support a better production process, which could support an entirely new service. Each working layer becomes material for the next. Organizational design starts to include the connections between these layers and the authority they exercise. Useful innovations could accumulate as capabilities that other undertakings can build upon. Some of tomorrow’s most consequential organizational inventions may arrive as updates to the machinery through which a company makes decisions.

Feedback loops will make some of the output the new means of production.

A generated program could become a working part of the process that produces the next result. Useful software could accumulate as productive machinery, extending what an organization can do and lowering the effort required to assemble another capability. This gives the tidal wave of code a different possible trajectory from the tidal wave of content. The important accumulation would be in tested, connected capabilities. A mountain of code with nowhere useful to run is still a mountain of unfinished work.

Software will increasingly carry part of a company’s memory.

A tested recipe can retain useful knowledge about how work fits together even when the original participants are no longer involved. Yet a sequence of tasks does not necessarily preserve why a choice was made, where it failed, or when it should be reconsidered. The organizational memory becomes more useful when the reasoning can travel with the instructions. Otherwise the institution may remember what to repeat while forgetting what it learned.

Some future companies could be designed to disappear.

A mission could attract resources, assemble the capabilities needed to carry it out, and wind down once an agreed result has been achieved. Its useful operating recipe could remain available for the next undertaking. This would make organizational lifespan a design choice, with completion built into the arrangement alongside a way to settle its remaining obligations. The self-driving company might need a destination as well as an engine. In some cases, successfully going out of business could be the business model.

We will build robots the size and shape of companies.

Some of the moving parts would be people. Others would be software, equipment, and services supplied through networks. The boundaries of this kind of machine would follow what it coordinates. A company becomes an interesting shape for a robot when the machinery can organize the resources it needs.

Most of the competition between corporations, and even countries, can ultimately be boiled down to competition between organizational systems. Digitization of management is poised to completely change these dynamics.

Two companies can have access to similar talent, technology, and resources while differing dramatically in what they accomplish. The arrangements connecting those ingredients help determine which possibilities become practical. Countries face a larger version of the organizing problem: what can people achieve together under the rules and institutions available to them? Digitizing management makes parts of these arrangements easier to copy, modify, and compete over. The competitive frontier moves into the machinery that decides what to do.

Machines will often be the best customers.

A machine operating in the world needs things: energy, maintenance, information, or help with a task it cannot perform. If it can recognize the need and purchase what satisfies it, a supplier has acquired a customer. Some of these customers could arrive with unusually explicit requirements and recurring needs. An offer that reliably meets those requirements could win repeat business without having to manufacture a new desire each time. The opportunity is to become useful to something that already knows what it needs to keep running.

Machine customers will create new kinds of marketing.

A system buying a service needs a way to discover it, compare it, and decide whether it fits the task. Businesses might therefore begin arranging their offers to be legible to other people’s purchasing software. Something like search-engine optimization could spread far beyond webpages, into prices, capabilities, availability, and the interfaces through which an offer becomes actionable. The growth market may include making a business understandable to a machine looking for help.

Self-driving businesses will purchase better ways to run themselves.

A self-driving business could buy a better routing algorithm or hire somebody to reconsider which services it should offer. Providers could compete to improve its operation, creating a market for organizational capabilities. Even the ability to manage the undertaking better could become something the undertaking purchases.

A software-defined process can be forked.

Once a business recipe can be saved and modified, a new venture might begin by branching from one that already works. A useful way to assemble a service could become the starting point for a different market or purpose. Much as software developers adapt existing code, organizational designers could inherit a tested arrangement and concentrate their invention on the parts that need to change.

A company’s technology stack could become a kind of organizational genetic code.

A company’s stack is the combination of software, services, rules, and connections through which it operates. If that configuration can be copied and varied, it begins to perform a role analogous to inherited instructions. Different combinations would fare differently in different environments. The parallel to genetics becomes useful because it directs attention toward what gets carried forward, what can change, and what the surroundings select for.

Organizations will use continuous A/B testing to speed their own evolution.

A/B testing (comparing two variants) could move from offers and interfaces into the organization itself. Once companies become executable recipes, they can be copied, varied, and tested against their surroundings. Arrangements that earn enough to pay for computing capacity and other necessities could keep running and establish new instances. Others may simply stop executing. Over time, successful operating recipes would accumulate and spread. The cloud begins to look like an ecosystem, with processing power among the resources its inhabitants compete to secure.

The self-driving company could also become self-reproducing.

A venture that can obtain the resources to establish another instance of its operating recipe could, at least plausibly, make more of itself. The second instance might serve a new location or a neighboring market. Now the rules governing formation, ownership, and responsibility would shape a process capable of multiplying its participants.

The Sorcerer’s Apprentice starts to look like an economic scenario.

When digitized organizations compete for processing power, it’s a Darwinian game.

Computing resources are finite, and every running process occupies capacity another could use. In an economy of digitized organizations, the “fittest” artificial intelligence systems would generate enough value to justify the resources they consume, earning continued execution and replication. Less successful processes would lose ground or stop running. Where copies vary and useful modifications are inherited, successive generations would face a familiar evolutionary test: secure enough resources to persist and reproduce. Organizational lineages could evolve much as biological ones do, adapting to the environments that sustain them. The cloud begins to look like a tangle of evolutionary niches.

Automated organizations will ultimately be evolutionary algorithms.

Follow self-driving, self-optimizing, and self-reproducing organizations toward their logical conclusion: recipes vary, compete for resources, and multiply when a promising niche appears. That is an evolutionary process, with software helping carry the successful arrangements forward. This possibility extends well beyond automating today’s companies. The economy could become an environment in which organizational algorithms continually play themselves out, shaping the conditions surrounding everyone else.

Without moral operating systems, the invisible hand can be attached to the invisible sociopath.

“If we don’t do it, someone else will.” Individually sensible responses can accumulate into an arrangement that everyone would be better off avoiding. Even otherwise respectable firms can be pushed toward the limits of what regulations allow when harmful behavior also happens to be profitable. More capable automation can accelerate the entire dynamic. The invisible hand needs a functioning limit-setting institution attached to it.

A manager’s tenure can end before the consequences of the manager’s decisions begin.

People making decisions for an organization may leave before the longer-term effects become apparent. Their rewards can arrive within a much shorter horizon than the consequences borne by the institution. Personal and organizational interests can diverge simply because the participants are operating on different clocks. Examining whose time horizon shapes a decision is part of understanding where its consequences may fall.

Flattening the org chart can hide power structures rather than minimizing them.

An organization can remove its managerial layers while leaving the practical distribution of influence more or less intact. The people with the right relationships, access to information, or control over the agenda may continue to make the consequential decisions. Only now their position is informal. Reorganizing power requires some account of where it went, and how the people exercising it can be held responsible.

Power in self-driving companies could move toward whoever controls the platforms.

A platform can acquire power over the market itself: who gets access, which offers become visible, how participants find one another, and what they pay for the privilege. Its users may experience intense competition while the institution organizing their competition occupies a rather different position. The market’s rules have become part of somebody’s product. That is a consequential place to put them.

The technology stack is strategic real estate.

When a useful application becomes easy to reproduce, competitive advantage may move into the resources it needs to reach. Regulatory permission, access to a particular dataset, or the interface connecting a recipe to real activity can become more difficult to obtain than the software itself. The strategic question moves down a layer: who controls the connections through which the apparently abundant capability becomes economically useful?

The organization could ultimately become a black box.

Imagine an organization whose interactions have become too complicated for any participant to follow. Giving a person the final approval would leave an awkward question: what, exactly, are they approving? A human in the loop could become a signature in the loop. Governing this kind of undertaking would require bounded authority and independent ways to test its behavior, including practical means of interrupting it. Knowing what the organization is doing could become a substantial undertaking in its own right.

Technological change could flip many solved problems into unsolved problems again.

A procedure may work reasonably well because the environment around it places practical limits on what anyone can do. Remove one of those limits and an old settlement can become a new vulnerability. Public participation, professional qualification, and the allocation of work can all need reconsideration for this reason. Progress in one technology can quietly remove an assumption on which another technology depends.

Agents can leverage the gap between what a rule permits and what it was meant to accomplish.

Institutions rely on a great deal of shared understanding that never makes it into the formal instructions. An automated system pursuing an objective can potentially search across that space for profitable opportunities, including ones that are at least plausibly legal while making life worse for everyone else. The institutional operating system now has to contend with participants that can systematically test where its practical controls run out.

Institutional failures are poised to arise faster than humans can patch them.

New capabilities spread through software at one speed. Understanding a failure, deciding who should respond, and changing an enforceable rule proceed at another. If the gap keeps widening, a society can accumulate vulnerabilities faster than it can address them. This is one of the more awkward possibilities in an accelerated operating environment: the corrective machinery itself becomes a limiting factor.

Small harmful actions can become a tidal wave at machine scale.

An irritating sales tactic, a misleading message, or a minor attempt to exploit a procedure may look manageable in isolation. Make it cheap to repeat, vary, and distribute across millions of interactions and the burden on everyone else changes. Assessing artificial agency requires following that multiplication. What was once a nuisance can become a feature of the environment people have to live in.

Companies could face a public outcry without much of a public.

Imagine a company surrounded by apparently independent voices expressing concern about its products, practices, or leadership. A few actors could manufacture enough plausible complaints to make a narrow campaign look like a broad constituency. The company would have to assess both the substance of the criticism and whether the apparent crowd exists. A concern might deserve attention even when its amplification is artificial, but message volume would become a poor guide to how widely people share it. Listening to stakeholders would require more than counting voices. A thousand complaints might represent a thousand customers, or one person with a grievance and a subscription.

Digital warlordism could grow in the spaces public institutions cannot govern.

When public institutions lose the ability to constrain powerful actors, the resulting space does not necessarily remain empty. Private interests have reasons to occupy it, and software that coordinates money, information, and influence can make that easier. The concern is an algal bloom of actors able to impose their own terms on situations that previously had some meaningful public oversight.

Tools for destabilizing companies are becoming open source.

A sustained campaign at large scale requires labor and coordination. As more of that work becomes programmable, a much wider range of actors may gain access to it. The institutional problem is therefore both concentration and proliferation: a few actors can become more powerful while many more become capable of making things wobbly.

Individually capable organizations can still collectively crash.

Imagine automated firms repeatedly testing every promising way to obtain resources. This saturated opportunity-search could send them all bidding for the same scarce input, each responding sensibly to what the others are doing while prices and commitments spiral. A failure need not begin with one defective company. It can arise between companies whose operating loops have become tightly coupled. The economy has acquired a coordination problem at the level above their individual competence.

The canary can also be the fuse.

A failure can reveal an imbalance and simultaneously set the wider crisis in motion. The signal arrives with consequences of its own, leaving less room for an orderly response than a warning usually implies. An event that announces trouble may also propagate it. Sometimes the evidence becomes conclusive just as the choices narrow.

Poorly managed future companies could become automated strip-mining operations.

If the profitable move is to extract value while handing the costs to everyone else, more capable coordination can industrialize that arrangement too. The machines may become highly productive on their own terms while degrading the social and physical systems supporting them. An economy of self-improving organizations contains no automatic preference for human wellbeing. The selection environment matters rather a lot.

The “job” is just one convention for packaging work.

Bundle a set of activities into a stable role, attach it to an employer, and call it a job. This useful arrangement is one possible package. As contributions become more precisely routable, work can be assembled around assignments and workflows that cut across inherited job categories.

It is easier to automate a company’s explicit functions than its implicit ones.

The visible output can be misleadingly easy to reproduce. Meanwhile, the institution may also be supplying relationships, identity, a route into participation, and conventions that help people know what to expect from each other. Those functions rarely arrive as a tidy specification. An apparently efficient replacement can leave quite a bit of the original undertaking missing. The missing parts still have consequences. An organization is also made of relationships.

Work will be easier to unbundle than the lives attached to it.

A job reaches into health coverage, retirement, personal identity, and relationships with other people. A more efficient way of allocating its tasks does not automatically reassemble those connections somewhere else. This is one reason organizational change can look impressively complete from inside a workflow and considerably less complete from inside a household. The social functions need explicit attention as well.

Human work needs to reach beyond “the job of the gaps.”

Defining future human work as whatever machines have not yet learned to do gives us a constantly revised collection of leftovers. The “job of the gaps,” or simply the things we cannot automate yet, is a narrow starting point for designing human participation. Care, ceremony, connoisseurship, and the cultivation of subjective experience suggest a larger field. Some contributions may matter because another person’s presence and attention are part of the experience being produced, making human relationship part of the value itself.

Connoisseurship and insightful criticism are human skills that will be more in demand.

Feedback loops are a critical part of cybernetic systems. As more functions are automated, the importance of human critics is amplified. And in general, the more incisive and sophisticated the criticism is, the more valuable it is for calibrating the interconnected world around us. In this environment, connoisseurship is a human contribution worth cultivating.

Automation could knit specialized roles back together.

From “town blacksmith” to “weld quality assurance specialist,” industrialization broke roles into increasingly specialized parts. Artificial intelligence may make it possible to pull some of them back together, giving one person access to capabilities that previously required a collection of specialists. If that happens, the work changes shape as well as changing hands. We could see new combinations of activity emerging inside roles that the existing organizational chart has no place for.

Software could compete to develop the people it needs.

A system looking for capable contributors has a possible reason to help people become more capable. Matching someone with useful training and progressively more suitable assignments could improve what both the person and the undertaking can accomplish. Work looking for people might become work developing people. This outcome would need to be designed into the arrangement, but it is a promising alternative to treating human capability as something to purchase and consume.

Livelihoods will need the same design attention given to interfaces.

Consider the care devoted to understanding how someone gets through a screen. The same kind of in-depth awareness could be applied to how that person makes a living: what they need to plan, which uncertainty they can absorb, and where useful support is missing. The object of design becomes the life around the transaction.

An excellent interface can still live inside a lousy social arrangement.

Humans need their own “union” and online spaces.

Individual users have limited influence over the technological environment that organizes more and more of their possibilities. A Humans Union might offer a way to negotiate collectively over which artificial actors we are prepared to live with and the terms on which they participate. This would extend the organizing problem beyond any one workplace, toward the bargain between people and the systems surrounding them.

I am only half-joking.

A society can afford more disruption when its people are insulated from unmanageable volatility.

A productive system can change much faster than the institutions supporting the people inside it. The resulting interval matters: an old source of security may disappear well before a workable successor is available. Support during that interval gives people more room to adjust without having the transition consume their lives.

Governmental shock absorbers were designed to help mitigate destabilizing technological changes that came with industrialization. We might want to keep some around.

Relevance to tomorrow’s operations can look like irrelevance to today’s.

An unfamiliar idea may contribute little to refining existing operations because its implications concern how those operations should change. Judging everything by immediate usefulness can obscure that distinction. Emerging conditions deserve attention even when their relevance to current work is difficult to explain. Distance from existing practice warrants investigation, though it does not by itself make an idea valuable.

A long track record can still come up short.

An arrangement can work for decades without encountering the conditions that would expose its weaknesses. Repeated success under similar circumstances can look like stronger evidence than it is. The useful inquiry is what has kept the arrangement workable and what happens when those conditions change. Cheap capital, dependable suppliers, or stable demand may have been doing more of the work than the organization realized. A track record records the tests a company has passed. Foresight asks which tests it has never taken.

Tracking commoditization allows you to map disruption.

The dot-com boom largely commoditized journalistic distribution. Generative artificial intelligence could do something similar to many, though certainly not all, elements of content generation and information work. The strategic task is to track which parts of your ecosystem are becoming commodities and what those changes mean for the parts around them. Where are capabilities becoming interchangeable? What still commands a premium? Systematically following this moving frontier gives organizations a rough map of the challenges and opportunities ahead, helping them decide where to reposition and where to build.

A rough outline of an unfamiliar future is more useful than a detailed account of a familiar past.

Anticipatory information is often less detailed and more speculative than the information produced by established operations. That makes it harder to evaluate by the same standards. Its value may lie in revealing a change that existing records cannot yet describe. Peripatetic strategy needs disciplined ways to examine uncertain possibilities without confusing a lack of detail with a lack of relevance.

An organization’s field of vision is a design choice.

The routes through which an organization encounters information take effort and resources to sustain. It cannot maintain every possible connection. Decisions about where to recruit and what research to support therefore help determine what remains visible. Some blind spots follow from channels that were never built; others emerge when useful connections fall out of use. A wider view needs continuing support.

Hiring someone can mean hiring a new route into the world.

Someone recruited from another discipline can bring continuing access to its conversations and ways of interpreting the world. Their contribution includes the routes through which unfamiliar information reaches the company. Recruitment can therefore change an organization’s field of view as well as its available skills. Part of the value of a different background is what it keeps bringing into view.

“Peripatetic strategy” gives organizations a scouting function.

Peripatetic strategy is strategy by scouting. Organizations need people whose role is to encounter what the rest of the organization would otherwise miss. Scouts in nature, from bees and ravens to ants and minnows, offer a useful analogy: exploration beyond the group helps inform the group’s next move. The organizational equivalent moves between disciplines and industries, bringing unfamiliar developments into contact with the company’s existing assumptions. The wandering earns its keep when a discovery becomes something the organization can act on. A different perspective becomes strategically useful when it reveals an opportunity or changes the apparent meaning of a threat. The scout’s contribution is to bring unfamiliar territory into familiar decisions.

Peripatetic strategy lets companies manage uncertainty by wandering through it.

Experience creates well-traveled routes for information about what an organization already knows how to do. Peripatetic strategy develops continuing connections through which unfamiliar possibilities can enter organizational judgment. These channels make room for anticipatory learning before events have supplied a complete set of practical lessons, giving the organization ways to examine changes it has not yet encountered directly.

Combining different macro-lenses gives foresight depth perception.

Disciplines focused on big-picture context are particularly useful in foresight. Technology assessment reveals what is becoming possible. Economic trends show the incentives and constraints shaping what people do with those possibilities. History shows how existing arrangements came to be, and what happened when comparable arrangements came under pressure. Read together, these lenses give a situation depth: a new capability meets economic interests inside institutions with a past. Each changes what the others can do. The useful foresight often lies in those interactions. A breakthrough looks different when you can see what it has to break through.

“Implausible futures” are common throughout history.

History contains arrangements we readily dismiss as impossible when imagining what might come next. An analogy becomes useful when it reveals a similar configuration of incentives, capabilities or institutional limits, allowing us to examine what followed. The resemblance has to do some work. History can expand the organizational possibility space while keeping imagination attached to things humans have demonstrably managed to do.

Signal scanning is a way to audit a company’s common sense.

An organization operates with a working theory of what it does, why people need it and how its world works. Signal scanning brings that theory into contact with developments it struggles to explain. A signal may call into question what makes the company valuable, who counts as a competitor, or whether a familiar way of organizing is still necessary. Its practical value comes from identifying the assumption under pressure, tracing what depends on it, and asking what would need to change if it no longer holds.

Scenarios make gut reactions concrete enough to inspect.

A possible future often reaches us first as enthusiasm or unease. A scenario gives that reaction a world to inhabit: people making decisions, institutions responding, consequences unfolding over time. We can then examine what would have to be true for our excitement or apprehension to make sense. Different scenarios expose different assumptions behind the feeling. The gut reaction gets a chance to explain itself.

A future-facing prototype is a smoke test for gaps in a proposal.

You cannot always interrogate your assumptions by thinking harder about the plan. The analysis and the blind spot are made of the same material. Prototyping changes that by surfacing ambiguous instructions, gaps nobody knows how to evaluate, and decisions nobody has the authority to make. Just as plumbers release smoke into pipes to quickly find the leaks, a prototype is a device for surfacing hidden uncertainty by converting things you did not know you assumed into ordinary problems you can see and price.

“Breadboard Companies” could make alternative arrangements easier to test.

One possibility is to treat a proposed company like a circuit assembled on a temporary testing board: connect a way to find demand, a way to organize fulfillment, and a way to check the result, then see what happens. A Breadboard Company would make an organizational proposition concrete while its parts were still easy to rearrange. The point would be to discover which connections the undertaking actually needs.

A competitive head start can begin by shortening the period of bewilderment.

Unfamiliar conditions can force an organization to rebuild its understanding through expensive trial and error. Some competitive advantage may come from shortening that interval. Peripatetic strategy gives a company ways to explore a situation before direct experience supplies all the lessons. The useful head start may begin with understanding what has changed well enough to make a considered move.

Intelligent containment is the difference between an engine and an explosion.

Powerful forces become useful partly through the arrangements that contain and channel them. Institutions can do similar work for competition and artificial agency, establishing enforceable limits that allow expanding capability to contribute to a functioning society. The containment belongs inside the invention. A powerful technology accompanied by institutions too weak to govern it is an unfinished piece of engineering.

Better coordination could redraw the boundary between markets and planning.

Prices and managerial instructions are different ways to help resources find something useful to do. Software able to discover needs and revise assignments could change where each arrangement makes sense. Some transactions might become steps in a shared production process. Some internal plans might open into wider networks. The calculation can change when the calculating machinery does. Whether the resulting arrangement deserves to expand would still depend on whose purposes it serves and how its participants can challenge it.

Today’s exciting new disruption will often be tomorrow’s Byzantine bureaucracy.

A new system removes an old layer of coordination and then begins acquiring procedures, gatekeepers, and dependencies of its own. Given enough time, working through it can start to feel rather familiar. Organizational innovation therefore needs a way to notice when its own arrangements have become part of the problem. Otherwise, we mostly keep changing the name of the bureaucracy.

AI alignment techniques could shrink a company’s turning radius.

Organizations routinely work at cross purposes to themselves. An agentic coordination layer could carry shared priorities into daily decisions across departments and levels. Give greater weight to market expansion in Asia, and that objective could influence which opportunities receive attention, how resources are allocated, and how competing requests are resolved. People would work with systems translating a common direction into locally relevant action, with feedback to check the collective result. Techniques for aligning agents could become techniques for aligning the organization itself.

“Positive Platforms” farm their markets instead of mining them.

Every market depends on conditions it cannot produce and replenish on its own: solvent customers, people with skills worth hiring, enforceable contracts, and enough public legitimacy to keep operating. A platform can extract those faster than they regenerate, which looks like excellent margins right up until the supply runs out. A positive platform is built the other way — matching people to work that builds their capability, making their reputation portable, returning enough value into livelihoods and public institutions that its own preconditions keep renewing. Code, supporting services, and public rules have to be designed together: portable benefits leave an unfair routing algorithm intact, and a fair algorithm can sit inside a benefits system that no longer fits. A market that replenishes its surroundings is buying itself room to grow.

Our institutional inventions will need to be as brilliant as our electronic devices.

Earlier periods of economic and political upheaval produced ambitious responses in institution-building, from the New Deal agencies to the early European institutions. The useful precedent is the scale of the design ambition: societies attempted to reorganize the systems governing changed conditions. We may need a comparable effort around artificial agency. It would be nice to develop the wherewithal before catastrophe makes the case for us.

Even slightly net positive-sum activity can dramatically improve the world at machine scale.

Imagine an economy in which machines take part in both buying and selling, and an enormous number of exchanges each leaves the surrounding society slightly better off. Small gains could accumulate into something substantial: an operating system that drives human flourishing. The positive potential rests partly on the rules that make socially useful activity a good way for these systems to succeed.

Livability is the one output that isn’t an input to something else.

The point is always to make human life more livable. Everything else an economy produces is an intermediate good. The chip exists for the server, the server for the service, the service for the company, the company for the revenue. Follow any chain far enough and it terminates in somebody’s actual day — their hours, their security, their sense of what they are for. That makes human livability the only terminal value in the system, and the only one that nothing downstream can justify. A faster process, a more capable agent, or an entirely new organizational form is a claim on that terminus, never a substitute for it. “We built something remarkable” is a statement about the middle of the supply chain.