The following quick checklist will give you a feel for whether your OSS is too complex for general users:
Don’t just estimate, collect actual user experiences / feelings.
Readers of this blog probably tend to spend all our working hours on our OSS, but for many of our users OSS are only a part-time means-to-an-end. Many of the users of our OSS will also be situated in roles where there is high turnover (and therefore high training costs). As such, our user experience design has to assume a lower level of expertise than your peers have.
Now to extend the list above just a little further:
5. How do we use our understanding of item 2 above to monetise our OSS (either internally or externally)
6. Is there a clear association between a customer’s investment (ie item 5) and the value it’s creating for them (ie a value multiplier)
If the value equation (item 6) is too complex, your OSS will get lumped into the “cost-centre” bucket that is holding our industry back.
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.
