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!!
Over the years, I’ve often referred to The Corkscrew Analogy or Momentum Spiral to describe a mindset of incremental improvement that’s needed to keep an
We’ve embarked on a journey of trying to plan for the future of OSS/BSS, not by predicting the future, but by seeking ways to be
As discussed in the previous article, “Future Scenario Planning: Have you given up on doing an OSS transformation? (part 1)” part of the fun of
Earlier in the week, a friend mentioned he was reading “Alchemy” by Rory Sutherland. It’s not an OSS book per se, but does provide some
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.
