Property Management Cloud Dashboard
Project Description
UnitVPM's property management dashbaord allows property owners and managers to easily manage their tenants and inventory. Using the dashboard managers can send out mass announcements, receive payments and invoices, create and search customers, create units and upload 3D walkthroughs, receive maintenance requests send by tenants, and schedule labor their partners.
Our Role
Our role in this project was to create a dashboard for property owners and managers to be able to accomplish their day to day tasks by ease. Our main development goal was to create a dashboard so easy to use and navigate around that property owners that are not tech savvy can easy handle and complete their tasks. We made the web dashboard user-freidnly and mobile friendly so no matter what device it was used the functions were simply accessed. It was crucial that the platform's performance was fast and easy to use.
Our Development Process
Product Scope
We focused on the business vision and created a comprehensive brief for the project by gathering all the research on the market, competitor benchmarks and any other necessary information. Then we met with the client in an immersive session to craft a value proposition and set the main assumptions to prove. Finally, we created the ultimate list of user stories and features necessary to prove those main assumptions within the MVP.
1
Product Rationale and Tech Scope
After an immersive session with all the stakeholders, we had all the information we needed to create the ultimate list of User Stories and features necessary to prove the main assumptions in a Proof of Concept (POC). Our experts in Product, UX/UI and Tech Architecture focused on finding the answers to all of the questions raised throughout the scope preparation. On the tech side we elaborated a memorandum tackling our suggested approaches for tech stack selection, database technology and orchestration. Together with Bocconi University and AlixPartners we started defining the useful datasets and the algorithm behind the lending decisions.
2
Clickable Prototype
We developed a non-functional prototype to simulate user interaction. The experience of using the clickable prototype was very much like the final product itself, this was the adequate phase to test the information architecture, the UX and most importantly to present all involved counterparts a concrete outcome.
3
Full Development
With the decisions closed in the previous steps, we went on developing the product through agile cycles.
4
Iterations
Once the product went live we started to gather end-user feedback and improve the product. New iterations were made in parallel with new features so that the end-user has the best experience possible.
5