From 2049, constant escalation looked less like careful management than a structure that had forgotten where decisions belonged.
Summary
From the perspective of 2049, many organisations of the 2020s appeared highly controlled because managers remained involved in an extraordinary number of decisions. Questions moved upwards, approvals multiplied and employees routinely sought confirmation before proceeding. What looked like managerial diligence, however, often revealed a structural problem: decision authority had not been placed reliably where the relevant work occurred. The R2049 Method shows how excessive decision escalation created waiting, interruptions and dependency while simultaneously increasing the workload of managers. The decisive question was not whether leaders should delegate more, but whether organisations had made sufficiently clear which decisions could be taken where, by whom and within which boundaries.
R2049 Method
This contribution examines the present retrospectively from the year 2049, using temporal distance to make structures and consequences visible that remain difficult to recognise from within the present.
The Manager Who Was Needed Everywhere
Looking back from 2049, one figure appeared with remarkable frequency in descriptions of organisational life during the 2020s: the permanently interrupted manager. Employees came with questions, messages accumulated, approvals waited, meetings filled the calendar and seemingly minor issues repeatedly required managerial attention. The manager moved from one decision to another and often ended the working day with the uncomfortable sense of having been extremely busy while making little progress on the work that actually required sustained attention.
At the time, several explanations were common. Perhaps the manager needed to delegate more. Perhaps employees lacked initiative. Perhaps the team had become too dependent on its leader. Time-management techniques, leadership training and rules for reducing interruptions were obvious responses.
All of these explanations could be correct. Yet later structural reconstruction revealed another possibility. In many organisations, the problem was neither primarily the manager nor the employees. The organisation itself had failed to establish a reliable architecture for decisions.
People therefore did what the structure encouraged them to do.
They asked.
Why Asking Was Often Rational
From the outside, an employee who repeatedly sought approval could easily appear hesitant. From inside the work situation, however, asking was often the most rational option available.
The employee might know what needed to be done but not whether they were authorised to decide it. Previous decisions may have been corrected afterwards. Rules might exist formally but be applied differently depending on circumstances. Responsibility might be assigned without corresponding authority, or managers might expect independence while continuing to intervene whenever outcomes differed from their own preferences.
Under such conditions, asking was not necessarily evidence of insufficient confidence. It was a form of risk management.
If making a decision independently could later be criticised while asking a manager transferred part of the risk upwards, repeated escalation became structurally predictable. Employees learned where uncertainty was safest to place.
The organisation then interpreted the resulting behaviour as a characteristic of its people.
From 2049, it increasingly looked like a characteristic of its decision structure.
The Difference Between Responsibility and Decision Authority
One of the persistent organisational ambiguities of the period concerned the relationship between responsibility and authority. Employees were frequently told that they were responsible for outcomes while remaining uncertain about which decisions they were actually permitted to make in producing those outcomes.
The distinction mattered. Responsibility without decision authority created dependency, while decision authority without clear responsibility created inconsistency. Stable organisational structures required both to be connected.
Consider an employee responsible for handling customer complaints. If every deviation from a standard procedure required managerial approval, the employee might own the task but not the decision necessary to complete it. The process therefore paused whenever an exception appeared.
The customer waited. The employee waited. The manager was interrupted.
The visible event was a question.
The structural event was a decision that had no reliable location.
How Decisions Began to Travel
Later Struction analyses described this phenomenon as decision migration. A decision migrated when it repeatedly moved away from the point at which the relevant information and operational responsibility were located.
Sometimes migration was necessary. Strategic, legally consequential, financially significant or exceptional decisions genuinely belonged at another organisational level. Hierarchy itself was not the problem.
The revealing pattern was repetition.
When minor operational questions repeatedly travelled upwards, the organisation was generating vertical movement that added little information but consumed time at several levels. Employees formulated the issue, managers reconstructed its context, decisions travelled back down and work resumed.
A question that might have required two minutes of judgement at the operational point could therefore create substantially more organisational activity.
This activity rarely appeared as a process defect.
It looked like management.
The Queue Nobody Could See
The consequences became particularly visible when many small decisions converged on one person. Each employee experienced only their own question and often regarded it as minor. The manager, however, received questions from the entire system.
A queue formed.
Unlike a physical queue, it was distributed across email, messaging platforms, meetings, telephone calls, project systems and informal conversations. Its existence was therefore difficult to perceive as a single structural phenomenon.
Employees experienced waiting.
Managers experienced interruption.
Customers experienced delay.
The organisation often treated these as separate problems.
From the perspective of 2049, they were frequently different expressions of the same architecture: too many decisions were converging on too few decision points.
This became increasingly important as organisations attempted to become faster. Processes could be digitised, communication accelerated and information made instantly available, yet if decisions still had to pass through the same narrow points, overall speed remained constrained by decision capacity.
The bottleneck was no longer information.
It was permission.
Why Good Managers Could Make the Problem Worse
As with other forms of structural compensation, capable managers often concealed the weakness.
They answered quickly, remained available and accumulated enormous contextual knowledge. Because they knew the organisation well, they could resolve questions in minutes that might otherwise have delayed work for hours. Employees appreciated their accessibility and senior leaders saw a manager who appeared closely connected to operations.
The arrangement worked.
That was precisely why it could persist.
The more efficiently the manager absorbed decision uncertainty, the less pressure existed to clarify the underlying decision structure. Accessibility became compensation for ambiguity.
Over time, a paradox emerged. The manager’s competence increased the organisation’s dependence on that manager. More questions arrived because asking worked. More contextual knowledge accumulated centrally because more decisions passed through the same person. The manager became increasingly indispensable, and that indispensability was interpreted as evidence of managerial value.
From 2049, the pattern was read more cautiously.
Indispensability could indicate exceptional competence.
It could also indicate excessive structural concentration.
Why “Delegate More” Was Not Enough
The standard managerial response was delegation. In principle, this was sensible. In practice, simply instructing managers to delegate more often addressed the visible behaviour rather than the structural conditions producing it.
Delegation could fail when employees received tasks without clear decision boundaries. They were told to take responsibility but remained uncertain about the limits of their authority. As soon as an unusual situation appeared, the question returned to the manager.
The task had been delegated.
The decision had not.
This distinction explained why some organisations repeatedly attempted empowerment programmes without substantially reducing managerial involvement. Employees were encouraged to act independently, but the architecture around them continued to make independent action risky.
Structural decision clarity required something more precise than encouragement. People needed to understand which decisions belonged to their role, where their discretion ended, which exceptions genuinely required escalation and what principles should guide decisions within the permitted range.
Only then could decision authority become structurally located rather than personally borrowed from a manager each time it was needed.
Decision Density
Later organisational analysis increasingly examined decision density: the concentration of decisions at particular points within a system.
High decision density was not inherently problematic. Some roles existed precisely because complex judgement had to be concentrated there. The structural question was whether the decisions arriving at that point genuinely required the knowledge, authority or perspective available there.
If a senior manager repeatedly decided matters that could have been resolved safely at the operational level, the organisation was consuming scarce managerial attention without gaining equivalent decision quality.
This created an opportunity cost that the organisations of the 2020s often underestimated. Every minor decision occupying a manager’s attention displaced another possible use of that attention: strategic thinking, staff development, problem analysis, innovation or simply uninterrupted consideration of difficult issues.
The cost of unnecessary escalation was therefore not limited to waiting below.
It also changed what could happen above.
Digital Systems Did Not Remove Decision Ambiguity
Digitalisation made this particularly interesting. Organisations introduced workflow software, automated approvals, dashboards and increasingly AI-supported processes. These technologies could dramatically accelerate decision preparation and routine execution, but they could not solve an ambiguity the organisation itself had never resolved.
If nobody had decided where authority belonged, software could merely digitise the uncertainty.
Approval buttons reproduced existing hierarchies. Automated notifications accelerated requests for permission. Dashboards supplied more information to managers who were already involved in too many operational decisions.
Later experience with AI made the distinction even more important. Systems could generate recommendations, identify anomalies and propose actions, but the question of who was authorised to accept, reject or modify those recommendations remained organisational.
Technology could support decisions.
It could not substitute for a decision architecture.
What Changed the Structural Diagnosis
By the 2040s, mature organisational analysis had moved beyond the question of whether managers delegated enough. The more useful diagnostic question was where decisions repeatedly travelled and whether that movement was structurally necessary.
Whenever a question moved upwards, analysts examined what had caused the movement. Was additional expertise required? Was the financial or legal consequence significant? Did the issue cross organisational boundaries? Was it genuinely exceptional?
If so, escalation performed a useful structural function.
If not, another possibility became relevant: perhaps the decision had simply never been given a stable home.
This distinction transformed the interpretation of everyday managerial interruptions. A manager receiving twenty operational questions was no longer viewed only as a person with a demanding workload. The questions themselves became structural evidence.
Each one marked a point at which the organisation had temporarily failed to decide where deciding belonged.
What the Organisations of the 2020s Had Failed to See
From the perspective of 2049, the organisations of the period did not suffer from too many decisions simply because work had become more complex. They also suffered because decisions were often structurally concentrated in places where they did not need to be.
This concentration produced a characteristic organisational constellation: employees waited for answers, managers complained about interruptions, processes slowed at approval points and everyone experienced the problem differently.
The employee saw an unavailable manager.
The manager saw dependent employees.
The customer saw delay.
The organisation saw a communication or leadership problem.
Structural reconstruction connected the observations.
They could all originate from the same missing element: a clear location for recurring decisions.
The decisive improvement therefore began not with telling employees to become more independent or managers to become less controlling, but with examining the decisions themselves. Which decisions occurred repeatedly? Where did they originate? Where did they travel? What information was added by that movement? And which of them could remain safely at the point where the work actually happened?
Once these questions were asked, organisational autonomy became less a matter of leadership style and more a property of structure.
R2049 Structural Reading
Structural Trace: recurring operational questions, approvals and escalations converging on managers
Structural Pattern: decisions migrate upwards because authority is less clearly distributed than responsibility
Structural Mechanism: uncertainty about decision boundaries makes escalation safer than autonomous action, concentrating decisions at higher organisational levels
Visibility State: frequently Normalised in the 2020s because managerial availability compensated for structural ambiguity
Primary Structural Properties: Decision · Orientation · Sequence · Closure
The structural weakness became visible where work could not continue without repeatedly importing decision authority from another organisational level. What appeared as employee dependency or managerial overload was often a shared consequence of the same missing decision architecture.
Closing Aphorism
The organisations of the 2020s often asked why employees kept coming to managers for decisions. From 2049, the more revealing question was why so many decisions had nowhere else to go.
Transparency
This article was developed within the framework of the concept The Second Thinking Space with the support of generative artificial intelligence. AI is used to explore questions, broaden perspectives, generate alternative formulations, identify patterns, and facilitate the critical examination of ideas and assumptions. The article has been substantively reviewed, editorially revised, and approved by the author. All editorial decisions, evaluations, interpretations, and conclusions are the sole responsibility of the author.
R2049 