top of page
AutoDesk Collaboration
AutoDesk programs have been used by designers who created projects for school or work. This team project was creating a collaborative cloud-based platform for users who from the different academic background and contribute their knowledge to accomplish the same project. According to our research, there are some existed collaboration programs which can tracking program progress, but very few are focused on the specific needs of a 3D designer. Our mission was to come up with a collaborative platform that included all of the functionality that a 3D designer or team member could be satisfied.
Teammates
Our team was consist of five UX/UI designers and an Industrial designer with a background in 3D Max of AutoDesk program. Through teamwork, we developed an efficient platform which we consider can be successful.
.
Zack
UX/UI Designer
Stephanie
UX/UI Designer
John Paul
UX/UI Designer
Mike
UX/UI Designer
Sandeep
ID Designer
Mounica
UX/UI Designer
First of all, we were looking for the similar collaboration programs on the market and then to analysis what functions had to provide. The most two popular programs we looked are Wrike and Redbooth. These two programs are helping teams to collaborate the projects and work efficiently. We tested the programs and analyzed the features that they had.
Competitive Analysis
Wrike
Wrike is an online tool for project management centered around task collaboration. Firstly, we were using post its to create a flow diagram of Wrike, so we can look into the insight of Wrike, which include the method and structure of the program worked. And then we were able to create a state flow for Wrike and to find out positive and negative features that we encountered while we collected the information.
Features:
-
It enables users to manage and track multiple projects, deadlines, schedules and other workflow processes.
-
It allows being invited as users or as collaborators.
Positive:
-
Real-time activity stream/live editing.
-
Collaboration surrounding individual tasks.
-
Ability to create subtasks allows for more details.
-
The project timeline is a helpful visual tool.
-
Mention functionality using @ tags to keep members up to date in discussions panel.
-
Useful Time-tracking feature.
Negative:
-
The number of features overwhelms user at times.
-
The interface can be counter-intuitive.
-
Not enough customization of look and layout.
-
Email task notification outside app creates disconnect/ need to keep checking email.
-
Not enough interactive feedback throughout the process to confirm task creation process.
-
.Onboarding offered late in the introduction phase.
-
Dashboard panels do not stand out and nothing distinct.
-
Unable to have private chat or communication.
Insights:
-
No Hierarchy
-
No private chat
-
Can see other user actions with a specific color
-
Users (if projects are deleted) cannot see tasks later on
-
Color coding for tasks, easy to recognize
-
All widgets are the same color
-
No options for current task
-
The user can customize the dashboard
Redbooth
Redbooth is a collaboration and communication platform. We were using the same way to analysis Redbooth, include using post its to map out the structure and then create flow diagram to look insight of Redbooth.
Features:
-
It provides a single place for shared tasks, discussions, file sharing, group chat and HD video conferencing.
Positive:
-
Dashboard and interface are simple, clean and user-friendly.
-
Introduction an onboarding effective.
-
Ability to assign roles w/permission easy to use.
-
seamless HD video conferencing & group chat built in.
-
Links located all in one section so easy to navigate.
-
Filter tool allows the user to find files quickly.
-
premade task list templated help to cut down setup.
-
Helpful feedback in the form of tooltips, popups and positive feedback throughout the process.
-
Tasks both public & private/ use workload view.
-
Reporting section is very robust and has several visual overview features.
Negative:
-
Cannot create dependency for tasks.
-
Limited customization/basic color options only.
-
Conversation section a bit clunky and disjointed.
-
Task list area and workflow seem pointless or redundant in some areas.
Insights:
-
Info. will be lost after you exit workspace
-
No due dates for tasks
-
No notification of new work
-
Consistent UI of workspace
-
Public and private task section
-
Different templates to work on
-
Can define your own workspace color and name the workspace
-
Tasks are shown in the graph
-
Task sections are color coded
-
Activity list in the graph view
-
Choose all users or individual users for tasks
-
Calendar with time tracking feature
Design Thinking Workshop:
We attended a Design Thinking Workshop, which was an excellent opportunity for us to meet some people who were actually working and using programs of Autodesk. They talked about their demands and needs when they were using programs on daily, which was helpful for our design platform.
Our Philosophy:
Smart program intuitive features, such as, intelligent version tracking, live editing, with the ability to see the big picture and to see the fine details on one screen.
"Stop tailoring your work projects to the project management software, start tailoring your project management software to your work."
Logo:
Design thinking workshop really helped our team to understand and tailor user's needs, so we came up with the idea to design a program and decided to name our program STITCH.
Future State Flow:
We were picking some features and structures that we should have in our design platform after analyzing Wrike and Redbooth. We sketched our rough ideas on the whiteboard and were able to come up with the first draft of state flow.
And then, the first draft of state flow would lead us to design our wireframes and UI design pages which according to our thoughts and ideas.
Wireframes:
Based on our future state flow diagrams we created the basic layout of wireframes.
UI Design:
During the design process, each team member was asked to design two main page. After that, we had a meeting to discuss whose design we would be continuing to work forward. And then each team member took sections of the wireframes structure to design in, which using that team member's UI kit we decided.
Prototype:
bottom of page