When speed stopped being a means and became evidence of quality.
Few organisational ambitions appear more reasonable than wanting work to move faster. Customers should not wait unnecessarily, decisions should not remain unresolved, information should reach the people who need it and avoidable delays should not accumulate between one stage of a process and the next. In this sense, speed is an entirely legitimate organisational variable. A process that requires ten days because information sits unattended for eight of them has an obvious problem.
The difficulty begins elsewhere. It begins when speed ceases to describe one characteristic of a process and starts to function as evidence that the process itself is good.
This shift rarely occurs through an explicit decision. Few organisations announce that rapidity will now take precedence over judgement, reliability or completeness. Instead, the change enters through hundreds of individually plausible expectations. Emails should be answered promptly. Requests should be processed without delay. Managers should remain accessible. Decisions should be accelerated. Projects should move continuously. Customers should receive immediate feedback. Internal enquiries should not remain unanswered. Each expectation appears sensible on its own.
Taken together, however, they can alter the architecture of work.
Speed begins to migrate from the process into the interpretation of the process.
A rapid response becomes evidence of attentiveness. A quick decision suggests decisiveness. An empty inbox looks controlled. A short turnaround time signals efficiency. Immediate availability appears cooperative. Progress becomes easiest to recognise when something visibly moves.
The organisation has not merely become faster. It has begun to use speed as a proxy for organisational quality.
When Time Becomes Suspicious
Every process contains different kinds of time. Some of it is pure delay: waiting for an approval that could already have been given, searching for information that should have been available, repeating work because an earlier handover failed. Removing such time improves the process without creating an obvious trade-off.
Other time performs a function.
A difficult decision may require comparison. A diagnosis requires observation. An unusual customer request may need clarification before processing. A complex document may benefit from remaining unfinished long enough for inconsistencies to become visible. Someone taking responsibility for a problem may need a period in which no outward activity is apparent because the relevant work consists of thinking rather than transmitting.
Once speed becomes a quality signal, these different forms of time begin to collapse into one category: delay.
The distinction between unnecessary waiting and necessary duration weakens.
This matters because organisations see some forms of work more easily than others. Sending, forwarding, acknowledging, updating and closing produce visible events. Reflection, verification, reconsideration and waiting for relevant information often do not. When organisational environments become increasingly instrumented through response times, ticket states, dashboards, service levels, timestamps and notification systems, visible movement acquires a structural advantage.
What moves can be measured.
What can be measured can be compared.
What can be compared can become an expectation.
The result is not simply that people work faster. It is that work which does not produce rapid visible movement increasingly requires justification.
The Acceleration of the Wrong Things
The consequences are easiest to miss where every individual action remains defensible.
An employee receives a message and answers immediately, although a better answer would have required information expected later that afternoon. The response is fast, but the issue returns.
A manager decides quickly because several people are waiting. The decision removes the immediate blockage, but creates additional coordination elsewhere because one dependency was not yet understood.
A task is handed over as soon as one stage appears complete. The next person discovers that an unresolved detail has travelled with it.
A customer receives an immediate acknowledgement, followed by several subsequent communications because the first response could not yet resolve the matter.
None of these events necessarily constitutes poor work. Their structural significance appears only when they recur.
Acceleration then produces a paradox. Individual transactions become faster while the overall system accumulates additional loops.
Issues reopen. Questions return. Decisions require correction. Handovers become more frequent. Clarifications multiply. More people are copied into communication because nobody wants to become the point at which movement stops.
The organisation appears highly active.
Its work may nevertheless be travelling through an increasingly complicated structure.
This is where speed and flow begin to diverge.
Speed describes how quickly something moves at a particular point.
Flow describes whether it proceeds through the system without unnecessary interruption, reversal or repetition.
A fast organisation is therefore not necessarily an organisation with good flow. It may simply contain many locally accelerated activities.
Responsiveness as Compensation
Once rapid movement becomes expected, organisations frequently compensate for the difficulties created by that expectation with additional coordination.
More messages keep processes moving. More meetings prevent rapidly made decisions from drifting apart. More status updates provide visibility when numerous activities are running simultaneously. More escalation ensures that blocked work does not remain blocked for long. More dashboards make the resulting complexity observable.
Again, every intervention can be reasonable.
But the compensation has an unintended effect. Because it succeeds in preserving movement, it can prevent the underlying problem from becoming visible.
A system that repeatedly requires urgent coordination may therefore be interpreted as dynamic rather than structurally unstable. A manager who resolves dozens of issues quickly may appear highly effective even when the concentration of those issues around the manager indicates that decisions have migrated away from where they could originally have been made. A team responding continuously to incoming requests may appear responsive while losing the uninterrupted time required to complete work that would reduce those requests.
The organisation does not experience the full cost of its speed expectation because people continuously absorb that cost.
They switch tasks.
They answer between tasks.
They clarify prematurely transferred work.
They remain available.
They compensate.
And because the compensation prevents visible breakdown, the underlying configuration stabilises.
What began as an expectation of faster work gradually becomes a system that requires constant human intervention in order to remain fast.
The Structural Migration of Urgency
Urgency was once associated primarily with particular situations. Something became urgent because delay would have a meaningful consequence.
When speed becomes a general indicator of quality, urgency changes character. It no longer needs to originate in the task itself. It can originate in the architecture surrounding the task.
A notification creates immediacy because it is visible now. A message acquires priority because another person is waiting. A dashboard highlights an unresolved item because the system can measure how long it has remained open. An unanswered request becomes increasingly conspicuous simply because time is accumulating beside it.
The organisation thereby begins to generate urgency independently of substantive importance.
This changes decision architecture.
Tasks that can signal their waiting status acquire an advantage over tasks whose importance develops slowly. Incoming work competes successfully with existing work because the arrival itself is an event. The new becomes structurally louder than the unfinished.
Over time, the distinction between responsiveness and reactivity can become difficult to maintain.
The organisation may still possess priorities formally. But its actual sequence of attention is increasingly determined by which issue can most effectively announce that it is waiting.
Speed has then ceased to be merely temporal. It has become a mechanism for allocating attention.
When Fast Looks Efficient
The attraction of this arrangement is understandable because speed is unusually legible.
Quality often reveals itself late. A robust decision proves its value through what does not subsequently go wrong. A successful handover is largely invisible because no clarification is required. Thoughtful preparation becomes apparent only when later stages proceed without friction. Structural reliability frequently produces an absence of events.
Speed produces evidence immediately.
Something was requested at 09:14 and answered at 09:21.
A ticket was opened and closed.
A decision was requested and made.
A customer received a response.
A project changed status.
The resulting indicators are not meaningless. But they can create a particular asymmetry in organisational perception: the organisation sees velocity more readily than it sees the quality of the architecture through which work moves.
This can lead to an unusual inversion.
Instead of asking whether a process produces good outcomes with appropriate use of time, the organisation begins to infer good organisation from short intervals.
The measurement does not merely describe performance.
It begins to define what performance is presumed to mean.
The Point at Which Speed Became Normal
Once this interpretation becomes established, it ceases to feel like an organisational choice.
A response within hours no longer appears exceptionally fast; a response the following day begins to appear slow. A decision made immediately appears normal; taking time to reconsider can look hesitant. Availability is no longer interpreted as additional responsiveness but as the expected baseline from which absence becomes noticeable.
The reference point has moved.
This is how organisational normality often changes. Not through a dramatic redesign, but through successive reductions in what counts as an acceptable interval.
The individual adjustments remain small enough to appear insignificant. Their cumulative effect is structural.
People do not necessarily notice that the organisation has adopted speed as a value because nobody needs to state the value explicitly. It is embedded in response expectations, escalation thresholds, performance indicators, communication norms and the social interpretation of waiting.
Eventually, speed no longer needs to prove that it improves work.
Slowness has to explain why it should be allowed.
A Different Reading of Fast Work
The structural problem is therefore not that organisations became too fast. Some work genuinely benefits from immediate action, and many processes contain delays that add no value whatsoever.
The more consequential shift occurred when speed stopped being treated as contingent on the function of the work.
A rapid emergency response and a rapid strategic decision may both be fast, but the significance of that speed is entirely different. One may depend on removing delay. The other may require preserving sufficient time for judgement. Treating both through the same temporal logic confuses acceleration with organisational quality.
What looks like an increasingly fast organisation may therefore require a different reconstruction.
Its people may not simply be completing work more quickly. They may be maintaining a system in which visible movement has acquired priority over appropriate duration. The additional communication, coordination, escalation and correction that follow are then not separate inefficiencies surrounding an otherwise efficient organisation.
They may be the compensation required to keep the organisation looking fast.
Speed, in that case, has not eliminated organisational friction.
It has changed where the friction appears.
And what seemed to be evidence of good work may have become one of the structures determining what work is allowed to look like.
Summary
Speed was once one variable among many in organising work. Gradually, however, rapid responses, shorter processing times and immediate availability began to function as visible evidence of organisational quality. The structural consequence was subtle: work was increasingly judged by how quickly activity became visible rather than by whether decisions, handovers and outcomes occurred at the right time. What appeared to be greater efficiency could therefore conceal a growing architecture of interruption, premature decision-making and compensatory coordination.
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 