High-level system flow
Challenge during the flows
Creating a platform multi-stakeholder business idea involves a lot of considerations, we had to accomplish for the MVP.
We defined the various touch points of the business idea: Employer, Employee and Workspace managing, as well as to understand the horizon of work and time required by tech & design. To build the system that the founder envisioned!
User-stakeholder stories
to begin flows for primary tasks of 3 main user types
App for the employees
The main users the app is catered for, are the employees.
Key tasks: Book & check spaces, browse remote spaces based on your vicinity, reflect space availability, and build a habit of QR sign-in as Norway doesn’t have a common practice to log down entries but it's required to keep track of spaces.
Profile with minimal information to edit.
Inspired by familiarity of use from: Google maps and Airbnb
Unfortunately, this <booking flow> has been postponed to Phase 3 of the launch when there are stronger backend and office & desk tracking integrations. In the meanwhile, it was okay to launch as most of the spaces always were at 50% of its capacity!
Problem faced:
How might we embed tracking of the space?
↳ The hardware integration of seltos, a door lock system came in! This was a revelation because the culture in Norway is very open that sits on trust; so it would be very odd to have users enter with identity credentials. How can remote modify this?
Goal: For a seamless transition of behaviour adaptation- we tested users to adapt to scanning QR codes before/ after entering which updates the system!
User Testing
Moderated user tests on google meet, following a semi-structured format. With a script enough to allow them to share their thoughts and purposeful enough to pass the message that they are the expert!
Testing goal: To test the level of acceptance towards the new concept in terms of functionality, usability and user experience. Understanding certain terms, and expectations from certain sections or actions.
Method: Clickable prototype with tasks and scenarios.
Learning: Use a screener to get more participants!
One of my first Online User tests, where I referred to a semi-structured script with a colleague and my senior observing, along with the participant!
Consent was taken ✅
Prototypes were accessed on phone with set task goals, to understand the level of familiarity of use.
Click the image to navigate through the sorted user tests
Before- After Insights
After employing all the smaller insights, and prioritizing them based on need;
The common problem areas were:
↳ Clarity of terms like 'OTP,'
Solution: More cultural-familiar methods.
↳ Preference to book certain spaces to make an informed decision,
Solution: Transparency during booking with a floor-plan view
↳ Vocabulary around the main and current workspace,
Solution: Reassuring message during booking temporary spaces and referring temporary office as 'travel workspace'
Employer web-app
Key tasks: manage, update, delete and add users, get/change billing details, and change the type of subscription.
Problem faced:
How might we embed tracking of the space?
↳ The hardware integration of seltos, a door lock system came in! This was a revelation because the culture in Norway is very open that sits on trust; so it would be very odd to have users enter with identity credentials. How can remote modify this?
Goal: For a seamless transition of behaviour adaptation- we tested users to adapt to scanning QR codes before/ after entering which updates the system!
Considering all cases: Adding members (employees) through 2 methods, varying by company size.
Flexibility & Efficiency of use: Gamifying payment screen with live calculation for upfront success feedback- a solution for companies as little to massive in Remote's radar.
Crucial visibility of system status of invitations sent and accepted-
to build trust around Remote's workings.
Overview of navigation
As there weren't many actions to take in Phase 1 for the admin, and as Remote's business team wanted to test the waters and move ahead. We grouped primary tasks into 4 simple pages to keep it all on view! I and Leighton created high-fidelity wireframes for each flow of the app. These were the hero of review sessions with the client and our Head of Design.
Learning: We also (after 60% of the screens were approved internally) created a design system to ensure that there was consistency amongst all the different screens
The primary focus on 'Signing up' as Remote is in its first rounds of gaining traction.
Problem faced:
How might we log in users onto the platform?
↳ Considerations about the company website being on a different platform and us not having access to it, if we do- only minor changes. Whether to redirect or not? Does one log-in suffice for all three portals?
Goal: For a clear entry point into the platform for respective users.
Login for solely the employer portal.
The co-working flow is currently manual, as it involves thorough vetting.
Key screen providing value to the company's well-spent offerings with key actions for admin.
Reflections
System touch points
↳ In the future, to design an eco-system map for a concept like this which includes many stakeholders and actions at play. It helps in fleshing out a clear set of requirements.
Lack of explorative stage
↳ To have a connected experience with spaces and work- solutions through shared communities and groups or tools to connect in today's remote work environment could be explored. But Remote already had a base consumer and need validation.
Design system early-on
↳ As I was onboarded in the middle of the 'lean process' [in a start-up] for Remote- unknown to some gaps. Late acknowledgements of certain screens resulted in revisiting some of the gap screens to be designed.
Timeline lock-ins
↳To take into consideration new findings that would end up requiring more time- for eg: the integration of hardware tech of the door-lock system in this case + more features to accommodate it.