Product delivery and engineering leadership

How product teams ship and keep shipping: what separates an MVP from a lovable product, how team structure shapes the system, how to keep decisions when people leave, and when open source is the safer choice.

PRODUCT ENGINEERING01

Product Development Isn’t a Straight Line, and Ignoring the Loops Costs You

Product development is often drawn as a straight line of stages, but validation and testing routinely send work backwards. Those loops are cheapest when they come early, and a stable product with proven demand rarely triggers them.

AUG 19, 2026 · 4 MIN READ
ENGINEERING PRACTICE02

Redis and Terraform Left Open Source the Same Way. Only One Came Back.

Redis and Terraform both left open source for a more restrictive licence within months of each other, and outside groups copied each one within weeks. Only Redis came back; for Terraform, the copy became the lasting open version.

AUG 19, 2026 · 8 MIN READ
ENGINEERING PRACTICE03

Conway’s Law: Your System Is Shaped by Who Actually Talks to Whom

Conway’s Law says a system’s architecture ends up mirroring how its teams communicate, whatever the org chart on the wall says. The fix is mechanical: make approvals, deploy access and the on-call rota match how teams work.

AUG 19, 2026 · 5 MIN READ
PRODUCT ENGINEERING04

MVP, MLP, MMP: The Names Don’t Matter. What Changes Under the Hood Does.

Every stage in this ladder gets defined by what a user sees. The expensive part — what a system is allowed to fake, and what it has to stop faking — is architectural, and almost never written down.

AUG 16, 2026 · 9 MIN READ
ENGINEERING LEADERSHIP05

The Half-Life of an Engineering Decision: Institutional Knowledge and Continuity

Every workaround has a reason nobody wrote down. When the person who knows it leaves, the reason leaves first — the code stays behind and quietly stops making sense. What continuity is actually worth, in mechanism rather than platitude, and the honest case for when it isn’t.

AUG 14, 2026 · 8 MIN READ