InsightsPoint of View

The New Boundaries of the Firm

How changing coordination costs can change the organization a business needs

An internal warehouse team and an independent freight driver coordinating the handoff of a crated machine at a loading dock.
By
Cam Myers
Content type
Point of View
Reading time
6 min read
Status
Author’s perspective
Topics
Ownership & Economics

In brief

  • Some coordination work exists because useful operating information is scattered.
  • Technology can favor either internal coordination or external provision; neither is automatically superior.
  • Shared information still requires local knowledge, clear authority, and a workable response to exceptions.

The argument

An owner looks at a busy office and sees a staffing problem. Quotes are waiting, dispatch keeps calling sales, and someone spends half the afternoon finding out whether equipment is actually available. The obvious response is another coordinator.

That may be the right hire. But before adding the position, it is worth asking why so much coordination is required. Is the work inherently difficult, or does essential information have to travel through several people before anyone can act?

The answer matters beyond payroll. Businesses organize work into jobs, departments, branches, and supplier relationships partly to manage the cost of getting things done together. When technology changes that cost, the arrangement that once made sense may deserve another look. The opportunity can be larger than helping each person finish the same tasks faster.

The decision underneath

When the economics of coordination change, where should the work belong?

The work hidden inside a job

Consider a hypothetical regional equipment-rental business in the northeastern United States. Its office prepares quotes, checks availability, takes deposits, and coordinates deliveries. The yard knows which equipment has returned. Dispatch knows which routes have room. An experienced manager knows which customer commitments need special handling.

A customer asks for equipment next Friday. The booking screen shows sufficient stock, but some returned units have not been inspected. The office calls the yard, then dispatch, then the manager. Each person contributes a fact the others cannot reliably see. The customer waits while the business assembles an answer.

The coordinator is doing useful work. Yet part of that job exists because the operating picture is scattered. Better information could change the amount of coordination required without changing the customer promise.

Suppose the business records equipment as ready, committed, awaiting inspection, or unavailable. Delivery capacity is represented by date and service area. A confirmed booking reserves the relevant stock and transport capacity. Staff can quote ordinary jobs within defined limits and send unusual requests for review.

The underlying service remains physical. Someone still has to inspect the equipment, maintain it, load it, drive it, and place it safely. What changes is how many conversations are needed to establish whether a routine commitment can be made.

That can change the shape of the office. A role previously occupied by chasing information might devote more time to customer problems, collections, or growth. Another branch might share selected booking functions rather than reproduce the entire administrative structure. Whether either change pays depends on the work actually released and the obligations the new system introduces.

Technology changes the comparison

In 1937, Ronald Coase examined why some activities are coordinated inside firms while others are purchased through the market. Finding suppliers, negotiating arrangements, and adjusting performance all cost something. Managing work internally also has costs. The choice depends on the comparison between those arrangements.[1]

That argument remains useful when evaluating technology. A shared operating system may make internal coordination less expensive. A dependable connection to an outside provider may make purchasing a capability more practical. Either boundary can move. There is no general rule that better technology means a smaller company, more outsourcing, or fewer managers.

Return to the rental example. Overflow deliveries might once have required repeated calls to establish capacity, price, and timing. A connection that exposes usable availability and confirms reservations could make an outside delivery relationship easier to manage. Conversely, internal dispatch software might make the company's own fleet more economical to operate. The same broad technological change can support opposite organizational decisions.

AI adds another possibility by helping people interpret requests, search operating information, or prepare responses. Research on an AI assistant used by customer-support workers found productivity gains that varied substantially with worker experience. It did not establish that organizations should eliminate management layers or predict the resulting employment effects.[2] A task becoming easier is evidence to reconsider an arrangement, not a complete organizational design.

The relevant comparison includes the cost of handling change. How quickly can the business adjust a commitment, resolve a discrepancy, or recover when a participant fails? A low supplier rate can become expensive if every exception requires senior management. An internal team can also become costly when routine decisions repeatedly climb the hierarchy.

Keep decisions close to the knowledge they need

Faster communication does not put all useful knowledge in one place. A driver may know that a delivery entrance is inaccessible after rain. A yard technician may recognize a developing fault before it appears in an inspection record. A salesperson may know that the customer's stated requirement is incomplete.

Friedrich Hayek's work on dispersed knowledge drew attention to precisely this kind of information: particular circumstances known by people close to the situation.[3] For business design, the implication is practical. A central system can help coordinate work while still needing local observation and judgment.

In the rental example, dispatch should be able to flag an unsuitable route before a commitment becomes final. The yard needs a reliable way to remove equipment from availability. A member of staff who spots a missing fact must be able to stop a routine booking from proceeding. Making information visible without establishing who can act on it leaves the business with a faster reporting system and the same unresolved decisions.

Some activities belong together because they must adjust together. If a service depends on unusual equipment, close collaboration, or knowledge developed over years, dividing it across providers can introduce repeated negotiation and delay. A supplier that has invested specifically for one customer also faces different risks from one selling a standard service to many buyers. A software connection does not remove those underlying dependencies.

Nor should leadership redraw jobs around a demonstration. Test a bounded class of ordinary bookings. Observe which calls disappear, which exceptions remain, and what staff must do to keep the operating picture accurate. Include support, training, verification, and correction in the cost. That evidence can justify changing responsibilities; a promising interface alone cannot.

Reconsider the arrangement before multiplying it

This becomes especially important when a company expands. A new branch or acquisition often arrives with its own administration, systems, and coordination habits. Replicating those arrangements can appear safer than questioning them. Combining everything centrally can look efficient for equally superficial reasons.

The useful inquiry concerns the activity. What must be decided, what knowledge does it require, how often does it change, and who can resolve a problem when the normal arrangement breaks down? Some work may suit a shared capability. Some should remain local. Some may be better purchased from a specialist. The comparison should cover normal operation and the adjustments that keep the customer promise intact.

That is where digital transformation reaches organizational design. The business may need a different distribution of work because information can move differently, commitments can be checked earlier, and ordinary decisions can be made within clearer limits.

An organization chart records where responsibility sits today. It does not establish that the same arrangement will remain the most effective way to deliver tomorrow's work. When the economics of coordination change, owners should reconsider where work belongs before paying to multiply the structure they already have.

Sources

  1. R. H. Coase. The Nature of the Firm. Economica, 1937, 4(16), 386–405.
  2. Erik Brynjolfsson, Danielle Li, and Lindsey Raymond. Generative AI at Work. The Quarterly Journal of Economics, 2025, 140(2), 889–942.
  3. F. A. Hayek. The Use of Knowledge in Society. The American Economic Review, 1945, 35(4), 519–530.

For the leadership team

In practice

  • Examine the activity and its information requirements before replicating a job or branch structure.
  • Include support, adjustment, verification, and exception handling in the internal-versus-external comparison.
  • Test a bounded class of work before redrawing responsibilities around a promising demonstration.

Questions worth asking

  1. Which conversations disappear when an operating fact becomes dependable and visible?
  2. Which activities must stay close to local knowledge, and which can be shared or purchased?

Weighing this decision now? Tell us what you are considering and we will say plainly whether we can help.

Discuss your business