Skip to main content

Product design with end users

Have you ever noticed how terrible the parking signs are in any major US city. When you need to park your car in any major US city, it takes 5 minutes to decipher the information in the parking sign to understand if it is ok to park in that spot.

Nikki Sylianteng , a designer , turned this problem into an opportunity and posted her designs nearby some of these parking signs. The new designs evoked good response. You can read all bout that here at Priceonomics.




This designer tried out something that we should all be doing more often with products - design  and get feedback. While this is easier said than done, we set out to try and deism collaboratively with our clients.

When we designed a data product initially for retailers, we were looking at typical retailer data and inferences and designed our product.



This is how our product looked initially. When we presented this at the NRF Big show, some of the feedback made us look at decision points rather than inferences. Lesson well learnt.

Buyers in retail companies use a tool during a decision point and not randomly for data and inference they can get out of it.





Our next version that we developed was done within the space of 2 weeks.


We ran it through a couple of retailers and started to understand that when we design products, we have to sit with our end users not the people who might buy this tool for us by others.


We ran it through a couple of retailers and started to understand that when we design products, we have to sit with our end users not the people who might buy this tool for us by others.

This time we decided to hit the road with our design board, our tool and our prototypes with multiple versions of the tool.

We met 10 retailers across 3 cities at their retail locations, talked to the end users on constraints under which they operate the tool and found some very interesting scenarios for our product. We also had conversations with the designers from other products to understand a couple of more design inferences that we miss rout early.




With more annotated designs , copious notes from user research and interviews, we designed out final product and deployed it across 2 retailers.

We are getting more feedback as users have now started using the product.

Comments

Post a Comment

Popular posts from this blog

Counterfiet goods and the fledgeling e-commerce market places

India has a nascent and a very active market place. With good interest, the right climate for growth and right product mix, the indian retail marketplace seems to be going places. However, there are some alarming signals that seem to be ignored for growth that have a good chance of being dangerous to all the stakeholders involved. The issue I am talking about is the sale of counterfeit goods in all the indian market places. India has not had a history of strong Intellectual property rights. This time it is getting messier. The Indian marketplace model is very interesting and suits well to a country as diverse as India. The market place model floated by all the major e-railers suits the fact that the seller and the buyer can be connected for serving the needs for every day goods that are not necessarily covered by IP laws. India needs more effective IP laws since it is struggling with some products like traditional indian products that cannot be covered by IP versus modern produc...

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

Organizational growth and turn over

Organisations need to grow. However, they should not grow for the sake of growth. That would be a virus. Orgs should not grow to survive as well. Orgs should grow with a purpose.