Taking responsibility for what the record allows

Mandate

Make enterprise information preserve the professional decisions, service definitions and commercial relationships behind commissioned work

Outcomes

• Replaced latest-upload selection with an approved script-to-cut relationship
• Connected caption-service status with qualified acceptance
• Bounded text-delivery claims to tested environments
• Corrected a report that repeated commission fees across language versions

Decisions in context

I became CIO in March 2022 and report to Farhan. My twenty-five colleagues work through three leads within ₹4.8 crore FY 2026–27 expense and a separate ₹1.9 crore change programme. Dazqeni has 190 direct employees and ₹74 crore FY 26 service fees, with external performers and freelance practitioners counted separately. Anjali and qualified language, accessibility, commercial and rights owners retain professional acceptance and permissions. My responsibility is to make the enterprise systems carry those decisions accurately. The work has included correcting a latest-file rule I approved and a report that multiplied contract values across deliverable records. I hold no statutory seat or equity interest. A potential external contribution would concern information integrity and professional responsibility, with preparation in the whole enterprise and a clear understanding that board oversight differs from running another company's technology function.

Reason for the move

Current information-leadership role; preparing to assess a first board opportunity

Mandate

Support working environments and enterprise records without removing the meaning of professional distinctions

Outcomes

• Connected technology acceptance with the intended working environment
• Examined the service meaning carried by shared status fields
• Developed enterprise support and investment responsibility

Decisions in context

The January 2017 appointment widened my remit from business applications to enterprise IT. Dazqeni employed 132 people and recorded ₹43 crore service fees for FY ending March 2018. Twenty colleagues worked through three leads within ₹3.2 crore annual expense. I became responsible for the working environments and support arrangements around the application record, as well as investment choices about how they should develop. That work made me attentive to differences a common system could conceal. A track label might mean different things to different users, while a stored text sequence might require further examination when displayed elsewhere. I wanted the responsible practitioners involved before a technical milestone became a broad service claim. The CIO appointment extended that responsibility into the enterprise's management account and the professional and commercial decisions carried by its information.

Reason for the move

Promoted to CIO

Mandate

Connect the application record with the decisions language and production professionals need to make

Outcomes

• Established clearer relationships between working material and commissioned jobs
• Supported professional review without substituting a technical status for it
• Learned how service definitions affect workflow and reporting

Decisions in context

I joined Dazqeni in June 2010 to lead fourteen technology colleagues through two leads with ₹1.7 crore annual expense. The company had seventy-two direct employees and ₹18 crore service fees for FY ending March 2011. Language services placed applications beside practitioners who needed to understand timing, performance, audience and the purpose of a commission. A technically complete record could still omit something they needed to decide. I learned to ask for that context rather than assume the application's field list defined the whole job. Production and language owners retained acceptance, while my team supported the record and its movement through the enterprise. The later IT role gave me responsibility for more of the surrounding environment, including the conditions under which people encountered the material and the support required when a shared technical route did not serve every task equally well.

Reason for the move

Appointed head of IT

Mandate

Make application changes and support decisions understandable to the business owners who rely on them

Outcomes

• Coordinated business explanations with application changes
• Examined the assumptions behind defaults and automatic selections
• Developed responsibility for team support and delegated expense

Decisions in context

From March 2004 I managed twelve colleagues through two leads within ₹72 lakh annual function expense. Tazqoli had 118 employees and ₹29 crore revenue for FY ending March 2005. The role required me to organise support and changes while explaining how the application represented the customer's work. I became interested in defaults because they often made a useful process faster while hiding an assumption about the meaning of a record. The developer implementing a rule was not always the person entitled to settle that assumption. I worked with business owners to make the required decision clearer before treating a technically valid change as ready. Moving to Dazqeni offered a continuing enterprise responsibility, where I could see how those choices affected professional work after a project delivery date had passed and the system had become part of ordinary operations.

Reason for the move

Moved to enterprise-side language-service systems

Mandate

Support assigned application work while understanding the business purpose of the record

Outcomes

• Investigated user questions about apparently complete records
• Learned to connect field values with their intended business meaning
• Delivered assigned work under senior technical supervision

Decisions in context

I began at Tazqoli in July 1998 after finishing computer science the previous month. The firm had fifty-four employees and ₹9 crore revenue for FY ending March 1999. I was a contributor in a seven-person applications group, with no direct reports or spending authority. Senior colleagues supervised my work, and business users supplied much of my practical education. They could explain why a valid field still failed to answer the question somebody needed to act on. That experience encouraged me to follow the purpose of the record before proposing how it should be changed. Application management later widened my responsibility to the people and support arrangements behind those changes. I chose that progression because I wanted to make the connection between technical implementation and business understanding more dependable, rather than treat a successful application response as the end of the enquiry.

Reason for the move

Promoted to application management