Tokenmaxxing Archives - Hoola Hoop - Executive Coaching for CEOs, CTOs & Boards

When AI Activity Gets Mistaken for AI Productivity.

Token leaderboards are the new lines of code. They look rigorous, they travel well in a board deck, and they reward the wrong behavior within six months. Here is why tokenmaxxing took hold, why it will not survive contact with a serious board, and what the scoreboard needs to look like instead.

Tokenmaxxing is the AI vanity metric of 2026, and it is already distorting how engineering leaders are evaluated, hired, and funded. In the last six months, token consumption has crossed over from a billing line item to a performance signal. Internal leaderboards, token budgets, and anecdotal reports of runaway usage are starting to shape how “AI productivity” is perceived. Whether exaggerated or not, they all point to the same underlying shift: AI usage is being treated as a proxy for AI output.

This article is not about any one company or example. It is about the broader pattern taking hold across the industry. When a board asks for AI ROI, the easiest number to show is usage. It is visible, it moves every week, and it looks rigorous in a deck. In my opinion, it is the wrong number, and every experienced CTO has seen where this leads.

Earlier this week, I had a conversation with CTO, Hunter Powers. Our conversation is what inspired me to write this article. We were discussing this specific trend and my predictions for where this fad is likely to go. What came to my mind was a reminder of the early “website hits” metric from the early days of the internet. It was something that could easily be gamed, but more importantly, it provided very little value in understanding a company, its product adoption, or its revenue. If you haven’t already, check out Hunter’s AI podcast on YouTube.

What follows is a field guide to the tokenmaxxing AI vanity metric: why it took hold, why it will not survive the next board cycle, and what a real outcome scoreboard looks like in its place.

Where the Tokenmaxxing Obsession Came From

Tokenmaxxing did not appear because anyone decided it was a good measure of productivity. It appeared because no one had a better one. For the last eighteen months, CFOs and boards have been funding AI tooling at a level that demanded justification, and engineering leaders have been unable to produce a clean answer to the question “what are we getting for this?” In the absence of a credible outcome metric, activity became the proxy. Token volume was visible, it was measurable in real time, and it went up every week. That was enough.

The pattern is familiar to anyone who managed engineering before AI. Lines of code held the same seat in the 2000s. Commits per week had a brief and ugly run in the 2010s. Jira tickets closed per sprint is still getting dressed up as a KPI in some companies. Every one of these metrics sounded rigorous, traveled well in a board deck, and rewarded the wrong behavior within six months. Tokenmaxxing is the same shape of mistake, delivered at a higher blast radius because the dollar figures are so much larger. If you think about it, it’s more of a marketing or fluff number than anything related to productivity.

What makes the tokenmaxxing AI vanity metric particularly dangerous is that it has two lives at once. Inside the company, it is a performance metric: who burned through the most tokens, who shows up on the internal leaderboard, who gets the reputation of being an “AI power user.” Outside the company, it is a marketing metric: the stat a founder uses on a podcast, the slide a CTO puts in front of a board to prove AI adoption. Both are unearned. Neither survives a serious review.

Five Ways Tokenmaxxing Breaks an Engineering Org

Across the CTOs and CPOs I coach, tokenmaxxing shows up in five distinct failure patterns. Recognizing yours is the starting point for the scoreboard conversation.

The Leaderboard Problem

Internal token leaderboards start as a visibility tool and quickly become an incentive system. Once usage is ranked, engineers adapt. Prompts get re-run, context gets inflated, and entire codebases get pulled in “just in case.” What looks like measurement is actually behavior being shaped in real time. Within weeks, the leaderboard stops reflecting productivity and starts producing the opposite of it.

The Unbounded Spend Problem

When token usage becomes a signal of effectiveness, spend detaches from outcome. Engineers who are most engaged with the tools naturally consume the most, and without a constraint, usage expands to fill the available surface area. Finance eventually notices a line item growing faster than anything else in the budget. At that point, the question is no longer “are we using AI?” but “what are we getting for this?” If the answer is unclear, the correction is usually blunt.

The Context Window Anti-Pattern

Separately from leaderboards, engineers are defaulting to the largest possible context window on the assumption that more context produces better output. In practice, dumping more files, more history, and more examples inflates cost, lengthens latency, degrades review quality, and often buries the signal the model needed. Tokenmaxxing as a craft failure is quieter than the leaderboard version, but it shows up as the same line in the same invoice.

The Junior Engineer Feedback Loop

A junior engineer watching the leaderboard learns the wrong lesson about what senior looks like. The culture starts rewarding volume of AI interaction rather than quality of judgment. Inside a year, you have an engineering org that confuses “I used the tool a lot” with “I shipped good work.” This is the same pathology as the lines-of-code era, and it breaks the apprenticeship model that turns juniors into the senior engineers you need three years from now.

The Board Deck Problem

A CTO who reports tokens to the board is setting a trap for themselves. Token usage always goes up, until it does not. The moment usage flattens or drops because someone finally optimized a prompt chain, the CTO has to explain why “adoption” has fallen. The board interprets the decline as AI losing traction. The real story, that the team got better at using the tools, never lands, because the metric was never structured to tell it.

The Common Thread

Every one of these failures has the same root cause. The organization is measuring AI activity because it has not figured out how to measure AI outcomes. That gap is the real problem, and closing it is what separates the CTOs who survive the next twelve months from the ones who get quietly reorganized out. Tokenmaxxing is the symptom. The missing outcome scoreboard is the disease.

What Good Looks Like: Replacing the Tokenmaxxing Scoreboard

The answer to tokenmaxxing is not to ban token tracking. It is to refuse to let token tracking be the scoreboard. A scoreboard that resists this specific failure mode tends to have five features in common, and each one takes deliberate work to put in place.

📈

Outcome metrics tied to real business impact

Time from feature idea to production, defect rate in AI-assisted code versus human-written code, revenue per engineer by quarter, cycle time on the kinds of work the business actually cares about. These numbers are harder to collect than token counts, and that is precisely why they deserve the top of the deck.

🎯

A per-engineer token budget, owned as a constraint

Tokens are an input, not an output. Treat them like cloud spend. Give each team a monthly token budget, hold them to it, and reward the teams that produce better outcomes within the cap. The goal is not to minimize tokens. The goal is to eliminate the incentive to inflate them.

🧪

Explicit separation of experimentation from production

Experimentation is where you want engineers burning tokens freely, because that is where learning happens. Production is where you want tokens ruthlessly optimized, because that is where margin lives. A scoreboard that cannot tell these two apart will always look like chaos, and will always invite the wrong kind of intervention from finance.

✅

Quality signals, not just speed signals

Pull request acceptance rate on first review, post-release defect density, on-call hours caused by AI-generated changes. These signals tell you whether the AI work is actually holding up after it ships, which is the only definition of productivity a CFO eventually cares about.

🗣️

A narrative layer above the numbers

A CTO walking into a board review needs to be able to say what the AI investment is buying the company, in language the board uses, not in tokens. That sentence almost never begins with “our consumption grew.” It usually begins with “here is the work we can now do that we could not do before, and here is what it costs us to do it.”

The Underlying Principle

Activity metrics measure the past. Outcome metrics measure the bet. A CTO who builds the scoreboard around outcomes is telling the board, in effect, that they know where this investment is supposed to land and are willing to be held to it. A CTO who reports tokens is telling the board that no one has figured that out yet. Boards can tell the difference, even when they cannot articulate it.

Token volume tells you who used the tool the most. It does not tell you who shipped the best work.

The Conversation With Finance

The finance conversation is where tokenmaxxing turns from a cultural issue into a budget problem. When the AI bill grows faster than expected, one of two conversations happens.

In the first, the CTO explains that token spend tracks productivity. The CFO asks for the productivity number. The CTO does not have one. At that point, the discussion is no longer about AI. It is about cost control. Budget gets cut, usually by a percentage that looks reasonable on a spreadsheet and is catastrophic in practice.

In the second conversation, the CTO walks in with a per-engineer token budget already in place, a small set of outcome metrics already reporting, and a clear answer to what the company is buying with its AI compute. The finance team is not being asked to trust a proxy. They are being asked to approve a line item that behaves like every other line item they trust.

The difference between those two meetings is not intelligence. It is preparation. One is reacting to a number that grew without a model behind it. The other is managing a system that was designed to be explained. That moment is coming for every engineering org still running a token leaderboard, and the time to prepare for it is shorter than most CTOs think.

Questions to Sit With

If the tokenmaxxing AI vanity metric is showing up in your org, these are the questions worth working through honestly before the next board or finance review:

If your company’s token spend doubled next quarter, what would you be able to tell the board you had gained in return?
If token usage across your engineering team dropped by 40 percent next quarter because your team got better at prompting, how would your current metrics present that?
Who in your organization is currently incentivized to inflate token usage, and who is incentivized to reduce it?
What are the three outcome metrics you would put at the top of your next AI review, if you were forbidden from reporting tokens, spend, or adoption rate?
If your top “AI power user” left tomorrow, would the loss show up in the work that shipped, or only in the leaderboard?

A Final Thought

Tokenmaxxing is what organizations do when they are under pressure to show progress on something they do not yet know how to measure. That is not a new problem. It is the same pattern that produced lines of code, commits per week, and other utilization metrics. Every one of those numbers looked rigorous at the time, and every one of them had to be dismantled once it started distorting behavior. The difference in 2026 is the scale. The dollars are larger, the feedback loops are faster, and the board patience is shorter.

The organizations that get this right will not be the ones that use the most AI. They will be the ones that measure it correctly. Tokenmaxxing is not the root problem. It is the first visible symptom of a scoreboard that is already broken. Fix the scoreboard, and the token conversation becomes a detail. Leave it broken, and tokenmaxxing is just the first thing that fails.

If you are a CTO or CPO staring at a token leaderboard and wondering whether the tokenmaxxing AI vanity metric is quietly breaking your team, that instinct is worth trusting. The next step is building the scoreboard you actually want to be measured against, and it is a conversation Hoola Hoop’s former-operator coaches have had from the inside of more than one engineering org. You can read our earlier piece on AI ROI board pressure for the broader context this article sits inside.

The operator-era question is not how many tokens you burned last week. It is what you can now build that you could not build before, and what it cost you to build it. Get the scoreboard right, and the token conversation becomes a detail. Get the scoreboard wrong, and tokenmaxxing is just the first thing that breaks.

Ready to talk about CTO coaching with Leigh?

Book a 30-minute introductory call to explore whether coaching is right for you.

Book a meeting with Leigh →

Leigh Newsome

Partner, Hoola Hoop · CTO Coach

Leigh Newsome is a Partner at Hoola Hoop and a CTO coach with 25 years of experience scaling product and engineering teams. He has worked with a wide range of startups and global enterprises, including Avid, Digidesign, WPP, and Kantar/Millward Brown, and successfully led TargetSpot (backed by Union Square Ventures, Bain Capital Ventures, and CBS) through its acquisition to Radionomy Group (Vivendi). When he’s not coaching CTOs, you’ll find him teaching digital audio to graduate students at NYU, building audio and signal processing applications, or flying fixed-wing aircraft, but never all three at once.

Tokenmaxxing: The Vanity Metric Eating Your AI Budget