top of page
Housing Development

EzCaza

B2B website for buying and selling homes

EzCazaMockup1.png

EZCAZA OVERVIEW

SUMMARY

The unpredictable rise and fall of the housing market creates distrust in buyers and sellers of homes, especially towards real estate agents. The lack of transparency in knowing what parties are involved further instills this. EzCaza's business-to-business platform aims to solve these problems.

Summary

CHALLENGE

Real estate agents often experience difficulty in selling enough homes due to not having enough listings in the first place.

 

With a selling team in place, sellers are unclear with everyone involved in the selling of their home. On the other hand, when a seller chooses separate parties to sell their home, they do not know who to contact and selling the home becomes extremely cumbersome. 

ROLE

Sole UX/UI Designer

TOOLS

Figma

SOLUTION

My Jira assignment was to design a Property Info page to provide basic information for real estate agents to view new house listings to sell. 

​

I also needed to design a Team Members page so the seller can add and keep track of the team members involved in the selling of the house. This information can then be accessed by all of the parties involved in the home selling. 

Discovery

01DISCOVERY

01.01 JIRA

First I went over the Jira tickets to remain organized with the project and understand the expectations and requirements.

Prop Info ticket.png
Team Mem ticket.png

01.02 RESEARCH

OBJECTIVE

To understand how EzCaza's Property Info page and Team Members page can assist users in the buying and selling of homes. 

​

As the name suggests, the Property Info page would focus the property's description so users (both buyers and real estate agents) can see what is currently available.  

 

The Team Members page would ensure organization and transparency for both the team members of the selling team and the seller. 

 

I focused primarily on reliable data from studies. After this, I turned to articles to understand the perspectives from more people and companies in a more conversational approach.

FINDINGS

In the study Real Estate Team Risks and Rewards, nearly one thousand agents were surveyed. The results revealed:

61%

of participants reported that

"confusion about who does what is the biggest issue clients face while working with a team." 

For sellers, the report found the following issues:

  • Uncertainty of who to contact (64%)

  • Not having a single dedicated point of contact (63%)

  • Poor communication (56%)

  • Lack of personalized service (48%)

source: https://www.homelight.com/blog/how-real-estate-teams-work/

Ideation

02IDEATION

USER STORIES

In order to include the necessary functions for the page designs, I used the following user stories:

Property Info page

Team Members page

Design

03DESIGN

03.01 UI INSPIRATIONS

03.01 STYLE GUIDE

Style Guide.png

To remain organized, I created a Style Guide with all of the design components that were used for the pages.

03.02 DESIGN

I followed the instructions on the Jira ticket to design the the Property Info and team Members pages. 

03.02.01 Property Info Page

Jira ticket required the following:

  • Image of the listing

  • Sites where the listing appears

  • Property name input

  • Property ID input

  • Address input

  • Apt/Suite/Floor input

  • City input

  • State input

  • Zipcode input

Property Info page.png

03.02.02 Team Members Page

Team Members page - Default.png

Jira ticket required the following:

  • Multiple rows for team members

  • Include a row for each of the following roles:

    •  Real Estate Agent (Buyer)

    • Lender

    • Inspector (Buyer)

    • Surveyor (Buyer)

    • Title Company (Buyer)

    • Appraiser (from Lender)

    • Insurance Agent (Buyer)

    • Moving Company (Buyer)

  • Prototyping to animate the functions

03.03 (RE)DESIGN

Some of the designs had already been created but needed cleaning up in the form of consistency and organization.

Overall, I achieved this by ensuring effective and accurate naming conventions, creating consistency in design by ensuring padding and spacing was the same throughout the objects on the screens, and creating new and expanded existing components / variables for reliable consistency.

Important Dates page

Issue

Inconsistent spacing/padding, dates not visible. Confusing and disorganzied page layers; several objects did not have a specific name (i.e. "rectangle""frame"). 

​

Solution

  • I corrected the padding to keep it consistent around the central container, as well as elongated the second column of containers.

  • I utilized Autolayout for further consistency and organization within the box containers and made the dates visible.

  • Throughout the redesign process, I ensured effective and accurate naming conventions within the layering of the page by renaming and grouping according objects together. ​

Important Dates page.png
Important Dates page-3.png

Upload Documents page

Issue

Inconsistent spacing/padding, confusing and disorganized page layers; several objects did not have a specific name (i.e. "rectangle""frame"). 

​

Upload Document page.png

Solution

  • I corrected the padding to keep it consistent around the central container

  • Added visibility to the arrow in the "Add File" button for improved accessibility 

  • Throughout the redesign process, I ensured effective and accurate naming conventions within the layering of the page by renaming and grouping according objects together. ​

Upload Document page-2.png
Deliver

04DELIVER

After all of the screens were designed and others redesigned and organized, I then prepared  everything for hand-off, cleaned up the screens, and prepared for developer hand-off and to attach to Jira.

EZCAZA WALKTHROUGH

I created a prototype of the final redesigned high-fidelity screens to best understand the user's navigation through the pages.  

Reflect

05REFLECT

FINAL THOUGHTS

When I received the Jira assignment, I focused on seeing what was already created. I followed the instructions to ensure I met all of the requirements. I created the Style Guide to keep the design seamless and all of the objects within the file in an organized manner. After this, I cleaned up the created content to ensure consistency and as I went along, organizing the layers, names, and groups for each screen for optimal organization and efficiency. Once this was all complete, I handed it off to developers. 

​

Through this EzCaza project I was able to work more on and more deeply understand the importance of remaining organized from the start for optimal efficiency. However, if given more time I would have loved to research more of users' needs and design these functions onto the screens for a more holistic and user-centric product. 

bottom of page