Do you think you have a great product?

Neshooni.ir

Project Overview

Neshooni is a PWA and B2B platform for Estate consultants (Operating system for real estate agents).
Our product has 2 main features:
1 Catalog Request: Users sent a request for drafting (taking photos and creating a plan and all details of a house by our experts)
2 assigning a file to themselves: The platform provides some files (houses), and users (agents) just need to pay money to have access to its owner information.

My Role

As a Product designer it was my task to increase the number of Catalog Requests and Owner access.

Interviews, guerrilla test, and Observation
I used qualitative user research so We called our users and asked them for an interview in their agencies, we wanted to hear their problems and observe their behavior when they are using our product. We interviewed different users.
‍
How we chose users?
Type1: Not Activated & Not engaged: (Owner access:0, Catalog request:0)
Type2: Engaged but not activated: (Owner access:+20, Catalog request:+3)
Type3: Early Stage, not yet activated: (Owner access:+1, Catalog request:0/1)
Type4: Royal potential: (Owner access:+20, Catalog request:+4)
‍
Target audience:
All involved agents ( Agents who got engaged in our interview process and give us feedback )
‍
Gorilla Test No. 8
‍Gender: Male
‍Agency segment type: A,+A
‍Agency's location: Tajrish, Pasdaran, Parkvey
‍Agency type: Office / Store
Questions:
‍We asked them to assign a file to themselves.
We asked them to send a Catalog request.
What products they are using to find files?
How they find files?

User Research

The old UX was not fulfilling the needs of the new product and it was the cause of so many CS calls.

Based on my research I gathered these problems:

1: Microcopies are not clear
2: extra features are provided
3: long forms for sending a request
4: product seems complicated for its users whose tech knowledge is not advanced.
5: When uses save a file, they don't know how to find it.

Crazy 8 Technique

I shared the result of the test with our stakeholders, and they had some concerns about redesigning the product. I Persuade them to remove some extra features.
‍
We all agreed that these features are necessary for our users:
1: Sending a Catalog request.
2: Owner access.
3: Profile and our messages.
4: A specific place for files.
‍
By using Crazy 8 Technique we shared our ideas,It helped us to don't miss any ideas

Our solutions

The most important thing in our new design was changing the navigation bar.we used to have bottom navigation for five destinations, but they were not useful, and based on our user's behaviors and our business need we change it to 3 destinations.

1: We added some new colors to show some differences between Files and Catalogs.
2: Adding tooltips
3: Having toast messages
4: Changing some microcopies
5: With new messages, we could communicate with our users better than before.

Sketches

I usually start the design process with low fidelity sketches. This is the way I iterate through many design options quickly. In this case, we did not need to change UI elements, so we just focused on user flows, and we wanted to be more simple.
‍
The idea behind a wireframe is to demonstrate to the client/stakeholder/user what elements will exist on the page and how those elements will interact with other areas of the Product.
‍
It is incredibly important to get the structure and user journey, so a wireframe can help us achieve this at an early stage.

Designed for Confidence

The interface design strives to be confident. It does not contain UI‐bling or unnecessary elements. We opted for clear, readable typography —choosing colors with high contrast to increase legibility in low‑light conditions. The design is clean, large and well spaced. All our design decisions help to exude a sense of confidence in the design

Result

Usability testing Gender: Male:
Tasks:
1- Catalog request
2 -Owner access
3 -Changing profile preferences
‍ResultThey successfully did their tasks and it was obvious, however, they need to trust and our next task was to work on it.We evaluated the product by testing it on users.
What have I learned from this project?
As a Product designer in this project, I have learned to identify users better than before, and our design has to be interactive, we have to talk to users in our product like the real world and we should guide them. Extra features in a bad time do not help our users, and it is better to release our product step by step.if our users do not trust so, we need to coordinate with the rest of the company. Sometimes, some problems are not due to the product, if it is not possible to solve all problems through product, we have to solve it via other parts just by having a superb communication.