Why do so many of the new buzz technologies, such as Internet of Things and analytics exist to provide faster / better feedback but OSS generally doesn’t make more use of it?
Sure, we provide dashboards and lists that provide customers with feedback, but are we using feedback enough to make our solutions better?
We don’t use enough of the feedback loops described here (I hope you’ll take a minute to check it out) to constantly monitor and refine the process of using our OSS. This could include data entry, designs, data integrity and constant learning.
We also don’t tend to get enough of an understanding of the when, how, why and how often regarding the use of our tools (and the components within). This could include logging usage patterns or more fundamentally, spending time with customers as they do their daily activities.
For an industry that exists to give feedback, we sometimes don’t make the best use of it ourselves do we?
Do you have any examples where you’ve used feedback to revolutionise the use of your OSS?
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.
