# The Transformation Succeeded. The Industry Didn't.

> The hardest builds of my career did exactly what they were supposed to do, and were still undone by forces nobody in the building could touch.

Published: 2026-08-06 · Updated: 2026-06-26 · Topics: Digital Transformation, Growth Leadership, Enterprise · Author: Alan Wizemann

I have spent most of my career telling people that if you do the work right, the outcomes follow, and for a long time I believed that was the whole story. You find the real problem, you build the thing that solves it, you watch the metrics move, and you take the win. What I did not say often enough, because it is the part nobody puts on a slide, is that some of the best work I have ever been part of did exactly what it was supposed to do and still did not survive – not because of the people, not because of the process, and not because of the technology, but because of forces in the industry around it that nobody in the building had any control over, and those are the ones that stay with you long after the wins have blurred together.

Let me give you the one I think about most. We built a platform in the oral-care world that, on paper, looked like about the best version of itself you could imagine. It drove people who owned a connected toothbrush back toward their dentists, and it put brushing-pattern data into the hands of insurers in a way that could genuinely lower the cost of care over time, which is not a small thing when you sit with it. You are talking about a closed loop between a consumer device, a clinical relationship, and the economics of an entire category, and when it was working it really did look like the largest oral-care platform that could plausibly exist.

Then it hit a wall, and the wall had nothing to do with the team. The question that stopped us was not "is the product good," because it was. It was "how do you get tens of thousands of dentists to sign up." What sales force does that actually take, how long does it take to build, and can a company carry the weight of that operation on the margins of selling hardware? The barrier was never the people or the technology. It was the economics of scaling something that big, and the appetite of the people funding it to keep going long enough to find out. The build was right, and the bet simply ran out of room before the math could catch up to it.

The other one is more recent, and in some ways harder, because it ran for longer before it turned. At Southern Glazer's we launched a B2B platform that drove very large growth over a couple of years, alongside sales tooling that meaningfully raised the rate at which our people closed deals (I will keep the actual numbers out of it, but they were the kind of numbers you build a strategy around). By every measure I am supposed to care about, it worked. The transformation did what we said it would do.

And it ran straight into an industry that is shifting underneath everyone in it at once. This is a post-pandemic beverage-alcohol world where younger generations are simply drinking less than the ones before them, where pressure is coming in from THC and from a dozen other directions nobody fully has a handle on yet, and where the ground does not hold still long enough for any single product to outrun it. The image I keep coming back to is that you are patching a leaky boat, and you can be very good at patching leaky boats, but there is no amount of duct tape that helps when the entire thing underneath you is coming apart. I have had to unwind teams I built and products I was proud of, not because they failed at what they were built to do, but because succeeding at it was not enough to counteract a market that was moving the other way faster than we could.

These are the rough ones, and I want to be honest about why. It is one thing to lose because you got something wrong, because then there is a lesson, a thing to fix, a better version of you that walks into the next room. It is another thing entirely to do the work right, to watch it do precisely what you promised, and to lose anyway because the world the thing landed in was not the world it was built for. There is no clean lesson in that. You do not get to walk away feeling smarter, you just get to walk away.

So what do I actually take from all of this, after a few of them? I think the first thing is a kind of humility about the limits of execution, which is uncomfortable for someone whose whole identity is built on executing. Doing the work right is necessary, and it is most of the job, but it is not a force field. You can be entirely correct about the problem, the solution, and the customer, and still be operating inside an industry whose math is quietly changing under your feet in ways that no roadmap accounts for. The second thing, which is harder to act on, is that the size and durability of the wave underneath you is itself a thing to read, as carefully as you read the customer, because a transformation that succeeds in a category that is shrinking is a different bet than the same transformation in a category that is growing, even when the build is identical.

I do not have a tidy bow for this, and I have stopped looking for one. The honest version is that some bets do not survive the world they land in, and no amount of getting the work right changes that. What I have made my peace with is a smaller, truer claim than the one I used to make. Sometimes the most you can say is that the build was right, that the teams did everything you asked of them and more, and that the bet simply did not survive the forces around it – and on the rough ones, that has to be enough, because it is the only part that was ever really yours to get right.

---
Canonical: https://alanwizemann.com/articles/transformation-succeeded-industry-didnt