OVERVIEW
项目概述
Problem Statement项目概述
问题陈述
Atlassian’s current product lineup serves a wide range of enterprises and organisations, but there is a gap in addressing the unique challenges faced by college students. College students often rely on multiple disconnected apps for group projects, which creates information gaps, a high operational burden, inconsistent app usage, and cognitive overload. These issues are especially challenging for groups with varying app preferences and software skills, highlighting the need for a streamlined, integrated solution tailored for students.
Atlassian 目前的产品线主要面向各类企业和组织，但在应对大学生群体面临的独特挑战方面存在不足。大学生在进行小组项目时往往依赖多个不连通的应用程序，这会导致信息不对称、操作负担重、应用使用不一致以及认知负担过重。这些问题对于具有不同应用偏好和软件使用能力的团队尤为突出，凸显了推出一个为学生量身定制的简化集成解决方案的必要性。
By simplifying the information architecture and integrating task management, file sharing, and communication features, along with AI-powered task creation and customisable options, this solution creates an intuitive all-in-one platform. It effectively reduces the complexity of switching between multiple apps and enhances project management efficiency, enabling students to complete their tasks and projects more efficiently.
通过简化信息架构、整合任务管理、文件共享和沟通功能，结合AI智能任务管理，以及提供适度的自定义选项，创建了一个直观易用的all-in-one平台。它有效解决了学生在多个应用中切换的复杂性，并提升了项目管理效率，使学生能够更加高效地完成任务和项目。
2023年8-10月，2024年3月完善
Project Info项目信息 Enterprise-College Collaboration Degree Project
校企合作毕业设计
Tools工具 Balsamiq, Figma, Spline3D and Adobe Illustration
Demonstration Video
演示视频
Space-Project-Content Navigation
The new product’s user flow is built on a simplified three-tier structure, allowing quick access to team spaces via the sidebar. The Activity module offers diverse communication tools for real-time collaboration. Once inside a project, users can manage content directly through the task board with easy tab navigation. This approach focuses on multi-project management while simplifying functions within the framework, making it easier for users to navigate.
新产品的用户流程基于简化的三级信息架构，用户可通过主页面的侧边栏快速进入团队空间。在团队空间中，Activity模块提供多种沟通方式，便于实时获取团队动态并协作。进入项目后，用户直接访问任务板，通过Tab切换管理内容。这个流程以多项目管理为主，将功能简化集成到框架中，降低用户的使用难度。
Quick Capture Tasks & Reallocate
In addition to the standard create button, the system includes a “Quick Capture” feature for swiftly recording tasks, notes, or starting a chat. Users can drag and drop tasks from the quick tasks list onto any project board, allowing them to easily jot down ideas and organise them later when they have more time.
除了常规的创建按钮外，系统还设计了一个快速捕捉功能（Quick Capture），用户可以快速记录任务、笔记或开启聊天。任务卡片可以从快速任务列表中拖放到任意项目板的任意列表中，方便记录灵感，并在有时间时整理到相应的项目中。
Customisable Widgets Within Defined Spaces
Within the space hierarchy, the main structure (including space overview, projects, and activity) remains fixed, but users can customise a dedicated whiteboard section. This whiteboard allows users to explore, add, and personalise their favourite productivity widgets, helping them learn and master new productivity skills tailored to their habits. This limited customisation approach effectively reduces the high learning curve associated with fully customisable systems.
在空间层级下，主要框架（如空间名称简介、包含的项目和Activity）布局固定，同时提供一个支持用户自定义的白板板块。用户可以在白板上探索、添加和定制自己喜欢的效率管理小组件，帮助他们学习并掌握更多效率管理技能，并符合个人使用习惯。通过这种有限度的自定义体验，用户能够降低面对高度自定义时的学习成本。
AI-Powered Task Builder
Users can utilise AI to instantly generate meeting summaries and create task lists directly from them. AI extracts key points to generate task cards, which can be easily edited and viewed in context. These tasks can then be effortlessly imported into the relevant project boards. This AI-driven process simplifies task creation, making it easier and more appealing for users to adopt the new product.
用户可以通过AI一键生成会议纪要，并在纪要中直接创建任务列表。AI会自动提取会议中的关键信息，生成对应的任务卡片。用户可以悬浮查看任务卡片的来源，并进行即时编辑，随后一键导入到相关项目的任务板中。通过AI简化任务创建流程，降低用户操作难度，大大提升了他们尝试新产品的意愿。
1.
THINK
「Learn about the context.」
思考「了解背景和上下文」
Client Needs InterviewTHINK
「Learn about the context.」
思考「了解背景和上下文」
客户需求访谈
Early on, I conducted interviews with Atlassian's internal design team to understand what the project needs from various angles, like user needs, business aims, and technical limits. I've noted down the most frequently mentioned points from our discussions, listed by importance.
在项目初期，我与 Atlassian 的内部设计团队进行了访谈，从用户需求、业务目标和技术限制等多个角度深入了解项目需求。我记录了讨论中最常提到的要点，并按重要性进行了排序。
Competitor Analysis竞品分析
Our competitor analysis approach involves comparing pairs of products like Atlassian's Confluence with Notion, Trello with Canva, and Jira with Microsoft's GitHub. This method allows us to understand the nuances in market positioning, features, and user demographics of each tool.我们的竞争对手分析方法是将产品进行对比，如Atlassian的Confluence与Notion，Trello与Canva，以及Jira与微软的GitHub。通过这种方法，我们可以深入了解每款工具在市场定位、功能和用户群体上的细微差异。
We identified six radar chart indicators by defining our analysis goals and evaluating competitors' UX and UI. This includes how competitors tackle usability issues, learning from their failures, assessing their strengths and weaknesses, and noting trends and innovation. These indicators are based on a SWOT analysis, direct experiences, and user reviews, aimed at understanding the market and guiding our design strategy.我们通过定义分析目标并评估竞争对手的用户体验（UX）和用户界面（UI），确定了六个雷达图指标。这包括竞争对手如何应对可用性问题、从他们的失败中学习、评估他们的优劣势以及注意市场趋势和创新。这些指标基于SWOT分析、直接体验和用户反馈，旨在理解市场并指导我们的设计策略。
By synthesising, we've outlined usability expectations for our new product, ensuring its competitive market stance. These principles guide my design and development strategies more effectively.通过综合分析，我们概括了新产品的可用性期望，确保其在市场中的竞争力。这些原则更有效地指导了我们的设计和开发策略。
Survey Research调查研究
To understand the latent needs of students, I combined quantitative research with a 「Background Questionnaire」 of 40 people and qualitative methods, including 「User Interviews」 with six users. Among these, one had experience with Atlassian products, while the others had used different productivity software. I summarised the data using 「Affinity Mapping」, identifying four key facts and five insights.
为了深入了解学生的潜在需求，我结合了定量研究和定性方法。定量研究包括对40人的「背景问卷调查」，而定性方法包括与6名用户的「用户访谈」。其中一位用户有使用Atlassian产品的经验，其他人则使用过不同的效率软件。我通过「亲和图法」对数据进行了总结，确定了四个关键事实和五个洞察。
Questionnaire Research / 背景问卷调查
「背景问卷调查」- 四个关键事实
大多数用户选择使用Atlassian产品主要是由于团队协作需求。它的专业性和复杂性特点迎合了具有一
定技术能力的用户。然而，在个人使用场景中，比如记笔记，其使用仍然相对有限。
与团队项目不同，几乎所有参与者都更倾向于随时随地使用高效快捷的方法记录个人日常任务。然而，
语音辅助记录的方法尚未被广泛接受。
对于大多数用户来说，选择此类软件的主要动机是通过有效的团队协作实现项目目标。这一功能构成了
这些工具的核心，其次是个人任务跟踪和高效的时间管理。
熟悉效率管理工具的用户往往具有较高的技术接受度，并且对组织任务充满热情。相反，那些未使用过
此类工具的用户则保持开放的态度和兴趣，主要是因为他们相信自己具备自律能力，
并渴望探索新工具。
Interview / 用户访谈
「用户访谈」- 五个洞察点
洞察一：了解效率管理的意义
洞察二：有组织的用户界面
洞察三：社群化且引人入胜的体验
洞察四：官方教程的支持
洞察五：个性化任务管理设计
Then, using the 「5 Whys Root Cause Analysis」, I explored why students hesitate to use productivity apps, revealing six latent user needs.随后，我运用了「5个为什么根因分析法」探讨了学生为何犹豫使用效率应用程序，揭示了六个潜在用户需求。
Persona & User Story
用户画像 & 用户故事
To better define the design focus of the project and to ensure the design’s validity throughout the process, I created the following personas and user stories based on the findings from my research. Cindy is prioritised over Terry, as I believe she represents the primary target audience for the new product.为了更明确项目的设计重点，并随时检验设计的合理性，我在调查研究的基础上创建了以下用户画像和用户故事。其中，Cindy的优先级高于Terry，我认为她代表了新产品的主要目标用户群体。
用户画像 & 用户故事
To better define the design focus of the project and to ensure the design’s validity throughout the process, I created the following personas and user stories based on the findings from my research. Cindy is prioritised over Terry, as I believe she represents the primary target audience for the new product.为了更明确项目的设计重点，并随时检验设计的合理性，我在调查研究的基础上创建了以下用户画像和用户故事。其中，Cindy的优先级高于Terry，我认为她代表了新产品的主要目标用户群体。
Actionable Insights
可执行的洞见
可执行的洞见
To better refine the design of the new product, I leveraged my two personas and used the ERRC Grid framework to pinpoint the real pain points to address and remove the unnecessary features from the existing Atlassian products.为了进一步明确新产品的设计细节，我以我的两个Persona为基础，使用ERRC Grid模型框架来确定新产品在现有Atlassian产品的基础上需要解决的“真实痛点”以及摒弃的“伪痛点”。
2.
MAKE
「Build prototypes as tangible representations.
制作 「构建原型，作为具体的展示」
Information ArchitectureMAKE
「Build prototypes as tangible representations.
制作 「构建原型，作为具体的展示」
信息架构
After identifying the 「Actionable Insights」, I focused on optimising user access and navigation for better content and feature accessibility. Based on user research, I adopted a 「Flat Hierarchy」 to simplify navigation, allowing students to quickly find what they need. This approach lowers the learning curve, brings core features closer, and boosts overall efficiency, leading to a smoother and more intuitive user experience.
在得出「可实施的洞见」后，我考虑如何优化用户访问和使用产品的路径，以确保内容和功能的高可访问性。基于用户调研数据，我选择了「扁平化层级结构」，通过减少层级、点击和跳转，帮助学生用户更快速地找到所需内容。这种易于理解的导航降低了学习成本，使核心功能更接近用户，提升了整体效率，提供更流畅和直观的用户体验。
User Flow
用户流
Before sketching and wireframing, I put myself in the shoes of the Persona, using specific features of the existing product to identify the most critical areas for improvement. Ultimately, I selected the following three tasks to highlight the key features the app will provide:
在开始绘制草图和构建线框之前，我将自己代入 Persona 的视角，使用现有产品的特定功能，深入体验并发现他们最迫切需要的功能升级点。最终，我选择了以下三项任务来突出应用程序的核心特性：
- Quick Capture & Reallocate Tasks 快速捕捉任务并重新分配
- Customisable Widgets within a Fixed Workspace Layout
固定工作空间布局中的自定义小组件 - AI-Powered Task Builder AI 驱动的任务一键生成
Low-fidelity Prototype
低保真线框图
I started to create the initial wireframes illustrating what the app might look like. Creating wireframes first helped me visualise my ideas as well as gave me the basic structure for how users would use the app for reviewing projects and managing different types of content. When creating these wireframes, I made sure to keep the user needs from my persona and research in mind.我开始绘制初步线框图，展示应用程序的外观。首先创建线框图帮助我将想法进行可视化，并为用户如何使用应用程序审查项目和管理不同类型的内容提供了基本结构。在创建这些线框图时，我始终考虑到 Persona 和研究中的用户需求。
3.
BREAK
「Testing potential solutions」
打破 「测试潜在解决方案」
Usability Testing Procedure
可用性测试流程
In my usability testing process, I start by creating Lo-Fi Version 0, followed by a 「Cognitive Walkthrough」 and 「Heuristic Evaluation」 to assess the initial design. These two steps allow me to identify early usability issues from an expert’s perspective and refine the user flow, leading to Hi-Fi Version 1.
Next, I run the 「Think-aloud Protocol」, where users verbalise their thoughts and feelings as they interact with the product. By listening to their feedback, I gain deeper insights into their real needs and any pain points they encounter. I then polished Hi-Fi Version 2, ensuring that the final product better meets user expectations and enhances the overall user experience.
在我的可用性测试流程中，我首先创建 低保真模型-V0，并通过「认知走查」和「启发式评估」来对设计进行初步评估。这两个步骤帮助我从专家的角度识别早期的可用性问题，并优化用户的操作体验，最终迭代出 高保真模型-V1。
之后，我会使用「大声思考法」进行用户测试。在这个过程中，用户会在使用产品时大声表达他们的想法和感受。通过倾听用户的反馈，我能够深入了解他们的真实需求和困惑，并据此改进设计，推出更完善的 高保真模型-V2，以确保最终的设计能够更好地满足用户需求，并提供更优的用户体验。
Design Rationale
设计说明
Here is the design rationale for this project, where I detail the reasons, thought processes, and logic behind each decision. This includes why specific design choices were made, the project’s objectives, and how the design aims to achieve them.
以下是项目的设计依据，我详细阐述了每项决策背后的原因、思考过程和逻辑，包括为何选择特定的设计方案、项目的目标以及如何通过设计实现这些目标。