Responsibilities
UI Design, UX Design, User Research, End-To-End Ownership
Team
1 Product Owner
1 Head of Design
1 Head of Operations
2 Full Stack Developers
Summary
HomemoveOne is a web application designed to simplify the house-moving process by consolidating essential services into one platform. I applied Object-Oriented UX (OOUX) principles to restructure the user experience and refine the customer dashboard, thereby enhancing usability and aligning with business goals.
Pain Points
Movers lack a reliable source of information on steps to take and in what order, making the process confusing.
Hidden legal and mortgage-related fees often result in unexpected financial strain.
Managing multiple service providers with different timelines creates coordination challenges.
Logistical issues, like furniture not fitting through doorways, cause last-minute delays and stress.
The Process
Discovery and Planning
Upon joining the project, I worked with the Head of Design to develop a high-level plan using the Double Diamond framework. This iterative method allowed me to adapt to changing requirements.
Reviewed existing designs and feedback.
Collaborated with stakeholders to define project timelines.
Proposed using a pre-built design system to accelerate development, which the CTO approved.
Deep Dive into the Domain
Understanding the complexities of home moving and the Homemove ecosystem was crucial for making informed design decisions.
Conducted domain research and user interviews.
Developed an Object Map using OOUX (Object-Oriented User Experience), refining it iteratively with stakeholder input.
Results
OOUX clarified object relationships, reducing process ambiguity for developers.
The learning curve of OOUX at this scale was steep.
Iterative Design and Testing
With the Object Map as a foundation, I created low-fidelity wireframes to gather functional feedback before refining visuals. I typically avoid them, but given the development team's limited experience with designers, I wanted to prevent early focus on visuals.
Actions Taken
Developed prototypes tested internally with key stakeholders (CEO, CTO, developers).
Conducted moderated tests with two target users to validate assumptions and usability.
Insights
Users greatly appreciated the "Now/Upcoming" task hierarchy for its clarity.
Developers required clear task-to-service connections, influencing final design decisions.
Results
Internal testing streamlined developer alignment.
Limited external user testing due to time constraints.
Navigating Challenges
The project faced challenges due to miscommunications and shifting technical constraints. For instance, developers pushed for a service-first task flow despite prior agreement on a user-centered approach.
Results
Data-driven rationale resolved stakeholder conflicts.
Initial delays arose due to unclear technical requirements.
High-Fidelity Designs and Final Push
Once alignment was achieved, I developed high-fidelity designs focused on:
Dynamic task prioritisation ("To-do/Pending/Completed")
Seamless integration of essential services
Developer-ready edge cases
Highlights
Worked closely with the sales team to ensure strong customer alignment.
Staged handoffs effectively facilitated parallel design and development workflows.
Outcomes and Impact
While the project was not launched due to my layoff, anticipated impacts included:
Enhanced user clarity: The "To-Do/In-Progress/Completed" hierarchy simplified task management.
Developer efficiency: Adopting a robust design system streamlined implementation.
Business alignment: Design decisions supported broader sales and operational objectives.
Although quantitative metrics are unavailable, qualitative feedback and stakeholder buy-in validated the design’s potential.
Key Learnings
Stakeholder alignment matters: Cross-department collaboration minimised rework and clarified priorities.
Adaptability is key: Embracing OOUX expanded my skillset and added project value.
Presenting evidence is powerful: Data-backed presentations, such as the "Tasks Page Retro," were instrumental in resolving conflicts and building consensus.
