Skip to main content

Being sensible with sensitivity


One of my first projects as a scrum master was to develop a product that would be used by teenage girls and mothers who are afraid of an unexpected pregnancy.

I had to work with my clients on this project that was sensitive in nature on multiple grounds.

Sensitivity #1:

I was working with women on a topic related to measuring menstrual cycles and ovulation periods. It is not easy for people in India to hear a guy talk about menstrual cycles so openly.

I had to balance between being sensible on how do we treat the entire topic as an objective discussion to shape the product while at the same time not seem like turning women into objects. It was a tight rope but we did it.

Sensitivity #2:

This was a realm that fell between medical and religious. The stand that the product took was not overtly endorsed by the medical fraternity in India. It was a new methodology that had data that was not collected by medical fraternity and hence concerns were there.

This was a blessing in disguise since we did not fall under the ambit of medical products. We still designed the product to respect the privacy and concerns of the users.

Sensitivity #3:

The stand of the product was something that was supported by the Roman catholic church. This brought concerns on the product being used for christian missionaries to further christianity and its ideas instead of being scientifically backed by data. This was the most sensitive issue of all the 3 that I had to handle.

We had to balance it since we were presenting it to the USAID at New Delhi and were not sure where the sensitivity lay. USAID was the primary sponsor for the product. We choose to ignore the stand of a specific religion and rather focussed on how we worked around the user’s preference for the product to talk about a taboo topic and be non-instrusive.

Working as a scrum master and a product owner on the development of a non-conventional software product was very interesting. Being sensible when handling these sensitivities was a very good learning for me.
Labels:

Comments

Post a Comment

Popular posts from this blog

The right business model for your product

How would you decide what is the best business model for your product? Deciding on the right business model is very important for the product. It does not necessarily mean what is the price of your product. There could be no price for your product - though that is a myth. For example, we think google or Facebook is free. However, we are never the customers for Google or Facebook. It is the advertisers that are its customers. What we need to figure out when we decide on a business model are as follows: Who is my target audience? Who is my customer What is the price. How is the support model going to work Who are my partners While we do not absolutely need to price a product, we need to understand how we would make money. For example Open ERP does not price its product. However, its product is not the ERP software but really the hosting, service and training that it offers. While pricing is an important part, what is more important is in realising who is you...
Post a Comment
Read more

Finding your target audience

The biggest task of the product manager is to find your target audience. Typically it is a very tight rope walk. You define it too narrowly and you would struggle to generalize the product later. You define it too broad and you would struggle to satisfy a lot of people and the product might not take off at all. There is this awesome post by Dave Mcclure on why Niche target segment works. Blog link here . What he says is mostly right and that is what we did as well. We did it mostly by accident. We had to define our niche because we could only talk to those kind of retailers and get data from them to start developing the data. It did have its upside. We were very clear on what we wanted to develop and we are slowly talking to retailers and adding more scenarios. As we are doing this, we are also talking to a slightly different set of retailers. This helps us incrementally build our product while also generalizing the existing features. In our case, we did not fin...
Post a Comment
Read more

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 - Inter...
Post a Comment
Read more