From instrument readings to company obligations

Mandate

Build a commercially durable specialist service whose conclusions remain grounded in the work performed.

Outcomes

• Removed raw finding counts from a recognition component after a nine-engagement review
• Funded a thirty-six-person apprenticeship cohort with protected mentoring
• Renegotiated an automated regression engagement around defined scope
• Retained a qualified technical report despite a delayed ₹42 lakh milestone

Decisions in context

Taking the CEO role made me accountable for the company choices that surround technical work. I now lead five executive heads and report to the board on strategy, performance, investment and risk. My executive directorship began with this appointment; it is not an external or non-executive seat. I have concentrated on the relationship between what we sell and what our specialists can substantiate. That includes the incentives used to recognise teams, the cost of developing new colleagues and the commercial terms needed when a better method reduces effort. Directors receive the consequences as well as the rationale. A delayed payment, a lower proposed invoice or protected mentoring time cannot disappear from the account simply because the technical argument is sound. The role requires me to make those choices supportable across the company and remain responsible for their results.

Reason for the move

Current appointment; developing specialist depth and more explicit commercial commitments.

Concurrent appointment

Executive directorship is held alongside the CEO appointment at the same company.

Mandate

Reconcile specialist capability, client commitments and operating capacity across two offices.

Outcomes

• Distinguished skill-ready capacity from nominal staffing availability
• Brought engagement assumptions into joint delivery and commercial planning
• Assigned ownership for operating exceptions crossing office boundaries

Decisions in context

The COO appointment took me beyond the engagements I could know personally. I had to build an operating view that showed whether the company could meet its promises across two offices and a growing mix of clients. Five heads managed the principal operating groups. We examined the skills and review capacity behind the staffing totals, because an available colleague was not necessarily ready for the work being proposed. I also worked with commercial leaders to make assumptions visible before a delivery date was committed. My expense remit was substantial but distinct from the company's total revenue and P&L. I reported to the CEO and had no directorship during this period. The experience prepared me to lead the company by showing where a plausible sales plan could become an unrealistic operating plan unless capability, timing and supervision were considered together.

Reason for the move

Appointed CEO and executive director after the board's succession review.

Mandate

Develop repeatable specialist delivery without confusing a common method with identical client risks.

Outcomes

• Required engagement teams to state the consequential questions before staffing requests
• Made environments and exclusions explicit in delivery plans
• Developed managers who could explain qualified findings to client sponsors

Decisions in context

I joined Belsori to work on testing as a specialist service rather than a supporting stage within one software product. My delivery group grew to seventy-two colleagues, organised through four managers. We needed consistent ways to plan and review work, while recognising that clients faced different consequences from failure. I asked managers to describe the important questions and operating conditions before choosing the size of a team. We also became more explicit about exclusions, so that a narrow engagement did not quietly acquire the expectation of a broad assurance conclusion. I managed a defined operating allocation and escalated scope or commercial conflicts to the COO. This period developed my ability to lead through managers and to explain why useful qualification was part of a service, rather than an embarrassment to be removed from its final report.

Reason for the move

Promoted to COO as the company expanded beyond one delivery centre.

Mandate

Provide usable evidence about retail workflows and the limits of release testing.

Outcomes

• Expanded scenario reviews to interrupted and repeated transaction sequences
• Documented tested conditions alongside findings
• Separated the test team's evidence from the authorised release decision

Decisions in context

Retail software moved my attention from instrument behaviour to the sequences created by people using a system. I led twelve testers and reported to the engineering head. We examined ordinary transactions alongside returns, interruptions and repeated actions, asking where a technically correct component could still produce an unsuitable overall result. The work required close discussion with developers and colleagues who understood client operations. I learnt to present tested conditions and unresolved questions in a form that a release meeting could use. My team did not own the business decision to release, and its completed plan did not establish that every possible use had been examined. After nearly seven years, I wanted to develop this discipline across different client environments. The delivery-head position at Belsori offered that breadth and responsibility for managers as well as individual testers.

Reason for the move

Moved to a specialist testing-services business to lead multiple client engagements.

Mandate

Establish and document instrument performance under specified operating conditions.

Outcomes

• Recorded test setup and operating ranges with results
• Introduced technician review of incomplete or ambiguous test sheets
• Connected unusual findings with repeat investigation before conclusions

Decisions in context

I began work a month after completing my engineering degree. The test bench taught me to ask what a result meant before deciding whether it was reassuring. A reading taken under one condition could not stand for a different operating range simply because it looked precise. I prepared tests, recorded setups and investigated unexpected behaviour with the engineering manager. From 1998 I supervised four technicians, which added responsibility for the clarity of instructions and the review of other people's records. I had no authority over the company's contracts or P&L. The experience gave me a lasting respect for the conditions attached to evidence. It also made me curious about software, where the combinations created by users could be more varied than the conditions on a physical test bench. That interest led to my next appointment in retail-software quality.

Reason for the move

Moved into software quality to investigate the interaction between systems and user behaviour.