From assembling the packet to questioning its purpose

Mandate

Make preparation workflows support the producer's judgement without assuming editorial or transmission authority

Outcomes

• Corrected a timing view that omitted ordinary programme components
• Separated production notes from presenter-copy exports
• Supported deliberate rehearsal editions alongside live drafts
• Kept original names visible beside optional pronunciation aids

Decisions in context

I became CPO in January 2022 and report to Anil. Twenty-two product colleagues work through three leads within ₹5.4 crore FY 2026–27 expense, including ₹1.7 crore discovery and design work. Tevqari has 116 direct employees and ₹41 crore FY 26 revenue. Riniki leads producer research; engineering, security and legal colleagues retain their respective responsibilities. Our product supports preparation rather than operating a station or controlling transmission. The timing correction required me to acknowledge that I had approved an answer to a smaller question than the producer needed. Other work has made the purposes of presenter copy, rehearsal editions and pronunciation aids more explicit. I hold no equity or statutory seat. A future board contribution would concern the judgements professional tools distribute among their users, with broader preparation in finance, collective duties and the company's actual obligations before any appointment.

Reason for the move

Continuing product leadership while preparing to assess a first board opportunity in professional tools

Mandate

Develop preparation workflows that distinguish a continuing draft from the copy used for a particular production task

Outcomes

• Extended product responsibility across preparation and collaboration
• Examined when a draft becomes an edition someone relies on
• Connected workflow choices with producer research and engineering review

Decisions in context

From September 2016 I led fourteen product colleagues through two leads within ₹2.9 crore annual expense. Tevqari employed eighty-four people and recorded ₹26 crore revenue for FY ending March 2017. I reported to the chief operating officer. Collaboration was becoming a larger part of the workspace, and I began to question whether immediate propagation was useful for every preparation task. A team could keep developing a draft while another person needed continuity for a read-through. The product needed a clear account of those related activities, rather than assume that the most recently edited text was always the right object for everyone. I worked with research and engineering colleagues to understand the practical transitions. The later CPO appointment broadened my accountability from a workflow portfolio to the promises the whole product made, including choices I had previously accepted too readily because they looked simple in a design review.

Reason for the move

Promoted to chief product responsibility

Mandate

Turn recurring preparation difficulties into product choices that producers can understand and use

Outcomes

• Brought producer-service experience into software discovery
• Learned to distinguish a workflow default from a universal user need
• Coordinated research findings with engineering constraints

Decisions in context

I joined Tevqari in June 2010 and moved to Vadodara. The company had forty-nine employees and ₹11 crore revenue for FY ending March 2011. Eight product colleagues worked through two leads within ₹1.1 crore annual expense, reporting through me to the head of product. I wanted to address recurring preparation problems through the workspace rather than ask service colleagues to explain the same distinction repeatedly. Software made that possible, but it also made our assumptions easier to scale. A default that helped one team could make another team's legitimate task awkward. I learned to ask producers and engineers different questions and then connect their answers in a proposition that neither discipline could settle alone. Workflow leadership later gave me responsibility for the relationships among those features, where an apparently small change in one part could alter the meaning of a copy or action elsewhere.

Reason for the move

Appointed to lead the workflow product portfolio

Mandate

Coordinate preparation material around the different responsibilities of producers and presenters

Outcomes

• Clarified the purpose of working documents before handover
• Managed producer-service staffing and the function budget
• Learned to manage revisions without assuming every recipient needed the same copy

Decisions in context

The March 2004 appointment brought responsibility for six colleagues through one lead within ₹44 lakh annual function expense. Lamqeshi had seventy-eight employees and ₹16 crore revenue for FY ending March 2005. I reported to the head of production services and worked with teams whose documents served several purposes at once. A note could help organise an interview without belonging in the presenter's reading copy. A revised script could be necessary without making an unannounced replacement useful to somebody already rehearsing. I learned to ask who would use the material next and what they would reasonably believe about it. Those questions connected preparation with the consequences of a handover. The move to Tevqari offered a way to make the distinctions part of a product, though I would later learn that putting them into software required the same care as explaining them through a service conversation.

Reason for the move

Moved into software product management for programme workspaces

Mandate

Assemble assigned preparation material and resolve routine coordination questions under senior review

Outcomes

• Learned to connect scripts with the running order
• Prepared materials for rehearsal under senior review
• Recognised that a document's purpose depends on its next user

Decisions in context

My first role began in July 1998 after communication studies completed in June. Lamqeshi employed thirty-seven people and reported ₹5.2 crore revenue for FY ending March 1999. I belonged to a four-person coordination group under the senior production coordinator, without reports or spending authority. The work involved scripts, running orders and questions that arrived close to rehearsal. A document could contain all the expected material and still leave someone uncertain about what to read, what to prepare or which change had been accepted. I learned to assemble the pieces with their purpose in mind and to ask a senior colleague when the decision exceeded my role. Producer-services management later widened that responsibility from assigned packets to the way a team coordinated preparation. The early work remains useful because it showed me the task before I had a software feature to fit it into.

Reason for the move

Promoted to manage producer services