Impact / Beyond the product
The race to an exit
What happens inside a company racing to build, hire, and show momentum before an IPO or acquisition.
The race
When a company sees an exit on the horizon, everything speeds up. The goal is more customers and more revenue, and the market's sense of momentum matters as much as the product itself.
So teams build as much as they can, as fast as they can, and hiring grows just as quickly. It turns into the Wild West.
What breaks
What I've seen, again and again.
- 01Teams stop talking to each other.
- 02Experiences that were already decided get built again.
- 03New pieces appear that already exist somewhere else in the product.
- 04The rush shows up in the product, in front of paying customers.
- 05After the IPO or acquisition, there's a lot of cleanup.
What I do
I'm not a waterfall guy. This isn't about slowing the race down.
It's the stage where design operations has to step in. Not to dictate or play big brother, but to record decisions and show each team where its choices affect parts of the product it never sees.
That record pays off later. When the race slows down, at or just after the IPO, the adults in the room have to clean up the mess and the debt it left behind. Without a record of what was decided and why, the product's ethos gets lost, customers feel it, and the cleanup takes far longer.
The 12 companies
I've worked with 12 companies that went on to IPO or acquisition, often during this race.
- New RelicIPODev tools
- ElasticIPODev tools
- NutanixIPOCloud
- PivotalIPO, later acquired by VMwareCloud
- UdemyIPOLearning
- CylanceAcquired by BlackBerryCybersecurity
- SourceClearAcquired by CA TechnologiesCybersecurity
- CliQrAcquired by CiscoCloud
- QuipAcquired by SalesforceComms + Collaboration
- AppceleratorAcquired by AxwayDev tools
- SugarSyncAcquired by J2 GlobalCloud
- CollabNetAcquired by TPG CapitalDev tools
Related thinking
What I've learned from this work.