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

My Journey in Inquiry and Advocacy - An experience report

It is recently that I have consciously started practicing Inquiry. Let me explain. I am a consultant who constantly looks at the situation and comes up and implements the solution to progress from there. While I do that, I constantly use Inquiry as a means to progress - one of the key facilitation technique specifically in multiple stakeholder situations.

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 is a very valua

User Personas

User Personas are a very good tool for the product owners, business analysts or product managers to be able to co-create with designers. It is predominantly a product of the user research and should not be an amalgamation of demographic data. It is the best way for us to list all scenarios that a persona would take when they want to attain a goal. It is predominantly used to build empathy with user, focus the team and build consensus in a large diverse stakeholder group. The website I referred to is here:  https://www.smashingmagazine.com/2014/08/a-closer-look-at-personas-part-1/