_edited.png)
Media
Center
Understanding the problem
The customer felt that the Media Center was not prepared to be competitive in the brokerage market.
Creating an action plan
1 - Benchmarking
2 - Observe users
3 - Generate ideas
4 - Usability tests and new insights
5 - Final result
Understanding the context
The Media Center was created inspired by physical property catalogs, with the aim of being a tool used by brokers when selling a property.
A software that could be used to demonstrate images of rooms, shared spaces and floor plans, as well as institutional videos and 360º navigation.
Prioritizing solutions
Opportunity solution trees help product teams focus on key areas of customer need
-
Metrics constrain discovery to business-relevant areas
-
Opportunities identify customer pains to solve
-
Solution ideas provide hypotheses for creating customer value, and
-
Tests and experiments validate or disprove solution ideas.
Benchmarking
A benchmarking was carried out with the main competitors, comparing the main features.
Generating ideas
The main insight perceived was the need for White Label customization, as this would generate the most impact with the least effort.
The current media center features an aesthetic known as Glassmorphism.
Despite being visually appealing, Glassmorphism is a very specific aesthetic, which goes against the need for a generic aesthetic that White Label has, but it also brings a futuristic aspect to the product, which ends up intimidating and alienating the average user.
In addition, it also presented contrast issues.
Removing the glassmorphism helped not only improve contrast, but also bring an aesthetic that was generic enough to work across different types of brands.
Observing users
During the implementation of the product pilot, I visited a client's store and observed the first contact that users had with using the interface.
Generating ideas
As shown in the images above, the interface was designed to be used on touching devices, and presented on screens or totems. The interface presented ergonomic problems.
As the interface was distributed on all sides of the screen, some ergonomic problems were encountered.
Users had to stretch their arms to reach the other side of the screen, in addition to blocking the view of those behind them observing what was being presented.
I mapped out the main interface elements (buttons, switches, etc.) and concentrated them on just one side of the interface, with the goal of preventing the user from having to reach the opposite side of the screen to use all the interface elements.
Priorizing solutions
I used an Opportunity Solution Tree to prioritize solutions because it is a simple way to visually represent the paths we can take to achieve a desired outcome.
The company's outcome was set to facilitate IMXR's entry into the display market, and the product team's outcome was set to have a scalable product and make Media Center a competitive product.
Initially, we prioritized leaving the interface unilateral to solve ergonomic problems, and making the product white label, to improve scalability.
Usability Test
An A/B test was applied to understand which side was ideal to focus the interface on, and other tasks were requested to evaluate the rest of the flow.
Group A
Main observations
All the 4 users did not experience any ergonomic difficulties
Only 2 users easily found the A.I button
1 user had a lot of trouble finding the AI button.
All the 4 users were able to easily generate the decoration options using the A.I
Group B
Main observations
All the 4 users did not experience any ergonomic difficulties
Only 2 users easily found the A.I button
1 user had average trouble finding the AI button.
All the 4 users were able to easily generate the decoration options using the A.I
2 users had the expectation that the AI would be with the images, not in a separate environment
Details about the usability test
Eight internal participants were selected for qualitative usability testing, and were divided into two groups of four people. Each group consisted of three right-handers and one left-hander.
One group tested the one-sided interface with the content on the left, and the other tested the one-sided interface with the content on the right. Furthermore, it was an opportunity to test the flow of an AI that the client wanted to implement.
The solution
After evaluating the feedback collected and gathering new insights, I worked on some flow and interface changes until I reached the result below:
This will be the version developed and launched as a pilot, with which we will gather new feedback, learn more, and further develop the Media Center.