I'm curious if anyone else has experienced projects or ideas fizzling out because of the uncertainty we face, like wondering if a backup will actually work when we need it, or if our processes will run smoothly every time. There's that constant nagging fear about whether our projects will survive when life gets busy or we step away for a while. While many of us try to tackle these issues with redundancy, monitoring, and policies, sometimes unpredictability can still derail our initiatives. I'm developing a concept that I like to think of as a 'certainty layer'—a way to ensure that our digital goals (whether they're files, processes, or ideas) keep moving forward without the usual guessing game. I'm looking for advice on how to design this system effectively, preferably something that could be summed up as: 'We make sure what you want actually happens because we give you certainty.'
2 Answers
I get you on wanting to tackle unpredictability. But let’s be real, not every problem can be solved by software. The core issue often lies in the management side—bad management kills more projects than anything else, in my experience.
Interesting idea, but I wonder if you’re thinking too far outside the box. Software can improve many things, but not everything could be fixed by just adding a 'certainty layer.' After all, if projects are failing, it often points to poor planning or management issues rather than just technical uncertainty.
That's a fair point. It’s true that management issues can be the root cause of many project failures. However, sometimes tech could offer solutions to help mitigate those risks.
I agree with the management angle, but there’s something to be said for offering a safety net tech-wise. It’s not about fixing management; it’s complementing it by reducing risks.