Impact As The Main Transformation Metric
Vikas Verma, CEO & MD of Zimetrics, founded the company with one promise: Bringing ideas to reality, fast.
gettyHype cycles have a familiar shape. I saw this when big data went from a buzzword to the baseline for decision-making, and again when cloud-native went from an architecture debate to the default way of building software. Each time, the industry filled with noise about the technology itself: what it could do, how fast it was moving, who had adopted it first.
We are living through another one of those moments now. But the noise is not what makes this shift different. What makes it different is that, for the first time, intelligence itself has been commoditized. The capability that once separated one technology partner from another is now available, in some form, to everyone.
To be fair, the shift is real. As per a GitHub Accenture study, timelines that once took weeks now take days. Work that once required a team of specialists can now be handled by a fraction of that team, with the right augmentation. Clients have come to expect this the same way they once expected offshore delivery models or cloud-native architecture: not as an advantage, but as the baseline.
That is precisely the problem. A baseline is not a differentiator. It is simply the cost of remaining in the conversation.
What commoditized intelligence has not changed is judgment: the ability to know which problem is actually worth solving for a specific client, in their specific context. Accountability has not changed, either: the willingness to stand behind an outcome rather than a deliverable. No model, however capable, decides on its own which risk matters most to a client’s business.
For decades, our industry has measured itself on things that are easy to count: hours logged, tickets closed, projects delivered on time and on budget. These were always proxies. They persisted because they were simple to report, not because they were what clients actually cared about. Now that raw capability is no longer scarce, the excuse for hiding behind these proxies has quietly disappeared.
This is why I believe impact, not transformation in the abstract sense we have used the word for years, must become the metric that matters. And to use that word precisely, I think transformation deserves a stricter definition than the industry has generally given it: an irreversible change for the better. If a client’s business looks the same six months after an engagement ends, or if the gains fade the moment the vendor leaves, that was delivery. It was not transformation.
Here is what I have learned watching teams try, and sometimes fail, to create real impact: it is never found in a statement of work. You find it by becoming part of a client’s process, not a vendor observing from the outside. It requires genuine dialogue and a depth of familiarity with the client’s ecosystem, their operations, their day-to-day reality, that goes well beyond the brief.
That depth is what allows a team to surface a problem the client had not asked us to solve, sometimes one they had not even recognized as a problem.
Which brings me to a question I get asked often, usually early in a client relationship: Who decides what the impact metrics should be? The client, or us?
My honest answer is that if you ask this question too early, you will only get poor answers. You can’t negotiate impact metrics in a kick-off meeting. They have to be earned by first understanding the client’s world deeply enough to know what actually will matter to them.
We work with a medical device client whose engineering teams develop surgical systems used in some of the most precision-critical procedures in medicine. Our initial mandate was conventional software engineering and delivery. But by working closely with their clinical objectives, therapy requirements and engineering processes, we identified opportunities to improve system performance and reduce error tolerance by margins as small as 0.1%.
On a software scorecard, a 0.1% improvement may appear immaterial. In a precision surgical implant setting, that same margin can be the difference between restoring function or merely stabilizing it. It’s the difference between an acceptable outcome and one that materially changes a patient’s quality of life.
So here is what I would ask any technology partner going forward, and what I hope our clients ask us: not “did you deliver what we agreed to,” but “what changed, irreversibly, for the better, because you were here?”
Intelligence was never going to stay scarce for long. Impact was always the thing that couldn’t be commoditized. That is the metric worth building a company around.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
