Imagine a mid-sized company having to justify why it has no one responsible for its finances. The question alone would be absurd, no one would take it seriously, the managing director would assume it was a bad joke. Now imagine the same question for the domain that decides, every single day, whether what the organization set out to do actually happens: the action of the people it is made of. Here the missing accountability is not the scandal but the normal state of affairs. Not one person in the company would ask for the individual responsible, because that individual does not exist and their absence strikes no one as odd.
That is the strange asymmetry this piece is about. An organization treats its capital, its technology and its law as something that has to be built, owned and audited, and it treats the action of its people as something that simply happens, like weather, like a question of character, like a matter of the right attitude. And yet it is precisely this action that is the raw material every financial figure, every technical roadmap and every satisfied compliance requirement is ultimately made of, because it is people who operate booking systems, run through processes, adopt technology or quietly sabotage it.
An infrastructure no one has built
A precise term is worth introducing here, because the word most people use misses the phenomenon. They call it culture, and with that the matter is already lost, because culture sounds like something grown, diffuse, that at best can be nurtured but not built. What people in an organization actually do, however, is not the product of an atmosphere but the product of an infrastructure, a very concrete arrangement of defaults, incentives, feedback signals and transition points that decides every day which action is frictionless and which costs effort. This arrangement already exists in every organization, I call it action infrastructure, and its problem is not that it is missing but that it was never recognized as infrastructure and therefore never built.
Action infrastructure is the systematic design of the environmental conditions under which people act, with the goal that the desired action is the most obvious consequence of the context and not the product of willpower, knowledge or daily mood. It answers no question about personality or talent, but a single, very sober one: what context must exist for the desired action to be the most likely one. Anyone who has looked at the phenomenon from the design side will know it under the name behavioral architecture, and action infrastructure is nothing other than the same thing, named after what it is for an organization: not a soft variant of leadership, but an infrastructure beneath the infrastructures.
The point at which most discussions of culture and behavior fall apart is the assumption that all of this is too soft to be treated like finance or IT. The exact opposite is true, and it can be shown through the infrastructures that already exist.
Why CFO, CTO and General Counsel exist at all
It is a worthwhile question why an organization has a finance lead, a technology lead and a legal lead at all, because the obvious answer is wrong. These roles did not emerge because money, technology and law suddenly became important, they were always important. They emerged because in each of these domains the same constellation of three conditions eventually came together, and once you have seen that constellation, you recognize it again.
The first condition is a complexity threshold: the domain became so interwoven that the sum of well-meant individual decisions no longer reliably produced a coherent state. The second is a damage asymmetry: failure was no longer gradually unpleasant but abruptly catastrophic, and it was attributed to someone, legally or reputationally. The third, and this is the most insidious, is a failure latency: the error arises today and explodes in two years, at a point where no one remembers the single decision that triggered it. The CFO, the CTO and the General Counsel are all institutional answers to exactly this triple problem, and their shared principle is always the same: the infrastructure makes the organization independent of the individual qualities of its members, so that the sum of local decisions yields a globally sound state, even when individual decision-makers are sometimes overwhelmed, sometimes under pressure and occasionally simply incompetent.
These roles did not emerge because their subject became more important, but because the cost of the missing accountability reached a magnitude no one could ignore any longer.
And now the uncomfortable question that carries the whole argument: which domain meets these three conditions most clearly today? Not money, not code, not law, but the action of people in organizations that are forced, by AI transformation, by the complexity of knowledge work and by a global competition for talent, to steer action at a speed and scale for which they never built a systematic tool. The complexity threshold has long been crossed, the damage asymmetry is enormous, and the failure latency is longer than in any other domain, because a badly set default or a perverted incentive system takes years before its consequences become visible. Anyone looking for the full derivation of this structural pattern will find it in the piece on the layer nobody designs; what interests me here is what follows from it, and that is a personnel question.
The second question no one has answered yet
If an organization already has an action infrastructure, and it does, then the question is not whether it wants one, but only whether it continues to leave that infrastructure to chance or starts to build it. I have answered that first question elsewhere. There is, however, a second question, which presupposes the first and which no organization has yet answered systematically: who is responsible for it.
This is not a rhetorical question but a very practical one. Every other critical infrastructure of an organization has a dedicated leadership role, its own budget and its own design methodology. The financial infrastructure has the CFO, controlling and internal audit. The IT infrastructure has the CTO, systems architecture and security governance. The legal infrastructure has the General Counsel, the compliance framework and the regulatory-affairs structure. The infrastructure on which all three run, because all three are executed by people, has none of these, neither role nor budget nor method.
Instead, responsibility for the action of people is distributed across the organization, which in practice means that no one holds it. Part of it sits with HR, which mostly administers processes rather than designing behavior. Part of it sits with managers, who are paid for their own targets and influence behavior on the side. Part of it sits with a communications department that sends messages and hopes they become action. And part of it sits with external consultants who are called in for the next transformation when the last one failed to produce what it was supposed to cost. Distributed responsibility is the most elegant form of no responsibility, because it feels as though the topic is covered, while in truth no one owns the error when it explodes.
When an AI transformation fails, the story is that the culture was difficult, the communication insufficient, the middle management unwilling to come along. When a bonus system produces toxic action, the story is that the wrong people were hired.
The action infrastructure is never named as the cause, and the reason is strikingly simple: it does not exist as a category. What has no category has no accountability, and what has no accountability is not fixed but booked as bad luck, a question of character, or a culture problem.
What the numbers say when no one is responsible
One could object that all of this is a theoretical problem, an elegance for organizational sociologists, without practical urgency. The numbers say otherwise, and they say it more bluntly than I would like. Gallup puts the annual productivity loss from disengagement in its State of the Global Workplace at 8.8 trillion US dollars, which corresponds to around nine percent of global gross domestic product, and the share of engaged employees worldwide fell to 21 percent in 2024. That is not a mood reading, that is a balance-sheet item the size of a mid-sized national economy, and in no organization does anyone sign for it.
The same pattern shows up everywhere action decides success. Gartner predicts that at least thirty percent of generative AI projects will be abandoned after the proof of concept, and the reasons given, poor data quality, unclear business value, escalating costs, are in truth all action problems, because they depend on what people actually do with the technology. The often-cited rule of thumb that around two thirds of all transformations miss their targets is disputed in its precision, yet even its most cautious critics land on the statement that between half and two thirds disappoint, and this failure too almost never lies in the strategy but in the action that would have to carry it out.
Take these numbers together and a strange picture emerges: organizations spend enormous sums on strategy, technology and transformation, and a substantial part of those sums is consumed by the same gap, namely the action that would have to occur for the investment to pay off, and for which no one has built the infrastructure. A Chief Behavioral Officer is therefore not the next budget line next to the others, but the condition under which the already spent budgets produce any return at all.
What a Chief Behavioral Officer actually does
At this point I have to head off a confusion, because the title does exist here and there, and it usually means something other than what is meant here. Where companies have a Chief Behavioral Officer today, for example at Maritz or Opower, this role almost always sits on the customer side and applies behavioral science to marketing and consumer decisions. That is sensible and it works, but it is not the role that is missing here. The missing role is the one responsible for the internal action infrastructure, that is, for the layer on which the organization itself runs, and that is precisely the one no one has filled systematically.
A Chief Behavioral Officer in the sense meant here owns not the behavior of customers but the environment in which the organization's own people act. The role asks which defaults in the digital tools, the processes and the policies make the wrong action the easiest option and the desired one the most laborious. It checks whether the incentive structures produce the action they are supposed to produce, or an action that maximizes the reward and misses the goal, which are two very different things easily mistaken for one another. It looks at which identity and feedback signals an onboarding sends, in what order changes are embedded, and which early indicators measure real behavior change before it eventually shows up in the outcome figures, or fails to.
This is not a consulting stance and not a workshop, but a function with a mandate that structurally resembles the CFO's. Just as the finance lead has the right to stop an investment whose numbers do not hold, the Chief Behavioral Officer needs the right to test a new policy, a new tool or a new incentive system for its effect on action before it is rolled out. Without that mandate the role is just another consultant with good ideas and no lever, and then it can be spared.
The CFO may stop an investment whose numbers do not hold. The Chief Behavioral Officer needs the right to stop a default whose effect on action does not hold, otherwise the role is just a consultant with good ideas and no lever.
The real resistance
If the argument is this clear, why does the role not already exist? The answer is uncomfortable, because it lies not in missing knowledge but in the incentive structures of the very organizations that would have to introduce it. A designed action infrastructure is expensive, slow and hard to show in the quarterly report, while the alternative, another training, another campaign, the next transformation consultancy, looks cheap, goes quickly and immediately resembles action. As long as the measurable beats the effective, an organization will sooner book the tenth leadership seminar than create the one role whose success shows up in figures only two years later, figures that by then have long been attributed to someone else.
There is also a status problem that is rarely spoken aloud. A CFO administers something hard, countable, respected, and no one would question its right to exist. A person responsible for human action administers something that, in the perception of many organizations, is soft, fuzzy and somehow beneath the dignity of real leadership, even though it is the one thing without which none of the hard numbers ever come into being. This disdain is itself a symptom of the missing category, because what is not an infrastructure cannot justify a serious leadership role either, and so the blind spot keeps itself alive by taking itself for granted.
How an organization would begin
At Engaginglab the answer to the accountability question is not an appeal but a method and an instrument. The Behavioral Systems Analyzer makes visible what acts invisibly in an organization, that is, which defaults make the wrong action the easiest option, which incentive structures produce the opposite of what they should, and where the signals are missing that would reinforce the desired action. It delivers not an opinion but a systems diagnosis, by the same logic with which an auditor examines capital flows. The Drive Method is the design methodology that turns this diagnosis into a configuration, and the Chief Behavioral Officer is the role that owns both, the same institutional answer that money, technology and law received long ago.
An organization does not have to fill this role overnight with its own board seat, which for most would be too large a step and would fail at exactly the status problem I described. It can start smaller, with a clearly mandated function that has the right to test the action-relevant decisions before they are made, and that is assigned to a single person whose name sits underneath it. The decisive step is not the size of the role but that responsibility moves from diffuse distribution into a named accountability, because only then can the failure that is today ascribed to culture be handed to anyone at all to work on.
The question at the end is therefore not whether an organization needs an action infrastructure, because it already has one, and it acts every day, whether anyone looks or not. The question is only whether that infrastructure remains left to chance, as the accumulation product of thousands of decisions no one made from the standpoint of action, or whether someone finally fills the post whose absence was normal for so long that no one noticed it any more.