How can we reduce the size of the OSS buyer-seller chasm?
Our previous post highlighted a chasm between buyers and sellers. It has sparked quite a lot of conversation, which is exactly as intended. In another
“There are no exceptions to the rule that everybody likes to be an exception to the rule.”
Charles Osgood.
When it comes to customer experience management at a CSP, Charles Osgood’s statement rings true. A friend of mine recently talked about the challenge of solution design where “Everyone is an exception.”
When it comes to designing OSS systems and processes, too many engineers / analysts treat Osgood’s statement as gospel, that every single exception has to be handled as part of the rule.
There are too many OSS that have the rule (ie the ~80% of cases in Pareto’s 80/20 rule) bogged down by designing processes to handle all the exceptions (ie the 20% of cases).
My preference is to streamline the normal (ie the 80%) and hand off exceptions to special resolution processes. I also try to suggest / impose ruthless simplification and standardisation where possible to ensure that there are less variations of exceptions to be handled.
Our previous post highlighted a chasm between buyers and sellers. It has sparked quite a lot of conversation, which is exactly as intended. In another
I’m currently lucky enough to be involved in a couple of vendor selection processes where we’re helping carriers (buyers) to find the best-fit OSS vendors
There aren’t a lot of podcasts out there that specialise in OSS (apart from ours of course), so I tend to listen to a lot
As you may have noticed, we recently launched a new report, “The Future of AIOps: A Definitive Guide.” In the rapidly evolving landscape of carrier
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.