Harmeet Zerqemvi

A leadership monograph

Harmeet Zerqemvi

Design the promise around the actual task

Portrait of Harmeet Zerqemvi

Chief Product Officer · India · Volume I · 2026

Design the promise around the actual task

I lead product at Nerqavli Inspection Lighting in Udaipur, with assembly in Kota. We make portable rechargeable task lamps for ordinary non-hazardous industrial workspaces. The company employs 390 people and recorded ₹164 crore revenue and ₹13.4 crore operating profit for FY ending March 2026. Twenty-one product colleagues work through three heads within a ₹7.2 crore annual programme budget. Engineering director Nikhil Tevqami retains technical, safety and release decisions.

My work begins where the specification meets an ordinary task. A runtime belongs to a mode and test condition. A mounting option needs a suitable place to attach. A lamp passed between colleagues carries a setting the next person must understand. A brighter range does not automatically answer every kind of inspection question, and a repair promise must describe the work qualified service teams can actually perform.

In 2018 I approved an eight-hour runtime headline derived from low mode while the main use image showed high-mode work. Under the defined test conditions, high-mode runtime was 3.2 hours. Twelve of thirty reviewed customer jobs needed six hours in that mode. We withdrew the unqualified headline and spent ₹37 lakh on repositioning and field-material repair. The account concerns a product promise I allowed to become misleading; it does not invent a battery defect or recall.

One base could not describe the placement choices customers needed

A study of forty nonferrous workstations found twenty-six needed an assessed clamp option and fourteen a bench stand. We funded a ₹1.1 crore programme and retained two bounded choices rather than present the magnetic base as universal. Actual attachment suitability remained with qualified owners.

The next user needed to understand the inherited mode

In thirty-six prototype handover tasks, fourteen users misread the retained brightness setting after restart. A ₹68 lakh physical-indicator programme made mode visibility part of the product work. The reviewed account contains no accident claim or assertion that every future misunderstanding was eliminated.

Repairability was a qualified service outcome, not a promise for every return

A service pilot received forty-eight lamps. Thirty underwent lens-only repair and returned to service after qualified acceptance; eighteen required further housing or electrical assessment. The ₹56 lakh programme did not establish that every lamp was repairable or a measured environmental saving.

Current focus

Making the task-lighting range easier to choose and understand through mode-specific promises, assessed placement options and clear handover state. Application differences and qualified service scope should shape the proposition before a simple feature count decides it.

Conversations I welcome

A first outside board contribution where product judgement can complement financial, operating and technical perspectives. My present responsibility is executive product leadership, with neither a statutory appointment nor a personal shareholding. Fictional IICA preparation has not yet reached registration, and twenty-one provisional days depend on employer consent, relationship review and the actual demands of an appointment.

Chapter I

Preface

Eight hours was the number I had approved. It came from low-mode testing, while the main product image showed work in high mode. Under the defined conditions, the high-mode runtime was 3.2 hours. When we examined thirty customer jobs, twelve needed six hours in that mode. The figure was not a battery defect. The product story had allowed the reader to combine a duration and a use condition that did not belong together.

We withdrew the unqualified headline in 2018 and spent ₹37 lakh on repositioning and field-material repair. I was the group product manager who had approved the account. I did not want the correction presented as a matter of adding small print after marketing had finished. Product leadership had to explain the proposition a customer could reasonably understand, and my approval had not kept the mode beside the promise.

I grew up in Amritsar and completed a design degree at the fictional Selvquri Design College in May 2004. That July I joined Zhevqani Product Works as a product designer. The company employed seventy-five people and recorded ₹16 crore revenue for FY ending March 2005. I worked among seven designers without direct reports or spending authority. The work taught me to follow an object into the task it was intended to support, rather than judge it only in the setting where it was presented.

In July 2009 I became product manager. Zhevqani then employed 170 people and recorded ₹48 crore revenue for FY ending March 2010. I led six colleagues within ₹82 lakh annual budget under the product director. I became more involved in the choices that shaped the offer: which use to prioritise, what the customer needed to understand and how to work with specialists whose approval the product required. A clear proposition depended on those relationships as much as on the design itself.

I joined Nerqavli in September 2015 as group product manager. The manufacturer employed 240 people and recorded ₹91 crore revenue for FY ending March 2016. Ten colleagues worked through two leads within a ₹2.9 crore programme budget under the head of product. Portable task lighting appeared easy to explain through brightness and duration. The runtime mistake during this appointment showed me how quickly a simple specification could become an implied promise about a different task.

I became head of product in April 2020. The company had 310 employees and ₹127 crore revenue for FY ending March 2021; I led fifteen colleagues through three leads within ₹4.8 crore annual budget under the CEO. A study of forty nonferrous workstations brought placement into the range discussion. Twenty-six needed a clamp option and fourteen a bench stand. Retaining two assessed choices was less simple to describe than a universal base, but it was more faithful to the settings we had examined.

Since January 2023 I have served as CPO. Twenty-one colleagues now work through three heads within ₹7.2 crore annual product-programme budget. CEO Asha Vezhqumi owns executive direction, and Nikhil Tevqami retains engineering, safety and release authority. Founders own 58%, a regional industrial fund 32% and employees 10%; I have no personal shares or statutory appointment. My product decisions do not replace technical acceptance or commercial authority over orders.

Recent work has examined what a user inherits during a handover and what different inspection tasks require from the range. Fourteen of thirty-six prototype handover users misread a retained brightness setting after restart. A separate study of twenty-eight teams distinguished nineteen colour-comparison needs from nine geometry-and-shadow tasks. We developed bounded propositions rather than assume a brightness-only hierarchy answered both groups. The work did not certify defect detection or make the product suitable for hazardous, medical or emergency settings.

A qualified service pilot brought another boundary into view. Of forty-eight returned lamps, thirty received lens-only repairs and returned to service after acceptance; eighteen needed further housing or electrical assessment. I wanted the service account to preserve both groups. Repairability should describe the supported route and the decisions of qualified people, not invite a customer to assume every return can be repaired in the same way.

I have no statutory board role. In this fictional profile, IICA preparation remains before registration, with no assessment pass or exemption claimed. I provisionally allow twenty-one days for a first external appointment, subject to employer and relationship review. After twenty-two years in design and product work, I would bring a habit of connecting the promise with the actual task. I would also need to learn the receiving enterprise beyond product and contribute to collective judgement without becoming another executive approver.

Chapter II

A Philosophy of Leadership

I want the person using a lamp to recognise the product we described before the order. That means explaining which mode produced a runtime, how the light can be placed, what state the next user inherits and which service work is actually supported. I once approved an eight-hour headline whose context belonged to a different mode from the work pictured beside it. The product account must keep those conditions together.

Harmeet Zerqemvi

Chapter III

Areas of Practice

  1. IMode-specific product propositions
  2. IIPlacement choices grounded in the workspace
  3. IIIUnderstandable handover and application choice
  4. IVQualified service scope in the product offer

Chapter IV

Selected Work

§ 1

Withdrawing the eight-hour headline I had detached from its operating mode

In 2018 I approved an eight-hour runtime headline derived from low-mode testing. The main use image beside it showed high-mode work. Under the defined test conditions, high-mode runtime was 3.2 hours. A review of thirty customer jobs found twelve needing six hours in that mode. The presentation encouraged a combination of duration and task that the evidence did not support.

We withdrew the unqualified headline and spent ₹37 lakh on repositioning and field-material repair. The case does not describe a battery defect, a recall or an invented customer loss. It describes the meaning of the product offer I had approved. The low-mode result could remain useful if presented with its actual condition; it could not stand unqualified for the high-mode task illustrated beside it.

I worked with engineering and commercial colleagues to rebuild the account around mode and intended use. Engineering retained testing, safety and release decisions. Product leadership had to make the proposition intelligible before a customer relied on the main impression. A later qualification was not an adequate substitute for that coherence.

The twelve jobs did not establish that every customer needed six high-mode hours. They showed a material need within the reviewed group that the broad headline could mislead. Other jobs could have different requirements, and runtime would still depend on defined conditions rather than become a universal assurance.

The outcome was a narrower, more accurate proposition and an explicit correction cost. I retain my approval in the story because the error was not merely a graphic designer's placement choice. I had allowed the product's most attractive duration to travel away from the mode that produced it. The case changed how I review the relationship between a specification, an image and the task the customer is being invited to imagine.

§ 2

Keeping two assessed placement choices instead of a universal-base story

A 2022 study examined forty nonferrous workstations where customers wanted portable task lighting. Twenty-six needed an assessed clamp option and fourteen needed a bench stand. The magnetic base alone could not serve the settings we had observed. A simpler universal-base story would have made the range easier to present while leaving the placement question unresolved.

We funded a ₹1.1 crore programme and retained two bounded options. My recommendation concerned the product proposition and the customer situations it would address. Qualified engineering owners retained attachment suitability, safety and release decisions. The programme did not certify a clamp for every surface or invite users to improvise a mounting arrangement.

The study changed what we treated as central to the offer. Placement was not a minor accessory decision after the lamp had already been chosen. It affected whether the customer could position the light appropriately for the task. A feature that worked in the demonstration setting could not be assumed to travel unchanged into every workstation.

I worked with commercial colleagues to explain the two choices without presenting either as universally superior. The twenty-six and fourteen counts described this reviewed population, not the entire industrial market. A customer outside those settings would still require assessment rather than a forced fit into the nearest option.

The reviewed outcome is a programme and a clearer range choice, not a measured improvement in every customer's work. It also retains the cost of complexity: the enterprise had more than one placement proposition to explain and support. I considered that preferable to a simpler claim whose apparent universality depended on overlooking the environment in which the product would actually be used.

§ 3

Making the retained mode visible to the colleague who used the lamp next

In 2023 we followed thirty-six prototype handover tasks. Fourteen users misread the brightness setting retained after restart. The product remembered a state, but the next person did not necessarily understand the state being inherited. The finding concerned the interaction between product behaviour and the user's interpretation, not simply whether the prototype could store a setting.

We funded a ₹68 lakh physical-mode-indicator programme. Engineering director Nikhil Tevqami retained control design, safety assessment and release authority. My role was to make the handover problem a product priority and ensure that the proposition accounted for the person arriving after the original user.

I did not want the response reduced to telling users to remember more. A portable product can move between colleagues and tasks. The account needed to examine how its current mode would be understood in that ordinary transition. At the same time, the study did not establish that a particular indicator would remove every misunderstanding. The revised work still required assessment.

The fourteen observations came from the defined prototype tasks. The case claims no accident, actual operating loss or universal rate of user error. It also does not provide instructions for modifying a lamp or overriding its controls. Responsible technical owners remained involved in deciding what the product could properly do.

The outcome was a funded design direction with the handover condition made explicit. I use the case to show why product leadership should examine the sequence around a feature, including the next person and the next task. A retained setting can be useful, but its value depends partly on whether the person using the product can recognise it. The feature's existence alone did not settle that experience.

§ 4

Separating colour-comparison and geometry tasks before ranking the range by brightness

A 2024 application study involved twenty-eight teams. Nineteen needed to compare colour-related appearance, while nine focused on geometry and shadow in their work. A brightness-only hierarchy would have put the range on one simple ladder. The study suggested that the product question should first distinguish the tasks customers were trying to perform.

We funded a ₹1.6 crore programme for two bounded application propositions. The decision did not establish universal colour accuracy, reliable defect detection or suitability for any regulated inspection process. Technical owners retained the assessment of optical performance and intended use. Our lamps remained within ordinary non-hazardous industrial settings, without medical, emergency or explosion-proof claims.

My contribution was to keep the task distinction inside the range discussion. More output could be relevant without being the only feature through which a customer should choose. A person comparing appearance and a person examining shape may need different questions answered before selecting a product. The product account should make those questions visible rather than imply that moving up a brightness tier resolves every need.

The nineteen and nine counts described the studied teams. They did not establish a permanent market segmentation or prove that the two groups never had overlapping work. The propositions would need to remain bounded by evidence and be revised if further learning challenged the initial account.

The reviewed result was a funded direction and a more task-specific way to explain the range. It contains no invented quality improvement or customer productivity gain. I wanted the enterprise to understand why it was carrying more than one proposition and which evidence each required. A clear range should simplify the customer's decision by preserving relevant differences, not by making every difference disappear behind one headline specification.

§ 5

Returning thirty lamps through a qualified repair route while retaining eighteen for further assessment

A 2025 qualified-service pilot received forty-eight lamps. Thirty underwent lens-only repair and returned to service after qualified acceptance. Eighteen required further housing or electrical assessment. The programme cost ₹56 lakh. I wanted the product's service proposition to describe that actual route and preserve the group whose outcome remained unresolved.

The pilot showed that a lens-only intervention could be appropriate for the thirty accepted units. It did not establish that every returned lamp was repairable in the same way or that customers should undertake the work themselves. Authorised specialists retained diagnosis, repair and return-to-service decisions. No procedural repair instructions are offered in this profile.

My responsibility was to connect the ownership experience with the capability the enterprise could support. A customer should understand what happens when a product needs attention, including assessment and the possibility that the required work is different from the simplest available repair. The existence of a service option should not become a universal lifetime promise.

I kept the eighteen units in the account instead of reporting only the thirty successful returns to service. Their further assessment mattered to the scope of the offer. The programme also did not establish a measured carbon benefit, financial saving or extended life for every lamp. Those claims would need their own evidence beyond the repair count.

The reviewed outcome includes completed qualified repairs and unfinished work. That combination is useful for product judgement. It shows an ownership proposition becoming concrete without making it broader than the demonstrated capability. I would rather explain the supported service route and its remaining limits than let the attractive word repairable imply that the customer no longer needs qualified assessment or that every future case will end the same way.

Chapter V

Essays

An invitation

Contact

A first outside board contribution where product judgement can complement financial, operating and technical perspectives. My present responsibility is executive product leadership, with neither a statutory appointment nor a personal shareholding. Fictional IICA preparation has not yet reached registration, and twenty-one provisional days depend on employer consent, relationship review and the actual demands of an appointment.

Open to
  • Board appointments
  • Advisory roles
  • Speaking invitations

office@harmeetzerqemvi.example