(a) Critically evaluate the contingency theory of leadership propounded by Fiedler. How is this theory different from situational…

(a)(i) Critical Evaluation of Fiedler’s Contingency Theory

Fred Fiedler’s Contingency Theory posits that organizational performance depends on matching a leader’s orientation with situational favorableness. A leader's style is measured through the Least Preferred Co-worker (LPC) scale, categorizing individuals as either task-motivated (low LPC) or relationship-motivated (high LPC). Situational favorableness is evaluated through three structural variables: leader-member relations (quality of trust and confidence), task structure (degree of procedural clarity), and position power (formal authority to reward or punish). Fiedler demonstrated that low LPC leaders excel in extreme situations—either highly favorable (octants I–III) or highly unfavorable (octants VII–VIII)—whereas high LPC leaders are most effective in situations of moderate favorableness (octants IV–VI).

Critically evaluating the model reveals both profound insights and significant operational limitations. Positively, Fiedler dismantled the classical assumption of a single universal leadership style, establishing that leadership effectiveness is relative to environmental demands. However, his core premise treats leadership style as fixed and personality-driven, implying that leaders cannot adapt their behavior; organizations must instead alter the situation through "job engineering" or replace the manager. Additionally, the LPC construct suffers from low test-retest reliability and ambiguous psychological interpretation, the situational variables are hard to assess in practice, middle-LPC leaders are left unexplained, and meta-analyses (Peters, Hartke and Pohlmann, 1985) support the model mainly in laboratory rather than field studies.

(a)(ii) Fiedler versus Hersey-Blanchard Situational Leadership

In contrast, Paul Hersey and Kenneth Blanchard’s Situational Leadership Model rejects this static paradigm. While Fiedler views style as invariant and focuses on macro-situational control, Hersey and Blanchard emphasize behavioral flexibility tailored to follower readiness (originally called maturity), defined by ability and willingness. Fiedler measures the leader through the LPC score, while Hersey and Blanchard diagnose the follower, and they combine task and relationship behaviour as two separate dimensions rather than one bipolar orientation. Leaders dynamically transition across four styles—Telling (S1), Selling (S2), Participating (S3), and Delegating (S4)—as subordinates advance from low readiness (R1) to high readiness (R4). Thus, whereas Fiedler advocates selecting or engineering the environment to fit the leader, Hersey and Blanchard champion leader adaptability and subordinate development.

(b)(i) Causes of Line-Staff Conflict

Although line and staff functions are inherently complementary—line executives maintaining chain of command for core operations while staff specialists provide technical counsel—inter-group conflict is endemic.

The primary causes of this friction include: Role and Status Ambiguity: Staff specialists frequently feel sidelined as non-authoritative advisers, while line managers view staff as ivory-tower theorists lacking ground-level accountability. Encroachment on Authority: Conflicts escalate when staff bypass formal channels and attempt direct command over operational personnel, diluting unity of command. Jealousy and Demographic Disparities: Staff personnel often possess higher formal education, specialized technical vocabulary, and younger profiles, fostering resentment regarding status and compensation differentials. Credit and Blame Asymmetry: Staff specialists are often perceived as claiming undue credit for operational successes while leaving line executives to bear exclusive blame for implementation failures.

(b)(ii) Suggestions to Minimize the Conflict Clear Delineation of Authority: Formalize operational boundaries via precise job descriptions and responsibility matrices, defining staff authority strictly as advisory, concurrent, or service-oriented. Shared Accountability: Integrate staff specialists into the implementation phase, tying staff performance evaluation directly to line operational results. Institutionalized Collaboration: Establish joint problem-solving committees and cross-functional task forces to foster mutual respect and bridge perceptual divides. Dual Experience Mechanisms: Implement job rotation between line and staff roles (as practiced in conglomerates like Tata Group) to build mutual empathy and realistic operational awareness.

(c) Information Technology and Organizational Structure

The implementation of Information Technology (IT) and organizational structure exist in a dynamic, reciprocal relationship. IT serves not merely as an operational tool but as a structural redesign driver. By automating routine workflows and providing real-time data processing, IT eliminates intermediate data-filtering layers, flattening vertical hierarchies and widening the span of control.

Simultaneously, enterprise networks and Enterprise Resource Planning (ERP) systems reconcile the classical dilemma between centralization and decentralization; they facilitate decentralized operational decision-making at the frontline while maintaining real-time, centralized strategic oversight. Furthermore, advanced communication platforms enable fluid, non-traditional structural arrangements such as virtual teams, project-based matrix designs, and modular network organizations. As environmental volatility demands structural agility, evolving structural needs compel further IT innovations, confirming their dynamic, co-evolutionary interaction.