Product Designer

MyHome Client Portal





A digital space for a builder and homeowner to collaboratively on new residential builds or renovations. 

Scope

Buildxact at this stage had a missing nexus, it was connecting well builders with trades (B2B) but not builders with clients effectively (B2C). 


Following a competitive analysis and numerous requests from clients, an investment of 6months with an agile team of 5 engineers delivered a full responsive module used by roughly a third of our customer base.*


My input was to research and design an optimal experience by which a minimum viable product flourished into an ecosystem. I delivered the foundational design for a responsive app used by a third of our customer base after a year of launch.   


Responsibilities involved:

1. User Research

2. Stakeholder management

3. Prototyping

4. User Testing

5. Success Metrics

6. Design System

Timeline: 4 months

“We need a client portal so we can share items easier to our home clients”

Customer Quote




Definition of Scope and User Research

The research took the shape of several in-depth interviews to better understand user needs and possible market gaps. Assumptions were clarified while achieving a better scope.


A customer journey was mapped out from the unstructured interviews that allowed us as a business to architect the app in such a way not come across bottlenecks in the future. Such as: 


Allowing multiple projects owned by different builders to co-exist under the account. 


To allow the client to own the project rather than administered by the builder.


Allow growth within the portal into areas identified as good to have like design and maintenance. 


Personas as well came in handy to articulate in our presentations of a new type of customer and user as a company we started servicing.


Stakeholder management

‍‍‍‍‍‍‍‍‍Periodic catchup meetings ensured the MVP was executed in a timely manner, with updates given to critical stages of the design process. The designs allowed easier strategic decisions with respect to the ecosystem.

Prototyping

A full click-through prototype was set up to test information architecture, navigation, labeling, and small screen interaction. This later was used as walk-through material for the development team.

User Testing

With a fully clickable prototype, we tested the product first internally than externally. Capturing insights and iterating designs based on a hybrid of Qualitative vs Quantitative data.

Success Metrics

The success metrics were not defined as a product team, since other features were in the product roadmap meant the business was aware the project had to stay dormant for a while, any growth was organic and priority only was given to few enhancements and bugs. 


Overall the uptake was steady and consistent, with a third of users finding value, this correlated roughly with the number of users requesting the feature that tend to have more projects at a go as well as more structure in their process.

Key features delivered:

  • Social login integration
  • Smart visual personalization for branding
  • A chat service
  • Ability to view documents and raise comments against objects.
  • A portfolio area
  • Additional functionality such as digital acceptance of documents
  • Notification model via emails and in-app.

1/3 of customer base adopted the module

“I like client portal as I can share with my clients documents knowing I dont need to dig in my emails”