Yes, that Arnold Schwarzenegger.
He has a newsletter on beehiiv. So do Codie Sanchez, Jay Shetty, David Begnaud, Colin & Samir, and Joanna Stern.
They could publish just about anywhere. They chose beehiiv to build a direct connection with the people who want to hear from them most. And you can do the same, whether you’re world-famous or just at the start of your plan for world domination.
The best sign a tool is working is someone saying "look what I built." The best sign it's finished is the same person saying it about something else.
Last week asked which human reviews the AI. This week asks how long a tool lives after the person who loved it moves on. Here is the case, and what I would do about it.
What a Champion Looks Like
I judge a champion by a few things. They take part end to end. They advocate for the change. They're flexible with technology benefits … and faults. And they aren't afraid to give feedback, including the uncomfortable kind, in professional and respectful ways.
The more someone takes part, the more they see where the platform is headed and why. The strategy behind the choices. The more they push back and complain, the less of a champion they are.
The tell is simple. A champion says, "Look what I built with this." They're proud of it. They keep coming back, build more, and try new things, sometimes things that have nothing to do with work and only make their day better. When you see that sparkle of ownership, they're all in.
They vouch for it, too, to their peers, to their manager, and up the chain.
But what happens when all that changes?
How It Ended
We had a tool with one of those champions in front of it. It did what it promised.
Then, in this order, three things happened. First, the "look what I built" kept coming. Second, something newer showed up. Third, the funding and support dried up.
The champion never left. Their focus did. They preferred to build things themselves rather than pay someone else to, and one day they showed me what they'd made. It took the premise of the original tool and extended it, and they were more excited about it than they had ever been about the original.
That was when I knew. Not the usage numbers. The license was still active. The enthusiasm had been reassigned.
The tool sat on the shelf like a toy that got replaced by a newer one. It wasn't broken. Nobody picked it up.
Nobody was blamed and nobody was embarrassed. The hard part was a difficult conversation with the others who had helped build it.
What I Took From It
I talked with those groups afterward to find out why they had moved on. There wasn't one specific reason. They felt they were moving beyond what the tool offered. We debriefed, and we reflected on how to be ready if a decision like this came up again, so we spend only what we need to.
I think it was experimentation of the best sort. We failed fast, found what we needed, and moved on to bigger projects and better technology, guided by what we'd learned.
That only worked because we saw it early. A tool's budget rests on one person's excitement more often than we admit, and excitement moves first.
Three Moves
Here is what I would do. I haven't run a clean test of it.
Ask the horizon question at kickoff. How do you see this tool in one year, three years, five? Will you extend it yourself? Will the vendor? Or is it a one-trick pony we'll replace once the newness and polish wear off? Write the answer down and ask it again later.
Watch what the champion builds, not just who logs in. When "look what I built" is about something else, you have your answer. Make the decision while the funding still exists, so it's a plan and not a drift.
End it on purpose. Tell the people who helped build it first. Debrief without blame: what it was for, what you learned, what you keep. Failing fast only counts if the lesson gets written down.
One caution: this is one tool and one champion. Treat it as a pattern worth checking for in your shop, not a law.
Try This Monday
Twenty minutes, on tools you've rolled out in the last couple of years.
List every tool you own that someone championed. For each one, answer two questions:
Who is the champion? A name, not "the team."
When did they last show you something they built with it? Not "are they still logged in." Did they show you anything?
When you finish, you'll have two numbers:
Named: how many tools have a champion with a name next to them.
Still showing: how many of those champions have shown you something in the last quarter.
Here's an example. You list 8 tools. 5 have a named champion. Of those 5, 2 have shown you something recently. Your result is "5 of 8 named, 2 of 5 still showing."
The gap is where a tool is running on momentum. For every champion who has gone quiet, ask the horizon question. You might learn what they're building instead.
Who's Still Showing?
A tool lives as long as someone is excited to show it off.
Most budgets are written as if the tool were the asset. The asset is the attention. A license renews on a date printed in the contract. The day a champion stops showing you what they've built isn't on any calendar, and no dashboard reports it.
In my case, no report flagged anything. The signal came in a conversation, and the license was still active when it did.
A champion who moves on has also left you something. Their build is a free requirements document: what they wished the tool did, and what they cared enough to spend their own time on. I'd ask to see it, ask what the original couldn't do, and keep the answer for the next evaluation.
None of this makes the tool a mistake. Ours did what it promised, it earned its keep while the excitement lasted, and when the excitement moved, the money moved with it. That is how it should work.
Your portfolio has champions in it right now, and some have gone quiet. Go find out what they're building before the renewal date finds out for you.
ACTION ITEM: How many of your tools have a champion who still shows you what they've built? Run the Monday exercise and send me your two numbers: tools with a named champion, and champions who have shown you something this quarter.
Reply, I read every one.
Go hug your ERP. Then ask “What your champions are building?”
Plant Floor to Cloud: The Newsletter goes out every Tuesday. The podcast runs monthly. Same charter, more room to think out loud. Watch or listen on the website, or wherever you get podcasts: Apple Podcasts, Spotify, YouTube, iHeart, and more.



