Back to all projects返回全部项目
Application Home · UX Case Study
Autodesk · 2018

Application
Home

One extensible homepage framework for Autodesk products为 Autodesk 产品建立可扩展的统一首页框架

Role · Research, UX & UI角色 · 用户研究、UX 与 UIScope · Revit to cross-product platform范围 · 从 Revit 到跨产品平台System · Autodesk HIG
Application Home shown on a laptop with Revit and BIM 360 project access
Project overview

Start with one product. Design for an ecosystem.从一个产品出发,为整个产品生态设计

Autodesk products had different home experiences even when users were trying to do the same things: resume a model, start work, learn or connect. I began with Revit's fragmented cloud workflow, validated a clearer home experience, then helped abstract it into a shared framework other products could adopt and extend.Autodesk 不同产品的首页体验彼此割裂,但用户要完成的核心任务高度相似:继续工作、开始新项目、学习或连接协作。我先从 Revit 分散的云端工作流入手,验证更清晰的首页体验,再将其抽象为其他产品可复用、可扩展的共享框架。

CompanyAutodesk
TimeMar 20182018 年 3 月
RoleUser research, UX design, UI design, client-facing video production用户研究、UX 设计、UI 设计、客户端演示视频制作
OutputRevit pilot, shared architecture, HIG contribution and cross-product guidanceRevit 试点、共享架构、HIG 规范贡献与跨产品落地指导
01

Fragmented cloud access云端访问链路割裂

Projects, models, versions and sharing lived across disconnected flows.项目、模型、版本与分享分散在不同流程中。

02

Inconsistent products产品体验不一致

Revit and BIM 360 differed in interaction, visuals and information architecture.Revit 与 BIM 360 的交互、视觉与信息架构缺少一致性。

03

No shared mental model缺少统一心智模型

Home screens reflected product structure rather than users' recurring jobs.首页更多反映产品结构,而不是用户反复要完成的任务。

Design question设计命题

How might we make Revit's first screen immediately useful, while creating a foundation that remains coherent across products without erasing product-specific needs?如何让 Revit 首页立即解决真实任务,同时建立可跨产品保持一致、又不抹平产品差异的基础框架?

01 · Understand

Map the workflow before redesigning the screen先理解工作流,再重做首页

The homepage problem was not cosmetic. Research connected the current cloud-model journey, user pain points and the stakeholder system around Revit.首页问题并不只是视觉老旧。研究把现有云模型工作流、用户痛点与 Revit 周边的利益相关方系统连接起来。

Current fragmented BIM project delivery workflow
Current workflow现有工作流Model access, collaboration and management crossed multiple environments.模型访问、协作与管理跨越多个环境。
Revit Home user problems and opportunity areas
Problem synthesis问题归纳Turn scattered observations into design priorities.把分散观察转化为设计优先级。
Revit Home stakeholder map
Revit stakeholder mapRevit 利益相关方地图The pilot aligned product, cloud, engineering and design-system dependencies.试点需要协调产品、云服务、工程与设计系统之间的依赖。
02 · Revit pilot

Use Revit to validate a task-first home用 Revit 验证任务优先的首页

The pilot rebuilt information architecture, interaction and visual hierarchy together. It also created the first evidence for what should become shared versus product-specific.试点同步重构信息架构、交互与视觉层级,也为判断哪些能力应该共享、哪些需要保留产品差异提供了第一轮证据。

Three principles guided the first release三个原则指导第一版方案

Each decision had to improve immediate task completion and remain legible as the system expanded.每个决策既要改善当下任务完成效率,也要能在系统扩展后保持清晰。

  • APut recent and relevant work first优先呈现近期与相关工作
  • BBridge local and cloud models连接本地模型与云模型
  • CUse one coherent Autodesk language使用一致的 Autodesk 体验语言
High-level Revit Home design strategy
Design strategy设计策略A phased path from file-driven access toward a cloud-connected home.从文件驱动访问逐步走向云端连接首页。
Interaction prototype · task flow and model access交互原型 · 任务路径与模型访问
Visual design · applying the Autodesk language to Revit Home视觉设计 · 将 Autodesk 体验语言应用于 Revit Home
03 · Platform pivot

Abstract the proven patterns, not the whole product抽象已验证的模式,而不是复制整个产品

After the Revit pilot, the work shifted from one homepage to a cross-product system. The shared core had to be stable enough for consistency and open enough for Civil 3D, AutoCAD, BIM 360 and future products.Revit 试点之后,项目从单个首页转向跨产品系统。共享核心既要足够稳定以建立一致性,也要足够开放,让 Civil 3D、AutoCAD、BIM 360 与未来产品保留扩展空间。

A shared core with clear extension points共享核心,加上清晰的扩展边界

Product homes reuse architecture, components and behavior where user intent is common. Teams extend the framework only where their workflows genuinely differ.当用户意图一致时,各产品复用架构、组件与行为;只有在真实工作流存在差异时,团队才扩展框架。

Application Home shared technical and component architecture
Shared architecture共享架构Product homes sit above reusable components and HIG guidance.各产品首页建立在共享组件与 HIG 指南之上。
01

Flexible灵活

Support different product contexts without fragmenting the core.支持不同产品环境,同时不分裂核心体验。

02

Shareable共享

Reuse behavior, components and implementation knowledge.复用行为、组件与实现经验。

03

Adoptable易采用

Let teams migrate incrementally instead of rebuilding at once.让团队渐进迁移,而不是一次性重建。

Cross-product stakeholder map for Autodesk Application Home
Cross-product alignment跨产品协同Revit, Civil 3D, BIM 360, AutoCAD and HIG shaped the shared framework.Revit、Civil 3D、BIM 360、AutoCAD 与 HIG 共同塑造共享框架。
04 · Information architecture

Organize every product home around four recurring jobs围绕四类高频任务组织所有产品首页

A shared task model made the system familiar across products while leaving room for each team to select relevant content and actions.共享任务模型让不同产品保持熟悉感,同时允许各团队选择与自身场景相关的内容和操作。

01

Resume work继续工作

Return to recent and relevant projects.快速回到近期与相关项目。

02

Start new work开始新工作

Choose the right creation path.选择合适的创建入口。

03

Learn学习

Find help, samples and guidance.获取帮助、示例与指导。

04

Engage连接

Reach services, teams and updates.连接服务、团队与更新。

Final Application Home information architecture
Shared IA共享信息架构Four durable jobs create a common structure across products.四类稳定任务构成跨产品的共同结构。
05 · Adoption & HIG

Turn a design into guidance other teams can ship把设计转化为其他团队可以落地的规范

The system became useful only when teams could understand its logic, reuse implementation patterns and contribute improvements back to Autodesk's Human Interface Guidelines.只有当团队能理解框架逻辑、复用实现模式,并把改进回流到 Autodesk Human Interface Guidelines 时,这套系统才真正具备平台价值。

4core user jobs类核心用户任务
5product and HIG groups in the first collaboration个产品与 HIG 协作方
1extensible home framework套可扩展首页框架
Application Home pattern adopted across Revit, Civil 3D, InfraWorks and AutoCAD
Product adoption产品落地The framework moved from the Revit pilot into a broader Autodesk product family.框架从 Revit 试点进入更广泛的 Autodesk 产品家族。
Application Home guidance documented in Autodesk HIG design lab
HIG design labTranslate project learning into reusable company guidance.将项目经验沉淀为可复用的公司级指南。
Civil 3D and Revit · shared structure, product-specific expressionCivil 3D 与 Revit · 共享结构,保留产品表达
06 · Validation

Validate the framework through people, rollout and data用用户、灰度与数据共同验证框架

The team combined qualitative research and product instrumentation to evaluate usability, adoption and the assumptions behind shared patterns.团队结合定性研究与产品埋点,评估可用性、采用情况,以及共享模式背后的关键假设。

01

Global sessions全球面对面测试

Feature testing with users in China, the US and Europe.在中国、美国与欧洲进行功能测试。

02

Internal beta内部 Beta

Observe real use before wider release.在扩大发布前观察真实使用。

03

Remote 1:1线上一对一研究

Probe workflow detail and product-specific differences.深入理解工作流细节与产品差异。

Application Home workshops and user research sessions
Research evidence研究证据Workshops and sessions connected product decisions to user behavior.工作坊与测试把产品决策连接到真实用户行为。
Application Home product instrumentation and data analysis
Data feedback数据反馈Instrumentation defined what to observe after rollout.通过埋点明确上线后需要持续观察的行为。

Data shown in source materials has been manipulated to protect sensitive information.源材料中的数据已做脱敏与调整,以保护敏感信息。

07 · Outcome

From a better Revit entry point to a shared product foundation从更好的 Revit 入口,走向共享产品基础

The project established a reusable architecture and task model that product teams could adopt without losing their own context. It also connected design guidance, implementation and validation into one learning loop.项目建立了可复用的架构与任务模型,让产品团队在不丢失自身场景的前提下采用统一框架,并把设计规范、实现与验证连接成一条学习闭环。

A platform succeeds when the shared core makes adoption easier, while its boundaries make product differences intentional.平台设计的价值,在于共享核心让采用更容易,而清晰边界让产品差异变得有意而可控。

This project changed how I think about design systems: the strongest system is not the one that makes every screen identical, but the one that gives teams a common mental model, reusable building blocks and a clear way to extend them.这个项目改变了我对设计系统的理解:最好的系统不是让所有页面看起来一样,而是为团队提供共同心智模型、可复用模块,以及清晰的扩展方式。