From explaining the market to owning the recommendation

Mandate

Compare growth routes with the capabilities, relationships and service arrangements each would require.

Outcomes

• Recommended preserving the service position instead of launching a separate parts brand.
• Supported a bounded two-year capability-development route with unfinished stages visible.
• Revised a universal centre proposal around work that remained at customer sites.
• Separated monitoring and periodic-assessment choices in a diagnostic-service trial.

Decisions in context

I lead twenty-two strategy colleagues through four leads and work with four external advisers counted separately. The ₹4.8 crore function expense is distinct from the ₹23 crore proposal portfolio, whose commitments require separate authorisation. The employer's 420 people and ₹236 crore revenue describe the whole service and parts enterprise. I report to Sudhir, with no personal equity or statutory seat. My remit is to clarify the organisation and relationships each growth route would require, rather than approve repairs or customer-site work. The cases retain qualified technical, commercial, financial and capital owners. They also retain what the selected routes did not provide immediately. A future outside role would need employer, relationship and capacity review alongside my unfinished assessment preparation. The provisional twenty-four-day estimate is an opening for that discussion, not evidence of a commitment already made.

Reason for the move

Current appointment; considering a first outside contribution after specific preparation and review.

Mandate

Translate growth choices into workable organisational arrangements while preserving the relevant technical and commercial responsibilities.

Outcomes

• Supported a central quotation route after an acquired-workshop integration.
• Accepted responsibility for insufficient specialist input in that route.
• Recommended local technical review with bounded commercial delegation after examining the quotations.

Decisions in context

The director title described a functional employment responsibility; it did not confer a statutory appointment. I led fourteen colleagues with ₹2.9 crore annual expense in a business then employing 285 people. In 2016 I supported centralising quotation work after a ₹18 crore workshop purchase. Forty-two reviewed proposals included sixteen requiring specialist treatment, twelve of which had returned for reassessment. Farida's challenge made me reconsider the arrangement I had helped approve. Restoring local technical review and bounded commercial authority cost ₹61 lakh including ₹14 lakh customer credits. I did not treat that correction as proof that the acquisition itself had failed. The experience changed how I examined the organisation a strategic recommendation requires, without removing the commercial team's valid concern about consistency. It remains an owned error in the later CSO account, rather than a problem attributed only to implementation colleagues.

Reason for the move

Appointed CSO as the enterprise needed a broader account of its growth routes and capabilities.

Concurrent appointment

Functional director designation only; no statutory seat or concurrent board appointment.

Mandate

Connect market choices with the service capabilities and relationships needed by the operating enterprise.

Outcomes

• Moved from external industrial research into an operating company's planning function.
• Examined how equipment-maker relationships affected routes to new work.
• Developed closer planning discussions with service-engineering and commercial owners.

Decisions in context

Joining Reqvathi brought responsibility for nine colleagues and ₹1.4 crore annual function expense. The enterprise had 180 employees and ₹74 crore FY2008 revenue, a different scale from the current company. I moved from delivering research to participating in the decisions that followed it. A new service route could change workshop priorities or the way an equipment maker regarded us. I needed to understand those consequences with people who owned the work, not simply add a market estimate to a growth paper. Reporting to the commercial director helped connect the analysis with actual relationships while leaving contract and technical authority where it belonged. The appointment developed my interest in the organisation behind a strategy. It did not make every later design sound, as the integration case would show, but it gave me a closer view of what a recommendation asked colleagues to deliver.

Reason for the move

Promoted to the wider business-design role as growth required more explicit organisational choices.

Mandate

Develop decision-relevant industrial research with its definitions, limits and participation requirements visible.

Outcomes

• Took responsibility for a research team and its expenditure.
• Examined what a client would need to participate in a proposed market.
• Developed interest in the operational consequences of recommendations.

Decisions in context

The promotion gave me six colleagues and ₹60 lakh annual expenditure. The employer's ninety-six employees and ₹28 crore revenue were separate measures of scale. I became responsible for the account a client received, including the assumptions behind a market description. Two services could share a category while depending on different access, knowledge or commercial arrangements. I wanted those distinctions to remain visible when a client considered participation. The work was still research rather than management of the client's business, and I did not claim responsibility for every later decision. Over time I became more interested in the organisation required to deliver a recommendation. Moving to Reqvathi offered a way to work with those consequences directly, in a defined service setting where technical and commercial colleagues could challenge an attractive market account against the actual work.

Reason for the move

Joined an equipment-services enterprise to work closer to the choices and consequences following the research.

Mandate

Gather and interpret industrial evidence while distinguishing the categories that materially changed a client's question.

Outcomes

• Learned to examine what broad service categories concealed.
• Supported research under supervision without client operating authority.
• Built the analytical foundation for later research-team responsibility.

Decisions in context

I began in July 1994, following the master's degree completed in June. The forty-six-person firm recorded ₹8 crore FY1995 revenue, while my own position carried neither a budget nor staff responsibility. I gathered evidence under a research manager and learned to question the boundaries of an apparently familiar market. A maintenance activity could depend on knowledge or access that did not appear in a broad category total. My work was to make such distinctions visible for the supervising team, not to approve a client's strategy or technical work. The early experience explains the analytical starting point of the career without assigning executive authority to it. Later responsibility would add people, expenditure and ownership of recommendations. It would also require a willingness to correct an arrangement that my own reasoning had helped make persuasive.

Reason for the move

Promoted to research manager after sustained industrial-analysis work.