Development Management: Genesis, Rationale, and the Foundations of an Emerging Discipline

1. Genesis: Why Development Management Emerged

Development Management (DM) arises at a junction that neither development studies nor mainstream management fully occupies on its own. Development thinking has traditionally concerned itself with what change is desirable and for whom, while management thinking has concerned itself with how collective effort gets organised and executed. Practitioners working at the frontline of social change have long felt the gap between these two bodies of knowledge: technically competent management that misses the point of the work, or values-driven development thinking with no disciplined way of acting on it.

This gap is not incidental — it is structural. Development goals are normative, contested, and long-term; they resist the stable objectives and predictable cause-effect chains that conventional management tools assume. At the same time, good intentions alone do not build institutions capable of sustaining change at scale. DM emerged, across decades of scattered literature, as an attempt to hold both truths at once: that social change work must be organised with discipline, and that this discipline must itself be reshaped by the ethical and political nature of development.

The intellectual history of development itself helps explain why. Development thinking moved through four broad phases — technocratic planning in the 1950s–80s, people-centred and participatory approaches from the 1980s, a critical and reflexive turn from the early 2000s that questioned managerial neutrality itself, and, from 2015 onward, a systems-oriented view attentive to complexity, ecology, and identity. DM as a field draws on all four phases; it is less a single theory than a synthesis of what practitioners and scholars have learned, often the hard way, about what it takes to manage for social change rather than merely manage development projects.

2. Rationale: Why a Distinct Discipline Is Needed

Three observations make the case for treating DM as a discipline in its own right rather than a subfield of public administration or business management.

First, conventional management assumptions do not hold in development contexts. Most management models assume relatively stable goals, predictable relationships between action and outcome, and a meaningful degree of control over results. Development work typically has none of these. Goals are contested and evolving; outcomes depend on institutional dynamics, community agency, and structural conditions well outside any one organisation's control; and over-reliance on tools, metrics, and standardised approaches can flatten context and quietly reinforce the very power imbalances the work is meant to address.

Second, neutrality is neither possible nor desirable. Public administration has historically claimed a form of institutional neutrality; business management treats financial performance as the central measure of value. DM cannot borrow either premise. Every decision about priorities, resourcing, or measurement advantages some interests over others. A discipline built for development work must therefore treat values and power as part of the management task itself, not as an external constraint on it.

Third, India — and contexts like it — demonstrate the stakes at scale. Because Indian development work sits at the dense intersection of state systems, civil society, markets, and community structures, it makes visible tensions that are present everywhere but easier to ignore elsewhere: centralisation against local autonomy, growth against equity, efficiency against inclusion. A discipline of DM grounded in these realities is more durable than one derived from abstraction alone.

Taken together, these observations argue for a genuine reworking of management — not the import of business tools into the social sector, but a discipline built from the actual conditions under which development happens.

3. Current Thinking: What Development Management Is Becoming

3.1 Three conceptions of what is being managed

Alan Thomas's influential distinction remains a useful entry point: management in development (applying standard organisational practices within development settings), management of development (running interventions, project cycles, and coordination), and management for development (centring dignity, equity, and empowerment as the purpose of management itself). Current thinking treats these not as competing definitions but as layers — most real practice moves across all three, and the discipline's distinct contribution lies in insisting that the third, purpose-centred layer, actively shapes the other two.

3.2 Three axioms anchoring the field

Recent synthesis work — drawing on Thomas, Brinkerhoff and Coston, Chambers, Freire, Sen, Korten, and Schön, among others — converges on three axioms that describe what is distinctive about DM as a form of management:

• Values and power are made explicit. Neutrality is treated as neither possible nor desirable; decisions must surface whose interests are advanced and whose are constrained, and success criteria must include equity and legitimacy alongside efficiency.
• Legitimacy derives from external social consequences, not internal performance. The purpose of the work lies in changes to people's lives, institutions, and environments — organisational efficiency that erodes trust or excludes marginalised groups is a cost, not a saving.
• The work operates through complexity and iterative learning. Plans function as hypotheses rather than fixed commitments; accountability systems need to distinguish between negligence and responsible adaptation.

These axioms are deliberately not prescriptive. They function as orienting commitments that shape judgement under uncertainty, rather than rules that can be applied mechanically — a reflection of the field's underlying premise that development work resists standardised formulas.

3.3 From values to action: the Heart, Head, Hand framing

A recurring difficulty in the literature is the weak bridge between normative commitment and everyday managerial decision-making. Current thinking addresses this through six "action lenses" organised under three faculties: Heart (purpose and justice — holding the line on core purpose, surfacing justice and power in practice), Head (understanding and decision architecture — positioning participation where it can influence decisions, reading the system that sustains the problem), and Hand (execution and learning — strengthening the conditions that carry the work, and making reflection part of everyday management). A weakness in any one faculty produces a recognisable failure mode: weak Heart produces efficient but misdirected work; weak Head produces well-intentioned but naive work; weak Hand produces insightful but unsustainable work.

4. Building the Theory and Discipline of DM

What makes this body of work foundational, rather than simply descriptive, is the discipline it imposes on a previously fragmented field. Four moves are doing the foundational work:

• Naming the field's boundaries. By distinguishing DM from public administration and business management on explicit grounds — non-neutrality, non-financial value, and context-dependence — the field becomes something that can be taught, examined, and built on, rather than an implicit sensibility.
• Converging fragmented literatures into a shared structure. Development studies, public administration, organisational theory, political economy, and systems thinking each offer partial insight; the axiom-and-lens architecture gives these strands a common frame without forcing false consensus.
• Translating norms into managerial design, not just intention. The explicit layering — from normative orientation, to interpretive judgement, to managerial design choices, to everyday operational routines — is what allows values like dignity or participation to show up in decision rights, incentive design, and accountability systems, rather than remaining aspirational language.
• Leaving the open questions visible rather than resolved. The field candidly acknowledges what remains unsettled: no shared theory of change linking management practice to development outcomes, thin guidance on organisational culture and emotional labour, limited engagement with digital and algorithmic systems, and unresolved tensions between scale and local grounding. Naming these gaps is itself a disciplinary act — it defines a research and practice agenda rather than presenting DM as a finished body of knowledge.

This is the sense in which the current synthesis is foundational rather than final. It does not claim to have solved Development Management; it claims to have given the field enough shared architecture — a definition of scope, a set of axioms, a translation mechanism from values to action, and an honest account of its own gaps — that further theory-building, curriculum design, and practitioner training can now proceed cumulatively rather than each starting from first principles. For an institution seeking to build Development Management as a discipline in India, this is the necessary first layer: not a finished theory, but a stable enough foundation for one to be built.