Decided. Not Translated.
Search Info
Primary topic: The structural gap between organisational decisions and their implementation
Central question: Why do formally approved decisions sometimes fail to produce corresponding changes in everyday organisational activity?
Key concepts: decision implementation, organisational change, execution gap, operational coordination, decision rights, workflow integration, implementation planning
Core insight: A decision changes an organisation only when its consequences are translated into operational responsibilities, sequences and conditions; formal approval alone does not establish those connections.
Summary
Organisations make decisions through meetings, approvals, management instructions and formal resolutions. Yet a decision can be clearly documented and widely accepted without producing the intended change in everyday work. The difficulty does not always lie in resistance, weak leadership or insufficient communication. Sometimes the decision has never been translated into the operational structure that would allow it to take effect. Struction examines this as decision translation: the conversion of an approved intention into changed responsibilities, sequences, resources and working conditions. Without that conversion, an organisation may possess a completed decision while continuing to operate according to its previous arrangements.
The Decision Had Been Made
A management meeting ended with a clear agreement. The organisation would introduce a new procedure, change a reporting requirement, simplify an approval process or establish a different approach to customer requests. The decision was recorded in the minutes, responsibilities appeared to be understood and the participants left with the impression that an important issue had been resolved.
Several weeks later, little had changed. Employees continued using the previous procedure, reports were still prepared in the familiar format, approvals followed the old sequence and exceptions were handled through established routines. The decision had not been rejected, and there was no obvious disagreement about its purpose. Nevertheless, its practical consequences remained limited.
Such situations were commonly interpreted as implementation failures. Management might conclude that employees had not understood the instruction, that communication had been insufficient or that greater commitment was required. These explanations were sometimes correct, but they overlooked another possibility: the organisation had completed the act of deciding without establishing the conditions under which the decision could become operational.
The distinction is central to Struction. A decision is an event within a decision-making process, while implementation is a change in the structure through which work occurs. The first can be completed without the second having begun.
When Agreement Was Mistaken for Implementation
Formal agreement creates a particular kind of organisational certainty. Once a decision has been approved, the underlying question appears settled. Meeting minutes provide evidence that the issue was discussed, the outcome can be communicated and the responsible management level can legitimately regard the decision-making stage as complete.
Yet agreement does not automatically alter the arrangements that govern everyday activity. Employees may understand that a new procedure is intended without knowing which existing steps should disappear, when the change becomes effective, how exceptions should be handled or what to do when the new instruction conflicts with established requirements.
The resulting difficulty is not necessarily a lack of willingness. People may support the decision while continuing to work within an operational environment that still reflects the previous one. Forms, software settings, approval rights, reporting schedules and established dependencies do not change simply because an intention has been approved.
This creates a structural distinction between decision closure and operational activation. Decision closure establishes that an organisation has selected a course of action. Operational activation establishes that the conditions required to follow that course have been created. The two are related, but they are not the same achievement.
The Missing Translation
Consider an organisation that decides to reduce unnecessary approval stages. The objective is clear: routine cases should move more quickly, and management should become involved only when genuinely exceptional circumstances require additional judgement. The decision is communicated as a simplification of the existing process.
For the change to become effective, however, several operational questions must be resolved. Which cases now qualify as routine? Who is authorised to approve them? What happens to approval requirements embedded in software systems? Which documentation remains necessary? How should employees respond when an existing policy still refers to the previous approval sequence?
If these questions remain unanswered, the organisation has changed its declared intention without changing the structure that determines behaviour. Employees may continue seeking the familiar approvals because doing so remains the safest way to complete their work. What appears to management as unnecessary adherence to an obsolete process may be a rational response to unchanged operating conditions.
Struction describes the missing connection as decision translation: the conversion of a formal decision into the specific changes in responsibilities, sequences, decision rights, information and resources required for implementation. The concept does not describe an additional communication campaign. It describes the structural work necessary to make a decision executable.
Why Communication Was Not Enough
Organisations frequently respond to implementation difficulties by communicating decisions more intensively. Instructions are repeated, presentations are circulated, managers explain the intended benefits and employees are reminded that the new approach has been approved. These measures can improve understanding, but they cannot substitute for missing operational conditions.
An employee may know precisely what management wants while lacking the authority to act accordingly. A department may understand a new priority while remaining subject to performance measures that reward the previous one. A team may support a simplified procedure while being required to use a software system that still enforces the original sequence.
In such cases, communication is not the missing element. The decision has reached the people concerned, but it has not reached the structures through which their work is organised.
This distinction explains why repeated announcements sometimes produce frustration rather than change. Management experiences the need to repeat an instruction that should already be understood, while employees experience pressure to deliver an outcome that their working conditions do not yet support. Both sides may interpret the other as failing to act, although the underlying problem lies in the relationship between the decision and the operating system.
The organisation does not necessarily need to explain the decision again. It needs to establish what must become different for the decision to have consequences.
The Old Structure Continued to Decide
Established organisational arrangements exert considerable influence because they define what can be done without additional negotiation. Employees know which forms to complete, which systems to use, whose approval to obtain and what constitutes acceptable completion. These arrangements provide stability, but they can also preserve earlier decisions long after new intentions have been announced.
A formal decision that does not alter these conditions enters an environment already organised around another course of action. The old procedure continues to determine behaviour because it remains embedded in the available sequence of work.
This can create the appearance of organisational resistance even where no deliberate resistance exists. People continue doing what the structure enables, requires or rewards. The new decision remains present as a statement of intention, while the previous decision remains present as an operational arrangement.
The difference is particularly important when organisations interpret implementation through individual behaviour. Asking why employees have not adopted the new procedure may be less informative than examining which elements of the previous procedure still govern their actions.
From a Struction perspective, the existing organisation is not a neutral surface on which new decisions are written. It is a system of accumulated decisions that continue to operate until their consequences are explicitly changed.
When Responsibility Was Assigned Too Early
Another difficulty arises when organisations assign responsibility for implementation before defining what implementation requires. A department head may be designated as the owner of a new initiative, or a project manager may be instructed to ensure that a decision is carried out. The appointment creates visible accountability, but it does not necessarily establish the means through which the change can be achieved.
Implementation may depend on resources controlled by other departments, technical modifications, changes in decision rights or the removal of conflicting requirements. The person assigned responsibility can coordinate these matters but may lack the authority to resolve them.
The result is a familiar organisational asymmetry: responsibility for the outcome is concentrated, while control over the conditions required to produce it remains distributed.
This is not simply a problem of insufficient authority. It reflects an incomplete translation of the decision into the organisational relationships on which implementation depends. A named owner may be necessary, but ownership alone does not create a viable sequence of work.
The relevant diagnostic question is therefore not merely who is responsible for implementation. It is whether the responsible person has access to the decisions, resources and dependencies that must change before the intended outcome can become possible.
The Difference Between Starting and Changing
Implementation is often treated as something that begins once the first visible activity has occurred. A working group is established, a project plan is prepared, training is scheduled or an initial report is produced. These activities demonstrate that the decision has generated work, but they do not necessarily demonstrate that the organisation itself has changed.
A project can remain active for months while the operational conditions that originally justified it remain intact. Meetings take place, documents are produced and progress is reported, yet employees continue working through the same underlying arrangements. The organisation has created an implementation process without necessarily producing operational activation.
This distinction is important because activity is easier to observe than structural change. Project milestones can be counted, meetings documented and deliverables completed. Whether a new decision has altered the actual sequence of work requires a different form of observation.
For Struction, the decisive evidence is not the existence of implementation activity but the point at which the new arrangement becomes the normal condition of work. A changed approval rule has become operational when routine cases actually proceed under the new authority. A simplified reporting requirement has taken effect when the old report is no longer necessary. A new coordination procedure has been implemented when the intended interaction can occur without repeated exceptional intervention.
Until then, the organisation may be working on the decision without yet working differently because of it.
The Hidden Importance of Removing the Old
Many implementation plans concentrate on introducing new elements. They specify what employees should begin doing, which systems should be adopted and what information should be collected. Less attention may be given to the arrangements that must cease.
This omission can create competing structures. A new reporting format is introduced while the previous report remains mandatory. A revised approval process is announced without removing the old approval fields. A new responsibility is assigned while an existing department retains formal control over the same decision.
Employees then face an environment in which the new and old arrangements coexist. To avoid errors, they may comply with both, creating additional work rather than achieving the intended simplification.
The structural problem is not that the new decision was ignored. It is that the organisation failed to establish which previous requirements the decision was intended to replace.
Decision translation therefore includes subtraction as well as addition. Implementation may require removing obsolete steps, withdrawing earlier permissions, retiring documents and changing established expectations. Without this work, new decisions can accumulate on top of old structures rather than transform them.
An organisation may consequently become more complicated each time it attempts to simplify itself.
When Success Was Reported Before It Could Be Observed
The distinction between decision closure and operational activation also affects how progress is reported. A decision may be classified as implemented once an instruction has been issued, a training session completed or a new procedure formally published. These are legitimate milestones, but they measure preparation for changed work rather than necessarily demonstrating that the change has occurred.
This can produce premature closure. Management receives confirmation that the initiative has been completed, while operational routines remain only partially altered. Because the implementation project is considered finished, the remaining differences may later appear as isolated compliance problems rather than evidence of incomplete structural change.
A more precise distinction separates three conditions: the decision has been made, the conditions for implementation have been established, and the intended change has become observable in everyday work. These conditions may occur close together in simple cases, but complex organisations cannot assume that they coincide.
The value of this distinction is diagnostic rather than bureaucratic. It prevents organisations from mistaking evidence of administrative completion for evidence of operational change. A decision should not be regarded as ineffective merely because its consequences are not immediately visible, but neither should it be regarded as implemented solely because the formal process surrounding it has ended.
Decision Translation as a Structural Requirement
Decision translation does not require every management decision to become a large project. Many changes are simple enough to take effect through a brief instruction or a direct adjustment to an existing procedure. The complexity of translation should correspond to the complexity of the dependencies involved.
What matters is that the organisation recognises translation as a distinct requirement. A decision that changes priorities must reach the mechanisms through which priorities are established. A decision that changes responsibilities must reach the allocation of authority and accountability. A decision that changes workflow must reach the sequence of activities and the conditions under which one stage can proceed to the next.
The practical significance of this approach lies in its ability to distinguish different causes of apparent implementation failure. A decision may be poorly understood, actively opposed, insufficiently resourced or structurally incomplete. These explanations require different responses, and treating them all as failures of commitment can lead to repeated interventions that do not address the actual problem.
Struction therefore treats the relationship between decision and operation as something to be examined rather than assumed. The presence of a formal decision establishes intention; only the corresponding operational conditions establish the possibility of consistent execution.
The Structural Reconstruction
The conventional understanding of organisational decisions often places the decisive moment at the point of approval. Once agreement has been reached, attention shifts to implementation, which is expected to convert the decision into results. When those results do not appear, the organisation searches for weaknesses in execution.
The Struction reconstruction introduces an earlier question: Was the decision ever translated into a form that the organisation could execute?
This question changes the diagnosis. It directs attention away from the assumption that employees have failed to carry out an instruction and towards the possibility that the instruction never became part of the structure governing their work. The decision may have been clear, legitimate and widely accepted while remaining disconnected from the operational conditions required for change.
Organisations therefore need to distinguish between deciding what should happen and establishing how the existing system must change so that it can happen. The first creates a new intention; the second creates a new operating condition. Neither can reliably substitute for the other.
The underlying problem is not always an inability to make decisions or a lack of determination to implement them. Sometimes it is the absence of a defined connection between a completed decision and the sequence of work through which its consequences are supposed to emerge.
An organisation can therefore accumulate formally completed decisions while continuing to operate according to arrangements those decisions were intended to replace. The resulting discrepancy may remain invisible for some time because decision records show progress even when the structure of everyday work has barely changed.
The central Struction insight is that a decision is not operational simply because it has been made. Its practical significance depends on whether the organisation has changed the responsibilities, sequences, permissions and conditions through which that decision can become effective.
The organisation had decided what should change. It had not changed what made the old way continue.
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.
