Chief Marketing Officer / India
The stronger headline gave way to the supported claim
- Marketing employees
- 29
- Four heads; six external creative personnel counted separately
- Annual marketing authority
- ₹6.3 crore
- Company revenue is a separate ₹146 crore measure
- Career since June 2000
- 26 years
- Industrial communications through energy-equipment CMO
Decisions & consequences
01Withdrawing the eighteen-reference steam campaign I had approved
In 2019, while leading application marketing, I approved a campaign that described eighteen installations beneath an industrial-steam proposition. Ten were hot-water applications and eight involved industrial steam. The portfolio list was accurate, but the presentation implied that all eighteen established experience of the more specific application. Engineering head Asha Qevzlari challenged that inference during the release review. I had checked whether the projects existed and overlooked whether the group answered the buyer’s intended comparison.
The commercial team wanted to retain the headline and place the application split in supporting material. The campaign had already consumed design time, and eighteen appeared more reassuring than eight. I rejected that compromise because the qualification would arrive after the principal impression. I withdrew the release I had approved and asked the technical and marketing teams to rebuild the reference account around the actual applications. The decision did not suggest that hot-water projects lacked value; it stopped us borrowing their number to support a different claim.
Management authorised ₹24 lakh and six weeks for the replacement work, including reference descriptions and the related sales explanation. The final account retained all eighteen installations, visibly separated into ten hot-water and eight industrial-steam references. Qualified owners reviewed the relevant application descriptions. No installation was removed from the underlying portfolio, and no claim was made that eight references established suitability for every prospective steam project. Buyers still needed a site-specific technical conversation before any proposed equipment or arrangement could be assessed.
The result was a more precise account of experience, not a measured increase in sales or a finding about universal performance. I told the team that the initial approval failure belonged to me. That mattered because otherwise the correction could have become a lesson about designers including longer captions, while leaving the commercial instinct behind the misleading group unchanged. I now want reference selection to begin with the buyer’s comparison and the scope of the claim, rather than with the largest number the portfolio can supply.
Replacing one partner-map symbol with the actual scope of each relationship
A 2023 review examined thirty-two organisations in our proposed partner directory. Twenty-one had completed training to explain the proposition; eleven had that training and a separate, defined installation authorisation. The initial map used the same symbol and a broad partner label for all thirty-two. A buyer could reasonably read the presentation as an equivalent route to installation support, even though twenty-one organisations did not hold that authority. The directory made a useful commercial network look like a uniform technical capability.
Channel colleagues argued that different labels would create a hierarchy between relationships and make some partners less willing to introduce enquiries. I wanted the directory to represent the relationship we actually had, rather than use ambiguity to preserve the appearance of equality. Asha Qevzlari and the channel owner supplied the scope account. Marketing could explain it, but could not extend an organisation’s authority or certify individual competence. We suspended publication of the common map while the descriptions were rebuilt.
The approved programme used ₹38 lakh over nine weeks for directory changes, partner explanations and the related enquiry routes. The revised account distinguished the twenty-one proposition-trained organisations from the eleven with the additional installation scope. All thirty-two remained represented. The eleven were not described as authorised for every technology, site or future project; their stated limits still governed the route. We also assigned responsibility for updating the directory when a relationship changed, rather than treat the launch review as a permanent certificate.
The outcome was clarity about where an introduction should lead and who could confirm the next step. We did not claim that the change proved safer installations or increased conversion. No adverse physical incident was invented to make the decision appear more dramatic. The commercial issue was already consequential: a buyer should not have to discover the difference between training and authority only after approaching the wrong organisation. I wanted the same standard applied to our own description of the network, even when a more candid map looked less extensive than the original proposition.
Separating completed-work photographs from convincing project renderings
In 2025 we reviewed forty images used in a proposed customer presentation and related web material. Twenty-seven were photographs and thirteen were computer-generated scenes. Nine of the thirteen renderings lacked sufficiently clear status in the reviewed presentation; four were already identified appropriately. The visual finish was consistent enough that a reader could mistake the unlabelled proposals for completed work. The problem concerned what the images established, not whether a rendering was a legitimate way to explain a possible arrangement.
The creative team preferred a general note at the end, arguing that repeated labels would interrupt the presentation. I asked them to consider the point at which the buyer formed an impression of our completed portfolio. A distant note could not reliably travel with an image when a slide or page was viewed separately. I withheld the affected material and requested a source account for every image, with clear status beside the computer-generated scenes. Permissions and customer approvals were checked as separate questions; a correct caption could not substitute for them.
Management approved ₹31 lakh and seven weeks for the revised library and its publication rules. The forty-image set retained twenty-seven photographs and thirteen renderings, with all thirteen clearly identified in the bounded release review. The nine previously ambiguous scenes were corrected. Qualified owners also checked that captions did not imply technical acceptance or performance beyond the material they supported. We did not assert that every historical copy held by a recipient had disappeared, and the revised library was not evidence that the depicted proposals had subsequently been built.
The result gave sales colleagues a more useful way to discuss possibilities without presenting them as accumulated delivery experience. A rendering could remain attractive and informative when its purpose was explicit. My responsibility was to prevent visual consistency from erasing a factual distinction. I asked the team to make status part of the reusable asset, not an optional addition dependent on the memory of the next person assembling a presentation. The correction addressed an avoidable inference before we asked buyers to rely on the images as evidence of our work.