A manufacturing company owner in Osaka told me something recently that stuck with me.
"We spent two million yen on DX last year. Nobody uses the system anymore."
He said it with a half-laugh, but his eyes weren't smiling.
Two million yen. That's not a trivial amount for a small business. And now it's sitting there as an unused SaaS subscription collecting dust on a shelf. The employees went back to the same Excel spreadsheets they'd always used. The owner concluded "DX was too early for us" and lost the appetite to try again.
Unfortunately, this story isn't rare. At SolidTech, we've heard variations of it over and over from small and medium-sized business clients. But the more we listen, the clearer the pattern becomes: the problem isn't DX itself — it's the approach.
And the mistakes? They're remarkably consistent.
Reason 1: Starting with tools instead of problems
This is the most common failure pattern by far.
A business owner sees a "workflow optimization tool" at a trade show or in a web ad. The sales demo looks incredible. They think, "This is going to change everything." They sign the contract. They roll it out. And — nobody uses it.
The reason is simple: they bought the solution before identifying the problem.
Tools are exactly that — tools. A tool only has value when there's a specific problem it needs to solve. But in so many cases, the motivation for buying is "we should probably be doing DX," "our competitors are doing it," or "there's a government subsidy available."
A wholesale company in Hyogo Prefecture implemented a high-end CRM for their sales team. Several tens of thousands of yen per month. But here's the thing — their sales team was five people managing about 200 clients. They'd been handling it fine with a shared Excel file.
The CRM had so many required fields that the salespeople felt like "if I have time to fill this in, I'd rather make one more phone call." Within three months, data updates had stopped. Within six months, they cancelled the subscription. The only lasting result was a false lesson: "IT tools don't work for us."
What they should have done: Start by mapping out where the real bottleneck in the sales process was. Maybe the issue wasn't client tracking at all — maybe it was that creating each quote took 30 minutes. Or that deal history was scattered across individual notebooks, making handoffs impossible.
When the problem is clear, the right tool becomes obvious. And in many cases, the answer isn't a feature-rich CRM — it's something much simpler.
Reason 2: The big bang approach
There's a trap that business owners fall into once they've committed to DX: "If we're going to do this, let's do it properly." "No half measures."
I get it. As a leader, when you decide to transform, you want to think big. But this "all at once" approach is one of the biggest reasons DX projects collapse.
Here's why.
First, people have a limited capacity for change. Humans can barely adopt one new habit at a time. Yet companies will announce: "Starting next month, the ordering system is changing, expense reports are going digital, all meetings will be online, and documents are moving to the cloud." Veteran employees understandably panic.
Second, when multiple systems are introduced simultaneously, troubleshooting becomes impossible. When something goes wrong, is it the new system? A configuration issue? A gap in the operating procedures? Nobody can tell. The result is a mess where everything is half-working and fully confusing.
And most critically, people are being forced through massive change without ever tasting success. When the prevailing feeling becomes "DX is just a hassle," every future improvement proposal hits a wall of resistance.
Nearly every success story I know started small.
An accounting firm in Osaka chose "digitizing invoices with automated delivery" as their first DX step. The task that used to take two full days every month-end — printing, stuffing envelopes, mailing — became a single button click.
The staff reaction was dramatic: "Month-end isn't terrifying anymore." That small win created genuine enthusiasm for the next improvement. Today, they've also moved attendance tracking to the cloud and shifted client document sharing online. But none of it happened at once — it was one change at a time, each one adopted before the next began.
Reason 3: Dumping it on "the IT person"
There's a scene that plays out in small businesses everywhere.
The president announces: "We're doing DX." Then turns to whoever in the company is best with computers and says, "Handle it, would you?"
That "IT person" usually has a full-time job already. They were nominated simply because they happen to be good with technology. No budget authority, no decision-making power, no vision — just a vague mandate to "make things digital somehow."
This never works.
DX is not an IT department project — it's a business strategy. Which processes to change, where to invest, how to communicate with employees, how to measure outcomes — these are all management decisions. They have nothing to do with how good someone is with computers.
What makes it worse is how miserable it is for the person who gets dumped on. They have their real job to do, but now they're also responsible for researching, selecting, implementing, and training on new tools. They don't have the authority to coordinate across departments. If things go wrong, they take the blame. It's not empowering — it's a stress trap.
In companies that succeed, the business owner personally defines what problem needs solving. They understand the specific operational pain, and they make the decision: "We're fixing this." Tool selection and technical implementation can be delegated to specialists, but the "why" stays firmly in the owner's hands.
One staffing agency owner in Osaka can't configure a system to save his life, but he could clearly articulate: "Shift scheduling takes 20 hours every month. I want to cut that in half." Because the goal was crystal clear, we could make the right recommendation, and measuring results afterward was straightforward. The outcome: shift scheduling dropped to 8 hours per month.
The one thing successful companies do differently
Flip the three failure patterns around, and a single common thread emerges among SMBs that actually succeed at DX.
They pick the single most painful workflow and focus exclusively on that.
That's it.
"The most painful workflow" is easy to find — just ask your employees. "This is the task I dread every month." "I'm working overtime because of this." "We keep making mistakes here and it's hurting our clients." Those voices are always there.
For that one workflow, get the numbers. How many hours per month does it take? What's the error rate? What does that cost?
Then fix it. Not with a grand enterprise system — with a solution that fits the specific problem.
After the improvement, measure the impact. How much time was saved? How did errors change? How do employees feel about it?
Only when you have those numbers do you move to the next step.
The beauty of this approach is that ROI is undeniable. There's no "we did DX but we're not sure what changed." The results are visible in hard numbers, which makes the next investment decision easier. And because the team has a genuine success story — "that last improvement actually helped" — they're open to the next change instead of dreading it.
DX isn't a megaproject
If you've read this far, you've probably noticed something. The DX we're talking about isn't a multimillion-yen system overhaul.
It's about finding the daily "this is inefficient" and "this is wasteful" moments in your operations — and eliminating them, one at a time. That's what digital transformation actually means.
At SolidTech, we always start by looking at our client's actual workflows. We don't talk about technology. We start with one question: "Where does it hurt?"
Then we propose the single highest-impact improvement, start small, and measure results. If it works, we expand. If it doesn't, we adjust course.
You don't need to gamble two million yen all at once. Just start by telling us the one workflow that's causing the most pain. From there, we can map out a DX path that actually fits your company.
