Latest
How Famous Memoirs Were Really Written: What the Collaborators DidStranger in a Strange LandProfiles in CourageDid I Ever Tell You This?: A MemoirFlorida RoadkillTeam of Teams: New Rules of Engagement for a Complex WorldMy Share of the Task: A MemoirWe Were Soldiers Once… and Young: Ia Drang, the Battle That Changed the War in VietnamThe Columbia Restaurant: Celebrating a Century of History, Culture, and CuisineA Tiger among Us: A Story of Valor in Vietnam’s A Shau ValleyTop Sergeant: The Life and Times of Sergeant Major of the Army William G. BainbridgeSailing True North: Ten Admirals and the Voyage of CharacterPodkayne of MarsMake Your Bed: Little Things That Can Change Your Life…And Maybe the WorldSam Walton: Made in America: My StoryI, RobotOpen: An AutobiographyShattered Sword: The Untold Story of the Battle of MidwayA World at Arms: A Global History of World War IIL.L. Bean: The Making of an American IconA Higher Standard: Leadership Strategies from America’s First Female Four-Star GeneralLife21 Days to Success Through Networking: The Life and Times of Gnik RowtenCampus BattlefieldThe Bell JarRight Wing RevolutionThe Sage of SagittariusTime for a Turning PointDesigning Casinos to Dominate the CompetitionLove’s Executioner and Other Tales of PsychotherapyBeneath a Scarlet SkyThe Library BookThe Phone Book: The Curious History of the Book That Everyone Uses But No One ReadsTrump: The Art of the DealThe MAGA DoctrineThe College ScamSea Stories: My Life in Special OperationsPa’anNetworking Your Way to SuccessMasters of NetworkingRadioSoldier for Life: Leader Lessons from the 12th Sergeant Major of the ArmyThe Melting Point: High Command and War in the 21st CenturyAmerican SoldierIt Doesn’t Take a HeroStop, in the Name of GodDoes Explicit Sex Sell Books? An Answer to The Absolute Degeneracy of Modern WritingThe Mary Sue: How a 1973 Star Trek Parody Became a Writing TermWhat the AI Writing Survey Says About Jobs, Freelancers and Fiction AuthorsHow Long Does Google Take? Crawling, Indexing and Recovery Times

Why You Don’t Put All Your Eggs in AI

TL;DR: In finance, the first rule is diversification. You never put all your money in one asset. The same rule applies to technology, and most companies are breaking it right now by betting everything on AI. A strategy executive I interviewed made the case plainly: today’s AI won’t be tomorrow’s AI, one security breach can collapse a single-vendor stack, and an all-in bet isn’t a strategy. This article makes the argument for spreading your technology risk, with a hard-won backup story to prove it.

Spend twenty-five years in financial services and the discipline comes through in how you read technology strategy. It works the same way it does in investing. Diversification. You don’t put all your eggs in one basket, and you don’t put all your eggs on AI.

It’s the most useful reframe I’ve found for the current rush, because it turns the whole decision from a technology question into a risk question. I first heard it put that way in a conversation with a strategy executive on seeing the whole chessboard.

Think of your technology like an investment portfolio. A financial advisor who told you to put every dollar into one stock would be fired, no matter how good the stock looked. Yet that’s exactly what companies are doing with AI right now, pouring the entire budget into one bet as though the bet can’t go wrong. It can. And the way it goes wrong is the same way a concentrated portfolio always goes wrong.

Why is betting everything on AI a bad strategy?

Start with this: the asset is unstable. Today’s version of AI won’t be tomorrow’s version. That’s a bigger deal than it sounds. If you rebuild your entire operation around the current models, you’ve tied yourself to a technology that’s changing under your feet. Something else could evolve, a different approach could win, and now you’re holding a system built for a moment that’s passed. In finance you’d call that concentration risk. In technology it has no fancy name, but it’s the same trap.

Then add the failure modes. A single-vendor, single-technology stack has a single point of failure. One cyber attack, one security gap, one breach from our friends outside the borders, and all of it can collapse at once. Diversification is how you survive the day one piece fails, and in technology, on a long enough timeline, that day always comes.

What does diversification look like in practice?

I learned this in the least glamorous corner of technology, backups, and it saved me.

My backup strategy has three layers, three separate backups from three different vendors. None of them are expensive. If any one of them fails, I still have two. That’s diversification at the smallest scale, and it’s the reason I still have my life’s work.

I’ve taken more than 980,000 photographs over my life, along with thousands of videos and 113+ books’ worth of manuscripts. I nearly lost all of it once, years ago, when a disk drive died and I had to rebuild it by hand, a nightmare I never wanted to repeat. Recently a disk failed again. This time it was a shrug instead of a disaster, because the data lived in three places and I recovered it.

It took a few days, because it’s terabytes, but I got everything back. One vendor, one copy, and that story ends very differently. The principle scales all the way up. What protects a photo library protects an enterprise.

Does diversification mean avoiding AI?

No, and people get it wrong in the other direction too. Diversification is a reason to hold AI as one position in a broader portfolio instead of the whole portfolio.

Use it where it helps, which is real and worth using, as I’ve written about in Six Places AI Will Break Your Work. Just don’t tear out systems that work to bet everything on a technology that will look different in a year.

The organizations that come out ahead are the ones that think in five and ten year horizons, holding a mix, keeping what works, adding the new thing as a measured position instead of an all-in shove. The ones that lose are the ones chasing the crowd, ripping out functioning systems to slap AI on everything because everyone else is. That crowd behavior has a cost, and I traced why these bets fail in Why Most AI Rollouts Fail.

What is the vendor lock-in trap with AI?

There’s a second layer to this, and it’s about vendors as much as technology. Sticking to one vendor is its own concentration risk, and it’s always bad, whatever the vendor promises. When you build everything on one provider’s stack, you inherit their outages, their price hikes, their security holes, and their business decisions. If they change their terms or their direction, you have no move. My three-vendor backup rule is a vendor-diversification rule as much as a technology one, and the logic is identical at enterprise scale.

Vendors know this, and plenty of them design for it. Proprietary formats, exit fees and integrations that only talk to each other exist to make leaving painful. I’d treat any AI provider that makes it hard to take your data elsewhere as a risk to manage, and I’d keep a working alternative ready before I needed it.

This is what a transformation done right looks like.

It spreads the positions so no single failure can take down the whole operation, and nobody’s betting the company on one shiny thing. I’ve written about the order of operations that makes transformation work, starting with people before technology, in People, Process, Technology. The through-line is the same as the finance rule. Don’t concentrate. Spread the risk, keep what works, and treat every new technology, including AI, as one position in the portfolio.

I think the executives ripping out working systems to go all in on AI are gambling with money and jobs that belong to other people. When that bet goes bad, they won’t be the ones up at night rebuilding the data by hand.

There’s a fuller version of this argument, including a three-horizon read on where the AI infrastructure race is heading, in this conversation on seeing the whole chessboard. If you’re leading technology decisions and want to think about them as risk instead of hype, start with the Digital Transformation Hub, and if the lessons you’ve learned running real systems belong in a book, my writing services are built for exactly that.

Frequently Asked Questions

Why should you not put all your technology budget into AI?
Because it’s concentration risk, the same mistake as putting all your money into one stock. Today’s AI won’t be tomorrow’s AI, so building your whole operation around the current models anchors you to a technology changing under your feet. A single-technology stack also has a single point of failure, where one breach or outage can collapse everything at once.
What does technology diversification mean?
It means spreading your technology and vendor risk instead of concentrating it, the same way a financial portfolio holds many assets instead of one. In practice it looks like multiple backup layers from different vendors, keeping systems that work while adding new ones as measured positions, and never depending on a single provider for anything critical.
Does diversification mean a company should avoid AI?
No. Diversification is a reason to hold AI as one position in a broader portfolio instead of the whole portfolio. AI is real and worth using where it helps. The mistake is tearing out functioning systems to bet everything on a technology that will look different in a year.
Why is relying on a single vendor risky?
Because a single vendor is its own concentration risk. When you build everything on one provider’s stack, you inherit their outages, price increases, security holes, and business decisions, and you have no move if they change terms or direction. Vendor diversification, like using multiple backup providers, protects against being trapped by one company’s failures.
How does a backup strategy show the value of diversification?
A three-layer backup with three different vendors means that if one fails, two remain. That’s diversification at the smallest scale. It’s the difference between a disk failure being a shrug and being a disaster. The same principle scales from a personal photo library to an enterprise, where spreading risk is what lets an operation survive the day a piece fails.

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment