HubbleHQ

As Product Designer it was then key to emphasise with the different archetypes' various needs and pain points. Using the personas, it was then important to think about the different user stories and how they fit into the user flow within the system.

Once the squad had a good understanding of the different user stories and userflow, it was then my job to articulate this research into device specific flows - from sketches through to wireframes.

Once the team had put the wireframes through its paces, happy with placement of key elements and information hierarchy it was then my duty to build a prototype using Sketch and Invision. The prototype by its very nature comes with limited interactive elements, but once in front on a user gave it would give us good understanding of what wasn't working.

It was then my duty to start recruiting a mix of tenants and hosts through various channels. I approached users that had recently been through the platform funnel with varying outcomes, advertising at our HubbleHQ Wizards of Ops Events, reaching out to the WeWork (we were based at WeWork Monument) Community. Once we had a good number of recruits, I then organised the testing sessions by planning various tasks and scenarios in which we could validate the prototype and gain some useful insight. Some testing sessions were less orchestrated and formal and involved some guerilla testing to validate specific parts of UI or UX. We also ran some AB tests through various remote platforms to gain quick insight on specifics when needed.

Once I conducted the user testing sessions or collated feedback via other means mentioned, the next step was to then synthesise the results. I had to transcribe the sessions and add notes to the testing sheets which validated task completion or fails and collected other pieces of feedback and suggestions. From this data, I then facilitating workshops like an affinity mapping session that allowed us to visualise pain points and feedback, categorise and then continue onto feature prioritisation.

Once we had synthesised the results, I could then iterate the designs to reflect what new features or improvements could be made across mobile and desktop. Now it was important to produce high quality UI, plus get the project files ready to handover to the engineers. It was then important to work closely with the engineer to iron out any build or accessibility issues . Then finally, correctly labelling and organising layers makes the engineers life a lot easier once inspected in the handoff platform, in our case Invision.

At HubbleHQ, I was the champion for the design system and managed the components in partnership with the lead engineer. Once the designs were handed over to the engineers, the next step was to look at building the components in Sketch, making use of the responsive and override features. If the component graduates into the design system, it was important to ensure it could be used by other designers in the future enabling them to quickly build new prototypes and features.