Constructing the Product Roadmap

When I started out in the team, I was tasked out with coming out with a plan so that we can demonstrate the product with real data.

The idea was to demonstrate it to our prospect with their own data and win them over. However, when I started working, I found out that what we lacked was not a plan but a vision.

I quickly put together a one day workshop with our team and our product owner. When we started talking, we talked about several things and figured out that we needed a plan of various proportions.

We needed a plan that could help us one the following:

Provide a focus for the long term with near term focus on just one thing
Help us talk to prospects on what we are going to do
Help us decide on when we would need to focus shift on which function - Engineering , sales etc

We also did a quick “Product in a box” exercise so that all of us in a team can practice and imbibe the elevator pitch. We needed this since we had to do this pitch at several levels - Internal as well as to prospects.

This is how the “Product in a box” looks like.

This is how the product roadmap looks like.

Comments

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...

The cost of delayed decisions in Enterprise

Large enterprises have started their IT journey in earnest. However, they are miles behind what is happening. Some of them have been trying to learn faster by creating research programs or separate business unites to try out and learn a few exotic ideas that have not yet gained acceptance in the industry or enterprise. Enterprises have moved record collection and data to IT long back and were pioneers in that. However, since the advent of personal computers, they have been left behind. Internet and mobile have left them far behind. For example, Network security, big data, mobile apps. social applications are solved problems that the enterprise choose to ignore.

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 ,...

Life of a Business Principal in Consulting

Search This Blog