Shiny object syndrome: why business owners accumulate tools, courses, and strategies they never implement

Series: Decisions that Move the Needle: Article 4 of 10

Do this exercise honestly: open your company's subscription dashboard and count how many tools have an actual active user. Then look at your library of purchased courses and the frameworks your team learned in workshops over the past two years. The question that follows is the one that hurts: out of all of that, what is actually in use, and what is executive decoration?

Shiny object syndrome is not a character flaw. It is the predictable outcome of combining three things: fear of falling behind, an excess of options, and decisions that never close. This article diagnoses it using industry data and provides a "strategic debugging" method to recover the money and energy trapped in accumulation.

The evidence: accumulation is massive, and it is measured in money

Software shelfware. The SaaS Management Index from Zylo estimated that companies waste an average of US$18 million annually on unused licenses, that more than a third of a company's applications are "shadow IT" (purchased without going through IT), and that 67% of IT leaders admit to software purchases outside official channels (Zylo, 2024). Meanwhile, Vertice's analysis estimates that 65% of all SaaS licenses are completely unused or underutilized, a percentage that rose from 62% the previous year (Vertice, 2025). If your SMB does not have tens of millions to waste, the problem is proportionally more severe: in a company with 20 tools, applying that 65% (Vertice, 2025) means that around 13 are in ornament mode.

Purchase regret. Capterra found that 60% of software buyers regret at least one purchase made in the past 12 to 18 months (Capterra, 2024). It is not just money: each regretted purchase leaves behind a cultural residue: "we already tried something like that and it didn't work", making the next necessary change harder.

Strategies that are not executed. And the shiny object is not just software. McKinsey estimates that around 70% of large-scale transformations fail to reach their goals (McKinsey). Each of those failed initiatives left behind a barrage of training, methodologies, and dashboards that the team learned not to take seriously. Accumulating "the new" without execution is, in part, why organizations develop immunity to improvements.

The psychological root: too much spectacle, too little buying

The classic experiment by Sheena Iyengar and Mark Lepper at a California supermarket highlighted the effect of choice overload: in front of a tasting booth with 24 jams, more people stopped by to look, but only 3% bought; in front of a tasting booth with 6 jams, fewer people looked, but 30% bought (Iyengar & Lepper, 2000).

Translated for the modern business leader: there have never been more options to "improve" (courses, methodologies, AI tools, growth frameworks), and it has never been harder to buy one and implement it. The shiny object does not seduce because of its quality; it seduces because of its novelty. And novelty wears off in weeks, long before implementation, which is what produces results, has even begun to pay off.

The typical cycle has four phases: enthusiasm (purchased or adopted with energy), friction (implementation demands tedious work), new object (the fresher promise appears), abandonment (the previous object joins the collection). Each turn of this cycle costs three times: the purchase money, the half-invested time, and the damage to the internal credibility of the next initiative.

And there is a fourth cost that is only seen from a distance: the compounding opportunity cost. A tool half-implemented over six months is not a neutral expense: it is a capability the company thinks it has, but does not. Decisions are made assuming that capability ("we already have a CRM, so we can launch the campaign") and fail in execution, generating a second cycle of purchase and frustration. Accumulation does not add: it multiplies failure points.

That is why the correct diagnosis of the syndrome is not "we are scattered": it is "we open more than we close." And that metric, unlike enthusiasm, can be audited: count how many initiatives were opened in the last 12 months and how many were closed with an outcome (good or bad, but closed). The gap between both numbers is the exact measure of your internal shiny object.

Diagnosis: 5 signs that your company accumulates instead of executing

1. The 60-day rule broken: no tool, course, or methodology from the past two years reached 60 days of consistent use.
2. Collection vocabulary: the team talks about tools "we have" (inventory) and not results "we are achieving" (execution).
3. Abandonment stations: parallel processes exist: the old spreadsheet keeps running even though "the system" has already been purchased.
4. Executive FOMO: adoption decisions are triggered by what the owner saw at an event, on a podcast, or on LinkedIn, rather than by an internal diagnosis.
5. Ghost budget: no one can tell how much the company spends on subscriptions and licenses, because the list does not exist.

If you recognize three or more, the company does not have a tooling problem: it has a decision-closing problem. And the solution is not buying better: it is debugging.

The strategic debugging method (4 steps)

Step 1: full inventory: everything in plain sight

List in a single table: tools and subscriptions (with monthly cost and actual last use), purchased courses and training, and methodologies/frameworks adopted in the last 24 months. The rule is not to negotiate yet, only to make things visible. In this step, duplicate subscriptions and licenses for people who are no longer at the company almost always show up: the easiest waste to recover.

Step 2: classify by actual use, not potential

For each item, the question is not "could this be useful to us?" but "who used it last week and for what?". Classify into three categories: in production (weekly actual use, identified owner), on trial (actual but recent use, with a decision deadline), and on display (no actual use in 60 days). The temptation to move items from the third to the second category "just in case" is shiny object syndrome talking.

Step 3: eliminate with criteria: the opportunity cost test

For each "on display" item and each strategy no one executed, apply the inverted question: if this tool/strategy were as valuable as it seemed when we bought it, would anyone be using it? If the answer is no, the perceived value was from novelty, not content. The money and hours you free up by eliminating are not a cut: they fund what you actually will implement.

Step 4: consolidate: one bet at a time

The structural antidote to the shiny object is a focus rule: the company executes a single improvement initiative per quarter, with an owner, metric, and review date. Everything else is explicitly put on hold. The evidence that "many initiatives" does not equal "more transformation" was already shown above: most transformations fail, and accumulating open fronts is one of their most frequent causes.

Debugging table (template to complete with your team)

Closing criterion: an item only stays "on trial" for 60 days. At 60 days it becomes production or is eliminated. No exceptions: the exception is the archive where shiny objects are stored.

What changes when you debug

The benefits of debugging are not abstract. First, the direct one: money from unused licenses returns to cash flow or is reinvested in what is actually used: in an economy where 65% of licenses lie dormant, there is plenty to recover. Second, the operational one: fewer tools means fewer contexts, fewer fragile integrations, and less continuous training. Third, the cultural one, and it is the most important: when the team sees that the company closes what it opens, the next necessary initiative is met with seriousness instead of cynicism.

The shiny object is seductive because it promises the outcome without the work. Strategic debugging reverses that promise: it turns the collection into focus, and focus into execution. That is what shows: on the cost spreadsheet and in the team's morale.

Sources consulted

1. Zylo (2024). 2024 SaaS Management Index Reveals an Average of $18M in Annual License Waste. Accessed October 14, 2026: https://zylo.com/news/2024-saas-management-index
2. Vertice (2025). Unused SaaS applications: the scale of the problem. Accessed October 14, 2026: https://www.vertice.one/insights/unused-saas-applications
3. Capterra (2024). Tech Trends Report: Software Purchase Regret. Accessed October 14, 2026: https://www.capterra.com/resources/tech-trends-software-purchase-regret
4. McKinsey & Company. Perspectives on transformation. Accessed October 14, 2026: https://www.mckinsey.com/capabilities/transformation/our-insights/perspectives-on-transformation
5. Iyengar, S. S. & Lepper, M. R. (2000). When Choice is Demotivating: Can One Desire Too Much of a Good Thing? Journal of Personality and Social Psychology, 79(6). Accessed October 14, 2026: https://faculty.washington.edu/jdb/345/345%20Articles/Iyengar%20%26%20Lepper%20(2000).pdf