C-TPO

Coming up · On the list · Site + LinkedIn

What to build, and who builds it

Product and delivery are both hard, and you never do either one alone. Everyone on the team comes from somewhere different and wants something different, and getting them pointed the same way is most of the job. Also, why is “how long will it take” always the first question?

A few things I want to get into. You can do the work perfectly and still lose money, because effort is what you spend, not what you get. “How long will it take?” usually gets asked before “What is it worth?”, which anchors the decision on cost. Estimating is real work that nobody budgets for. And ideas often arrive as a solution rather than a problem, so we end up measuring the wrong thing precisely.

This one is still being written. If you've lived this, or see it differently, I'd like to hear about it on LinkedIn. And if you want to know when it's up, the email list below is the easiest way.

← Back to everything coming up

Get new posts by email

Just new writing, when it's ready. No spam, nothing else. And if you reply to one, it comes straight to me.

For people short on time

TL;DR

Matt thinks out loud here about technology, mostly how teams decide what to build, fix and protect.

The first series argues that security gets better fastest when the teams that each hold part of the answer share it earlier. The newest piece, Clay first, chisel later, is about roughing out the whole thing before polishing the parts.

Every piece says how much AI helped, and the site changes in the open. The discussion happens on LinkedIn.

Start with Part 1 →
AI score 2/4 me. Idea 1.5/2 · Words 0.5/2. AI drafted these from what's on the site; I haven't rewritten them yet

Updated October 13, 2026. A TL;DR for the whole site, by reader, is an idea by Matt at ctpo.io. Copy it freely, just link back.