Leadership review
Nirved Kharote
Chief Information Officer · India
Highlights
212
Internal technology employees
Six direct reports; fifty contracted specialists separately
₹128 Cr
Technology authority
FY2026–27: ₹82 crore operations and ₹46 crore change
33 years
Internal systems career
Support, enterprise applications and operations leadership
A letter from the chief information officer
I want the people making a delivery commitment to know which internal records they can rely on and which still require a judgement.
I began my career in July 1993 as a systems analyst at Veyantra Software, after completing a computing degree at Meralvi Institute that June. I was one of nine colleagues supporting internal systems, with no direct reports and no budget of my own. Much of the work involved records that looked mundane beside the software being built for customers: which version had been installed, who had approved a change and how a colleague could resume work after a failed setup. I discovered that a small ambiguity in those records could consume more time than an obvious technical fault.
Nirved Kharote
Chief Information Officer
Strategic priorities
01
02
03
04
Performance
Priority outcome 01
Our internal staffing pilot covered 960 assignment requests across twelve delivery units. The new system could display all the requests in one place, which made the pilot appear ready for wider use. A closer review found that only 720 had consistent project, skill-record and approval references. One hundred and fifty had conflicting start dates, while ninety lacked adequate sponsor authority. I did not interpret the 720 as proof of competence or customer permission; they were simply the requests whose specified records agreed. The delivery sponsor wanted to extend the pilot before the next planning cycle. His concern was reasonable: returning to separate spreadsheets would lose the visibility already gained. My applications lead suggested allowing the disputed requests through with a warning that could be resolved later. I disagreed because the downstream staffing view did not preserve that qualification clearly enough. A named person against a dated project could be taken as an authorised commitment by colleagues who never saw the warning. I held the 240 requests outside the confirmed schedule, accepted a seven-day delay to expansion and committed ₹1.8 crore to review and workflow changes. I asked the operating sponsors to correct the decisions and records; the technology team could not supply missing authority on their behalf. The revised view separated a proposed assignment from a confirmed one and retained the reason for each unresolved request. This created more work for unit leaders at an inconvenient point in the cycle. After six weeks, 205 of the held requests had been corrected and thirty-five remained unresolved. I reported that remainder rather than count the pilot as wholly complete. The programme did not establish that every engineer was ready for the assigned work, and I did not claim an increase in billable utilisation from it. It established a more dependable distinction between a request and the evidence needed to treat it as confirmed. I would make the same choice again, while bringing the downstream users into the initial design earlier so that a warning could not disappear between screens.
Priority outcome 02
The proposal for a common development environment began with 180 client projects and a desire to reduce repeated setup work. My platform team had a convincing technical design, but the initial business case treated every project as a candidate. Delivery reviews identified fifty-four projects with client-specific restrictions that could not simply be replaced by an internal standard. The remaining 126 formed the adoption cohort. I kept the distinction visible rather than classify the excluded projects as a failure of cooperation. Finance questioned whether the programme still justified investment at that scale. The first twelve months would cost ₹8.4 crore, compared with ₹7.1 crore for the previous fragmented arrangement over a comparable period. Transition, parallel support and the continuing exceptions all had a cost. A delivery executive argued that retaining separate environments weakened the point of the programme. I agreed that fragmentation was expensive, but disagreed that my authority extended to removing a condition accepted in a customer engagement. I approved the narrower programme with named sponsors for the fifty-four exceptions and a review date for each category. I gave up the claim of an enterprise-wide standard and the prospect of a first-year saving. My team supplied clear setup guidance for the participating projects while delivery leaders remained accountable for customer permissions. The programme review tracked the participating cohort separately so that faster setup there could not conceal unresolved work elsewhere. Median setup time for the 126 participating projects fell from nine working days to three. That was a useful operational improvement within the measured cohort, not evidence that every developer had gained six productive days or that customer delivery had accelerated by the same amount. The exceptions remained supported and the higher first-year expenditure remained in the report. I learnt that a common platform becomes more credible when its boundary is explicit. The next investment decision could then examine whether particular exceptions could change, rather than start from a fictional assumption that they had already disappeared. I would identify the commercially necessary exceptions before presenting the common-environment economics, so the initial funding discussion includes the cost of supporting a deliberately incomplete consolidation.
Priority outcome 03
I sponsored an eight-week internal code-assistant pilot involving 240 consenting engineers and six representative maintenance tasks. The evaluation used comparable task conditions and recorded both first-draft time and the review and rework that followed. My purpose was to decide where further use justified its cost, not to produce a universal measure of engineering productivity. Security and engineering colleagues agreed the permitted contexts before work began; customer material remained subject to its existing restrictions. The median first-draft time fell from seventy-four to forty-nine minutes. That result attracted immediate attention. The supplier's account team wanted to use it as the central case for a wider purchase, and a business leader asked how quickly the apparent capacity could be reflected in staffing plans. The subsequent review and rework measure rose from twenty-six to forty-three minutes. Across those measured stages, the combined median-based task comparison was one hundred minutes before and ninety-two after. I made clear that this arithmetic was a limited comparison of the reported task-stage measures, not a distributional estimate for every engineer. I retained the ₹75 lakh pilot expenditure, including training, and proposed restricted continuation for the tasks whose evidence supported it. I declined to annualise the first-draft improvement into an equivalent number of employees. That reduced the apparent scale of the business case and postponed the larger supplier commitment. The engineering sponsor supported continuation but asked for better guidance on what reviewers should examine, because a plausible draft could demand a different kind of attention from an obviously incomplete one. The result was neither an enterprise rollout nor a rejection of assistance. It was a bounded next step with a more honest account of the work. I would improve a future study by retaining paired task-level observations through the full workflow, rather than relying mainly on stage summaries. I would also examine later defects and maintenance burden before discussing broader economics. A useful internal CIO should be able to preserve a modest benefit without turning it into a staffing promise the evidence cannot support.
Priority outcome 04
An acquired application's support team brought 1,260 user accounts into an integration programme. The commercial transaction had its own legal completion date. My responsibility was the separate operating question of which accounts should continue with which permissions in the receiving organisation. An administrative transfer could copy the accounts quickly, but it could not establish that every previous permission still matched an authorised responsibility. I asked for that distinction to be recorded before the migration schedule was described as a single completed task. The integration office wanted the account work aligned with its financial close checklist. The acquired team's manager worried that a blanket restriction would prevent colleagues supporting existing customers. My initial technical proposal had leaned towards a rapid uniform transfer, and the discussion exposed its weakness. I changed the plan to require a named business sponsor for permissions that could not yet be mapped confidently. I did not claim that an unexplained account had been misused or that an incident had occurred. The review mapped 910 accounts to authorised new responsibilities. Another 220 continued under time-limited arrangements with named sponsors, while 130 were disabled pending explanation. I approved ₹62 lakh for the review and clean-up, and the access work finished four weeks later than the administrative date finance had wanted. That did not delay the legal acquisition close. It required the integration report to carry an incomplete operational item after the transaction itself had completed. I accepted the additional support burden and required a route for legitimate users to obtain review, rather than treat a disabled account as proof that access was unnecessary. The value of the work lay in a more explicit permission decision and a visible temporary population. I would not describe it as eliminating access risk. In future integrations I would ask for responsibility mapping earlier, alongside the systems inventory, so that the receiving business can make these decisions before the pressure of a single closing date encourages unlike obligations to be treated as one.
Priority outcome 05
Our annual shared compute and tooling pool was ₹18 crore. Finance needed a more useful account of its relationship to project economics, and delivery leaders wanted to understand charges that appeared against their units. The initial records supported ₹12.6 crore of project attribution and ₹3.6 crore of shared platform capacity. The remaining ₹1.8 crore could not be assigned reliably. A proportional allocation would have made the schedule add up neatly, but it would have hidden the fact that the underlying records were incomplete. The finance partner proposed distributing the remainder using a consistent usage proxy. That was a defensible management convention if labelled as such. My objection was to presenting the resulting project numbers as directly observed consumption. A delivery leader also wanted the unclassified amount removed from his unit's discussion altogether. I disagreed with both extremes: incomplete attribution did not make the cost disappear, and a formula did not turn an estimate into evidence. I published the three categories separately and funded improvements to the project references behind the unclassified portion. Finance retained authority over the accounting and commercial treatment. My team supplied the technology records, the known gaps and the effect of any proposed allocation convention. I gave up the simplicity of a fully distributed schedule, and the monthly review had to spend time on a remainder that would otherwise have been hidden within apparently precise project totals. Three months later, better records supported assigning ₹1.1 crore of the original unclassified amount. The remaining ₹0.7 crore continued as shared cost pending stronger evidence. This was a change in understanding, not ₹1.1 crore of savings or cash released. It did not establish project profitability without labour, contract and other commercial costs. The lesson for me was that transparency about an unresolved category can improve a financial conversation more than a detailed table that suppresses it. I would retain the distinction even where management chooses a practical allocation rule for its own planning. I would ask project owners to define the evidence needed for cost classification before integration begins, reducing the later temptation to allocate unexplained expenditure merely because a detailed report is expected.
Stakeholder voices
Nirved kept the conditions behind the platform proposal visible when a simpler presentation would have been easier to approve. That helped us distinguish a useful narrower investment from the larger promise we had not yet earned.
He asked my team to own the assignment decision while taking responsibility for how the system represented it. The discussion became more practical once neither side could treat a completed screen as the answer to the other's question.
Outlook
Developer-tool studies need to follow review, rework and the use of any released time before their results enter staffing or commercial plans.
Read the essayStandardisation can reduce repeated work while costing more during transition. Its case becomes stronger when client restrictions and exception costs remain visible.
Read the essayA technology-services enterprise needs clear boundaries between the systems that support delivery and the people authorised to make its commitments.
Read the essayAn invitation
I welcome conversations about internal CIO responsibilities, responsible use of developer tools and a carefully assessed external board contribution. My present executive duties continue; any appointment would require consent, conflict review and an agreed time commitment.
office@nirvedkharote.example