Skip to main content

Defining your product's business value

What is in it for your customer and user to buy and use your product?

While we all would have answers for this question, we need to understand what the users think of our product.

When we started our product, this is what we came up with:


We were all excited and would roll our tongues and try to convince our prospects that this is the business value that it was providing.

Turns out we were wrong. While we are providing these value adding aspects in our product, these are not the real ā€œBUSINESS" values.

Notice that the word business is in bold.

What they really wanted was a simple web page that tells them how their business is doing without jumping through hoola hoops.

The biggest business value for saving time on doing mundane calculations.

They did not want to manually consolidate sales of 3 stores every month or every time they needed to take a decision.

Once you have captured the business value, how would you track how you are doing on that business value.

That is a topic for another post.

Comments

Popular posts from this blog

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile:  http://djrusso.github.io More reading from his paper here:  https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision.  I liked the approach of principles for developing systems that are anti-fragile. It i...

Designing for Accessibility

The software world has starting being more inclusive. After serving only the geeks and the techies, a lot of the software that is produced in this world has started looking at how it can be mor euseful. One of the key constituencies of software usage is people with disability. The ADA (Americans with disability Act) has forced a lot of the software developers to look at this issue. The software world has also responded sensitively and with care making as much of the software usable by people with disability. One of the key components that we are looking at in this are people with visual impairment. Over a period of time, a lot of the software has made sure that the user experience is adjusted in such a way that is is intuitive. Google has been a front runner in this and a lot of others are also not left behind. Text The size and the font typology is very important. Choose those aspects with ADA in mind. Media like Images A lot of the media , including video and images ,...

Public Policy and Software Development practices- Convergence

My last 2 posts on public policy discussed on the need to revisit our public policy making process and how it can be mapped to software development . There are a few areas that I would love to focus on for convergence of policy making process and software development process. To provide some context on what is really happening in policy making today, please check this video out.