The scope behind each operating appointment

Mandate

Connect authorised programme instructions with production, quality and downstream delivery work.

Outcomes

• Funded selective retiming and review for seven of eighteen revised versions.
• Preserved source-to-delivery identity for twelve episodes prepared as ten authorised deliveries.
• Kept six withdrawal destinations unresolved pending evidence and held four versions awaiting territorial confirmation.

Decisions in context

The COO appointment brought responsibility for the operating chain rather than one delivery department. I lead 117 colleagues through five leads and report to Leela; Ashwin retains quality leadership, with editorial and rights authority held by the appropriate owners. The ₹24 crore annual operating scope is distinct from the ₹4.5 crore systems programme and from company revenue. My cases show where that division becomes difficult: a small revision can reopen dependent work, a delivery format can conceal an editorial change and a withdrawal account can exceed our downstream control. I have funded review and follow-through while keeping unresolved permission visible. The record does not turn those interventions into audience outcomes or universal delivery performance claims. It describes my operating decisions and the evidence available for them. I hold no statutory directorship and do not treat presenting to directors as equivalent service.

Reason for the move

Current role; a potential future governance contribution remains subject to preparation and assessment.

Mandate

Coordinate delivery preparation and the operating records used across recipient handovers.

Outcomes

• Owned the design weakness in the 2018 midnight release calendar.
• Separated eight explicit timing instructions from four needing written clarification.
• Authorised ₹27 lakh coordination and rescheduling expense while the four entries were held.

Decisions in context

This period is important because the later executive story begins with an error in a process I approved. The midnight calendar appeared to simplify work, but four of twelve entries lacked the date and zone clarity required to identify the intended release instant. I had allowed an incomplete instruction to look settled. We held those four entries, retained the eight clear ones on their agreed path and paid for clarification and rescheduling. No early public release is asserted in this fictional record. I reported to the COO and led seventy-six colleagues, with operating expense of ₹15 crore at the stated scale. The experience changed how I considered a form or status field: it could distribute authority as well as organise tasks. My promotion did not remove responsibility for that earlier design decision or prove that every subsequent process was beyond criticism.

Reason for the move

Promoted to COO with responsibility across the wider programme operating chain.

Mandate

Prepare authorised programme materials for recipients with different delivery arrangements.

Outcomes

• Developed a usable relationship between source programme identity and recipient requirements.
• Escalated ambiguous editorial instructions to their authorised owners.
• Built supervised delivery coordination into a broader departmental remit.

Decisions in context

Joining Veqzatri introduced me to a wider range of recipient arrangements. I managed twenty-seven colleagues within ₹4.6 crore annual operating expense and reported to the operations director. The enterprise's FY2010 scale was 102 employees and ₹35 crore revenue. I learned to distinguish the identity of commissioned material from the way a distributor organised its receiving slots. That did not give me authority to alter a programme's narrative or rights. It required me to make the unresolved editorial question visible and to preserve the answer in a form delivery colleagues could use. The work was departmental and practical: planning, preparation and escalation under a senior operating owner. It established the background for my later episode-combination case without inventing an early board role or claiming that a manager's coordination work determined the creative success of the programmes being prepared.

Reason for the move

Moved into operations direction with responsibility across larger preparation teams.

Mandate

Coordinate the preparation and handover of distinct programme versions.

Outcomes

• Made dependencies between shared programme elements visible in coordination work.
• Retained version-specific instructions through recipient handovers.
• Developed a small-team remit while leaving specialist approvals with their owners.

Decisions in context

My first management responsibilities involved five coordination colleagues and ₹42 lakh annual expense. Zevmalri employed sixty-one people and recorded ₹18 crore FY2004 revenue; I continued to report to an operations manager. Programme versions could share much of their preparation while differing in consequential ways. I learned to ask which instruction and which prepared element belonged to a particular version, rather than assume a common label meant all work could be treated alike. The role required patient coordination with specialists whose judgements I did not replace. It also showed me why a late change could create work outside the single item mentioned in the request. I did not control enterprise capital, hold a statutory seat or approve every release. This was a bounded managerial step, important for the operating questions it taught me to recognise before the later increase in scope.

Reason for the move

Joined Veqzatri to manage a larger delivery department.

Mandate

Support delivery records and preparation under supervision.

Outcomes

• Learned to preserve unresolved instructions for the person able to answer them.
• Supported the identification and checking of requested materials.
• Built practical production understanding following a completed 1997 degree.

Decisions in context

I began in July 1997, after completing my media-production degree that May. The twenty-nine-person enterprise gave me supervised responsibility for delivery records and practical preparation, with no budget or direct reports. My work was to support the delivery supervisor, not decide how the customer should release a programme. I encountered the gap between a familiar file label and the full instruction a recipient needed. Asking for clarification could feel slower than making an assumption, especially when colleagues were busy, but it preserved the authority of the person who could actually answer. The value of this early period was that habit and an understanding of the work around me. It should not be rewritten as enterprise leadership in retrospect. Six years of supervised practice preceded the first small-team role and provided a credible foundation for the later responsibility described in this chronology.

Reason for the move

Progressed to version coordination and a five-person team.