What problems are your OSS solving?

Problem-solving becomes a very important part of our makeup as we grow into maturity or move up the corporate ladder.
Zig Ziglar
.

What problems are our OSS trying to solve? Have you ever pondered what problems they could be solving?

Sometimes our answers to the first question show the day-to-day issues that we’re trying to overcome to benefit our customers / users. They are often the hot-topics, the short-term focus. An hour of effort on these questions might produce a result of 1x benefit for the customer.

These problems often relate to what your stakeholders think your OSS can do for them. In many cases the problems are framed by operational groups. But are there problems your OSS could be resolving for the organisation that provide a 10x (or more) benefit for a given amount of effort?

The bigger organisational problems are quite likely to reside outside the operational groups. It could be that the executive can’t get the right information quickly enough to make well-formed decisions or the marketing team doesn’t have the ability to test impacts from their work in near real-time, etc etc.

It may need you to get to know your customers / users better. From a wider viewpoint than most OSS experts.

If this article was helpful, subscribe to the Passionate About OSS Blog to get each new post sent directly to your inbox. 100% free of charge and free of spam.

Our Solutions

Share:

Most Recent Articles

No telco wants to buy an OSS/BSS

When you’re a senior exec in a telco and you’ve been made responsible for allocating resources, it’s unlikely that you ever think, “gee, we really

2 Responses

  1. OSS has its roots in the operations of the network which was when connectivity was the business; while technology has far advanced into the core of many facets of business, the focus of OSS decision makers still remains functional / technical. Strategic impact in the digital era especially with SDN, NFV, and service aggregation requires a different philosophy – beyond functional requirement discussions and product solutions.

    To the writer’s point on 10x vs 1x, value mapping is a critical exercise which has to be added / overlaid on top of the requirements layer, which talks to each of the four broad domains of business – clients, revenue & margin, asset utilisation and stakeholders (employees, investors, shareholders, community, government, partners, vendors, etc.)

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.