“We don’t know who discovered water, but we know it wasn’t a fish.”
Marshall McLuhan.
If you’re completely immersed in your environment and you don’t push beyond its boundaries, it tends to become invisible, just as water is to a fish. And if it’s invisible, there is no sense of a need to improve that environment
Unfortunately, many OSS developers don’t seek a perspective from outside their fishbowl. They don’t spend time alongside their customers and definitely not alongside their customers’s customers. They don’t seek out insight from parallel industries (eg ITSM and DCIM), competitor products or completely left-field learnings.
Credit where it’s due – they do often seek innovation in development and test environments. Unfortunately, I’m not completely convinced that this area of innovation leads to ground-breaking improvements for OSS if there is a “more of the same” thinking with regards to the user experience.
When was the last time you were wowed by a new OSS product, wowed by it’s totally different approach and corresponding usability improvement?
Where are you getting your alternative perspectives from to ensure that the revolutionary changes occurring within our environment don’t remain invisible?
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.
