Capability is not a product

I was recently interviewed by Roberto V. Zicari for ODBMS Industry Watch, a publication I follow and respect for the seriousness of its conversations. The full interview is linked at the bottom. But a few things I said there are worth pulling out here, because they are things I keep coming back to in my work and conversations.

The excitement in the room is not evidence.

A team builds something impressive. The demo works. The room is excited. And that excitement starts doing the work that evidence should be doing. The gap between "this works" and "this survives contact with real users" is almost always bigger than the team estimates. And the investment that happens in that gap, the building, the hiring, the storytelling, the executive enthusiasm, makes honest reassessment much harder later.

Speed is not the problem. Confusion about what speed is for is the problem.

There is a real difference between moving fast to learn and moving fast to look like you are moving. Real value shows up later and more quietly: repetition, retention, fewer manual steps, less friction. Those signals take longer to arrive, and they are less exciting in a review meeting, which is precisely why teams stop looking for them.

Technical readiness, operational readiness, and market readiness are not the same gate.

Data declared ready for development is not the same as a model ready for evaluation, which is not the same as a product ready for real users. The demo looking good is not evidence that the product is ready. It is evidence that one path through the system works, under favorable conditions, with someone who knows how to use it.

Some of what is being lost right now will not show up on a dashboard.

We are living through a moment where some of the people with the deepest design, product, market, regulatory, and operating judgment are being treated as more replaceable than they really are. The judgment about what to build and for whom. The ability to read a room, a market, a regulatory signal. The instinct that comes from having been wrong before in expensive ways. That is not nostalgia. It is a capability gap that will show up later and less visibly than a headcount reduction.

Read the full interview here: Impressive Is Not Enough, ODBMS Industry Watch