On the Deictic Function of a Universal Disavowal

Every sufficiently large organisation contains a place called “the Business.” No one works there.

The term appears in conversation with the definite article and the confidence of a proper noun — the Business, as though it were a department with a Slack channel and a cost centre code and a VP who could, if pressed, be invited to a meeting. It is spoken by engineers, by product managers, by designers, by data scientists, by infrastructure teams, by platform teams, by anyone who builds or operates or analyses or supports. It is spoken to indicate the origin of requirements, the source of deadlines, the place where priorities are set by people who do not understand the consequences of their choices. It is never spoken by the people it is spoken about, because the people it is spoken about are always speaking it about someone else.

This is the first and most important structural feature of “the Business”: it is a term used exclusively in the third person. No one says “we, the Business.” Everyone says “they want” or “the Business needs” or “we’re waiting on the Business.” The pronoun is always third-person, the tense always implies an external origin, and the speaker is always on the receiving end of a demand they did not generate. “The Business” is a speech act that simultaneously identifies a source of authority and disavows membership in it. It is deictic in the linguistic sense: its meaning is determined entirely by the position of the speaker, and it always points away.

The sociological puzzle is not that some departments call other departments “the Business.” The puzzle is that the designation is universal and mutual. In the standard account, an organisation contains a technical function (Engineering, IT, Operations) and a commercial function (Sales, Marketing, Strategy), and the technical function refers to the commercial function as “the Business” to distinguish the people who build from the people who want. This is the folk model, and it is wrong — not because the distinction doesn’t exist but because it doesn’t terminate. Engineering calls Product “the Business.” Product calls Sales “the Business.” Sales calls Marketing “the Business.” Marketing calls Finance “the Business.” Finance calls Operations “the Business.” Operations calls Engineering “the Business,” because Engineering keeps filing infrastructure requests with no regard for budgetary constraints, which is exactly the kind of unreasonable demand-generation that the term “the Business” was invented to describe.

The chain is circular. There is no function that accepts the designation. And the reason no function accepts it is that “the Business” does not denote a type of work. It denotes a relationship to demands. To be the Business is to be the one who generates requirements without having to fulfil them, who sets deadlines without having to meet them, who makes decisions without having to implement them. Every function experiences itself as the one fulfilling requirements generated elsewhere. Every function, from its own vantage point, is the technical function — the rational, procedural, constrained side of a dyad whose other half is the irrational, demand-generating, unconstrained Business.

This is why the term is so durable. It does not describe a group. It describes a direction — outward, away from the speaker, toward the place where accountability for demands is believed to reside. And because every function is, from some other function’s perspective, the origin of an unreasonable demand, the direction rotates with the observer. “The Business” is the organisational equivalent of “over there”: it is always somewhere else, always populated, never here.

Weber would have recognised the structure immediately, because it reproduces, at the level of language, the distinction he drew between formal and substantive rationality. Formal rationality is the logic of procedure: it asks whether the correct steps were followed, whether the process was consistent, whether the rules were applied. Substantive rationality is the logic of ends: it asks whether the outcome served the purpose, whether the decision was good, whether the result was desirable. Weber’s central observation was that these two forms of rationality are in permanent tension and that modern bureaucracies resolve the tension by assigning them to different parts of the organisation, which then spend their time in mutual incomprehension.

“The Business” is the name each function gives to the place where substantive rationality lives — the place where someone is deciding what to do, as opposed to the speaker’s domain, where the concern is how to do it. But substantive rationality, viewed from the inside, always looks like formal rationality. The VP of Sales does not experience herself as the Business. She experiences herself as following a process: the pipeline, the quota, the forecast, the QBR. Her substantive decisions — which customers to pursue, which deals to prioritise — feel to her like procedural outputs of a system she operates but does not control. The Business, from her perspective, is the function that decides what the product does, which is Product Management, which in turn considers itself procedurally bound by what Engineering can build and what Sales says the market wants. Everyone is procedural. Everyone is formal. Substantive rationality is always somewhere else.

The term “the Business” is therefore not a label applied to a group but a projection of substantive rationality onto an absent referent. It is the mechanism by which every function maintains its self-understanding as a procedural, rational, rule-following entity while attributing the irrational, goal-setting, demand-generating function to someone who is not in the room. This is why “the Business” is always invoked in the third person and never in the first: to say “we are the Business” would be to claim substantive rationality for oneself, which would mean accepting that one’s decisions are not procedurally determined but chosen, and that the constraints one imposes on other functions are not inevitable but willed. No function can accept this without surrendering its claim to technical rationality, which is the basis of its institutional identity.

There is a deeper irony in the word itself. “The business” — absent the capital letter, absent the definite article — should denote the organisation’s core activity, the thing it exists to do, the reason it has revenue and employees and an office. A business’s business is its business: the tautology should be grounding. And yet the term, as deployed inside organisations, means almost exactly the opposite. “The Business” does not refer to the core activity. It refers to the thing the speaker is not doing — the opaque, non-technical, non-procedural other whose demands arrive without explanation and whose logic cannot be questioned because it is, by definition, located outside the speaker’s domain of competence. The Business is the company’s core activity treated as an externality by every function that constitutes the company. The business of the business is nobody’s business.

This suggests a condition more fundamental than misalignment or communication failure. If every function defines itself as Not the Business, then the organisation as a whole is constituted by a set of mutual negations. Each function knows what it is by knowing what it is not, and what it is not is the Business, and the Business is everyone else. The organisation’s identity is the sum of its parts’ disavowals. Nobody is the Business. Therefore everybody is. Therefore nobody is. The referent dissolves on approach, like a term whose definition is “the thing this term does not refer to.”

The practical consequence of this structure is well known to anyone who has attempted to “bring Engineering and the Business closer together.” The attempt fails not because the parties are too far apart but because one of the parties does not exist. There is no Business to bring closer to Engineering, because the Business is not a group with members and a location and an email address. It is a grammatical function — a third-person pronoun with no antecedent — and the alignment exercise is an attempt to introduce two parties, one of which is a noun and the other of which is a direction.

Consultants are hired to bridge the gap. They conduct interviews. They discover the cycle. They recommend that the organisation “define clear ownership of business outcomes” and “establish shared accountability frameworks.” These recommendations fail because they presuppose the existence of the entity they are trying to create. You cannot assign ownership of business outcomes to the Business, because the Business is the name for the place where ownership has already been assigned by everyone who doesn’t want it. The recommendations are implemented, briefly. Cross-functional committees are formed. The committees hold meetings at which each function explains its constraints to the others, and each function listens politely while thinking: “Yes, but you are the Business, and we are the ones who have to deal with your decisions.” The committees disband. The term persists. Another consultant is hired. The cycle of consultation is isomorphic to the cycle of referral it attempts to resolve.

The honest conclusion is that “the Business” is not a problem to be solved but a structural feature of organisations that have grown large enough to contain more than one self-concept. It is the shadow each function casts and no function claims. It is the name of the demand-generating, decision-making, substantively rational entity that every function needs to exist in order to explain its own constraints and that no function can acknowledge being without giving up the procedural innocence on which its identity depends.

The word persists because it works. Not as a referent — it has no referent — but as a mechanism: a way of saying “the source of our constraints is external, legitimate, and not our fault.” Every function needs this sentence. Every function needs a place to project it. “The Business” is that place: real enough to constrain, absent enough to blame, permanent enough to outlast every attempt to define it, and necessary enough that, if it did not exist, it would have to be invented — which, in a sense, is exactly what every department does every morning, when it opens its email and discovers what the Business has decided now.