When the “stupid” idea was the right one
A Denver construction firm we worked with nearly killed their best process improvement of the year because the person who proposed it was a 24-year-old field tech with no IT background. His idea — replace the project-management software the office had spent roughly $40K rolling out with a shared spreadsheet and a group text — sounded like a step backwards.
Three months later, that “downgrade” had cut daily admin time across the crew by several hours and the office stopped chasing field updates at 9 PM. The expensive software stayed installed; nobody opened it.
Bad ideas and breakthrough ideas look identical at the moment of proposal. The real question for an SMB owner isn’t which is which — it’s how do you tell the difference cheaply enough that being wrong doesn’t hurt.
Why good ideas look bad at first
Three things consistently make smart leaders dismiss ideas that turn out to matter:
- Pattern recognition works against you. Our brains are wired to prefer familiar solutions. Anything genuinely new triggers the same alarms that once kept our ancestors alive. Useful in 10,000 BC, expensive in 2026.
- Deep expertise narrows the lens. People who’ve spent 20 years in an industry know how things should work. That’s exactly what makes it hard to see how things could work differently. The field tech in the example above had no idea what the software was “supposed” to do — so he proposed what would actually work.
- Asking customers doesn’t help much. Customers can’t want what they can’t imagine. Focus groups produce incremental improvements, not category shifts. Historical sales data is useless for anything that hasn’t existed yet.
This isn’t a reason to ignore your experience, your team, or your customers. It’s a reason to put unfamiliar ideas through a different kind of test than familiar ones.
A 4-week test, not a 4-year strategy
Most innovation advice is written for Fortune 500s and assumes you have an R&D budget, a dedicated team, and time to run multi-year experiments. For a 30-person business, the practical version fits in a single month:
- Week 1 — Cost the idea at its smallest scale. Not the full rollout. What is the cheapest version that proves or disproves the core assumption? A spreadsheet beats a software trial. A manual process beats an integration build. A two-person pilot beats a department-wide one.
- Week 2 — Pick one team and one metric. Run the small version with people who will tell you the truth, measured against one number that matters: hours saved, errors caught, calls deflected, days to close.
- Week 3 — Watch what actually happens, not what people say. Self-reports lie, especially when someone is invested in the outcome. Look at the data the system records on its own.
- Week 4 — Decide: scale, kill, or iterate. No “let’s keep watching.” Indecision is the most expensive outcome — it keeps half-running pilots on the books for years and burns out the people running them.
This is the same loop we use when evaluating whether a client should migrate from QuickBooks to a full Enterprise Resource Planning (ERP) system, switch cloud providers, or roll out a new ticketing system. Most ideas die in week 2 — cheaply, before they become budget items. The few that survive are worth the full investment.
Watch-outs
Three places this framework breaks down in practice:
- Picking the wrong metric. “User satisfaction” is not a metric. “Average time from field update to invoice” is. If you can’t write the metric as a number with a unit, you’ll get a vibes-based answer in week 4.
- Running the pilot with believers only. The team that wants the idea to succeed will make it succeed regardless of merit. Include at least one skeptic — ideally the person who’ll have to support it after rollout.
- Skipping the kill decision. “Let’s run it another month” is how zombie pilots are born. Scale, kill, or iterate with a defined change. Nothing else.
Next step
If there’s an idea sitting in a notebook somewhere that you can’t tell is brilliant or terrible, that’s exactly the conversation we like to have. See how we approach technology strategy for Denver SMBs or get in touch and we’ll help you scope a 4-week test that costs less than a software trial.