Assess the need - Determine if they need consistency, speed, or both, and whether they're at the right stage for a design system
Define the scope - Clarify whether they need a component library, design tokens, documentation, or all three
Design for adoption - Help them make the system easy enough that non-designers can use it correctly
Plan for evolution - Guide them on how to maintain and evolve the system over time
当用户寻求设计系统相关帮助时：
评估需求 - 确定他们是需要一致性、效率，还是两者兼具，以及他们是否处于适合搭建设计系统的阶段
定义范围 - 明确他们是否需要组件库、设计令牌、文档，或是三者皆需
为易用性设计 - 帮助他们打造足够简便的系统，让非设计师也能正确使用
规划演进 - 指导他们如何长期维护和演进系统
Core Principles
核心原则
Separate concept from production
区分概念与落地
Bob Baxley: "Once we locked down on the block frames, we could send it to an agency and they could do the full high-res comps in a day, because they knew exactly what they were doing." Use low-fidelity 'block brain diagrams' to lock down conceptual logic, then apply the design system for rapid high-fidelity output.
Bob Baxley：“一旦我们确定了模块框架，就可以将其交给代理机构，他们能在一天内完成完整的高保真设计稿，因为他们清楚地知道要做什么。” 使用低保真的“模块脑图”锁定概念逻辑，然后应用设计系统快速产出高保真成果。
Design systems drive enterprise expansion
设计系统推动企业级扩张
Claire Butler: "Design systems are one of the main reasons you upgrade from pro to org or enterprise. That became just the key thing we leaned in on." Design systems practitioners are key internal champions for organizational scaling.
Jessica Hische: "My goal always when designing a logo is to design a logo that's so easy to use that you don't have to be an extremely skilled designer to design well with it." Design assets that 'teach' the user how to apply them through their inherent structure, prioritizing ease of use over complexity.
Brian Chesky: "I think flat design is over or ending. We're going to move back into a world with color, texture, dimensionality, more haptic feedback." Interface design is shifting from flat aesthetics to more dimensional, tactile, and AI-enhanced experiences.
Brian Chesky：“我认为扁平化设计已经过时或即将终结。我们将回归一个充满色彩、纹理、立体感和更多触觉反馈的世界。” 界面设计正从扁平化美学转向更具立体感、触感和AI增强的体验。
Questions to Help Users
用于引导用户的问题
"What's the biggest inconsistency problem you're facing today?"
"Who will be using this design system - designers only, or engineers too?"
"How will you measure adoption and success of the design system?"
"Do you have the resources to maintain and evolve the system over time?"
"What's the smallest viable version you could ship first?"
“你目前面临的最大一致性问题是什么？”
“谁会使用这个设计系统——仅设计师，还是工程师也会使用？”
“你将如何衡量设计系统的采用率和成功程度？”
“你是否有资源长期维护和演进这个系统？”
“你可以先推出的最小可行版本是什么？”
Common Mistakes to Flag
需要指出的常见误区
Building too early - Creating a design system before you have enough patterns to systematize
Over-engineering - Building complex systems that require expert designers to use correctly
No ownership - Creating a design system without dedicated resources to maintain it
Ignoring adoption - Building a beautiful system that no one actually uses
Static systems - Treating the design system as 'done' rather than continuously evolving