Brand Management

We chose to place primary icons on top because in many cases, use has to scroll down to engage with the content. In our initial design, I have used icons, Interface might be accessed from any part of the world. So I have tried to go with the icon with the button. But due to some guidelines limitations, we have removed it and went with a text button.

We have found out that users might spend more time on the Brand search screen. Quick nav action helps the user to sort the particular category listing form list.Admin/another user might handle partner details, so I have made quick access to sort partner forms. Colours make it more readable than text. So we have used colours to denote status. Additional nav has actions that users can do less often.

​

Layout

Background studies revealed that admin users manage the partner’s registration form without taking more time. I have tried to keep important information on cards and the rest of the information on the right side We choose a split layout like mail for the search screen. Since we are targeting desktop applications, We tried to utilize a full-screen size, So we have used a spit layout in many flows.

​

​

Workflow

Workflow is a streamlined process where internal users process the partners’ registration form with multiple verifications on behind the process. So I have decided to do some competitive research about how others are doing it. I have gone through Amazon, Swiggy flows and courier flow and management tools like Trello.

​

There are multiple flows that are required for workflow, Each form should move from one team to another team. eg, Admin got approved form, next it goes to finance team then the business team and so on.

Once the form gets processed, the registerer should get an update and should be able to update additional information if needed. So we have made two flows, one for internal and another of external user

​

​

View Fields/ Input Fields

While we designed a page where the admin can overview and take action, Initially DevOps team kept it in the input box-filled state for easier to implement and reuse the space while editing. I found that usability is affected due to this feasibility decision. It slowed down the admin to consume information.
'A Good Product is a balance of Feasibility, Usability and Viability.'

I argued with the devOPS manager and teams to understand the importance of making it information readable as fast as he can.  After a few iterations, We settled down to keep form from left to right reading to overview and clicking on edit turn editable fields like the old one.

​

Checklist in workflow

In the workflow, There is some information that needs to supervise by users. For example, If a new company tries to collaborate then it needs to check whether campy existed, whether its officials are registered, govt ID and background information about the company.  Generally, Humans make mistakes unconsciously. They also feel lazy when doing tasks on daily basis. Sometimes, the Autopilot mode drives humans to do daily activities. So In the workflow, we have to pause them and make then overview information. So we have a checklist for the user to make sure they have overviewe consciously. While we iterate, We had also thought of automating certain information which reduces human tasks and man-made errors. Since it’s a good to have feature, We went with a simple approach rather than automate.

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​​​

​

​

Design guidelines

Hence feature focused product, Each Features has its own visual language. So there is no consistency between flows. So i have created that covers Colors, Typography, Components, Buttons, Iconography, Layouts and Input Fields. Since user attention is required in crucial times. So I have used colors sparingly to highlight important information.

​