The product owner had laid out a list of user stories and requirements that were necessary to launch an MVP.
As I would work on other projects throughout the summer, we would revisit the app once a significant feature had been finished.
Before starting on UI, I spent time looking at other data visualization-heavy applications and started wire-framing designs that relied on the hierarchy of information more than overall navigation.
In traditional property management, quarterly reports are the only way for owners to receive updates on the properties. The app allows real-time data oversight and general property updates for the owner.
Giving access to the team for the owners allowed for direct communication about concerns on their property or the data they were viewing. By allowing owners to have a direct line and visibility, a higher sense of ownership and gratitude was achieved for their portfolio.
Snapshots to full run-downs of financial data including revenue, net operating income, occupancy, and more for the owner's real estate portfolio.
Owners can view their properties at a glance along with an occupancy rating. The properties tab details each unit at a property which includes their occupancy status, current residents, maintenance request details, and resident ledger.
Streamline the list of actions happening in real-time. See the creation of a maintenance request, leasing, prospect conversion, payments, and more. Each may be expanded to view further details.
Once a milestone was completed, I would meet with our product owner, investors, and multiple owner success managers to present new additions to the mobile app. These individuals were able to help define the hierarchy and overall information architecture for the app. The presentation of information was approached in a top-down manner with the broadest breakdowns at the forefront and detailed information drilled further into the app.
I would note any hang-ups or concerns for my designs that needed to be addressed before handing the pieces off to the development team.
After releases were pushed to production, the users would be in close contact with an owner success manager to ask questions on the data or concerns that would arise. The team used this feedback to help determine the prioritization of features for the customers.