From supervised observations to the practice's technical judgement

Mandate

Connect the practice's technical methods, procurement and evidence with the purposes promised in client engagements.

Outcomes

• Retained intermittent-event conditions in a sixty-period study account.
• Funded further work for two of four proposed hall arrangements.
• Declined a platform discount tied to exclusive supplier recommendations.
• Used reversals in model rankings to fund a discriminating investigation.

Decisions in context

I report to Ritu and lead twenty-one colleagues through four leads. The company's ₹41 crore revenue and 128 employees describe the enterprise, while my function expense and equipment provision define a narrower delegated remit. Daniel coordinates qualified project professionals, whose responsibilities are not displaced by the CTO title. My recent decisions concern how the practice defines and communicates the conditions of its advice. They include giving up a lower platform price and retaining uncertainty when model rankings change. My personal holding is 0.04% within the employee allocation; I hold no statutory directorship. Registration in the IICA databank is part of an unfinished preparation process, not evidence that a board role is already secured. I want a prospective nomination committee to understand the professional-practice questions I can contribute and the limits of that experience, including why another enterprise's circumstances need their own examination.

Reason for the move

Current appointment; exploring how the experience could support a first board contribution.

Mandate

Lead the practice's technical approach and explain the evidence supporting its recommendations.

Outcomes

• Approved the absorptive-treatment brief later challenged for its confidentiality claim.
• Accepted ₹24 lakh redesign and further assessment expense.
• Separated a useful internal-room treatment from an unsupported assurance about speech transmission.

Decisions in context

This role gave me responsibility for fourteen colleagues and ₹2.4 crore annual expense in a 106-person company. Its ₹32 crore FY2015 revenue provided commercial context without becoming my personal budget. The 2017 brief correction is the defining example because it concerns a decision I initially approved. I had allowed the legitimate function of an absorptive treatment to stand for a confidentiality result that the proposal had not established. Daniel's challenge required us to reopen the purpose, fund further professional work and explain the change to the client. The lesson was broader than remembering a technical distinction. It concerned the claim carried by an executive approval and the cost of correcting it. I took that experience into the CTO appointment without treating the revised brief as proof that every completed room would satisfy every subsequent use or that the same response should be prescribed elsewhere.

Reason for the move

Promoted to CTO as the practice expanded its methods, technology and procurement responsibilities.

Mandate

Develop consistent technical practice while retaining the purpose and conditions of each assignment.

Outcomes

• Connected measurement programmes with the questions clients intended to resolve.
• Built a continuing methods team within the consultancy.
• Learned to distinguish assignment evidence from a general assurance about a facility.

Decisions in context

Joining Teqzarmi moved me from leading individual projects into a continuing responsibility for the consultancy's methods. I led eight colleagues under the practice director, with ₹1.1 crore annual expense. The company employed ninety-two people and recorded ₹24 crore FY2008 revenue. Its combination of advisory and measurement services made the brief especially important: clients could buy observations without having agreed the question those observations should answer. I worked on connecting the programme with that purpose and explaining the conditions to the receiving team. The experience did not prevent my later premature approval, which is why I retain the distinction between a developing practice and a perfected one. The promotion reflected broader responsibility for recommendations, not a new authority to certify every room or replace the qualified professionals accountable for actual design and acceptance.

Reason for the move

Promoted to technical director with wider responsibility for the practice's recommendations.

Mandate

Coordinate supervised acoustic project work and retain the conditions relevant to interpretation.

Outcomes

• Led a small team across scoped measurement assignments.
• Connected study arrangements with the use described by the client.
• Preserved specialist review for conclusions beyond the team's delegated remit.

Decisions in context

I led five colleagues with ₹54 lakh annual expense in a seventy-eight-person enterprise. The company's ₹16 crore FY2000 revenue was distinct from the resources I controlled. Working under a senior project manager, I learned that a visit captured a particular operating condition rather than the whole life of a building. Changes in use or arrangement could alter the question a client needed answered. My responsibility was to organise the agreed work, preserve the relevant context and obtain professional review of the conclusion. I did not treat the title as permission to make every design or contractual judgement. After more than eight years in this appointment, I wanted to contribute to the methods and explanations that shaped a consultancy over time. The move to Teqzarmi provided that continuing practice responsibility alongside a larger team.

Reason for the move

Joined Teqzarmi to develop a sustained technical practice rather than remain focused on individual assignments.

Mandate

Support supervised observations and prepare an accurate record of the conditions examined.

Outcomes

• Recorded assigned observations under professional supervision.
• Learned to separate an observation from the conclusion a project required.
• Developed practical building-science experience after an electrical engineering degree.

Decisions in context

I joined in July 1992 after completing the full-time electrical engineering degree that May. Vaqzermi employed forty-four people and recorded ₹6 crore FY1993 revenue. I worked under a project engineer, with neither a team reporting to me nor delegated expenditure authority. The assignment was to support observations and prepare an accurate account of their conditions. I learned that a careful record could still require interpretation by someone with the relevant professional responsibility. My degree did not supply every judgement needed for an occupied building, and the early role should not be rewritten as if I already held the authority of a CTO. Nearly seven years of supervised work gave me a practical basis for coordinating a small team. It also established the habit of asking what a conclusion depended on before presenting an observation as a complete answer.

Reason for the move

Promoted to lead a small acoustic project team after supervised field experience.