What technical due diligence actually reveals
Most technical risk in a deal isn't sitting in the codebase. It's in the gap between what a team believes they've built and what they've actually shipped.
Product
Insights
Learning in public.
Writing on product, design, engineering, AI, leadership, and private equity, from inside the work rather than above it.
Design
Design systems are infrastructure, not decoration
A design system that only ships components is only half finished. The other half is the governance that keeps it honest as the product grows.
Leadership
What embedded leadership actually looks like
Not a workshop. Not a deck at the end of a sprint. A seat inside the team, accountable for what ships, for as long as it takes.
Nothing under this topic yet. More writing is on the way.
Have something worth writing about?
Send it over →