Listen to this episode on Spotify or Apple Podcasts
There was a time, Michael Ferranti reminds me, when people who loved Sonos would not shut up about it.
He says it almost fondly, the way you’d describe a friend’s old enthusiasm. The rabid fan base. The audiophiles who treated their speakers as a personality trait. Sonos wasn’t just good equipment — it was a great experience, he says, the kind where everything in the house seemed to talk to everything else without you having to think about it. Everything just worked together. People evangelized it.
“At least until a couple of years ago.”
That clause is the whole story, and Michael lets it sit there for a second before picking it back up. He’s the VP of marketing at Unleash now, an open-source feature management company based out of Oslo, and he’s spent well over a decade in and around dev tools and infrastructure — the kind of person who reads other companies’ engineering blogs for fun and remembers what they said. Which is why the Sonos story bothers him the way it does. Because Sonos, by his account, knew better. They had written down exactly how to avoid what they were about to do to themselves.
“From a DevOps perspective,” he says, “they had an internal engineering blog where they were always talking about, hey, we’re on Kubernetes now, we’re using containers, we’re doing CI/CD, we’re doing all these things, we’re monitoring with Datadog.” He runs through the list like a man reading a résumé that should have prevented a tragedy. By every technical measure, this was a company that understood how to ship software safely — incrementally, in small controlled batches, watching the metrics, ready to roll back.
And then, Michael says — and here his voice picks up a particular relish — “probably because of the pointy-headed business people.”
He catches himself. “No offense.” A beat. “People have accused me of being a pointy-headed business person myself, so I say that with love.” It’s a good line, and he knows it, and it does a real piece of work in the story: he is not an engineer taking a shot at the suits. He is one of the suits, indicting his own kind.
What the business people wanted was a moment. A new set of headphones, unveiled to the market all at once. Not just the headphones — a new version of the hardware, a new mobile app, the whole constellation lighting up on the same day so that anyone who owned all of it would have a single, coordinated, mind-blowing experience. To pull that off, they did the one thing the engineering blog warned against. “They held a bunch of changes that they wanted to make,” Michael says, “until this big bang release.”
He pauses, because we both know where this goes.
“Not surprisingly, since I’m talking about it on this podcast” — a small grin in the voice — “the outcome wasn’t everybody loved it and applauded.” He lets the real sentence land flat and hard. “The outcome was it broke everything.”
It took them months to unwind. And the part Michael keeps returning to isn’t the engineering damage, it’s what the engineering damage cost. The thing Sonos had spent years building — that rabid, won’t-shut-up loyalty — “they took this brand loyalty that they had accumulated through blood, sweat, and tears over the last couple of years, and just flushed it down the toilet.” He wants me to know he isn’t reaching for drama. “I’m really not exaggerating. Their market cap tanked.” Over $100 million in lost direct revenue, by his count — and that figure doesn’t even include the market capitalization or the brand equity, the harder-to-tally erosion of all those people who used to evangelize and now just felt burned.
The diagnosis is brutal in its simplicity. They didn’t follow their own blog.
I ask him how that happens. How a company writes the correct playbook, publishes it, brags about it, and then does the opposite. Michael doesn’t pretend it’s mysterious. “When the CEO says jump,” he says, “you say how high.” The blog was true. The incentives were truer. Somewhere above the engineers who knew how to release software incrementally was a person who wanted the splash, the unveil, the keynote moment where everything works at once — and the closer you sit to that person, the harder it is to be the one who says we should do this slowly, in pieces, where it’s less impressive and far less likely to detonate.
This is the failure mode Michael has built his argument around, and the Sonos story is its cleanest illustration. The instinct toward the big bang isn’t stupidity. It’s seductive. It promises that if you can just get the latest hardware and the latest app and the new product to land together, you’ll deliver something nobody could feel any other way. The trouble is what it requires you to ignore. To make the coordinated experience perfect, Sonos effectively told most of its existing customers — the ones a few generations back on hardware — that they weren’t sure how it would work for them yet. “For everybody else,” Michael says, channeling the bet they made, “people that are on four generations ago, we’re not sure how it’s gonna work yet. So we’re not gonna try to do that now.”
You’re either in the mind-blowing experience or you’re a casualty of it. There is no middle setting on a big bang.
What he wishes they’d done instead is the thing his whole company exists to make easy. “What’s the experience that we’re trying to create,” he says, “and how do we know categorically that we’re creating that experience?” You measure the user experience as you roll the products out. You do it in small batches over time. You build a feature, expose it to a few, watch what actually happens, and keep your finger near the switch. Underneath that is the mechanism — feature flags, the ability to turn functionality on and off in production safely, in a controlled way, without a deployment. And the piece he keeps coming back to, the one that would have saved Sonos, he calls surgical rollback. “If ever there’s an issue, you can roll it back very, very surgically.” Not a months-long unwind. A scalpel, applied to the one thing that broke, while everything else keeps running.
Picture the same launch run the way he describes it. The new app goes to internal users first, then to a small group of customers who like being on the latest and greatest, then to one region, then everywhere — each step measured, each step reversible. The hardware reaches the people on current-generation gear first, where the team is confident, before anyone promises a mind-blowing experience to a customer four generations back. Nothing gets held in a vault for a single coordinated detonation. The release stops being one enormous unobserved bet and becomes a series of small observed ones. And underneath it is the way Michael thinks about a feature across its whole life — he watches it travel from an idea to code to the thing a customer can actually touch, and then he decides what happens to it. “Sometimes I kill the feature because it doesn’t work,” he says. “Sometimes I roll it out globally.” A big bang offers exactly one of those endings and quietly removes your ability to choose between them. By the time you learn which one you got, it’s already everywhere, and the only tool left is the months-long unwind.
The deeper point, and the one that makes the Sonos story more than a cautionary anecdote, is about who holds the knowledge versus who holds the decision. The engineers knew. The blog proved they knew. But the call belonged to people optimizing for a different kind of metric — the launch, the narrative, the moment — and the org chart made sure the people with the safest path had the smallest voice. Michael’s case for feature ops is, underneath the tooling, a case for changing that. For giving the people who understand how software actually behaves a real seat when the irreversible decisions get made. “A developer could be like shrug emoji” if you ask them whether to ship to everyone, he tells me elsewhere — not because they can’t answer, but because the question was never fully theirs to answer alone. Sonos is what happens when nobody with the scalpel is in the room when the CEO says jump.
I find myself thinking about the fans. The ones who used to evangelize, who treated the brand as a piece of their identity, who would not shut up about how well it all worked together. A big bang is supposed to be for them — the grand coordinated experience, the payoff for their loyalty. Instead it was aimed straight at the thing they loved most.
Sonos got their market cap back, eventually. The headphones shipped. The systems got unwound. But Michael’s phrasing stays with me, because it names the part that doesn’t show up on a balance sheet. The loyalty, accumulated through blood, sweat, and tears, flushed in a single release.
You can recover revenue. The people who used to not shut up about you are quieter now.
Guest Bio: Michael Ferranti
Michael Ferranti is the VP of Marketing at Unleash, the world’s largest open-source feature management platform, where he leads go-to-market strategy for a company that has more than 500 enterprise customers, 13,500+ GitHub stars, and 35 million downloads. Rising to prominence in the 2010s through a series of infrastructure and developer-tools companies, Ferranti built a reputation as a marketer who can translate technically dense products — container storage, zero-trust access, feature flags — into category-defining narratives for engineering and platform buyers.
Previously, as Chief Marketing Officer at Teleport, the open-source infrastructure access platform, Ferranti joined in late 2021 and led the company’s marketing organization through a period of rapid enterprise expansion. Before Teleport, he spent nearly four years at Portworx as VP of Product Marketing and Corporate Marketing, where he helped build the category around Kubernetes-native persistent storage before Portworx was acquired by Pure Storage in 2020 in a deal valued at $370 million.
Earlier in his career, Ferranti held marketing and product roles at ClusterHQ and at Rackspace, where he worked in the early days of OpenStack and most recently served as head of marketing for Mailgun by Rackspace, the developer email API. A Virginia Commonwealth University undergraduate, he relocated from Richmond, Virginia to the Paris metropolitan area in 2023. At Unleash, he has been part of the team that tripled ARR over three consecutive years, closed the $35 million Series B in March 2026 led by One Peak with participation from Spark Capital, Frontline Ventures, and Firstminute Capital, and expanded the customer roster to include Lloyds Banking Group, Wayfair, Prudential, and Lenovo.
Hey,
Thanks for reading this. I mean that. There's a lot of content out there competing for your attention, and you spent some of it here. I hope it was worth it. Even better, I hope it prompted you to think about something differently enough that you'd share it with someone who'd get something out of it too.
I started this podcast because tactics never stuck with me. What stuck were stories — business biographies, autobiographies, the decisions people made and why they made them. The principle only clicks once you know the story behind it.
So I built the thing I wanted to read. Every week I have two conversations with people who build in technology and product. Then I write the essay I wish I could find — one that puts you inside the conversation, through my eyes. What caught me off guard. What I kept thinking about after we hung up. Where the principle actually lives once you strip away the jargon.
I make this for myself first. If you read the way I do, you’ll want it too.
PS — If you want to pitch coming on the show, or you know someone I should talk to, shoot me an email at caden@hey.com with "January752" in the subject line so it gets past my filters. I'm not optimizing for famous guests. I'm optimizing for interesting conversations, even from people who aren't LinkedIn influencers.
