The Dream Is Crumbling. Time to Get Scrappy.

Paul lives on the ninth floor of my building. He called me this week about a voice AI product his team has been building for a restaurant group, thirty stores opening Friday. The dev team had gone quiet. He wanted to know where to find someone to fix it quickly and cheaply.

I told him it was like fixing a tunnel where the two sides didn't meet. On the surface it sounds easy: it's one meter off, most of the work is done. But the meter is load-bearing, the original team is gone, and whoever you bring in now inherits every decision they made without ever having made them. Doable, yes. Quick and cheap, no. Most people I know wouldn't touch it.

He said he's writing the client off.

The people who built that product were probably doing everything right by the measures they were given. Tickets closed, sprints completed, standups attended. Nobody owned the outcome because the system wasn't built for anyone to own it, and when the system runs correctly, that's what you get.

I put the phone down and messaged Alistair.

Alistair is a good front end engineer, the kind who thinks clearly and ships things. I wasn't asking him to join a startup. I was asking him to help Bruce Anderson, a conservative political journalist, build a website and a Patreon so his readers can fund his writing. Two or three hours a week, some admin, some social media, the kind of work that sits just outside the box he's been put in at his day job. The skills were already there. I just needed someone to use them somewhere they hadn't been officially assigned.

His reply: "Sorry pal, I wanna go for senior next year. My work is my main priority."

I said OK, fair, and I meant it. I'll do it myself. But I've been thinking about that reply since, because what struck me wasn't the no. It was how small the ask was and how cleanly the system had taught him to say no to it anyway. Two hours outside the role, skills he already has, helping a real person with a real problem, and the instinct was to protect the promotion path. The risk of the small yes felt more concrete than the risk of the small no.

Andy was made redundant last year and spent three months looking for something new. Genuinely good engineer, the kind who could have taken a swing at building something of his own. He settled for a role that doesn't excite him because three months of visible daily uncertainty was enough and the job was there. The visible risk always beats the invisible one, and the invisible one is still running.

Sorin has been a skilled engineer for years, the kind who could build anything he put his mind to. He told me he's not enjoying his senior position anymore. I told him to start something. He's still there.

Nina is a product person who is very good and very stuck. Same conversation, same answer from me, same timing problem on her end.

I've had some version of this conversation with every one of them in the last six months. Different people, different situations, same answer at the end. At some point you stop thinking it's coincidence and start wondering what the pattern is.

Dobre was our first ever employee. QTT was one of our earliest people and one of the best I've worked with. Both of them are starting something now, both in the last few weeks, going into the uncertainty without a net.

They might fail. I hope they don't. But they're building something the safe path can't build: the tolerance for carrying risk themselves, without a process to distribute it into, without a sprint cycle to reset the clock. That tolerance is a skill. You lose it if you don't use it.

The seniors I've watched thrive through this period are not necessarily the ones who built something on the side. Some of them never left the job. But they were the ones who stepped up when a project nobody wanted was about to go wrong, who became the glue on something that had no clear owner, who decided that filling the gap was better than watching it widen. Scrappiness is not about startups. It's about not waiting for someone to hand you permission to do the thing that obviously needs doing.

You can succeed inside your company and still need this. The title doesn't protect you from the moment when the thing falls apart and someone has to own it. The people who own it are the ones who are still there when the dust settles.

The deal we were sold, those of us who came up through the industry in the 2010s, was that the abstraction was the point. That process was maturity, that titles meant something, that a well-managed career inside a well-managed company was the destination. And for a while the economy was growing fast enough that the gap between that promise and reality stayed invisible.

The gap is still there. The growth that papered over it isn't.

Paul's thirty stores are the loud version, a visible failure with a deadline and a client watching. Most of it is quieter: the senior who's been inside the same abstraction layer for five years and doesn't know what he's lost, the product that ships but doesn't solve anything, the promotion that lands inside a structure that's already quietly contracting.

I don't think we have. I think we need to get scrappy again, not because it's noble, but because the alternative is sitting in the water while it heats and calling it patience.