Just thinking about yesterday’s blog (about how OSS will become Whole of Business Support Systems and what impact that will have on the UI) when something quite simple dawned on me…
In most cases, OSS should be designed to provide answers, not just information.
But in most cases today, the opposite is true. We have user interfaces that show truckloads of information (as per the tongue-in-cheek diagram below)… but not necessarily succinct answers. Working back from that, perhaps we don’t get succinct answers because we don’t have the mechanisms to actually ask human-language style questions.
If we’re to design a more intuitive OSS interface, then we must have an interface that allows us to ask questions and therefore receive valuable answers (assuming the tools are sophisticated enough). Not only that, but if they get really sophisticated (as per the predictive and precognitive buttons at the bottom of the diagram below – tongue-firmly-planted-in-cheek sample again) then they’re telling us answers to questions we hadn’t even thought to ask yet. Now that would be valuable!!
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.
