True visionaries think outside the box, but most tech executives are forcing their employees into black boxes, out of fear of not doing exactly what their competitors are doing.
We have lemmings for leaders, and that means that—much like the LLMs that are being shoehorned into everything—there isn’t room for original thinking. Everyone’s strategy looks exactly the same.
They have a whole management team and can’t seem to find a way to judge or god forbid encourage developers…
For example, everyone talks about strategy, but when you ask them what's our strategy answer is usually something like:
* let's figure out together
* industry changing is so fast, we should revisit plans every quarter
...
"Welcome to the new contractor who will be the artitect our new infrastructure. What is your dream IT setup?"
"Yeah, we can't afford that. Lets revisit once you wrangle those 2003 Dell R620's running Windows 2008 with no patching."
And that is why after eight months i'm terminating my contract on Friday and swimming back to shore.
First is that despite a lot of waste, some innovation will arise from an enterprising employee finding some interesting use case. A lot of the tokenmaxxing is just waste, but out of that waste may arise a small number of genuinely powerful use cases.
Second is that many workers will be entrenched in their ways. If your executive goal is to achieve the above (find innovative ways of using AI), then you need to move everyone to use it. Most will just waste tokens, but someone may find a novel and useful way of using it that benefits the organization. It is difficult to achieve these without forcing people to act since their default is to follow the well-worn grooves.
So mandates like these are a top-down forcing function like a slime mold feeling out different paths to find resources.
Some devs in my org have fully embraced AI; some would not even use AI if not for leadership mandates and linking usage to performance reviews (I know, I think this is stupid, too). I can see why mandates could be useful since some folks definitely won't be inclined to use AI.
Imagine you employ me as a hotel manager, and I come to you and say: "sure I spent all our food budget internationally in three months, and sure I have nothing really to show for it, but for those three months, we had a lot of food fights"
Your manager then goes on to explain they not only need more money to cover the food budget, but also they need to quituple the cleaning budget too.
Oh and the service level has dropped, because not all clients liked being in the middle of a food fight.
However "we might have some innovation in the food delivery system of our hotel chain"
> we might have some innovation in the food delivery system of our hotel chain
> Imagine you employ me as a hotel manager, and I come to you and say: "sure I spent all our food budget internationally in three months, and sure I have nothing really to show for it, but for those three months, we had a lot of food fights"
Absolutely, but most management are not leaders, the moment someone pushes the idea to stack rank based on token usage, it gets approved and some genuine people will be impacted.
Post-ZIRP era proved there are very few strong leaders, before that everyone was behaving like they're most amazing leader because they read some books and raised $10M
So if the people who embrace AI areore successful then the others will follow. Just like every other new tech. Why does AI have to be forced? What's the hurry? Especially when there's no clear example of a company jumping ahead because of their use of it.
It's idiots being driven by FUD. That's the reason.
> What's the hurry?
There's also a need to quickly adopt and understand the technology; take the Internet for example. If we were talking about the Internet, forcing teams to build and publish web pages would be one valid way to get teams comfortable with the tech, the workflow, the shift in how to propagate and convey information to an audience.
Without a mandate, many teams won't adopt the Internet as a medium of information exchange because their processes work just fine and have worked for the last 20 years.
I think it's fair to put AI in a similar light. Unless teams adopt it and use it, it's hard for an org to understand how to get value out of this technology and how it affects existing processes and assumptions.
A lot of monkeys will also eventually type up Shakespeare?
If one is a CxO who's looking out for one's job security, herd-like behavior is the safest option, due to the (near universal) structure of "performance"-based executive remuneration.
https://en.wikipedia.org/wiki/Elinor_Ostrom#%22Design_princi...
What if the goal of an economic system was to support everyone instead of maximizing the upside for winners? Perhaps that's the sort of change necessary for improvement. Perhaps having billionaires is the failure state.
Lets talk my bonus, I will open the bidding at $1 per token.
I participate in some management-focused online communities. It’s crazy how many threads there are from frustrated managers trying to get their teams to stop thinking that their token use will be used as a proxy for their performance.
I think a few dumb companies did this and then it spread across social media, triggering a mass panic from engineers afraid their companies will be doing the same thing.
It’s getting so bad that the conversation is shifting to how to identify and coach the token-maxxers to stop wasting the team’s budget every week.
Because it is going to happen. Do you think metrics are tracked for fun?
Even if current leaders don't do it, next people might do it, how do you tell new leaders that we don't look at this metric? Metric exists to take action based on it
Nobody wants 90% of their token budget spend going to the 10% of people wasting them for number-go-up purposes.
Inefficient token use is going to become a metric.
I'd be curious to hear from people well versed in group psychology/dynamics and/or just a lot of leadership/people experience: what leads people to this type of thinking once they get in a group setting? It just... seems endemic at this point.
Obviously nobody here is going to know what I do or don't know, but I'm just increasingly curious what I am not understanding about this type of thing. It seems so obvious, yet that makes me ever more suspect that I'm oversimplifying it, or just totally ignorant about the problem in general.
Large and fascinating topic I'm researching, very relevant for agentic AI and ML too. One way that groups can fail is that they just don't to dampen / vote out individual errors properly (PAC learning, condorcet). Other kinds of errors only occur in groups, and can occur even when constituents individually aren't actually wrong.
https://en.wikipedia.org/wiki/Condorcet's_jury_theorem https://en.wikipedia.org/wiki/Group_polarization https://en.wikipedia.org/wiki/Availability_cascade https://en.wikipedia.org/wiki/Information_cascade
The last is probably the most relevant here and is related to negative effects of hierarchy. To quote one section:
> The negative effects of informational cascades sometimes become a legal concern and laws have been enacted to neutralize them. Ward Farnsworth, a law professor, analyzed the legal aspects of informational cascades and gave several examples in his book The Legal Analyst: in many military courts, the officers voting to decide a case vote in reverse rank order (the officer of the lowest rank votes first), and he suggested it may be done so the lower-ranked officers would not be tempted by the cascade to vote with the more senior officers, who are believed to have more accurate judgement;
For token-maxxing, our "senior officers" are just executives, and line workers aren't going to vote. Who is the senior officer for those senior officers? It's not shareholders! It's really the executives of even bigger companies, because that is the actually applicable promotion ladder. It's all kind of obvious, but it really is a slightly better explanation than "monkey see monkey do". These are just the simpler things, but there's more gnarly dilemmas in https://en.wikipedia.org/wiki/Common_knowledge_(logic)
Roll it all together and saying "just use it dammit" has some obvious advantages:
1. It's clear.
2. It's simple.
3. It eliminates all excuses employees might come up with for not using it.
The people at the top of these companies aren't stupid. They might have miscalculated how many tokens people can actually use, but that's very hard to calculate because usage is opaque and tools/processes change on a nearly weekly basis. They will eventually build out processes, tools, social conventions and performance metrics that take into account efficiency of token usage. But this is hard! Most managers aren't really assessed on the precise productivity of their teams, for instance, because productivity is often poorly defined.
Game theory! The downside of being brave vastly outweighs the upside. For the C-suite, there is no cost to herdlike-behavior, regardless of the outcome. However, there is a very high personal downside to being a maverick, and your board later discovers you made the wrong choice against the grain. The upside of being maverick and right is very limited.
Once a behavior has become mainstream, hopping on the bandwagon is no longer individually attributable to decision-makers, but is seen (and reported) as a macro-economic phenomenon: Nadella, Zuckerberg and Bezos didn't overhire - the American tech industry overhired.
Whats happening now and whos driving it is interesting. The CEO has a license for this new tool (think one of the top 4, Qwen Claude, Gemini, openAI) and really likes it. So much so that they (non coder) are making lots of little single page web apps.
The COO is bollocks deep in AI, and is saying that we cannot buy any SaaS products anymore. We must make it ourselves.
The engineering manager has seen this as an opportunity to build out a brand for engineering (its a small department in a medium sized company) by delivering quickly what the large year long efforts cant.
This has formed a slopnexus where PoCs are spun up left right and centre, but there isn't much time or thought going in to making them sustainable.
What started out as a (simple ish) asset management tool, neatly scoped into a deliverable PoC has morphed into a 5 product as one monster.
Its a mess that will either lead to burn out or disaster.
And myself being an infrastructure guy that needs to maintain all these PoCs that are now suddenly critical for production, it's the perfect nightmare.
And mind you, that dynamic always existed to a certain degree (laptop on a desk that runs some ugly Python script that does half the work of the BizOps team? Check. GCP account attached to the GSuite running a random instance for finance when the company is 101% on AWS? Check. Spreadsheet with macros that sends emails via Outlook as a mailing list manager? Check.) but at least when you discovered that you could scold them and tell them that we need to migrate this to a proper system because security. But nowadays with vibe-coded internal apps...it's a challenge.
"It is difficult to get a man to understand something, when his salary depends on his not understanding it." -Upton Sinclair
That VC funded gravy train is likely coming to an end. But fortunately there are also reasonably efficient models now so that the tokenmaxxers can still make the (much cheaper) tokens go brrrr.
Trying to operate as a rational, thinking person in a lot of environments right now feels impossible. Rational thought is being treated like AI skepticism.