Skip to content

Is Your Project at Risk?

This is a check on whether a software build you’ve got in flight is quietly heading for the rocks, while there’s still time and money to change course. You answer a set of questions about how the project is going — whether dates keep slipping, whether you understand what’s actually been built, whether scope keeps growing, whether you can still get a straight answer about status — and you get an honest read on how much trouble it’s in. The point is to catch it early. By the time a stalled project is obvious to everyone, the expensive part has already happened.

How to read your result

A high-risk result rarely means the code is bad. It means the signals are bad — and the signals go red long before the build does. The pattern is always the same: dates that slip a week at a time so no single slip looks alarming, a growing gap between what you were promised and what you can actually see working, and status updates that get vaguer the more you ask. None of those is a technical problem on its own. Together they’re the early shape of a project that’s losing its grip, and the read is meant to surface them before the budget’s gone.

A clear, low-risk result is worth trusting and acting on by not acting: it means leave the team to work. The most common own goal I see from worried founders is interrupting a healthy build with panic — adding oversight, demanding rewrites, reshuffling scope — and turning a project that was fine into one that isn’t. If the signals are green, the right move is to stay out of the way. Don’t manufacture a crisis because a project is taking the time it always honestly needed.

The middle band usually means one specific thing has drifted — scope that’s crept past the original plan, or a key decision nobody’s actually made — rather than a project in genuine trouble. That’s recoverable cheaply, and quickly, if you name the one thing now instead of waiting for it to compound.

What I’d do about it

If it came back high-risk, the instinct to either panic or look away are both wrong, and they’re the two most common reactions. The move is to get an independent, honest read on the actual state of the build — not the status report, the real thing — before you spend another month’s budget. That means someone senior looking at what’s been built, how far it really is, and what it’ll genuinely take to land it. Most projects I’m called into late could have been saved cheaply if someone had pulled that thread three months earlier. The fix for a project already in trouble is project rescue — getting a stalled, over-budget, or quietly-on-fire build back on the rails.

There’s a worldview thread worth naming here, because it’s behind a lot of high-risk results: projects most often go wrong when they got too big and too rented. An over-scoped build trying to do everything at once, or one wired so deep into a platform or vendor that nobody fully understands or controls it, is far more likely to drift than a lean build of the thing that actually matters. The MVP-first instinct isn’t just cheaper — it’s lower risk, because a small, owned, well-understood build has fewer places to hide trouble. If your project’s at risk partly because it ballooned, the recovery usually involves cutting it back to the version that should have been built first.

If you scored low, you’re done. Close the tab and let the team build.

Talk it through

If the result was worse than you wanted to admit, the worst thing you can do is wait for it to get more obvious. Tell me about it — a short, honest conversation about where the build actually is usually tells you whether it’s a wobble or a real problem, and that’s the difference between a cheap correction and an expensive one.

If you want to look deeper at why it’s drifting, the architecture risk assessment checks whether the foundations are part of the problem, and the tech debt calculator shows whether accumulated mess is what’s slowing it down — both part of my diagnostics. And if rescuing it properly turns out to need a whole team to take the build over and run it, that’s what my agency, Digital Royalty, is for.