Enshittification as Overproduction in Software
medium.com
medium.com
If everyone rationally responding to their incentives, produces an irrational behavior in aggregate, you have a systemic problem. We have a systemic problem.
Team A analyzes SaaS solutions and tries to replace existing systems with turnkey services.
Team B makes a cleanroom implementation mirroring the original product. This could confuse sales, though.
Team C is the skeleton crew that fixes bugs and still delivers new features, but at a reduced pace.
Would this be too costly? Too much duplicated work?
Maybe even having to choose only one team is an executive decision and determines the rest of the roadmap for the whole company.
Each team would need a vertical slice of each department, from marketing to QA. But there would be cross-pollination, because each business sponsor fields requests from different aspects of the same thing.
Some observations from other domains. The military has special forces, airborne, and frontline soldiers. Another is F1 technologies being adapted in consumer vehicles (if one car company manages the whole stack).
I think we are getting this equation wrong as a society.
We need figure out how to spin out the 900 that become medium-sized profitable companies. In a sense, companies like bending spoons are doing just that. We haven't found yet how to make 1000 bets, have one be the Next Big Thing, and profit from the 900 that are still profitable enterprises in their own but fail in the overproduction environment that we think we need for the Next Big Thing.