On most projects, you decide how much risk you’re willing to carry and the schedule follows. Every so often a project arrives where that order is reversed – where the clock is fixed, immovable, falling, and the only question left is how much risk you’ll accept to meet it.
NASA has one of those right now. The Swift space telescope, twenty-one years old and built for around half a billion dollars, has no engine. Its orbit is decaying. Without intervention it falls into the atmosphere and is gone, sometime late this year. So NASA did something unusual: it hired a small Arizona company to build a robotic spacecraft, from a clean sheet, that will fly up, grab a telescope never designed to be grabbed, and push it to a higher orbit. The build went from nothing to bolted-onto-a-rocket in about eight months. As I write, it hasn’t launched yet. It’s scheduled to go up on the very last rocket of its kind.
One of the engineers said something that should be pinned above every project director’s desk. “We’re in an unusual situation where the schedule dictates how much risk we’re willing to accept, rather than the other way around.”
That sentence is the whole lesson. And the reason it matters is that most project disasters come from accepting that trade by accident. You don’t decide to cut testing. You just run out of time, and the testing quietly doesn’t happen, and nobody names it. The risk gets taken, but in the dark, by omission, so that when it bites, everyone is genuinely surprised. They shouldn’t be. They chose it. They just never said so out loud.
What NASA is doing is the opposite, and that’s why it’s worth studying even if it fails. The risk here is enormous and it is being taken with eyes open, on the record, with named people saying “high-risk, high-reward” into a microphone. The project has looked at the falling clock, decided the asset is worth saving, and consciously traded caution for speed. That is a legitimate project decision. Running out of time and pretending you didn’t make a decision is not.
Hold this story next to a project that rushed and regretted it – the rail project that pulled a thousand kilometres of cable before the design was set. On the surface, both are projects accepting risk to beat a clock. But one is deliberate and one is delusional. The rail team rushed to feel like they were moving and created the delay. NASA is rushing because the telescope is genuinely falling and there is no slower option that ends well. The difference isn’t speed. It’s whether the project chose the risk on purpose.
There’s a second idea worth carrying off this one, quieter but useful. NASA is recovering an asset rather than replacing it. Boosting Swift costs a fraction of building a new telescope. On our own projects we’re often too quick to scrap and restart the thing that’s struggling, when a fast, well-judged intervention would have saved it. Recovery can beat replacement – but only if you move before the orbit decays past the point of return.
So when your project hits one of those rare moments where the deadline genuinely cannot move, don’t pretend you have options you don’t. Look at the clock. Decide what risk the prize is worth. And then say it out loud, in the room, on the record, so that everyone is carrying the decision together. The danger was never the risk itself. It was taking it without anyone admitting they had.
Note: as of writing, this mission is planned, not proven. It may yet fail. That doesn’t change the lesson – it sharpens it. NASA accepted the risk knowingly. That’s the point.
Leave a Reply