Work Tags: Webapp

Establishing First Back Office for E-Wallet

From the project prospective the product we have started was for B2B where we need to serve the internal team. This is often quite complex and need detailed understanding of each stakeholders requirement clear.

Research

We got to know from requirement that there will be different vertical which is going to manage their operations and hence it shouldn’t cater to just one cohort. So we kept approaching all stakeholders and gathered their inputs for their daily core needs. 

Our goal was not to focus too much on the best finest product as per the urgency. Instead requirement was to get the product out fast then then keep iterations rolling on top. That’s what seems feasible at that time. 

We collected all inputs and started making workflows for each vertical. Gradually we understood the problem team was facing with manual transitions happening with tech team. We kept noting those down on the side so that we can focus in detail in the solution discovery part. 

Challenges

There we many expectations coming from growth team, finance team and product team which are not easy to fit in one line. Still we kept adding all of them on the board and let all input comes to a single glance. 

After doing couple of card sorting exercises and brainstorming we got stuck at many places. 

Out of different pain points and workflow breakdowns we came to the conclusion that there are few metrics we need to set as a foundation,

  1. Comprehension
  2. Consistency
  3. Simplicity

Which really helped us to move in the direction faster then expected.

Solution Discovery

First we focused to have as minimal as possible top leavel hierarchy when it comes to accesing information. Many projects try to have everything upfront but what they don’t realise is that is creates a constant cognitive load to users. 

Here we were sure that we do not want any things less important taking front seat. Hence we limited the top navbar with most minimal version.

Iterating on the layout was the fun exercise as always.

Finally we went back to the team and got their inputs on,

  1. Comprehension
  2. Consistency
  3. Simplicity

Another reason the get the feedback is that this product is definitely going the be a huge as an internal tool and number of other things will also come to life. We want to make sure the foundation we get chance to work on should be the most flexible and adaptable. Else in the future it may become a bottleneck for team.

Since we were focusing on different verticals and their team to use the product the major module with needs in the system is User Access Control. And it caused significant amount of time in the overall project journey. But when the whole team got what they need in the last prototype it was worth solving it.

We we product that deliver the whole product in just 2 months and client was able to start the development as we were getting done with module one by one.

Conclusion

  1. It’s difficult to keep things simple unless you value everything you have to prioritise
  2. Understanding workflow of real person brings more understanding of a cohort too. Instead of creating personas also understand how their daily work life is, why they do what they do
  3. Industry practices shouldn’t underestimated in any ways. You can always build on top but never ignore the fact 
  4. When you Strat iterations on layout you get more understanding of inclusive workflows

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