Learning the service behind the recorded event

Mandate

Make operational evidence appropriate to its decision, timing and permitted use

Outcomes

• Stopped a prediction rollout using post-journey knowledge
• Brought the slower tail into a capacity-planning review
• Reopened cancellation categories and withheld a revealing granular report

Decisions in context

I became CDO in February 2021, leading 28 colleagues through four heads with ₹6.6 crore annual expense and separate ₹2.2 crore approved capital. I report to Anup; Sonal leads operations. The enterprise employs 620 people, operates 180 vehicles and serves 22 hospital contracts, with ₹210 crore revenue and ₹17 crore operating profit for FY 2026. I hold 2% of total equity within the employee owners' 20%. Recent decisions address prediction inputs, journey-time variation, cancellation reasons and revealing report detail. My remit is to make evidence usable for the decisions it can support. It does not give me authority over clinical suitability or treatment, and it does not make analytical corrections proof of an achieved service benefit. Those distinctions remain part of how I explain the role and its results.

Reason for the move

Current CDO remit, with no statutory appointment

Mandate

Develop the enterprise data account across operational planning and customer reporting

Outcomes

• Expanded responsibility beyond planning analytics
• Owned an approved report that excluded eighty unserved bookings
• Corrected the full-cohort account without claiming a punctuality improvement

Decisions in context

I became head of data in April 2017, leading twenty colleagues through three leads with ₹4.7 crore annual expense under the CEO. The company had 410 employees and ₹132 crore revenue for FY 2018. In 2018 I approved a report showing 884 on-time journeys among 920 completed, while eighty unserved bookings were outside the calculation. We corrected the full one-thousand-booking account to show 88.4% on time, with 36 late and eighty unserved separately visible. The ₹34 lakh reporting rebuild did not change any historical journey's timing. I accepted responsibility for allowing the narrower measure to stand for a wider service claim. The experience changed how I reviewed the relationship between a calculation, its population and the conclusion a customer would take from the page.

Reason for the move

Promoted to chief data officer in February 2021

Mandate

Connect transport records with the practical questions of service planning

Outcomes

• Moved from general transit analysis into planned patient transport
• Built collaboration with operating colleagues around event meaning
• Kept operational analysis separate from professional clinical decisions

Decisions in context

I joined Tazqeshi in July 2012. The enterprise employed 220 people and recorded ₹64 crore revenue for FY 2013. I led twelve analysts through two leads with ₹2.8 crore annual expense, reporting to the COO. The move required me to understand the records behind planned transport under hospital arrangements, including what a booking status could and could not explain. I worked with operating colleagues to connect those records with planning decisions instead of assuming that a familiar statistical measure carried the same meaning in every setting. The service did not provide emergency response or treatment. Qualified care teams retained clinical suitability decisions, and my analytical remit did not replace them. This period established the operating context I needed before taking responsibility for the enterprise's wider data account.

Reason for the move

Appointed head of data in April 2017

Mandate

Lead analysis that preserves the timing and meaning of operational records

Outcomes

• Took responsibility for people and analytical expenditure
• Developed review of event definitions across a team's work
• Learned to explain evidential limits to operating colleagues

Decisions in context

I became data lead in May 2008. Qerzumi had one hundred employees and ₹24 crore revenue for FY 2009. I led eight colleagues through two leads with ₹1.4 crore annual expense under the analytics director. The role made me responsible for how a team interpreted records, not simply the calculations I produced myself. I learned to ask when a field became available and whether a broad category preserved the distinctions needed for its proposed use. Explaining those questions to operating colleagues was as important as recognising them in an analysis. My authority covered the team's work and expenditure within its remit, rather than the whole company's decisions. The experience prepared me for a planning-analytics role closer to the ongoing delivery of a specific transport service.

Reason for the move

Joined Tazqeshi as head of planning analytics in July 2012

Mandate

Support transit analysis by understanding the events behind the records

Outcomes

• Applied statistics study to operational evidence
• Learned how event definitions shape an analytical account
• Built experience without people-management or spending authority

Decisions in context

I joined Qerzumi in July 2003 after completing my statistics degree in June. The company employed 45 people and recorded ₹7.2 crore revenue for FY ending March 2004. I worked in a six-person analytics group under the analytics manager, with no direct reports or delegated spending authority. I learned that a dataset needed an account of the work that produced it before its patterns could be explained confidently. Two rows with the same status could arise from different events, and a completed record could contain knowledge unavailable earlier in the process. My work was analytical support rather than ownership of client operations. This early experience gave me a foundation in interpreting service evidence, while later leadership roles would test how consistently I could apply that discipline to reports I approved.

Reason for the move

Promoted to data lead in May 2008