Surviving Failing Software Projects: Signs, Survival, and Sanity

There are failing projects… and then there are “brace for impact, grab your life jacket — the captain thinks the iceberg is optional” projects.

Failing software projects often follow the same pattern — warning signs appear early, but are ignored until it’s too late.

You know the type.
Costs spiral. Deadlines multiply like rabbits. “Must-have features” get quietly pushed into a mythical “phase two” that never arrives. And yet, from the top deck, the message is always the same:

“Everything’s fine, full steam ahead!”

Meanwhile, you’re below deck, scooping out water with a teaspoon, wondering if your LinkedIn profile needs a refresh.

Warning Signs of a Failing Software Project

In reality, these are the warning signs most people see in failing software or IT projects.

How do you know the ship is sinking? Easy. Just look for these universal warning signs:

• PowerPoints get shinier as the project gets shakier.

• Leadership swaps out “working product” with phrases like “strategic alignment” and “future potential.”

• The project plan is now 400 slides long, and still no one knows what you’re actually building.

• Team morale is measured in how much sarcasm can be packed into the daily stand-up.

If you’ve ever thought, “Am I the only one who sees the flames pouring out of the engine room?” — congratulations, you’re on a doomed project.

How to Survive a Failing Project Day-to-Day

So what do you do when you’re strapped to the deck of a slow-motion car crash?

1. Document Everything
   Not just emails. Etch it into stone tablets if you have to. You’ll want receipts when someone inevitably asks, “Why didn’t anyone warn us?”

2. Perfect Your Poker Face
   Practice nodding sagely in meetings while internally screaming. Bonus points for jotting nonsense in your notebook — no one will question “synergy roadmap,” but it makes a great doodle.

3. Redefine Your Goals
   Forget delivering the impossible. Instead, focus on achievable wins:

   • Did you stop yourself from flipping a table? ✅

   • Did you keep the junior developer from quitting today? ✅

   • Did you find a new meme for the team chat that perfectly sums up the chaos? ✅

4. Humour = Lifeboat
   If you can’t fix it, mock it. A well-timed joke in the trenches is worth more than a motivational speech from the captain.

The Emotional Impact of Failing Projects

The hardest part isn’t the failure itself. It’s knowing it’s coming, waving your arms wildly, and watching the “powers that be” blissfully ignore every red flag.

It’s like being on the Hindenburg and whispering, “Is anyone else smelling smoke?”
while management beams and says, “Nonsense! This blimp is the future!”

How to Protect Yourself in a Failing Project

When projects implode, leadership will be “shocked,” consultants will cash their cheques, and someone will quietly bury the lessons learned. But you? You’ll still have your sanity if you protect it.

Remember:

• You didn’t steer the ship.

• You didn’t order “full speed ahead.”

• And when it does go down in flames, at least you’ll have front-row seats to one of corporate life’s greatest comedies.

Because at the end of the day… sometimes the only motivation left is knowing you weren’t the one pressing the big red button.

And sometimes, the hardest part isn’t fixing the project — it’s dealing with the reality that it isn’t going to plan.

If you’re starting to see the warning signs of a failing project, it can be hard to know whether to push on or step back.

I help people make sense of messy situations and work out the most practical way forward.

If something feels like it’s heading in the wrong direction, take a look at my TechFix service.

Switching Off from Work Properly: My Holiday Routine (Even at Home)

When I take time off work, I take it seriously. Whether I'm heading away or having a holiday at home, I disconnect completely—and unapologetically. Working in IT, the lines between “on” and “off” can easily blur, especially when you have access to everything from your phone or laptop. But over time, I’ve learned that proper rest requires firm boundaries. So I’ve built a routine that helps me truly switch off, and here’s how I do it.

Switching off from work properly—especially when working in IT or from home—is harder than it sounds, but it’s essential for avoiding burnout and staying effective long-term. 

These are the practical steps I use to fully disconnect from work during time off.

1. Set Clear Out-of-Office Boundaries

I don’t send vague “I’ll get back to you when I return” messages. My out-of-office email reply makes it clear:
I am out of the office and cannot be reached.

I also provide the correct route for urgent support—usually pointing people to the help desk or main IT contact number. I do this for two reasons:

• I’m not being paid to monitor or respond to work while on holiday.

• There are capable teams in place to handle things without me.

Being clear sets expectations and removes the pressure to keep one foot in work mode.

2. Turn Off Work Notifications Completely

I don’t want work chats pinging me while I’m off, especially from apps that live on my personal phone. So I switch off Teams notifications entirely. If it’s urgent, people can go through the proper channels (which, spoiler: they rarely need to).

3. Power Down Your Work Laptop (and Put It Away)

When my holiday starts, I shut down my work laptop completely and physically put it away. Not just out of sight—but out of reach.
This sends a signal to myself: I am not working. I am not available. I’m off.

4. Avoid Your Work Space During Time Off

During workdays, my home office is where I sit and focus. But during time off, I avoid that space completely. I’ve learned that just being in that chair or at that desk can trick my brain into “work mode.” So I reclaim the boundary by physically distancing myself.

If I do need to use a computer—maybe to watch something, browse, or sort personal files—I’ll grab my MacBook and head to another room. That machine has no connection to work, and using it elsewhere helps reinforce the feeling of being off-duty.

5. Why Fully Disconnecting from Work Matters

I believe it's good practice to disconnect completely. Not half-on, not checking emails in the evening, not just “keeping an eye” on things. Fully off.

Because I’m not being paid to think about work while I’m on holiday. And frankly, thinking about it doesn’t help anyone—least of all me.

In many workplaces, constant availability is expected—but it often leads directly to stress, burnout, and reduced effectiveness. But more than that, taking time for myself is a boundary I’ve chosen—and I stand by it.

Final Thoughts

Whether you’re going abroad or taking a quiet break at home, you deserve time that is yours. The emails can wait. The messages can go to someone else. And the world won’t stop spinning if you don’t check in.

My routine may sound strict, but it gives me the space to recharge. And every time I stick to it, I’m reminded: rest isn’t something I need to earn—it’s something I’m entitled to.

If you’re working with systems that don’t quite match how people actually use technology today, I spend a lot of time helping simplify and improve how things work.

You can take a look at my TechFix service if that sounds familiar.