Moxi Engage helps agents and brokerages improve the way they manage their real estate business.
FINDING THE PROBLEM BEFORE THE SOLUTION
The goal is to help agents and brokerages improve the way they manage their real estate business.
I joined the project during the "Design" process.
Participate in the software development life-cycle including: functional definition, interaction models, user interface design, page layouts, content style guides and design patterns, wireframes, prototypes, site maps and navigation schemas
Customer Insights & Ideation
I partnered with one project manager and one Senior UX designer to uncover insights and translate concepts into features that address customer behaviours and motivations.
Experience Strategy & Vision
I created frameworks and prototypes to share the vision, design principles and content strategy. This helped to evangelise ideas, gain alignment and drive decision making.
Planning & Scope Definition
I helped to defined the product with my project manager and UX designer partner. I evangelised customer goals and balanced business goals. I prioritised and negotiated features for launch and beyond.
Oversight & Coordination
I designed across different mobile platforms to translate product features for mobile context.
Design Execution & Validation
I designed down on mobile. I executed wireframes, prototypes and design specs.
I designed up and presented works to gain buy‐in from executives, senior stakeholders throughout the project lifecycle.
- Allow agents to set their income goal within the CRM and receive activity recommendations based on where they are in relation to the goal.
- Relevant activities and tasks are recommended based on where a client is in the sales cycle. Automated email updates as the user closes transactions.
- Client data and insights at their fingertips.
- Responsive application design.
A software productivity solution for real estate agents and brokerages that could be accessed from smart phones, tablets, laptops, and desktop computers.
Research told us that 80% of the time agents are using mobile as a primary work tool. “Mobile First.”
I use scenarios to describe the stories and context behind why a specific user or user group comes use the tool. They note the goals and questions to be achieved and sometimes define the possibilities of how the user(s) can achieve them via the tool.
Each task is explained so stakeholders can review and comment on the design. After the wireframe is approved then I start working on a high-fi prototype where developers can visualize and interact with the design.
- Actions and elements of each screen.
- Screen Descriptions.
The size of this project and structured waterfall approach meant that I needed to have everything figured out before teams would commit to moving forward with the work. Many teams involved in the project needed to see it in a tangible document. This risk averse mindset meant I created a lot of reference documentation that was widely distributed and a high overhead to maintain.
Reduce Coding Time – This document helped to accelerate the development phase. Redline doc.
For the prototype I decided to use Axure RP to show the design and interaction of the idea. One of the main reasons why I decided to use Axure to develop the prototype was the limited time that I had to transform the idea into a playable artifact.
Encourage users to engage with the tools features.
- Help them get comfortable by setting expectations for what’ll happen.
- Provide an obvious way to move forward to that next step.
From the beginning of the project I was focusing my work trying to understand the necessities of the customers. I conducted six usability testing sessions to gather data regarding how agents navigate and search for information. I prepared the user testing scripts and I reported and presented findings to the stakeholders.
Six Months after release: 4,789 agents signed for a license.
"One of the best time management tools that I have seen in my 25 years in this business" - John Brauer, Broker
- Difficulty gathering user feedback.
- Participants were hard to schedule and to commit to participate in our studies.
- Responsive application design. It was hard to demonstrate to the devs how the tool adapts at different screen widths using AXURE as a prototype tool.
WHAT WOULD I DO DIFFERENTLY
- I would have used hand coding instead of Axure as a prototyping tool.
- Using hand coding would have demonstrated to developers how the tool adapts at different screen widths in a more accurate way. It would have eliminated some miscommunication with the devs.
- More user feedback.