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

(a) Critically evaluate the contingency theory of leadership propounded by Fiedler. How is this theory different from situational leadership theory propounded by Paul Hersey and Kenneth Blanchard? (10+10=20 marks) (b) Despite the complementary and supplementary relationship of line and staff, why is there a conflict between them? Give sound suggestions to minimize this conflict. (10+10=20 marks) (c) "The implementation of information technology produces change in organizational structure as their relationship is dynamic." Explain in brief. (10 marks)

हिंदी में प्रश्न पढ़ें

(a) फिडलर द्वारा प्रतिपादित नेतृत्व के आकस्मिकता सिद्धांत का आलोचनात्मक मूल्यांकन कीजिए। यह सिद्धांत पॉल हर्सी तथा केनिथ ब्लैंचर्ड द्वारा प्रतिपादित स्थितिपरक नेतृत्व सिद्धांत से किस प्रकार भिन्न है? (10+10=20 अंक) (b) रेखा एवं सहायक (लाइन एंड स्टाफ) में पूरक तथा अनुपूरक सम्बन्ध होने के बावजूद उनमें संघर्ष क्यों होता है? इस संघर्ष को न्यूनतम करने हेतु ठोस सुझाव दीजिए। (10+10=20 अंक) (c) "सूचना प्रौद्योगिकी का कार्यान्वयन संगठनात्मक ढाँचे में परिवर्तन उत्पन्न करता है क्योंकि उनका सम्बन्ध गतात्मक है।" संक्षेप में समझाइए। (10 अंक)

Evaluate your answer to this question → See all 2022 Commerce & Accountancy questions

Directive word: Critically evaluate

This question asks you to critically evaluate. The directive word signals the depth of analysis expected, the structure of your answer, and the weight of evidence you must bring.

See our UPSC directive words guide for a full breakdown of how to respond to each command word.

How this answer will be evaluated

Approach

The directive 'critically evaluate' in part (a) demands balanced assessment with strengths, limitations and comparative analysis; parts (b) and (c) require 'explain' and analytical exposition. Allocate approximately 40% of time/words to part (a) given its 20 marks and dual demand (evaluation + comparison), 35% to part (b) for conflict analysis and practical suggestions, and 25% to part (c) for IT-structure dynamics. Structure with a brief integrated introduction, three clearly demarcated sections for each sub-part, and a synthesizing conclusion on organizational adaptability.

Key points expected

Part (a): Fiedler's LPC scale, three situational variables (leader-member relations, task structure, position power), and the leadership effectiveness contingency model with its 'match' principle
Part (a): Clear differentiation between Fiedler's fixed leadership style assumption versus Hersey-Blanchard's flexible, developmental approach based on follower readiness levels
Part (b): Root causes of line-staff conflict—status ambiguity, role conflict, jealousy over expertise, differential rewards, and encroachment on authority
Part (b): Practical suggestions including clear role definition, mutual respect building, joint problem-solving committees, and integrating staff into decision-making
Part (c): IT impact on organizational structure—flattening hierarchies, decentralization, virtual teams, and the dynamic reciprocal relationship between technology and structure

Evaluation rubric

Dimension	Weight	Max marks	Excellent	Average	Poor
Demand-directive understanding	20%	10	Demonstrates precise grasp of 'critically evaluate' for (a) by presenting Fiedler's theory with balanced critique (validity of LPC, cultural bias, cognitive resource theory extension) before systematic comparison; for (b) addresses both 'why' and 'suggestions' equally; for (c) captures bidirectional IT-structure causality	Describes theories adequately but critique remains superficial or one-sided; comparison in (a) becomes list-like; suggestions in (b) generic without organizational context; treats IT impact in (c) as unidirectional	Misinterprets directives—describes instead of evaluates, omits comparison entirely, or fails to provide suggestions; confuses Fiedler with other contingency theorists like House
Content depth & accuracy	20%	10	Accurately details Fiedler's eight situational combinations and octant analysis; correctly identifies Hersey-Blanchard's four leadership styles (telling, selling, participating, delegating) and four readiness levels; explains line-staff distinction with Barnard/Simon authority concepts; cites specific IT impacts (ERP, AI, remote work) on structural variables	Basic accuracy on major concepts but errors in specifics (e.g., conflating LPC with behavioral theories); oversimplifies line-staff dynamics; generic IT references without structural specificity	Fundamental conceptual errors—misidentifies Fiedler's variables, confuses situational with contingency theory, or describes line-staff as identical to functional authority; irrelevant or outdated IT examples
Structure & flow	20%	10	Clear tripartite structure with visible sub-headings (a), (b), (c); logical internal progression in (a) from theory exposition → critical evaluation → systematic comparison; in (b) from diagnosis → causes → remedies; in (c) from thesis → mechanisms → implications; smooth transitions between parts	Identifiable structure but uneven weighting—overlong on (a) at expense of (c), or merges (b)'s two components confusingly; paragraphs functional but transitions mechanical	Undifferentiated mass of text without part demarcation; illogical sequencing (e.g., suggestions before causes in b); repetitive or circular argumentation; missing introduction or conclusion
Examples / case-law / data	20%	10	For (a): cites empirical studies (Chemers 1997 meta-analysis, Ayman et al. 1995) or Indian context applicability; for (b): references specific Indian organizational experiences (PSU line-staff tensions, ITC's matrix experiments) or classical cases (Mayo/Hawthorne for authority patterns); for (c): concrete examples (Infosys's flat structure, TCS's virtual delivery centers, or startup platform organizations)	Generic international examples (GE under Welch for leadership, IBM for IT) without Indian specificity; examples mentioned but not elaborated or linked to theoretical point	No examples or irrelevant ones; fabricated case studies; examples contradict the theory being illustrated
Conclusion & analytical edge	20%	10	Synthesizes across parts to argue that effective organizational design requires contingent leadership-fit, harmonious line-staff relations, and adaptive IT integration—positioning these as interconnected elements of dynamic capability; offers original insight (e.g., Fiedler's relevance in VUCA contexts, or AI's challenge to traditional line-staff boundaries)	Summarizes each part separately without cross-integration; restates main points without advancing argument; predictable conclusion on 'importance of good management'	Absent or abrupt conclusion; introduces entirely new concepts in conclusion; contradictory final position; purely descriptive ending without evalative or forward-looking element

Practice this exact question

Write your answer, then get a detailed evaluation from our AI trained on UPSC's answer-writing standards. Free first evaluation — no signup needed to start.

Evaluate my answer →