I’m drawn to leaders who’ve built both high-performing engineering organizations and durable products. Tido Carriero, the Chief Product Officer at Segment, a customer data platform which was recently acquired by Twilio, exemplifies that trajectory. Before that, he built out the engineering teams that worked on the core product and the initial business product at Dropbox. Tido started out his career in 2008 as an early member of the Facebook ads engineering team, and went on to become an eng manager on the Pages team — a pivotal IC to leadership transition that resonates with many of us in product and engineering.
What stands out in his journey are pragmatic lessons on building engineering orgs and launching new product lines at several top tech companies. His reflections on the pros and cons of single threaded leadership and the black box analogy for assessing a team’s performance offer concrete ways to interrogate how work actually gets done. In my own practice, I pair these lenses with outcomes vs output OKRs, tight product roadmapping and sprint planning, and a clean operating cadence that links QBRs vs OKRs. Together, these mechanisms create clarity in org design, planning, and execution — and make performance visible without micromanaging.
For new engineering managers and new managers-of-managers, I appreciated the practical “gems of advice.” That IC to manager transition is rarely linear; success hinges on shifting from personal velocity to organizational throughput. I coach first-time managers to build credible operating systems early: explicit decision rights, transparent prioritization, and lightweight feedback loops. One simple ritual I rely on is a weekly narrative update that forces crisp, outcome-focused thinking — a habit that complements any try do consider framework a team may use.
We also explored the path to product/market fit, especially for multi-product strategies — an area where many B2B teams struggle. Tido shares his advice for going from zero to one in a new product, including the simple milestone his teams have to hit before he’ll greenlight a new project, why he prefers iterative approaches over “big bang launches,” and his thoughts on why Dropbox struggled here. My own playbook mirrors this: invest in fast product discovery, define a clear gate tied to must-have user behavior, and resist vanity launches until repeatable pull exists. Small, well-instrumented bets compound; “big bang launches” rarely do.
If you want to go deeper on finding product/market fit in the context of multi-product strategies, Tido shares more of his thinking here: https://segment.com/blog/finding-product-market-fit-again/. It’s a useful companion for leaders calibrating zero-to-one efforts alongside an at-scale core business.
The through line across these lessons is disciplined simplicity. Whether you’re architecting engineering orgs, coaching the IC to manager transition, or charting zero to one in a new product, choose mechanisms that surface reality quickly, reward learning, and keep teams focused on outcomes. That’s how world-class organizations build, ship, and iterate their way to enduring product/market fit.
Inspired by this post on First Round.
Leave a Reply