The budget is also an organizational design decision

Imagine a leadership team approving faster delivery, lower costs, more innovation, and unchanged service quality for the coming year. The spreadsheet reconciles. But who has checked whether the organization can reconcile those promises in practice?

My argument is that a budget should be read as more than a financial plan. Read through an AO lens, it is also a set of assumptions about where authority belongs, which activities matter, how teams depend on one another, and who must absorb the gap between ambition and capacity.

That makes the central question organizational: are we funding a credible way of working, or expecting people to compensate for contradictions that remain unresolved? Asking managers to “make it work” is not a substitute for deciding what work should stop, which capabilities need investment, or which decisions must move closer to the people doing the work.

The answer is not to design an ideal organization and ask finance to pay for it. Financial constraints belong inside organizational design. But affordability and operational viability must be tested together, rather than using an approved spending ceiling as the only design criterion.

Budgeting for the organization we need means funding its ability to deliver, learn, and remain viable. It does not mean protecting every existing role, accepting every investment request, or promising transformation without making trade-offs.

Beyond Budgeting changes the management model, not just the calendar

Beyond Budgeting combines six leadership principles with six management-process principles, connecting purpose, transparency, accountable teams, autonomy, and customer focus with adaptive planning, resource allocation, and performance evaluation (BCG’s account of the Beyond Budgeting principles). It should therefore not be reduced to replacing an annual spreadsheet with a rolling forecast.

Bjarte Bogsnes describes the ambition as creating more adaptive and human organizations through coherent changes in leadership and management processes, rather than treating the removal of budgets as an end in itself (Business Agility Institute interview). The practical test is whether management behavior changes with the financial process.

Consider an organization that updates its forecast monthly but still makes local spending wait for central permission, rewards managers for defending departmental targets, and penalizes unwelcome predictions. My assessment would be that it has changed the reporting rhythm without resolving the underlying organizational problem.

AO and Beyond Budgeting overlap in their concern for autonomy, accountability, transparency, and adaptation. The synthesis proposed here uses AO diagnosis to examine how those conditions actually work in a particular organization, and Beyond Budgeting principles to challenge how its management processes support or undermine them. This is a proposed application of the two approaches, not a claim that their combination is a separately validated model.

Diagnose the organization before changing its funding rules

The AO starting point is not a preferred organization chart. It is an examination of the tensions between purpose, work, authority, relationships, and feedback. Before changing funding rules, I would investigate six conditions.

• Decision flow: Where do important decisions wait? Identify whether the constraint is expertise, evidence, authority, or habitual escalation before prescribing more people or another approval layer.
• Autonomy and risk: Which decisions are reversible and locally contained? Distinguish them from decisions that create irreversible, cross-unit, or enterprise-wide exposure.
• Candor: Can a team report that an initiative is failing without first negotiating a more acceptable story? Test the actual response to bad news, not only the stated commitment to transparency.
• Informal power: Who can secure resources through personal access, and whose evidence is routinely discounted? A formally open process still needs protection against influence replacing judgment.
• Coordination: Which outcomes depend on several teams, and who can resolve their competing priorities? Departmental affordability is insufficient if the combined commitments cannot be delivered.
• Continuity: Which capabilities depend on one sponsor, expert, or personal network? Test whether the proposed model can work when those people are absent.

The output should be a small set of evidence-backed design hypotheses, not a maturity label. For example: “The delay appears to come from unclear exception authority; adding delivery capacity is unlikely to resolve it.”

This also separates structural change from organizational transformation. A revised approval rule changes formal structure; learning to use that authority responsibly requires practice, feedback, and trustworthy relationships. I would not declare the transformation complete because the policy has been signed.

Separate aspiration, prediction, and permission

One of Beyond Budgeting’s central moves is to separate three purposes traditionally combined in a budget: setting targets, forecasting outcomes, and allocating resources (BCG, Agile Meets Beyond Budgeting). For an AO application, I would make that separation explicit in meetings, decision rights, and performance conversations, not just in different worksheets.

• Aspiration: what do we want to achieve? Establish direction and meaningful ambition. Keep the intended customer or stakeholder outcome visible rather than allowing a financial number to become the whole purpose.
• Prediction: what do we currently expect? Produce the most credible view available, including uncertainty and assumptions. An unfavorable forecast should trigger inquiry and action, not an instruction to make the number resemble the target.
• Permission: what resources should we commit now? Decide what is justified, affordable, and within the relevant authority. A forecast is neither a spending authorization nor an automatic funding claim.

Beyond Budgeting advocates directional and relative goals, unbiased forecasts, and resource decisions responsive to need, with time horizons suited to the decisions rather than automatically ending in December (BCG, Going Beyond Budgeting). Separating these functions does not make them independent: forecast evidence still informs choices about actions, funding, and the feasibility of the ambition.

The AO challenge is whether people can keep those distinctions intact under pressure. If a lower forecast threatens someone’s status or remuneration, ask what protects honest reporting. If resource requests depend on demonstrating certainty, ask how an uncertain but worthwhile experiment can receive support without an exaggerated business case.

Do not change the forecast merely because it is uncomfortable. Change the action, the allocation, or, where justified, the ambition, and make that decision visible.

Fund capabilities and value flow, not organizational territory

I would use the AO diagnosis to examine the capabilities required across an end-to-end service: expertise, shared infrastructure, decision capacity, coordination, and learning. Departmental accounts remain useful for financial responsibility, but they should not be the only view through which leadership evaluates investment.

Consider a hypothetical customer-onboarding service spanning sales, operations, technology, and compliance. Each department stays within its allowance, yet customers wait because information is repeatedly corrected and nonstandard cases circulate between decision makers. Each unit may be locally affordable while the service remains poorly designed.

An AO-informed response would first test where the delay originates. A Beyond Budgeting-informed response would then allow a justified intervention to be considered when the need is understood, rather than only at the next annual allocation round. Together, they could support a bounded cross-functional experiment with clear exception authority, access to relevant data, and a shared service outcome.

That intervention might require temporary specialist capacity, better information, or clearer responsibilities rather than a new department. Retaining the current structure should remain an option if changing the interactions is sufficient.

The assessment should distinguish total recurring cost, transition expenditure, delivery time, rework, quality, and risk. A lower cost in one function is not enough to establish an improvement if another team must absorb the work. Likewise, time released for better service is a capacity benefit, not automatically a cash saving.

Preserve stable capability where continuity matters, while allowing priorities and incremental investment to change. Dynamic allocation should not become permission to dismantle and reconstruct teams every time the forecast moves.

Make autonomy financially real and risk-calibrated

Beyond Budgeting calls for delegated operational decisions supported by transparency and accountability, rather than detailed annual allocations controlling every action (BCG, Going Beyond Budgeting). My AO application is to define the boundary of that authority according to consequences, not simply organizational rank or the amount of money involved.

• Local decisions: Allow teams to make reversible, contained choices within explicit financial and risk limits, with accessible decision records and outcome feedback.
• Shared decisions: Require coordination when a choice consumes another team’s capacity, changes a shared service, or creates dependencies that the deciding team cannot resolve alone.
• Enterprise decisions: Escalate choices affecting major capital commitments, liquidity, legal obligations, safety, or material cross-organizational exposure to the appropriate accountable authority.

A low-cost action can still have serious consequences, so a spending threshold alone is not a complete delegation policy. Conversely, routine low-risk choices should not require executive attention merely because that has been the custom.

In this design, enterprise leadership and finance remain responsible for aggregate affordability, liquidity, material commitments, and financial oversight. They should make the constraints usable: specify what teams may decide, what evidence must be visible, when consultation is necessary, and what triggers intervention.

Transparency should support informed decisions without exposing personal or confidential information indiscriminately. Accountability should include the quality of judgment and the response to new evidence, not only whether an expense remained within an earlier estimate.

The test is practical: can a team act responsibly without seeking a personal favor, and can the organization detect and correct a harmful pattern before it spreads? If not, autonomy exists in the vocabulary more than in the operating model.

Change performance conversations as well as funding

Beyond Budgeting advocates holistic performance evaluation, peer feedback, and rewards that recognize shared success rather than compliance with fixed performance contracts (BCG’s Beyond Budgeting principles). In this synthesis, changing incentives is part of organizational design, not an optional HR workstream after finance has finished.

For the hypothetical onboarding service, I would not judge success only by whether each function spent less. I would examine end-to-end service outcomes, total cost, risk, collaboration, and whether improvements survive without continuous intervention by a sponsor.

Relative comparisons can strengthen that assessment when the comparison is genuinely meaningful. But I would not turn benchmarking into a forced internal league table: differences in demand, customer complexity, and regulatory exposure need to be understood before results can be fairly compared. Absolute service obligations and safety limits still need to be honored.

I would also separate a forecast update from an automatic reward consequence. Review decisions against the information available when they were made, and examine whether people disclosed emerging problems, sought help, and changed course responsibly.

The objective is not to remove consequences for negligence or misconduct. It is to avoid treating honest uncertainty as failure while rewarding an attractive number detached from reality. Any changes to remuneration should be designed deliberately with the relevant people, legal, and governance functions rather than introduced by implication.

Use business rhythms without losing stability

Beyond Budgeting proposes management rhythms responsive to business events and decision needs, rather than governed only by the calendar year (BCG’s Beyond Budgeting principles). The AO extension is to make the feedback loop explicit: what has changed, who can interpret the signal, who can act, and how will we know whether the response helped?

A practical design could combine periodic reviews with event-triggered decisions. Liquidity pressure may require immediate attention; a capacity decision may need a short forecast horizon; a capability investment may need a longer one. The appropriate rhythm should follow the decision, not a universal rule that everything must be reconsidered monthly or quarterly.

Annual accounts, board processes, contracts, and applicable financial obligations remain constraints to accommodate. Where an annual budget is required, make its role explicit and progressively separate it from every operational permission and performance judgment. That is a transitional arrangement, not proof that a rolling forecast alone constitutes Beyond Budgeting.

Do not replace one annual bureaucracy with twelve monthly ones. Keep forecasts proportionate to the decisions they inform, avoid repeatedly rebuilding detail that changes nothing, and preserve commitments whose continuity is essential.

If resources cannot support the promise, change the promise or change the design. Revising allocations is useful only if leadership also resolves the consequences for work, dependencies, and expectations.

Start with a bounded experiment, not a budget abolition campaign

I would begin with one value flow where the connection between funding, decisions, and outcomes can be observed. A 90-day learning cycle could be a starting design, not a Beyond Budgeting requirement or a promise that financial benefits will appear within three months.

Before starting, identify what the pilot replaces. Adding new forecasts, reviews, and governance on top of every existing budget ritual would make it difficult to tell whether the alternative is useful or merely additional work.

• Establish the baseline: Record decision waiting time, service outcomes, rework, total cost, and forecast assumptions. Include the experience of people doing the work and receiving the service.
• Separate the three conversations: Make target setting, forecasting, and spending decisions distinguishable, with named owners and clear outputs.
• Delegate a defined set of decisions: Agree authority, consultation boundaries, financial capacity, risk limits, and stop conditions before funds are used.
• Fund the transition: Include learning, knowledge transfer, temporary overlap, and implementation capacity where needed. Do not book the full proposed savings before the new arrangement can operate.
• Review the whole result: Compare outcomes, cost, risk, and coordination effort with the baseline. Treat any observed improvement cautiously if demand or other conditions also changed.
• Decide what follows: Continue, adjust, stop, or expand based on evidence. Record which management behaviors and old procedures must change before wider adoption.

Leadership, finance, operations, and people functions should own that experiment together. The board should receive a clear explanation of what control is being replaced, what remains mandatory, and what new evidence enables oversight.

Before approving the next allocation, ask a stronger question than “Can we afford these requests?” Ask: “What capability and authority are we creating, what work are we stopping, and how will we respond if our assumptions prove wrong?”

The final test is whether the organization can deliver its purpose within real constraints and revise its decisions without losing accountability. AO diagnosis helps make the organizational conditions explicit; Beyond Budgeting challenges whether the management system enables them. Together, they invite us to fund not a fixed picture of next year, but a credible capacity to act, learn, and adapt.