Improved UX gets Invisible Homes over 35k registrants
About this project
After its MVP launch, Invisible Homes’ platform was buggy and its user adoption was below expectations. Our goal was to prepare and execute the handover of the project and design a roadmap to fix the existing issues.
Result: After delivering the improvements, user growth and adoption were back on track.
our INVOLVEMENT
Design
Build
technologies
Ruby on Rails
Invisible Homes aims to make it easier for buyers to buy off-market properties via a web application, answering to the growing demand of this service in the UK.
Putting it simply, it’s a direct link from people to real state opportunities without unnecessary steps in between.
Invisible Homes’ platform was initially built in Ruby on Rails, and because the goal was to add to the existing project, our team decided to keep the original codebase. But code coverage was low and one of the reasons why so many bugs were hitting production. We raised coverage to the ideal value of 80% and replaced deprecated libraries with new ones.
NEW PROJECT IN MIND? LET'S TALKduring the project
Since the client’s original tech team was not up to the challenge, Imaginary Cloud prepared and executed the handover of the project and designed a roadmap to fix the existing issues and revisit the workflows by applying our proprietary Product Design Process. It consisted of 4 stages:
four stages
Research
Ideation
Execution
Launch & Handover
two stages
Migration
Development
four stages
Requirements
Back-end integration
Website development
Advanced filtering and search
four stages
Research
Ideation
Execution
four stages
Backlog
Bootstrap
Wave 0
Wave N
four stages
Backlog
Bootstrap
Wave 0
Wave N
two processes
ADP
PDP
during the project
Since the client’s original tech team was not up to the challenge, Imaginary Cloud prepared and executed the handover of the project and designed a roadmap to fix the existing issues and revisit the workflows by applying our proprietary Product Design Process. It consisted of 4 stages:
We identify the main aspects of the business model and user needs.
First, we gather evidence that will support the decisions taken henceforth, ensuring that no decision is made based on vague assumptions.
This stage consists of 3 steps: a briefing with the project's vision and goals and business requirements; user research to guarantee product usefulness and effectiveness from the user's perspective; and a design benchmark to analyze the landscape of similar and complementary products, design patterns and technologies used in the industry.
The Research stage allows us to leverage the knowledge and skills of existing players and ensure features and design differentiation in the market, and ensure costumer fit.
We formulate an approach to the product based on the user's needs and the business model.
This is the core of the creative process and it is where the concept of the product is formulated based on the user's needs and the business model (both identified in the Research phase). Here, the UX designer, the product designer, and the product owner work closely together.
This stage consists of 4 steps: mapping out the user journey, by describing each user's action, with various user scenarios; a decision matrix that helps prioritize the users' and product's goals while considering the product life cycle's current stage; drawing the wireframes, i.e., the pages’ structure and navigation flow to ensure interface usability and reduce design time; and finally, a mood board to ensure that the product's look and feel conveys the desired user experience and is aligned with the user profile and market strategy.
We bring the concept to life and put it into practice.
In this stage, the product designer focuses on creating a physical representation of the concept that has been defined up to this point.
It consists of 3 steps: a style guide, where we define a graphic interface’s style, considering colour palette, fonts, image style, input fields, buttons, and so on, to ensure consistency throughout the application; a graphic user interface design (GUI) which are the end-looking screens by applying the style guide to the wireframes; and a click-through prototype to facilitate the feedback from stakeholders or potential users and investors.
We guarantee that all requirements and ideas generated are realistic to implement.
In this stage, all the work previously done should be achievable considering the available time and budget previously settled.
It consists of 2 steps: a high-level architecture where we detail how the product will be built, identifying baselines for the needed technologies and skills to make it; and a project plan to define the major milestones and provides a general understanding of the project's structure, phases, intersections and interdependencies.
The MVP starts with a 2-week business case to present the vision and goals of the project and clarify all necessary business requirements. This step is based on main competitors and exploration of personas to then, finally, define a project timeline.
In this stage, we put in place a briefing that includes the information gathered during the workshop with the team and stakeholders. It presents the vision and goals of the project and clarifies all necessary business requirements. This is also where an FAQ session relative to the nature of the project takes place.
The high-level architecture involves the development of the technical design, with the ideal balance between complexity and reach, This is where we identify external dependencies from third-party providers, such as Stripe, Facebook, Amazon, and so on.
We then start the CI/CD workflow which is the setup of the issue management tool, code repositories, continuous integration system, and development & staging environments. It’s followed by the setup of the code repo and automated test framework, the staging environment and production servers, as well as the continuous integration ecosystem (i.e. servers, deploy hooks, etc)/continuous deployment.
Finally, in Feature 0 we deliver the first meaningful feature: a homepage, a login screen, part of the first dashboard… This step ensures that there is something demonstrable with the perception of value at the end of the Bootstrap Phase.
With the Data Model, we provide the first baseline of the product’s evolutive data model. It identifies the main data entities and relationships and baselines the data sources and data stores (i.e. relational databases, document data stores, etc.). This step also consists of iterating the product concept and designing the first version of the data model.
Here’s when we present the Proof Of Concept (PoC), Minimal Testable Product (MTP), or Minimal Viable Product (MVP), and we deliver and deploy the first version of the product - even if that version is the implementation of a concept. This helps mitigate technical risks and test the main business premises for developing a market-ready version of the product through a viability assessment.
On the production increments step, we review technical and business risks and the impact of the PoC, MTP, or MVP on the initial premises or Wave 0. Here, we also identify reusable components from Wave 0 to Wave 1 (i.e. often PoCs are not reusable). This helps gather feedback about the first integrated model and assesses the product's viability before moving to Wave 1.
Finally, the wave retrospective reviews the product state, evaluates wave success against business goals, and identifies improvements. We then design goals for the next wave & prioritize features. Doing this allows the team to analyze the work that has been done in previous sprints and plan consciously what should be the next mountain to climb.
This initial stage involves gathering crucial information to understand the project's vision, goals, and business requirements. We present the business case, outlining the project timeline, main competitors, complementary products, and high-level exploration of personas. This also involves asking and answering questions to define objectives and explore ideas, ensuring differentiation from existing players in the market.
During the ideation phase, we provide the blueprint and structure for the whole website, which defines the relative importance of content as it flows down the page.
The site map establishes the website's structure and content hierarchy for optimal navigation. Wireframing outlines screen structure and navigation flow, prioritizing your digital product’s functionality over aesthetics. Lastly, for the content ideation we help you plan the page content, providing guidelines for audience-adapted material.
During execution, we deliver the first significant page, typically the home page, ensuring it aligns with your target audience and market strategy. We then apply style to wireframes through GUI design, focusing on visual aesthetics and maintaining consistency across the website. Our Webflow development process follows best practices, incorporating interactions, animations, and responsiveness across devices.
Finally, we present results on a test domain, with client involvement being crucial for a successful outcome.
We provide your teams with comprehensive training sessions and Q&A opportunities to empower them to autonomously manage the content. We offer ongoing support, ensuring all necessary information for website updates is readily available, and we configure permissions within Webflow as needed.
Additionally, we seamlessly integrate the website with essential marketing tools such as Google Analytics, configure SEO optimizations, and seamlessly migrate and connect the desired domain. Leveraging Webflow's reliable hosting services, we ensure the website is published with optimal performance and reliability.
Imaginary Cloud started by migrating the existing database from Wordpress to PostgreSQL. A daunting task because of the thousands of items and large size of assets that are normal in a CG marketplace.
After the migration was completed, the team focused on migrating its infrastructure. The site was hosted on Heroku, which had relevant constraints on the ability to scale. Imaginary Cloud was able to migrate it to AWS, completing the first stage in just 2 months.
After the successful delivery of Stage 1, the client continued to work with Imaginary Cloud on a continuous development basis, adding more features to its product to fuel its growth. The team worked on many different elements, from payment integrations to sales campaign tools to facilitate marketplace promotional campaigns. Imaginary Cloud also helped Flipped Normals improve its Google positioning by implementing an SEO audit, which tweaked the site’s performance and content relevancy.
The project started off with a team meeting to list all the client requirements. This thorough investigation allows for an easier, quicker, and more cost-efficient delivery. This meeting was led by our Project Manager, which supports the team all through the project, and our Developer, ensuring all technical details are discussed.
Eurofound provided a solid brief that captured the existing infrastructure, their vision for the website, and the technical constraints and requirements. It was a challenging task that needed to be completed in 6 weeks.
Our developer started the development process by creating the back-end integration that would allow the new website to fetch content from the existing database. Using a Django framework, we were able to create an efficient and quick application that retrieved data, generated listings of results and allowed for more advanced options.
Imaginary Cloud and Eurofound met on a weekly basis to ensure everything was being developed as required by the client.
With the main software completed, the next stage was to develop the website to access such tool. For this, our developer followed Eurofound’s style guide to ensure coherence across the client’s digital presence.
Although no designer was allocated to this project, our developer followed UX/UI best practices, since he was able to touch base with several of the designers at Imaginary Cloud.
In order to improve the content navigation, Eurofound wanted to include an advanced filtering and search capability in their database. Having fully mapped the database content in the new software, our developer was able to create a set of category filters that allowed users to select the content of a given topic, and implemented a search element to the page, allowing the user to freely search any document.
Our UX designers will target the users profiles and identify their needs when using your product, considering its usefulness and effectiveness from their point of view. Research on design patterns and the industry's most used technologies allows leveraging and understand existing players' knowledge and practice. Plus, it ensures your product/design is specific and different.
We will conduct a UX review to set the product requirements considering the established usability heuristics in the field to deliver a consistent and fluid user experience. All information regarding insights and analytics will be summarised in a visual and compelling audit report that showcases the UX Audit's main findings, quick wins, and recommendations regarding your product's potential improvements.
Together, we will baseline the style guide to ensure that your product's different visual interface elements' are consistent and coherent. Running a UX Audit allows us to solve the main encountered problems with the execution of end-looking screens. Plus, all recommendations that resulted from quick wins acknowledgement will be designed for implementation.
The product backlog is a list of business and project goals and contains what is forecasted to be developed by the development team, and maintained by the Product Owner. It is a living document, updated continuously, prioritized, and ordered by business value. It may also have product improvements, bugs, technical questions, and so on. Its purpose is mainly to have everything that is needed to reach the project’s Product Vision.
In this stage, we also create a sprint backlog, which is a list of tasks that need to be completed during each sprint. We prioritise the user stories for each sprint and ensure that the team knows what they need to work on.
With the sprint backlog in place, the development process finally starts - sprint execution. Working through the sprint backlog, and delivering small usable pieces of software frequently allows for continuous feedback and refinement, ensuring that the product is always on the right track.
In this stage, we put in place a briefing that includes the information gathered during the workshop with the team and stakeholders. It presents the vision and goals of the project and clarifies all necessary business requirements. This is also where an FAQ session relative to the nature of the project takes place.
The high-level architecture involves the development of the technical design, with the ideal balance between complexity and reach, This is where we identify external dependencies from third-party providers, such as Stripe, Facebook, Amazon, and so on.
We then start the CI/CD workflow which is the setup of the issue management tool, code repositories, continuous integration system, and development & staging environments. It’s followed by the setup of the code repo and automated test framework, the staging environment and production servers, as well as the continuous integration ecosystem (i.e. servers, deploy hooks, etc)/continuous deployment.
Finally, in Feature 0 we deliver the first meaningful feature: a homepage, a login screen, part of the first dashboard… This step ensures that there is something demonstrable with the perception of value at the end of the Bootstrap Phase.
With the Data Model, we provide the first baseline of the product’s evolutive data model. It identifies the main data entities and relationships and baselines the data sources and data stores (i.e. relational databases, document data stores, etc.). This step also consists of iterating the product concept and designing the first version of the data model.
Here’s when we present the Proof Of Concept (PoC), Minimal Testable Product (MTP), or Minimal Viable Product (MVP), and we deliver and deploy the first version of the product - even if that version is the implementation of a concept. This helps mitigate technical risks and test the main business premises for developing a market-ready version of the product through a viability assessment.
On the production increments step, we review technical and business risks and the impact of the PoC, MTP, or MVP on the initial premises or Wave 0. Here, we also identify reusable components from Wave 0 to Wave 1 (i.e. often PoCs are not reusable). This helps gather feedback about the first integrated model and assesses the product's viability before moving to Wave 1.
Finally, the wave retrospective reviews the product state, evaluates wave success against business goals, and identifies improvements. We then design goals for the next wave & prioritise features. Doing this allows the team to analyse the work that has been done in previous sprints and plan consciously what should be the next mountain to climb.
TECHNOLOGIES used
It was the original codebase of the project; we raised coverage to the ideal value of 80% and replaced deprecated libraries with new ones.
We followed our Specialized Squad model, which provides a complete set of resources to deliver an end-to-end solution.
UX/UI Designers: Responsible for the design, architecture and implementation of all the experiences a user has when interacting with the platform.
Front-end Developers: Responsible for ensuring that the platform’s users can easily interact with it. They do this through the combination of design, technology and programming the platform’s appearance, as well as taking care of debugging.
Project Manager: Define project requirements and outline the scope of a future web app. After that, they provide a high-level project plan, and give the client rough time estimates.
This project delivered an in-depth understanding of the customer persona and their interaction with the service.
after delivering the improvements, user growth and adoption was back on track.
Invisible Homes has grown their community to over 35000 registrants.
more than a hundred agencies have signed up to Invisible Homes in alternative to competitors’ websites
