Home         Work         About         Contact

NOM North Office Management**

UX/UI, UX Research, UI design 

**This project was developed as the final challenge inside Ironhack’s UX/UI bootcamp projects, in collaboration with a design studio as client (North Studio). It was selected by a design jury as one of the best entries out of all projects.

Scope of the project
We were asigned a real client (North Design Studio) which proposed us the brief to fulfill. We were asked to design an office management tool to track and handle the logistics and needs of a medium sized team office, just like theirs. An extra requirement: the tool also had to be capable of managing an office relocation.

Requirements
Develop both mobile & desktop interfaces, adapted to the use cases of each device.
Duration
We had a sprint of 2 weeks to fulfill this task.

Team
The project was developed in colaboration with Rafa Moreno and Nacho Tramoyeres.

User profile
Medium sized design studio (about 20 people + person in charge of the team logistics).




[ 1 - Research phase ]
Primary Research

a) Interviews
We conducted interviews with 10 users & 2 stakeholders, all of them involved in similar team structures and workflow as our client.

b) Primary Research Goals
· Know how mid-sized teams organize inside an office.
· Learn what tools they use and what needs these tools cover.
· Understand the problems they face on their daily basis.

Secondary Research

Indirect Competitors
We didn’t find tools that strictly focus on organizing the logistics of a design office, but we did realize some suites and tools we’re spreadly used by all the teams we reached, therefore we investigated them for reference. Here are some of them:

Asana · Trello · Calendar (iOs) · Airtable · Todoist · Google Calendar · Jira · Notion · Slack


[ 2 - Definition phase ]


User Persona A: The team’s office manager.

User Persona B: An office’s colleague.




Problem Statement
We realized we were facing two problems (resulting of each type of user) at the same time:

a) Office managers of medium-sized studios need a more efficient and unified way of working because they are worried about missing any pending task.

b) Office workers of medium-sized studios don't want to be distracted or waste time in office logistics or management tasks, because they want to be focused in their work.

[ 3 - Development phase ]


The Solution
Develop a management system that helps Office Manager to keep logistics scheduling and organization under control, as well as give employees acces to resources and information without distractions. This system stands upon 3 pilars:


1) 🖥🔁📱 It must be a cross-platform responsive web app. (Client mandatory)
2) 👩🏻‍🔧👨🏻‍💻👩🏼‍🎨 Functional and handful for the different office roles (not only for the office manager).
3) 🤔💡🛠Should respond an anticipate the Office Manager’s needs. (Client mandatory)

The Creative Concept
We based the concept upon some of the insights revealed during the interviews: office enviroment are oftenly stressful and busy. So we wanted to make the solution to produce the opposite effect: bring a chill and calm vibe while using it.
Therefore, we decided to go for a colour palette based on trees and earthy tones, friendly-yet-optimal fonts for daily work, and a big idea: we wanted the app to feel like a small urban garden brought into the office. A little oasis where you can keep things under control.


The design sprint & MVP: A complex sitemap

As we progress during the research, we came to the idea that the way an office manager leads office projects, is different from the type of project a team develops for a client. So we focus the tool in a way this person could find easy to create and edit projects involving the logictics of the office as well as the people in the team. 

In the following image you’ll notice a dashed line, it divides the focus for the first design sprint (the Minimum Viable Product) on the left side, and leaves on the right side the “should have” features (the ones that should be in, but aren’t core or that important to function) and also the “could have” features that weren’t a priority (the ones that aren’t even necessary, but would be nice and helpful).




User Flow & Prototypes

For this MVP we wanted to be sure that the users can accomplish at least two different basic user flows:


a) Desktop (Office Manager): create a project




In this flow, the office manager uses the platform on desktop and is capable of creating a new project, based on one of the proposed templates. This templates provide predesigned tasks according to different needs and types of office projects. Plus, the manager can edit the tasks of the project and assign them to a coworkers.
b) Mobile (Office Worker): check an asigned task



In the second flow, the office worker receives a notification in the mobile app. Then goes from the Home to the Schedule, and there he can check which tasks has been assigned to him.

[ 4 - Conclusions ]


Next Steps
1) Even all the functionalities of the mobile version to the desktop one.
2) Add all the features proposed that were left out the MVP.
3) Expand the scope of the tool to other types of teams/companies.


Key Learnings

1) Teamwork & task asignment: it’s important make a clear roadmap at the beginning and and learn the strengths of all the team members to optimize the workflow.

2) Expectations vs Reality: We first thought about a lot of features, but when tried to pull them off at once, quickly realized it wasn’t viable. Therefore, we focused in what was important for the MVP according to the basic needs of the main user persona.

3) Covering 2 user profiles with one solution: though the brief started focusing only in the figure of the office manager, we inferred we could not leave the rest of the office apart. Therefore we developed a multiprofile solution, which may seem easy but forced us to reorder the priorities of the project.