Mobile platform has always been at the margin of Meetoo’s product strategy.
But I have discovered its huge potential during user research with our clients.
Meetoo’s product strategy is framed around the technology of BIM+Iot, which largely relies on the desktop platform. Thus, product development on the mobile platform has never been the top priority.
According to my research with the clients, however, they value mobile features more due to their portability - approximately 80% of their work hours are spent on on-site tasks where they don’t have a laptop.
Furthermore, the other products they use at work are designed to be scalable and adaptable to mobile usage. This adaptability, combined with the clients' work habits, underscores the potential for growth in the mobile platform sector.
I covered the end-to-end product design process including user research, wireframing, user journey mapping, prototyping and UI design.
Timespan: 3 Years
I initiated the project with small but crucial features at first.
Then our mobile app expanded after we saw benefits and revenue.
The features iterated from “bottom-up.” I initiated the project with small but crucial features based on my research insights with facility management staff.
Once our team and clients saw users benefit from them (and we saw revenue coming in), we identified the interconnection among those features and more design opportunities in the future.
How might we reduce the effort of searching for crucial information on-site?
MVP: How can we leverage the existing features to reduce development efforts?
Health analysis has two values to offer for system managers.
First, concisely visualize the status quo:
Combining multiple dimensions to provide a comprehensive view.
Indicating how severe the situation is (trend overview and comparing with other equipment within the same type)
Then, guide users to put charts into action.
First of all, redesigning the IA boils down to two parts:
The navigation bar at the bottom - Card sorting combined with user interviews to understand the user’s mental model.
Home page redesign - Leveraging data as CTAs rather than displaying feature names.
Our users can’t reach the same mental model for categorization, and they use these features differently.
The interpretation is that there are not enough features (which means no need) in FM Go to categorize for now, and we can keep the bottom nav as it is now.
Thus, we are in a dilemma - the features are too many to be jammed into one page, yet too few to be divided into different tabs. Plus, adding new tabs breaks the users’ old habit of looking for information on one page, thus adding a new learning curve to establish new habits.
Redesigning the homepage, utilizing operational data as CTA for users to get engaged.
Categorizing features by different roles - Campus manager, system manager and base-level staff.
Utilizing the existing Access Management System for each role to prevent information overload on the home page.