Academic Reading Articles Practice 17 Test 04

A
The rise of large-scale industry in the nineteenth and early twentieth centuries created an organisational problem that small workshops had rarely faced: how to coordinate hundreds or thousands of workers, machines and materials with predictable results. Railways, mines and factories required timetables, standard operating routines and clear reporting lines, because informal supervision could not keep pace with the speed and scale of production. Management therefore emerged as a distinct activity—separate from ownership or craft expertise—concerned with imposing order on complex work. Early theorists tended to assume that efficiency could be designed into the system through planning, measurement and control, even if the human experience of work was treated as secondary.

B
The most influential early approach was classical management, which tried to convert work into an optimisable sequence of tasks. Frederick Winslow Taylor’s scientific management proposed that productivity could be raised by studying each job in detail, timing movements, eliminating “waste,” and then prescribing the one best method. In this view, managers were responsible for analysis and method design, while workers were trained to execute the standardised procedure. At the organisational level, Max Weber’s account of bureaucracy provided a complementary logic: a hierarchical structure with formal roles, written rules and impersonal authority was seen as the most reliable way to scale decision-making and ensure accountability. Together, Taylor and Weber helped normalise standardisation, specialisation and top-down coordination, but they also attracted criticism for treating workers as interchangeable units and for ignoring motivational and social realities.

C
By the 1930s, purely mechanical assumptions were increasingly questioned. The human relations movement argued that productivity could not be explained by pay and procedure alone, because work occurred within a social environment shaped by interpersonal dynamics, informal leadership and group expectations. The Hawthorne Studies, associated with Elton Mayo and colleagues, became emblematic of this shift. Although later scholars debated the interpretation of the findings, the broader message entered management thinking: feelings of recognition, participation and belonging can affect effort, cooperation and resistance. From this perspective, a workplace is not merely a technical system but also a social system, and managers who ignore morale and communication may unintentionally create conflict or reduce performance. Critics, however, noted that “caring” management could become paternalistic if it was used primarily as a technique for compliance rather than genuine well-being.

D
Later in the twentieth century, a more holistic vocabulary emerged from systems theory and contingency thinking. Instead of searching for universal rules, systems theorists described organisations as open systems that exchange information, resources and constraints with their environment—markets, regulations, technologies and cultural expectations. Outcomes depend not only on internal design but also on external shocks and feedback loops. Contingency theorists extended this idea by arguing that what works in one setting may fail in another: a rigid hierarchy may suit stable, routine production, while a more flexible structure may be better for uncertain tasks or fast-changing industries. Management, in this framework, becomes an adaptive activity—diagnosing context, monitoring signals and adjusting structures rather than applying a single formula.

E
From the 1970s onward, strategic management became a dominant theme as competition intensified and firms looked beyond internal efficiency to long-term positioning. Managers were urged to analyse industry structure, anticipate rivals, differentiate offerings and allocate resources to build sustainable advantage. At the same time, quality management and continuous improvement reframed performance as a learning problem. Approaches influenced by Japanese manufacturing emphasised reducing defects, understanding process variation and empowering front-line workers to identify problems. Although strategy and quality developed in different intellectual traditions, both encouraged managers to think in longer time horizons: success was increasingly defined by capability building, not merely by short-term output.

F
In many contemporary sectors, the growth of knowledge work and digital tools has further reshaped managerial assumptions. Where value depends on creativity, collaboration and rapid problem-solving, strict standardisation can become counterproductive. This helps explain the appeal of flatter structures, cross-functional teams and iterative “agile” methods that break complex projects into shorter cycles with frequent feedback. Yet critics argue that agility can become a slogan rather than a genuine redesign: organisations may keep traditional control systems—fixed targets, rigid approvals and punitive reporting—while using the language of flexibility. When this occurs, employees experience “pseudo-empowerment,” in which responsibility is decentralised but authority remains centralised, producing frustration rather than speed.

G
In the most recent debates, management thought increasingly includes ethical and sustainability considerations that extend beyond productivity and profit. Decisions about supply chains, automation, data collection, surveillance and environmental impact can impose costs on communities and future generations, not only on employees or shareholders. This has encouraged “stakeholder” approaches that evaluate organisational success more broadly—through resilience, fairness, well-being and long-term ecological constraints. Taken together, the history of management ideas suggests a recurring tension between efficiency and humanity, and a recurring lesson: no single model fits every organisation or era. Effective management is therefore best understood as the careful matching of methods to the nature of work, the surrounding environment and the needs of people.

Distributed teams—groups that collaborate across geography and, increasingly, across time zones—have shifted from an exception to a normal feature of organisational life. Yet the change is not simply logistical. When colleagues cannot rely on co-presence, many of the cues that once supported coordination and trust become unreliable: a manager cannot “see” effort, overhear emerging problems, or repair misunderstandings in a corridor conversation. As a consequence, leadership in distributed settings often replaces presence-based supervision with deliberate systems that make work legible and relationships sustainable.

A recurring difficulty is that communication channels vary in their capacity to carry nuance. Media Richness Theory proposes that “richer” media—those that allow immediate feedback, multiple cues, and a personal focus—are better suited to ambiguous or emotionally charged issues than lean media such as text. In a distributed team, however, text-based tools dominate because they are searchable, asynchronous, and scalable. The implication is not that text is inferior, but that leaders must match channel to task: complex conflict, sensitive feedback, or high-stakes negotiation may require synchronous conversation, while routine updates are often better handled through written records.

Time-zone separation intensifies this problem by forcing a choice between speed and inclusion. If decisions happen only when a critical mass is online, those outside the dominant time window may become structurally peripheral, receiving outcomes rather than shaping them. Many teams respond by adopting an asynchronous-first workflow: proposals are drafted in shared documents, updates are recorded, and decisions are documented so that progress continues while others sleep. This shift can make collaboration more equitable, but it also raises the cognitive demands of reading, interpreting, and responding to written material without immediate clarification.

That cognitive load becomes visible when roles, handovers, and ownership are vague. In co-located settings, ambiguity can sometimes be repaired informally; in distributed work it often produces duplicated effort, stalled tasks, or “phantom accountability” where everyone assumes someone else is responsible. High-performing teams therefore externalise thinking: they use templates for project briefs, standardise handover notes, and maintain decision logs that record what was decided, why, and by whom. The purpose is not bureaucracy for its own sake, but a shared memory that reduces confusion and prevents the same debates from recurring.

Trust formation also changes under distance. In many studies of team effectiveness, trust is linked to perceived competence, reliability, and goodwill. Remote colleagues rarely observe effort directly, so reliability is inferred from outputs, responsiveness, and follow-through. Leaders can support this by setting explicit goals, clarifying what “done” means, and recognising contributions in ways that are visible to the whole team. When work is documented and progress is auditable, the team can avoid a surveillance mentality while still making performance intelligible.

A subtler risk is proximity bias: the unconscious tendency to value, promote, or trust those who are physically closer—or, in hybrid arrangements, those who share the dominant office or time zone. Proximity bias can operate even when leaders believe they are being fair, because familiarity and informal access shape perceptions of competence. In distributed teams, this can translate into unequal opportunities to influence decisions, receive mentoring, or be assigned high-visibility work. Countermeasures are structural: rotate meeting times, write down decision criteria, distribute “ownership” of important projects across locations, and ensure that recognition is tied to outcomes rather than to online visibility.

Culture and belonging likewise require intentional design. In offices, identity forms through informal talk and unplanned contact; remotely, newcomers may struggle to infer norms and may hesitate to ask questions in public channels. However, “culture-building” can backfire when it becomes forced socialising that privileges particular personalities, languages, or caregiving situations. More durable approaches include predictable check-ins, mentorship pairing, and lightweight rituals that respect boundaries, while also creating psychological safety for disagreement.

Finally, well-being is not peripheral to performance in distributed work. The same technologies that enable flexibility can blur boundaries, encouraging an “always-on” norm—especially when colleagues are active around the clock. The idea of a Right to Disconnect has therefore gained attention as a policy principle: employees should not be implicitly required to respond outside agreed hours. Leaders can operationalise this by setting response-time norms, distinguishing urgent from non-urgent channels, and modelling healthy behaviour. Over time, sustainable productivity depends less on constant availability than on clear expectations and recoverable workloads.

Overall, distributed teams succeed when coordination is made explicit and fairness is engineered into systems. The central shift is from managing by observation to managing by design: selecting appropriate media for different tasks, protecting against proximity bias, reducing cognitive load through documentation, and evaluating people by deliverables rather than digital noise. When these conditions are met, distributed teams can combine diverse expertise and offer resilience; when they are ignored, distance can amplify misalignment, isolation, and invisible inequality.

Innovation is frequently narrated through a romantic lens: the lone inventor, the sudden insight, the heroic entrepreneur. This “Great Man” account is culturally convenient because it offers a clear protagonist and a tidy causal story. Yet it obscures a more uncomfortable reality. In organisations, novelty rarely arrives as a finished product authored by a single mind; it emerges from institutional conditions—funding rules, information flows, tolerance for uncertainty, and the mundane routines that decide which ideas receive oxygen and which quietly suffocate. In this sense, innovation is less a personality trait than a property of a system.

The system view becomes clearer when one considers the paradoxes organisations must manage. The very practices that make a firm reliable—standardisation, risk controls, predictable incentives—can also make it hostile to experimentation. At the same time, unchecked experimentation can degrade reliability and produce costly chaos. Scholars have described this tension as organisational ambidexterity: the capacity to exploit existing assets efficiently while simultaneously exploring uncertain possibilities that may disrupt current business models. The difficulty is not recognising that both are necessary; it is designing arrangements in which exploration is not perpetually postponed by the urgent demands of exploitation.

Psychological safety, a concept strongly associated with Amy Edmondson’s work on team learning, is often presented as a foundation for exploration. In psychologically safe teams, individuals believe that voicing doubt, reporting near-misses, and challenging assumptions will not trigger humiliation or punishment. This matters for innovation because early ideas are typically partial and socially fragile. If people learn that “being wrong” carries reputational danger, they will protect themselves by offering only safe observations and incremental suggestions. However, Edmondson’s argument is frequently misunderstood as a plea for comfort. Psychological safety is not the removal of standards; it is the removal of interpersonal penalty for engaging with uncertainty.

Safety, nevertheless, does not substitute for discipline. Many organisations become skilled at producing the theatre of innovation—hackathons, idea portals, brainstorming rituals—while leaving intact the bottlenecks that determine whether experimentation can mature into a scalable solution. Employees may generate lively prototypes, yet lack access to data, cannot obtain time from overloaded calendars, or are blocked by territorial boundaries between departments. The result is frustration disguised as creativity. In ambidextrous terms, exploration is symbolically celebrated while structurally starved.

Incentive architecture further reveals how ambidexterity can collapse. When rewards focus narrowly on short-term delivery, individuals learn that uncertainty is career risk. They respond rationally by avoiding projects whose payoffs are distant, whose outcomes are difficult to measure, or whose probability of failure is non-trivial. Conversely, if novelty itself is rewarded—“most innovative demo,” “best idea,” “fastest prototype”—the organisation may inflate creativity without producing impact. Teams become fluent in producing impressive artefacts that do not integrate with operations, compliance, or customer reality. Innovation then becomes a sequence of non-scalable experiments rather than a mechanism for durable improvement.

One common operational obstacle is the economics of attention. Meetings, urgent requests, and perpetual “alignment” can consume the time required for deep exploration. This is not simply a scheduling problem; it reflects a governance choice about what counts as legitimate work. Some firms attempt to protect exploratory time through internal grants, sanctioned slack periods, or rotating sprints that legitimise investigation rather than forcing it into evenings and weekends. Yet protected time must also be accompanied by an evaluative pathway—criteria for deciding when to invest further, when to stop, and how to harvest learning even from unsuccessful trials.

At this point, the conversation about failure becomes decisive. Contemporary innovation talk often romanticises failure as evidence of courage, but organisations cannot afford indiscriminate loss. A more precise notion is intelligent failure: small, bounded, information-rich experiments conducted in domains of genuine uncertainty, designed to test assumptions quickly and to generate learning. Intelligent failure contrasts with preventable failure, where the organisation repeats known mistakes, ignores available evidence, or allows avoidable errors to reach customers because safeguards were neglected. The ethical distinction is significant: celebrating preventable failure is a form of negligence; analysing intelligent failure is a form of stewardship.

Ultimately, an innovative culture is built through institutional design rather than motivational slogans. It requires an ambidextrous settlement: enough reliability to protect stakeholders, and enough exploration to prevent stagnation. Psychological safety allows inconvenient information to surface early, yet it must be paired with accountability so that candour produces action rather than endless debate. The goal is not to worship novelty, nor to punish risk, but to create routines in which learning is cheaper than silence and improvement is valued more than performance theatre.