layers-orient

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/layers-orient

Assumes
/layers-intro
has been loaded for framework context.

Orient is a rapid diagnostic. It maps the current state of decisions across all seven layers, identifies the bottleneck — the lowest layer with unresolved or risky decisions — and recommends where to focus next.

It is not a deep dive into any layer. That's what the individual layer skills are for. Orient answers the prior question: which layer deserves attention most urgently?

What it assesses:

Whether key decisions have been made at each layer, and how solidly
Whether decisions treated as solid are actually assumptions
Which layer is the most foundational with unresolved work, creating risk for everything above

Quality signals — when orient is done well:

The bottleneck layer is specifically named, not vaguely gestured at
Assumed layers are distinguished from Strong ones — they require different responses
The recommendation connects to a specific skill with a clear reason

假设已加载
/layers-intro
以获取框架背景信息。

Orient是一项快速诊断工具。它会梳理所有七层的当前决策状态，识别出瓶颈——即存在未解决或高风险决策的最底层，并建议下一步的重点关注方向。

它并非针对任何单个层进行深入分析，那是各层专属技能的用途。Orient要回答的前置问题是：哪一层最值得优先关注？

评估内容：

每层是否已做出关键决策，以及决策的稳固程度
被视为已确定的决策是否实际上只是假设
哪一层是最基础但存在未完成工作的层，这会给上层所有工作带来风险

优质信号——当Orient诊断完成得较好时：

明确指出瓶颈层的具体名称，而非模糊表述
区分“Assumed（假设）”层与“Strong（稳固）”层——它们需要不同的应对方式
推荐内容关联到特定技能，并给出清晰理由

Guided session

引导式会话

Describe your design situation and what prompted you to pick it up, or say "let's orient" to start.

Ask: "Where should I capture the work from this session?" (see

/layers-intro

for options)

Then ask:

What product or feature are you working on?
What design challenge are you facing right now?
How far along is this work — early exploration, active design, or fixing something in an existing product?

Listen for clues about which layers have already been worked through and which are thin or missing.

描述你的设计场景以及促使你使用该工具的原因，或者直接说“let's orient”开始诊断。

询问：“我应该在哪里记录本次会话的工作内容？”（查看

/layers-intro

了解可选方案）

然后询问以下问题：

你正在开发的产品或功能是什么？
你当前面临的设计挑战是什么？
这项工作的进展如何——处于早期探索阶段、活跃设计阶段，还是在修复现有产品中的问题？

留意哪些层已经完成梳理，哪些层内容薄弱或缺失的线索。

Layer audit

层审计

Work through each layer with one or two targeted questions. Rate each as: Strong / Partial / Assumed / Weak / Not started / N/A

Observed behaviour "What user research do you have? Have you spoken to users, observed them, or have analytics? Or is this mostly based on what the team believes users do?"

The domain "How well do you understand the space this product operates in — the real-world concepts, terminology, and how users think before your product enters the picture?"

User needs "Can you articulate what users are trying to achieve — not in features, but the underlying job and why it matters? Do you have job stories or equivalent?"

Product & service strategy "Do you know which specific user need this work targets and what business outcome it's meant to move? Is the connection between opportunity and business goal explicit, or informal?"

Conceptual model "Does the product have a clear model of the objects it works with — the things that exist, how they connect, and what vocabulary you use? Is this shared across the team, or does each person have their own version?"

Interaction structure and flow "Do you have a clear picture of the key user journeys — places, steps, decision points? A breadboard, rough flow, working code, or a description you can narrate?"

Surface "Is there an existing design system, visual language, or component library this needs to fit into?"

针对每一层提出一两个针对性问题，将每层评级为： Strong / Partial / Assumed / Weak / Not started / N/A

Observed behaviour（用户行为观察） “你有哪些用户研究资料？是否与用户交流过、观察过他们的行为，或者有相关分析数据？还是主要基于团队对用户行为的推测？”

The domain（领域认知） “你对该产品所处领域的了解程度如何——包括现实世界中的相关概念、术语，以及用户在接触你的产品前的思维方式？”

User needs（用户需求） “你能否清晰阐述用户试图达成的目标——不是从功能层面，而是其背后的核心任务及重要性？你是否有任务故事或类似资料？”

Product & service strategy（产品与服务策略） “你是否清楚这项工作针对的具体用户需求，以及它旨在达成的业务成果？机会与业务目标之间的关联是明确的，还是非正式的？”

Conceptual model（概念模型） “产品是否有清晰的对象模型——即产品涉及的实体、实体间的关联，以及所使用的术语？这一模型是否在团队内共享，还是每个人都有自己的版本？”

Interaction structure and flow（交互结构与流程） “你是否有清晰的关键用户旅程图——包括场景、步骤、决策点？比如线框图、粗略流程图、可运行代码，或者可以口述的描述？”

Surface（界面表层） “是否有需要适配的现有设计系统、视觉语言或组件库？”

Decision landscape

决策全景

Produce the audit as a table:

Layer                      | State       | Notes
---------------------------|-------------|----------------------------------------
Observed behaviour         |             |
The domain                 |             |
User needs                 |             |
Product & service strategy |             |
Conceptual model           |             |
Interaction structure      |             |
Surface                    |             |

将审计结果整理为表格：

Layer                      | State       | Notes
---------------------------|-------------|----------------------------------------
Observed behaviour         |             |
The domain                 |             |
User needs                 |             |
Product & service strategy |             |
Conceptual model           |             |
Interaction structure      |             |
Surface                    |             |

Bottleneck analysis

瓶颈分析

Identify the bottleneck layer: the lowest layer with Weak, Assumed, or Not started state. State it clearly: what decisions are missing, and what risk does that create for the layers above?

Also flag assumed layers — layers treated as decided but not verified. Assumptions that look solid are often where the most dangerous decisions hide.

If the designer has a deadline or constraint that changes the calculus, acknowledge it. Sometimes the right move isn't the most foundational one — name that tradeoff explicitly rather than ignoring it.

识别瓶颈层：即处于Weak、Assumed或Not started状态的最底层。明确说明：缺失哪些决策，以及这会给上层工作带来什么风险？

同时标记Assumed层——即被视为已确定但未经验证的层。看似稳固的假设往往隐藏着最危险的决策。

如果设计师有截止日期或其他约束条件改变了决策逻辑，需予以确认。有时正确的选择并非最基础的那一项——要明确指出这种权衡，而非忽略它。

Recommendation

建议

Recommend a specific skill to run next and why:

Conceptual model →
```
/layers-conceptual-model
```
Product strategy →
```
/layers-product-strategy
```
User needs →
```
/layers-user-needs
```
Domain →
```
/layers-domain
```
Interaction structure →
```
/layers-interaction-flow
```
Observed behaviour →
```
/layers-observed-behaviour
```

Close with: "Want to run [skill] now, or is there something in this picture to push back on first?"

推荐下一步要使用的特定技能并说明原因：

Conceptual model →
```
/layers-conceptual-model
```
Product strategy →
```
/layers-product-strategy
```
User needs →
```
/layers-user-needs
```
Domain →
```
/layers-domain
```
Interaction structure →
```
/layers-interaction-flow
```
Observed behaviour →
```
/layers-observed-behaviour
```

最后询问：“现在就运行[skill]，还是先针对当前诊断结果提出异议？”