REMOTE SPACE
Made for online collaborative working
Design based on project team workflow and way of thinking:
Improving the design process and project atmosphere
Improving the design process and project atmosphere
Project Types
Internal Virtual Project Competition within the Netease Game
Role
Conducted User Research
Functional Hierarchy Analysis
Wireframed sketches on Figma
Prototyped product
Project Length
2 weeks
Tools Used
Figma
3D Max
About
What is REMOTE SPACE?
Background
During the lockdown period, we were all working from home, the complexity of our environment configuration increased due to the extensive use of internal office software. In response to this challenge, our company initiated a Jira software design competition. My project actively participated and proudly secured the second prize.
Purpose
1.Achieve office integration
2.improve the working atmosphere
2.improve the working atmosphere
1.0
Questionnaire
User Research
All my group members (10 people) helped me answer the questionnaire I designed,
I selected the most core issues for data induction.
I selected the most core issues for data induction.
What problems did you encounter when using Feishu?
![[object Object]](/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fdata_1.38fa189c.png&w=3840&q=75)
1
Due to the different projects, Feishu's functions are not enough to cover all needs
2
Other tools of Feishu must be used together, otherwise jira will look very tasteless
3
Feishu cannot communicate quickly
4
Jira has limited functions, which is not good for pm update tickets
5
If want Feishu to run smoothly, have to relearn other Feishu software
6
The use of tools is not within the scope of cooperation with Feishu
7
Many function permission settings are too simple, without clear hierarchy, which is not conducive to collaboration
What aspects of our project do you think Feishu can’t cover?
![[object Object]](/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fdata_2.75fced18.png&w=3840&q=75)
1
After the files in the car testing process are uploaded to the cloud, permissions must be distinguished. The process is unnecessary
2
The unity test cannot directly transfer the file, we need to express it on the tickets, and then find the relevant person to test the file
3
There is not one meeting entrance, and the Feishu reminder has little effect and significance
4
Figma documentation cannot be linked directly
In what ways has it affected the efficiency of collaborative office work?
![[object Object]](/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fdata_3.aecae6d6.png&w=3840&q=75)
1
Slack and Feishu did not cooperate, and communication costs were enhanced at the tool level
2
During the remote work, I often couldn’t find the developer during the communication, and I was often found after get off work to ask about the job requirements
3
There is no working atmosphere, and there are often cases of inattention
4
Feishu covers the needs of most Internet projects, but does not cover the special needs of vehicle-type projects
Is there any part of communication that needs to be improved?
![[object Object]](/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fdata_4.1e46e737.png&w=3840&q=75)
1
When there is a demand problem, you can communicate quickly instead of finding someone;
2
If people have something to leave during working hours, can develop the habit of changing status?
3
Many times it is necessary to download files synchronously, need to transfer the file to the other party first, and then wait for the other party to download, which affects the efficiency
4
The content that is not clearly described on the tickets needs to be chatted privately, which is too time-consuming
5
Is it possible to know whether colleagues are free to communicate at any time, instead of being ignorant across the Internet and having no collaborative office atmosphere
1.1
User Research
Interview
For the questionnaire research, I chose two of the most representative colleagues
to conduct an interview and conduct in-depth research on their problems.
to conduct an interview and conduct in-depth research on their problems.
Amy Li
Senior UX Designer
Driverless-R Team
?
Under what circumstances did you feel the obvious communication inconvenience?
A
There are many people who need to communicate with us in ux. We often need to connect with pm and programmers, but it is often inconvenient to find the parties.
?
If there is a communication barrier, how do you usually solve it?
A
We generally use slack to communicate, but slack will only show whether you are online, even if you are not online, you can also show online, so this is useless at all. Is there a function that can display whether the person is at the station in real time, without looking like being monitored?
?
Do you think there is any way to solve the existing problems at this stage?
A
I will do other things first and wait for them to reply, but this is very inefficient, because some tasks cannot be carried out without direct communication.
Tim Guo
Front-end developer
Driverless-R Team
?
What is the biggest problem you encounter when using jira?
A
1. The ux requirements document and the development document cannot be synchronized, and it is very troublesome to switch files back and forth
2. The development document does not have the online loading function in jira, and re-downloading is a waste of time
3. Without a file sharing platform, the functions of Feishu are still not powerful enough
2. The development document does not have the online loading function in jira, and re-downloading is a waste of time
3. Without a file sharing platform, the functions of Feishu are still not powerful enough
?
What kind of form do you think can best solve the existing problems encountered?
A
Our previous project team had a back-end product called snv. This product is used to store all art resources and program resources. It is very useful. It would be great if we had this kind of product.
?
What kind of form do you think can best solve the existing problems encountered?
A
Too much needs to be improved. If jira is the core tool of our project, then all communication and file resource libraries should be merged into jira, so that jira can be used as a platform to replace physical offices for collaborative work.
1.2
User Research
User Responses
Through the round of user responses, I screened and invited them to conduct interviews,
and I made their interviews into affinity diagraming, so as to more easily find out the pain points of users.
and I made their interviews into affinity diagraming, so as to more easily find out the pain points of users.
Working atmosphere
A quiet space
No one disturb
A quiet space
No one disturb
Have the feeling working in the office
Efficient communication
Quickly understand requirements
Quickly understand requirements
Clear working schedule
Colleagues work and rest in the same schedule
Colleagues work and rest in the same schedule
When looking for colleagues to communicate, I can find him/her immediately
There’s so many things for me to solve in my family,it’s hard for me to pay attention to my work
Difficulty concentrating while working from home
It is too difficult to work online, every time needs to be communicated, I can’t get in touch with that guy
There is no fixed break time, so colleagues always contact me in the middle of the night
Because there is no need for commuting, I often work overtime unconsciously
Too many other things grab my attention, it's hard to concentrate on work
I'm always busy with other things during the day, and I start working overtime at night to catch up with work
The time is too free and flexible, so that everyone's working hours are not completely in one channel
Often work overtime unconsciously
Communication costs are too high
Insight
1.The project team members can work together in the same channel or virtual space, which can calibrate the work schedule and quickly find someone to communicate with.
2.Improve the functionality of jira, enable jira to connect to more software
Pain Points
1.There is no office atmosphere, and the parties are often not found when communication is needed.
2.Jira can't match many softwares. Currently, it is only friendly to pm's work. It can't coordinate the work of ux designer and programmers, and the file matching is very slow.
Observation
It is often necessary to communicate during work, if not communicated in time, it will affect the work progress. Secondly, jira is often needed for collaborative office work, but currently jira does not reflect the convenience of jira due to functional limitations.
What we need during the work?
Easy to communicate
Office atmosphere
Easy to find people
Real time update
Jira platform
Virtual office platform
Repository
tool collection station
2.0
Needs Analysis
Work Flow Analysis
Product development stage
Communication Needs
- PM-UX
- UX-UI
- programmer-UX
- QA-programmer
- QA-UX
Jira Doc Needs
- Product requirements document
- UX design introduction
- Unity development document
Jira Function Needs
- Ux/Pm Meeting
- Weekly Meeting
- Daily Stand Up
QA running test stage
Communication Needs
- QA-UX
- QA-programmer
Jira Doc Needs
- /
Jira Function Needs
- QA meeting
Iteration stage
Communication Needs
- UE-PM/UX
- PM-UX
- UX-UI
- programmer-UX
- QA-programmer
- QA-UX
Jira Doc Needs
- UE report
- Product requirements document
- Figma design prototyping
- UX design introduction
- Unity development document
Jira Function Needs
- UE meeting
Communication
Needs talking
The communication needs are high, and the communication can be linked with the jira platform to enhance the communication initiative
Meeting
The demand for meetings is also very high, basically every day, and the meeting function can be combined with the jira platform to increase the utilization rate of jira
Jira software
3.0
Design Process
User flows
working space
Office homepage -
find a suitable place
find a suitable place
Help your team to find a suitable place to work, there are 5 kinds of rooms for you to choose, you can find a good place based on your team numbers.
working space
Office homepage -
Booking & enter an office
Booking & enter an office
Lock the venue by making an appointment and include it in the plan for prompts to improve office efficiency.
working space
Office -
An Office atmosphere
An Office atmosphere
Visualize the office scene to improve the working atmosphere and facilitate communication.
Resources bar
You can quickly obtain document resources and facilitate resource summary.
Members Bar
Fast communication channels to reduce to jump to other products.
working space
Office -
private discussion
private discussion
This is based on the design of the game Among us: you can talk freely when you enter a certain space, and no sound can be heard from the outside world.
working space
Meeting Room -
Private communication space
Private communication space
The interface is designed in a scenario-based format, integrating functions into the scenario to make the experience more interesting.
working space
Meeting Room -
Slide Sharing
Slide Sharing
You can directly share the screen and convert the meeting room scene into a slide interface.
Jira platform
timeline -
check the schedule
check the schedule
The timeline can help project team users directly see the project progress and the priority of other functional requirements, which is a feature that was not available in the original Jira.
Jira platform
Board -
New Tickets Edit
New Tickets Edit
This function reuses the functional structure of the original product, but optimizes the level of information display to make the needs clearer.
Boards -
edit new tickets & Add assignees
edit new tickets & Add assignees
Use side pop-up mode to not block information from other tickets. You can select multiple stakeholders to join with one click, saving the interaction process.