
Designing a flow with flexible booking options within the actual website.
Team: 3 UX Designers.
Role: Visual / UX Designer.
Time: 4 weeks (October 2021).
Directly responsible for:
UX Strategy, UI Design using Marvel and Figma (wireframes and high fidelity mockups), Usability testing with internal users, Design documentation.
Participated in:
UX Research, Benchmarking, Analysis and sensemaking, Co-ideation workshops, Creation of user flows.
23 million workers switched to remote work in Latin America and the Caribbean due to COVID-19*, directly impacting the assistence to coworking spaces.
This has changed and will keep on changing how we work. Comunal needed to come up with a flexible solution that could adapt to the “new normal”, with a focus in remote workers, digital nomads and freelancers.
*Source: Organización Internacional del Trabajo (OIT)
Comunal Coworking design, implement and administer workspaces that optimize resources for the companies with the goal to create an ecosystem of collaboration within their spaces.
They have 12 branch offices in Perú and 1 branch office in México.
Design a new service that allows any person that needs a workspace to make an unique reservation in a simple and unattached way (without contracts) using their app.
Implemented a new flow within the website with functions to search and book workspaces in a fast and flexible way.
This solution was evaluated with 4.8 / 5 for Satisfaction, 9.5/10 chances to RAF and 65% Success Rate.














How might we include in Comunal’s actual system, a section to register, search, consult and book flexible workplace spaces immediately, for clients without a current contract?
by implementing a new flow within the website (responsive website)

because in Perú, 88.5%* of the population has access to the internet through their cellphones being Android the OS most used.
Source: INAI
with functions to search and book workspaces in a fast and flexible way

because the principal reasons to book a workspace according to the research is to “solve an emergency”, “book an important but indefinite meeting” or “meetup according to convenience”.
As the solution demanded a flow to be implemented within the actual design, there had to be an analysis of the Information Architecture, creating the Sitemap
This was essential to define where the solution will be implemented and what would be the steps of a regular user. It was captured in the User Flow
Finally with the basis and the structure defined, the sketches were created and disposed in a Wireflow



The Writing to describe the services wasn’t descriptive enough.
They were confused on why the would need an hour for the registration.

They would like to know who is sharing the space with them.
More information is needed on what they are purchasing.

The button on the last process of reservation was misleading.
The registration was duplicated.


Used the official branding in the UI so it could be aligned. Defined their uses, according to the manual.

Created cards to show the locations, specifing the proximity as it was the main and most important feature asked.

Created cards to show the type of spaces, in which floor it could be found and the capacity (due to COVID).




General Satisfaction
.png)
Task success

Promoter Score (NPS)

4.8/5
65%
9.5/10

Collaboration between departments is essential. We were lucky enough to have an small workshop with the IT department and it changed a couple of things as we had a different approach to the solution.
Stay focused, stay alert. Even though there might be some difficulties within the process, you are the face of the company while the project last in front of the clients. Be professional always.
Architecture Information is golden. Finally it was given to me the opportunity to work with it and I enjoyed every second of it.

Check the UX Writing. There are a couple of terms that are not embraced by the users, such as “Dashboard”, “My problems”, “Bag of hours”, among others.
Give control to the user. Allowing them to share their information in their profile for networking or keep it private.
Thanks for reading!
