“To be trusted is a greater compliment than being loved.”
George MacDonald.
In yesterday’s blog, we spoke of the shades of grey that different users feel on the spectrum of free services versus secure/private services.
We also spoke of the potential strategic advantage held by many traditional CSPs compared with their relatively newer Internet (OTT) equivalents – the advantage of a having a trusting customer base.
I wonder whether our BSS / OSS could potentially help leverage this even further? Do any CSPs provide complete transparency to their customers, providing a user portal that allows their customers to control what data is visible and to whom, as well as seeing how it’s been used and by whom? A PDB (Privacy Database) as it were.
Extending this concept further, could CSPs become a privacy abstraction layer between users and applications (eg made by OTT start-ups), whereby the CSP shares their subscriber base (another of the traditional CSP’s massive assets) with the start-up, but protects their customers’ data from unscrupulous data policies by the start-ups? A walled garden of big trust maintained by the CSPs.
Is this feasible (I can envisage a few potential road-blocks to overcome already)? Do any customers even want it or need it?
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.
