The Tool Isn't the Problem: What It Means to Be a Creative Solutionneur

I spent 15 years writing the SOPs, training guides, and onboarding docs that were supposed to make new systems make sense to the people actually using them — at a dental group, a home health agency, a plumbing company, a student loan servicer. Different industries, same pattern every time: a new tool would get rolled out to solve an operational problem, and somewhere between the pitch deck and the people using it every day, the human part got lost.

If you've ever stared at a screen wondering why the software that was supposed to save everyone time is creating more headaches instead, you've seen this pattern too. It's one of the quieter, more common frustrations in the modern workplace.

The numbers back this up, though not the way you usually hear them cited. McKinsey's 2018 global survey found that only 16% of digital transformations both improved performance and kept the improvement — most either didn't work or didn't stick. Boston Consulting Group found something similar in 2020: 70% of digital transformations fell short of their stated goals, though most of those still created some value along the way. (The "70% fail outright" version you'll see everywhere doesn't actually trace back to a real study — worth knowing if you're the one being handed that stat in a sales pitch.) Either way, the honest numbers still say the same thing: most digital transformations underperform, and it's rarely the technology itself that's the problem.

That's the gap a "Creative Solutionneur" is built to close.

It's not a technical skill. It's a way of looking at problems.

A Creative Solutionneur isn't a tech wizard or someone who treats people like data points. It's someone who treats the digital world — the apps, the workflows, the screens — and the operational world — the habits, the energy, the daily reality of doing the job — as two halves of the same thing. Change one without accounting for the other, and you get exactly what those numbers describe: a tool that works on paper and fails on the floor or in the field.

In practice, that mindset asks different questions than the ones a rollout plan usually asks:

• This tool can automate our emails — but does it make the customer service team feel disconnected from the people they're helping?
• This new process is efficient on a whiteboard — but does the team's current setup actually support it, or does it break by day three?

Those aren't technical questions. They're operational ones, and they're the ones that usually get skipped.

Check the soil, not just the leaves.

Once you start asking those questions, you stop seeing your organization as a machine with broken parts and start seeing it as a system where the parts feed each other. If a branch looks unwell, painting the leaves green doesn't fix it — you check the soil. The digital tools feed the daily operations. The daily operations determine whether the tools actually get used.

True innovation isn't about adding more technology. It's about removing the friction between how people work and how the tools assume they work.

If you're the person who pauses a meeting to ask, "Wait — how is this actually going to feel for the team on the floor?" — you're already doing this. It doesn't take a title or a budget. It takes the willingness to check both things at once, every time, instead of assuming the tool will take care of the rest.

That's the same instinct I bring to the writing and documentation work I do now — not just building the thing, but checking whether it actually holds up against how people work and live. If that's useful to you, let's start a conversation.

---

Sources

• McKinsey & Company, "Unlocking success in digital transformations" (2018 Global Survey)
• Boston Consulting Group, "Flipping the Odds of Digital Transformation Success" (2020)