“Failure is not fatal, but failure to change might be.”
John Wooden.
An attribute of many games is the ability to fail, get back up and try again in a slightly different way. If you fail again, you keep getting back up and trying again in slightly different ways, getting better at the game each time.
If you’re an operator, does your OSS allow you to do this – to fail and improve? When a new OSS is released into a customer’s production environment, many operators are petrified of making mistakes using tools that they’re still quite unfamiliar with.
You have to let them play the game, knowing that if they die, they will re-spawn and try again, getting better each time. I believe the best way of doing this is to provide a non-production environment for operators to play on before going live. That way they feel less threat of failing, but still get the chance to learn from mistakes.
Have you ever had an OSS or BSS project that’s impacted by poor data quality? The problem of data integrity gets raised on almost every
“One of my favorite things about designing software is designing the defaults. The defaults define the experience for everyone out of the box. And, therefore,
Have you ever been tasked with mapping out the processes for the telco you work for? Either as a way of documenting current state, or
In the last week alone, I’ve had two potent reminders that the world of OSS is simply (pun intended) too complex. This manifests in many
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
