A Government Affairs function is appraised on what can be counted: meetings taken, representations filed, forums attended, issues raised. Each of these can rise quarter after quarter while every matter of consequence stands exactly where it was, because the system makes activity easy to count and progression almost impossible to see. The function is therefore judged on the axis least connected to the outcome it exists to produce, and the mismatch is built into the metric, not the team. What would a progression-based account of the function measure instead, and why does the organisation keep reaching for the activity number?
The metrics a Government Affairs function reports against are, almost everywhere, metrics of activity. The quarterly review records meetings held with senior officials, representations and submissions filed, industry forums and consultations attended, issues formally raised, and arrangements concluded. Each of these is countable, each rises with effort, and each can be reported upward without any reference to where a matter actually sits inside the institution. This is the function's standard accountability currency, and it is the currency precisely because it is the one thing the organisation can read from outside the system.
Activity and progression, however, are different axes, and they move independently of each other. A function can hold forty meetings, file a dozen submissions, and attend every consultation in its sector, and the matter that determines the year's outcome can sit, across all of it, at exactly the stage it occupied twelve months earlier, because the noting was never placed, the concurrence was never sought, or the financial appraisal returned a query no one was positioned to answer. The activity metric measures how hard the function is working; it does not measure whether the matter is moving, and in the Indian system those two are only loosely related. A function judged on the first is judged on the axis least connected to the result it exists to produce.
The divergence is not theoretical; it is visible at the scale of a flagship mission. The IndiaAI Mission generated, through 2024 and 2025, almost every form of visible activity a programme can produce: tens of thousands of graphics processing units onboarded onto a national compute facility, a slate of startups and consortia selected with considerable fanfare to build India's foundational models, a global summit that drew headline investment commitments, and a steady cadence of ministerial announcements. By every activity measure, the mission was thriving. The specific outcome that mattered to the selected builders, the money actually reaching them, moved almost not at all: formal agreements with several of them remained unsigned many months after selection, and only a fraction of the mission's multi-year outlay was disbursed across its first two years, a position confirmed in a written reply in Parliament. The matter was held not in the grandstand but at the specific, unglamorous nodes where outcomes are produced: a memorandum of understanding with no precedent template, the concurrence of the ministry's Internal Finance Division under the General Financial Rules, the sanction order that follows it. And because the money did not move, the consequence arrived on the system's own terms: the mission's budget for the following year was cut. Activity is broad and visible; progression is specific and almost always invisible, and the outcome moves only at the specific node, never in the grandstand around it.
What the mission shows at scale, a company's own function shows in miniature, and the organisation reaches for the activity number not because it is a sound measure but because it is an available one. Progression is difficult to see from outside the institution: the file is not visible to the company, the system publishes no stage-by-stage status, and a matter can be advancing correctly and still show no external movement for two quarters. Activity, by contrast, is legible, immediate, and simple to place in a slide. So the function reports what can be counted rather than what matters, and the mismatch is a property of what the system makes visible, not a choice the head of the function made.
A progression-based account measures the matter rather than the effort around it. For each matter of consequence it records where the matter sits in its institutional lifecycle, which stage it has cleared and which it is held at, the specific next action the system requires, and the movement, or the absence of movement, since the last review. It separates a matter that is held because the company has not yet supplied what the system asked from a matter that is held because the pathway is structurally blocked, and it reports the two differently, because they call for different responses. It treats a matter carried one full stage forward as a result, and a quarter of meetings that advanced nothing as what it is. Measured this way, the function is accountable for the accuracy of its reading of where matters stand, which is the one thing within its control, rather than for an outcome only the institution can grant.
The activity metric carries a specific cost. It rewards visibility over progression, so the function is drawn toward the engagement that is easy to report and away from the unglamorous, matter-level work that actually moves a file. It lets a year of diligent effort look like progress when nothing has progressed, and it lets a year in which two hard matters were carried to closure look thin because the meeting count was low. And because it cannot show honest non-movement, it quietly pressures the function to dress estimates as momentum. The change a function needs is not to work harder against the activity number; it is for the organisation to change the number, and to be willing to receive a progression metric that sometimes, correctly, reports a matter standing still.