Co-working space

Groovy was looking for a management platform to help members to focus in their projects.
The demand for utilising co-working spaces has grown considerably and Groopy is now also offering meet-ups events, small conferences and mini hackathongs.

What I did

I was one of 3 UX designers. I collaborated with the team members in order to deliver solutions to the different tasks through an end-to-end processes.
Our Strategy was to work individually in a task and then compare our findings in group to reconcile a robust solution.

Our process

We started our research with a contextual inquiry. I looked into co-working paces taking notes of peoples behaviour (members as well as administrators). I followed it with a series of interviews to some of those users.
¥¥ The heuristic evaluation was utilised to analyse the competitors websites. In order to understand how these competitors were doing business, we
did a qualitative analysis which proved to be an important insider when looking into the UI elements utilised. We were attracted by two competitors
(Coworker and Tribes) because they were more focus in a management approach.

¥¥ Each of us collected our findings and put them together in an affinity map. This analysis allowed us to find two major insights to consider as our
primary tasks:
 — The need for a system to manage co-working spaces and
 — the need to understand members in order to increase their numbers.

¥¥ The team worked in a problem statement: this helped to keep the team focus and on track during the development of a solution.

¥¥ To turn this challenge into an opportunity we gather our possible solutions utilising the ‘How might we’ approach.

¥¥ From the beginning we felt confident with the hypothesis but while working in the metric, we realised that the problem statement was in fact complex to tackle. It was through this realisation that the team decided to focus in the administrator person as our main ‘user’.

¥¥ The persona together with the storyboard helped to keep the problem statement into context.
¥¥ To understand better the path utilised by the user we developed a simple user flow. We also took the opportunity to develop a user flow for the member.

¥¥ To find menu’s definitions for the member’s dashboard, we tested 5 people with card sorting.
¥¥ The paper prototypes allowed us improve the administrator’s tasks through users feedback.
¥¥ One of the team members created the mid-low clickable prototype using Sketch and Invision. We tested it with another 5 people and made the
changes accordingly.

What we found

Through the research face we encountered that in order to provide a seamless experience to Groopy’s members: We needed to focus primary in the administrator as a starting point. If the administrator could have a very efficient system to manage booking, membership and payments. Groovy could then offer a better service to its members.
In order to manage bookings and payments: Groopy would need to understand its clients (members).
This is why we took the membership phase as primary step. Having a platform that could help the administrator to collect member’s information in an efficient way would save administrator’s time.
During the research and design processes, we realised the complexity of the problem statement. 
The three main focus points: bookings, payment and membership were already a lot to tackle within 2 weeks (time given for the project). Furthermore having two main users: administrator and member would
make the project even more tangled.

What we recommended

Even though the intricacy of the project, it would be great to study each problem in phases taking it from both users perspectives. Once these phases are completely studied and designed it will set up a very robust and efficient platform.

What I learnt

As my first group project it was quite interesting to learn about the dynamic of a team. I found very important and rewarding how having 3 different opinions contributed in an efficient way to solved a problem very quickly (sharing and compering with each other output).
I learnt that by communicating, the team can achieve solutions in a quick and efficient way as well as being more accurate when coming up with those solutions. The communication helped us to stay focus in each others tasks. I learnt from the other team members strengths, the importance of documentation. Delegating to other team members early in the project. How egos have to be put aside. How time management is important for keeping the project on schedule. Encouraging and supporting each other. The importance of having the right tools.

Show your support

Clapping shows how much you appreciated Carlos Solarte’s story.