Crafted a Marketplace for Pregnancy Care Application

A neuclear family living in metro cities is what we were targeting. The whole idea is, when women lives in villages there they easily get helps from their relatives and nearest family members. But people who lives in metro cities hardly get that benefits.

Research

While doing a search about the domain and trying to figure out the detailed persona we concluded the expectation is very wide. Another concern we took in the consideration is to understand all the offerings in the first place and segregate accordingly when there is a needs to be shown. 

As a marketplace of products and services they offers including yoga, music, dance etc, everything has a different way to deal with. Few offers online and few are in online. Many just want to be on the platform and few want to be the influencer all together. 

It took good amount of time to meaningfully map all the offerings in one place. And now we had clear understanding of all offerings, users we want to caters to and plus points to have own marketplace

Challenges

Before we really jump on to start taking social media direction and just replicate the designs, we took a step back and thought to do a contextual inquiry and understand users daily needs, their core problems and how they deal with it on daily basis. 

Is there other options they find most comfortable and if yes then what is that and how it is helping them. We broken down all the inputs came form this research and made a moodpboard of liking and unliking.

After this exercise we have boserved few important pain points,

  1. Not many users were interested in buying product straight away. 
  2. Found useful of a particular pregnancy journey they get insights and right suggestions about the products they should try at that stage. 
  3. No advertisements of meaningless stuff
  4. Keeps the track of progress
  5. Related services from nearest place

Solution Discovery

In the research process we have conducted a small liking exercise too. Which helped us to define the design language of the application. Which eventually became the foundation for the application. 

We asked 10 questions with 3 answers to nearly 20 women about the liking of readability, visuals, interactions, etc. And set the foundation of design system in figma. 

We kept trying couple of layouts for the home page, profile and other modules. Which get us to the expectations client had. In the process we were able to reach the right stage where product can deliver what a business sets for. Including the right design system preferences

Continuously iterating on the layouts with already created design systems makes things seamless. There you get to see what is about the be finalised. And in the iterations also we were also not putting too much efforts as well. This was a great appreciation from client to see the finest work in iterations and that is in less time.

To fasten the whole process and to get the consistent experience we limited the components needed in the first release. And that became the game changer decision at the end. 

Which brought the simplicity and consistency for designs and development to adapt the different iterations faster.

Nearly it took around 40 days to finish up all hi fidelity screens and we did the dev handoff with all interactions detailed notes.

Final Solution

When all went live it was a big success and got noticed well too. We haven’t finished the project there. There were couple of things we needed to incorporate in the marketplace as well.

Conclusion

  1. For different persona you needs different mindset to think about 
  2. It’s easy to expect simple product but that’s what take the most time. So be patient until you make one 
  3. Marketplace is a father of the aggregators. You can do much more than a service aggregator 
  4. Never mix multiple use cases to deliver maximum output to users

Designed Support Environment for remote customer

Support executives are always trained to answer queries user often have repeatedly. Which becomes a tiering when a person reaches to a customer place and just fix a very minor thing in the machine and that’s done.

Blitzz solves that’s exact problem and helping both parties to collaborate effectively over a video call and take better calls without being in-person connceted to save more time for executive to help other customers who might be waiting for long otherwise. 

Research

Started with CTO discussion about the feasibility of the feature we want to integrate in the existing product. 

There couple of workflows which has a specific requirement and needed to establish information depending on the product API offers. We freeze the area and moved ahead with the rest.

During the research and competitive analysis we observed that support is a process which is solving just one side problem and not potentially on the service offering party. Where the outcome is not celebrated. Still that plays major role in the solving customer queries seamlessly remotely. 

On top instant problem addressing facility was kind of new in the industry that time and companies like Dell and Whirlpool were also bullish on the same. Blitzz already has them as a client but want to provide quality breakthough with this new feature. 

Challenges

We broken down the domain, understood competition and did enough research for the different product the ares. The support executives are people who understand how to operation computers and how to deal with basic systems. 

But not at the very extended level which remote support product can offers. Hence we stuck at how to go about the layout, infromation architecture etc. Again we brought the workflows and start critiquing inputs and outputs needed in order to run the product and then the focus area for solution discovery came out. Those are as follows,

  1. Feature should just curated for support team
  2. Workflows shouldn’t take much time of a executive in order to save time
  3. Reporting should be by product
  4. One ticket at a time

Solution Discovery

In the feature iterations we were working on two important aspects, one is workflows and second is video conferencing.

Workflows is something which allows support team to schedule and make sure the ticket is raised for a customer and everything related to the discussion or guidance get stored in the same even if the connection get lost in between. 

Video conferencing was kind of similar to the other video calls offered by popular tools. But here the catch was to enable executives to interact over a video to customer and guide them to do certain action. 

Which took the most iterations and after couple of reviews and feedbacks we finally concluded the below iteration for the hi fidelity

Final Solution

From the starting we were sure to not invent the wheel for the sake of it. Hence we try to leverage the existing layout of the product and yet bring the information interaction within it. 

Workflows was a bit complex then the video conferencing but we incorporated hi fidelity with the existing design system and layout to save front end efforts. 

Below is the final UI which later got released in the existing product.

Conclusion

  1. When time is less do save time in hi fidelity but keep the iterations on the same frequency
  2. All users expectations are different and hence the standard benchmarking fails
  3. Leverage insights of experienced POC in team to achieve faster result
  4. Sometimes inclusive solution is better