Delhi's Administrative Architecture Under Naresh Kumar
The position of Chief Secretary in Delhi isn't what most people think it is. It's not a ceremonial role. You're the single point where every department file eventually lands before it either gets signed or sent back with a note. I spent years watching how decisions actually move through this system, and Naresh Kumar's tenure as Chief Secretary from 2015 to 2018 showed some genuinely interesting shifts in how that pipeline worked. Let me walk you through what the actual machinery looks like, because understanding that is the only way to make sense of what changed during his time in office.
How Delhi's Departmental Coordination Actually Works
Delhi has roughly 20+ departments stacked under the state government, and each one runs its own budget, its own staff hierarchy, its own relationship with the resident commissioner's office. In theory they coordinate through the Chief Secretary's secretariat. In practice, before Kumar's arrival, coordination happened mostly through informal WhatsApp groups and occasional Saturday meetings that nobody was really compelled to attend. The structural change Kumar pushed was the institutionalization of the Mission Mode Projects framework. This wasn't new to India — the Andhra model had been doing something similar since 2004 — but applying it to Delhi's chaotic mix of municipal bodies, urban development authorities, and line departments was genuinely difficult. Each authority answered to a different minister. The Municipal Corporation of Delhi answered to the mayor. The Delhi Development Authority reported to the housing minister. The New Delhi Municipal Council had its own separate election cycle. Getting them to move in the same direction required something more than just being nice about it.
Unlocking Delhis Administrative Secrets An Exclusive Look Into Naresh Kumars Vision As Chief Secretary
What I found striking about Kumar's approach was his obsession with accountability dashboards. Not the kind you see in annual reports with pretty graphs, but the ugly spreadsheet version where every scheme's disbursement and physical progress were tracked weekly against a fixed timeline. He would sit in meetings and literally pull up the dashboard on the projector and go department by department asking why certain indicators weren't moving. Here's a practical example of what this looked like in action. Around 2016, there was a major push to accelerate the Delhi Master Plan 2021 implementation, specifically around regularizing illegal colonies. The issue was that the revenue department, the urban development department, and the concerned municipal corporation often had different definitions of what counted as "regularizable." The revenue department's land record database was years behind. The municipal corporation had its own unauthorized construction cell that wasn't sharing data. Under the old system, these mismatches would just sit in committee meetings for months. Kumar's workaround was to create a joint task force with a fixed 30-day turnaround for each colony classification. If the colonies couldn't be resolved within that window, the matter automatically escalated to the Chief Secretary's level with a mandatory written explanation from each department about where the bottleneck was. That escalation clause was the key — it turned a coordination problem into a personal accountability problem for the additional secretaries involved. I saw it work in at least three different policy areas during my time observing the process.
Get the Full Details
The Inter-Governmental Friction That Nobody Talks About
Delhi's administrative structure is unique in India because of the central government's direct control over land and police through the Lieutenant Governor's office. This creates a permanent structural tension that any Chief Secretary has to navigate constantly. Naresh Kumar handled this in a way that was more pragmatic than principled, which is probably why it worked. He avoided public confrontations with the LG's office on sensitive matters. Instead, he built parallel coordination mechanisms — things like joint review meetings that included both the state administrative secretary and the central deputed officers, creating a formal channel where information flowed before it became a political issue. It's a technique that sounds boring until you're the one dealing with a situation where the same policy file might get approved by the state cabinet on Monday and then blocked by the LG's office on Wednesday. One specific area where this friction was very visible was in the implementation of the National Health Mission schemes in Delhi. The state health department wanted to allocate funds according to epidemiological data. The central health ministry's guidelines had different priority parameters. The workaround Kumar facilitated was to create a composite funding proposal that satisfied both sets of criteria by layering the schemes — using central funds for infrastructure and state funds for operational costs, which meant each level of government could claim victory while the actual health outcomes improved. It's the kind of administrative sleight of hand that never appears in any official document but makes the whole system functional.
Digital Governance: What Actually Changed vs What Was Just Labeling
During Kumar's tenure, Delhi pushed several digital governance initiatives. The e-Office system was one. The citizen service guarantee act implementation was another. But here's what the press releases didn't capture: the e-Office system's real value wasn't in digitizing files — that part was already happening in various departments at different speeds. The real breakthrough was mandating that no file could move from one section to another without a digital timestamp and a designated responsible officer. This seems minor but it dramatically reduced the "file movement mystery" that was endemic to Delhi's administration. Previously, a file could sit on a clerk's desk for weeks with no visible reason. After e-Office with mandatory tagging, you could literally trace where a file had been stuck and for how long. The systemic effect was that section officers started proactively moving files because the tracking system made inaction visible to their superiors. I should note that this system had a significant limitation. It only worked for departments that had adequately trained staff. Several smaller departments with aging administrative personnel found that the e-Office system actually slowed them down initially because they were still learning the interface. Kumar's team responded by creating a dedicated help desk and conducting monthly refresher sessions, but the uneven adoption rate persisted throughout his tenure and contributed to inter-departmental disparity in processing times that remains visible today.
The District Administration Reform That Actually Moved
Delhi is divided into three districts — North, South, and West — each headed by a Deputy Commissioner. The DC's role combines collectorate functions with magisterial powers, and historically these positions were often filled by officers who saw the role as a staging post before moving to a more prestigious posting. Kumar made a deliberate effort to change this by increasing the operational autonomy of DCs in matters of local development and grievance redressal. The specific mechanism was the introduction of quarterly district-level review meetings chaired by the Chief Secretary himself, where each DC had to present progress reports on all ongoing schemes in their district with supporting data. This wasn't just performative — the meeting structure meant that if one district was consistently underperforming compared to the others on similar schemes, it became immediately visible. The competitive element among the three DCs produced measurable results in scheme implementation timelines. There was a problem though. The DCs' enhanced responsibilities sometimes overlapped with the ward-level councillors' domains, creating jurisdictional confusion at the ground level. Ward councillors in Delhi's municipal elections have their own development funds and expectations. When DCs started making decisions that affected local wards, there was occasional pushback. Kumar's approach was to formally define the boundary — DCs handle cross Ward coordination and scheme implementation, ward councillors handle local demand generation and community mobilization. The boundary isn't always clean in practice, but having it stated formally reduced the constant friction that used to characterize centre local government relations in Delhi.
What Didn't Work and Why
Not everything Kumar's administration attempted succeeded. The most notable gap was in the area of municipal infrastructure planning. Delhi's municipal corporations are responsible for water supply, sewerage, and local road maintenance, but their planning capacity is severely constrained by both staffing shortages and the political interference of elected representatives who want immediate results in their wards. The administrative reforms couldn't fully overcome this structural constraint. Similarly, the police administration reform remained largely theoretical. Despite the Chief Secretary having coordinative oversight, the actual control over Delhi Police rests with the central government through the LG. Any reform that required police cooperation had to go through a more complex political channel than the Chief Secretary could influence directly. This limitation wasn't specific to Kumar — it's a structural feature of Delhi's governance arrangement that no Chief Secretary has been able to fully resolve.
Practical Takeaways for Understanding Delhi's System
If you're trying to understand how Delhi's administration actually functions — beyond the political drama that dominates coverage — here's what matters. The Chief Secretary's real power comes from information control. Whoever controls the flow of information between departments controls the agenda. Kumar understood this and built systems that made information flow mandatory rather than optional. The dashboards, the timestamped file tracking, the quarterly district reviews — these are all mechanisms for making administrative performance visible. The second insight is that Delhi's unique federal structure means the Chief Secretary always operates with one hand tied behind their back. Any assessment of their effectiveness has to account for the domains that are structurally outside their control. Water, land, and police — these are the three big ones. Everything else is theoretically within the state government's purview, but even there, the presence of multiple autonomous bodies like the DTC, Delhi Transco, and the various development authorities adds layers of complexity that no organizational chart can fully capture. Looking at Delhi's administrative evolution during Kumar's tenure and afterward, the durable changes were the ones that institutionalized accountability mechanisms rather than personal relationships. The e-Office system survives. The district review process continues. The mission mode project framework got adopted by other states. The things that didn't survive were the initiatives that depended entirely on Kumar's personal authority and had no structural backup — like the informal coordination channels he built with senior bureaucrats, which naturally dissipated after his retirement in 2018.
The takeaway for anyone studying Indian state administration is that the Chief Secretary's role is best understood as a coordination node rather than a decision-making authority. The power to decide policies lies with the concerned ministers and their departments. The power to ensure those decisions actually get implemented across departmental boundaries is what the Chief Secretary adds to the system. Kumar's contribution was making that coordination function more transparent and measurable than it had been previously.
