Back to Details

alignment-values-north-star

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Alignment: Values & North Star

对齐管理：价值观与North Star

Table of Contents

目录

Purpose

目的

Create clear, actionable alignment frameworks that give teams a shared North Star (direction), values (guardrails), and decision tenets (behavioral standards). This enables autonomous decision-making while maintaining coherence across the organization.
创建清晰、可落地的对齐框架，为团队提供统一的North Star（方向）、价值观（约束准则）和决策原则（行为标准）。这能在保持组织一致性的同时，支持团队自主决策。

When to Use This Skill

何时使用本方法

  • Starting new teams or organizations (defining identity)
  • Scaling teams (maintaining culture as you grow)
  • Resolving misalignment or conflicts (clarifying shared direction)
  • Defining product/engineering/design principles
  • Creating strategic clarity after pivots or changes
  • Establishing decision-making frameworks
  • Setting cultural norms and behavioral expectations
  • Post-merger integration (aligning different cultures)
  • Crisis response (re-centering on what matters)
  • Onboarding leaders who need to understand team identity
Trigger phrases: "North Star", "team values", "mission", "vision", "principles", "guardrails", "what we stand for", "decision framework", "cultural alignment", "operating principles"
  • 组建新团队或新组织（定义身份认同）
  • 团队扩张（在成长过程中维持文化）
  • 解决不一致或冲突问题（明确统一方向）
  • 定义产品/工程/设计原则
  • 在战略转型或变更后明确方向
  • 建立决策框架
  • 设定文化规范和行为预期
  • 并购后的整合（对齐不同文化）
  • 危机应对（重新聚焦核心重点）
  • 新领导者入职（帮助其理解团队身份）
触发关键词："North Star"、"团队价值观"、"使命"、"愿景"、"原则"、"约束准则"、"我们的立场"、"决策框架"、"文化对齐"、"运营原则"

What is Values & North Star Alignment?

什么是价值观与North Star对齐？

A framework with three layers:
  1. North Star: The aspirational direction - where are we going and why?
  2. Values/Guardrails: Core principles that constrain how we operate
  3. Decision Tenets/Behaviors: Concrete, observable behaviors that demonstrate values
Quick Example:
markdown
undefined
包含三层结构的框架：
  1. North Star：具有抱负的方向——我们要去向何方，为什么？
  2. 价值观/约束准则：指导我们运营方式的核心原则
  3. 决策原则/行为：体现价值观的具体、可观察行为
快速示例：
markdown
undefined

Engineering Team Alignment

工程团队对齐框架

North Star

North Star

Build systems that developers love to use and operators trust to run.
打造开发者乐于使用、运维人员信赖的系统。

Values

价值观

  • Simplicity: Choose boring technology that works over exciting technology that might
  • Reliability: Every service has SLOs and we honor them
  • Empathy: Design for the developer experience, not just system performance
  • 简洁性：选择实用的成熟技术，而非花哨的新兴技术
  • 可靠性：每个服务都有SLO，且我们严格遵守
  • 同理心：为开发者体验设计，而非仅关注系统性能

Decision Tenets

决策原则

When choosing between options: ✓ Pick the solution with fewer moving parts ✓ Choose managed services over self-hosted when quality is comparable ✓ Optimize for debuggability over micro-optimizations ✓ Document decisions (ADRs) for future context
在选项间做选择时： ✓ 选择组件更少的解决方案 ✓ 当质量相当时，优先选用托管服务而非自托管服务 ✓ 优先优化可调试性而非微优化 ✓ 记录决策（ADRs）以便后续参考

Behaviors (What This Looks Like)

行为表现（实际场景）

  • Code reviews comment on operational complexity, not just correctness
  • We say no to features that compromise reliability
  • Postmortems focus on learning, not blame
  • Documentation is part of "done"
undefined
  • 代码评审不仅关注正确性，还会评论运维复杂度
  • 我们会拒绝影响可靠性的功能
  • 事后复盘聚焦于学习，而非追责
  • 文档编写属于“完成”标准的一部分
undefined

Workflow

工作流程

Copy this checklist and track your progress:
Alignment Framework Progress:
- [ ] Step 1: Understand context
- [ ] Step 2: Choose framework
- [ ] Step 3: Develop alignment artifact
- [ ] Step 4: Validate quality
- [ ] Step 5: Deliver and socialize
Step 1: Understand context
Gather background: team/organization (size, stage, structure), current situation (new team, scaling, misalignment, crisis), trigger (why alignment needed NOW), stakeholders (who needs to align), hard decisions (where misalignment shows up), and existing artifacts (mission, values, culture statements). This ensures the framework addresses real needs.
Step 2: Choose framework
For new teams/startups (< 30 people, defining identity from scratch) → Use 
resources/template.md
. For scaling organizations (existing values need refinement, multiple teams, need decision framework) → Study 
resources/methodology.md
. To see examples → Review 
resources/examples/
(engineering-team.md, product-vision.md, company-values.md).
Step 3: Develop alignment artifact
Create 
alignment-values-north-star.md
with: compelling North Star (1-2 sentences, aspirational but specific), 3-5 core values (specific to this team, not generic), decision tenets ("When X vs Y, we..."), observable behaviors (concrete examples), anti-patterns (optional - what we DON'T do), and context (optional - why these values). See Common Patterns for team-type specific guidance.
Step 4: Validate quality
Self-check using 
resources/evaluators/rubric_alignment_values_north_star.json
. Verify: North Star is inspiring yet concrete, values are specific and distinctive, decision tenets guide real decisions, behaviors are observable/measurable, usable for decisions TODAY, trade-offs acknowledged, no contradictions, distinguishes this team from others. Minimum standard: Score ≥ 3.5 (aim for 4.5+ if organization-wide).
Step 5: Deliver and socialize
Present completed framework with rationale (why these values), examples of application in decisions, rollout/socialization approach (hiring, decision-making, onboarding, team meetings), and review cadence (typically annually). Ensure team can recall and apply key points.
复制以下清单并跟踪进度：
对齐框架进度：
- [ ] 步骤1：了解背景
- [ ] 步骤2：选择框架
- [ ] 步骤3：开发对齐文档
- [ ] 步骤4：验证质量
- [ ] 步骤5：交付与推广
步骤1：了解背景
收集背景信息：团队/组织（规模、阶段、结构）、当前状况（新团队、扩张、不一致、危机）、触发因素（为何现在需要对齐）、利益相关者（需要对齐的对象）、存在分歧的关键决策、现有文档（使命、价值观、文化声明）。这确保框架能解决实际需求。
步骤2：选择框架
针对新团队/初创公司（<30人，从零定义身份）→ 使用
resources/template.md
。针对扩张中的组织（现有价值观需要细化、多团队协作、需要决策框架）→ 参考
resources/methodology.md
。查看示例→ 浏览
resources/examples/
（engineering-team.md, product-vision.md, company-values.md）。
步骤3：开发对齐文档
创建
alignment-values-north-star.md
，内容包括：有吸引力的North Star（1-2句话，有抱负且具体）、3-5个核心价值观（针对当前团队，而非通用表述）、决策原则（“当面临X与Y的选择时，我们会……”）、可观察行为（具体示例）、反模式（可选——我们不做的事）、背景说明（可选——为何选择这些价值观）。查看常见模式获取针对不同团队类型的指导。
步骤4：验证质量
使用
resources/evaluators/rubric_alignment_values_north_star.json
进行自我检查。验证：North Star既鼓舞人心又具体，价值观独特且明确，决策原则能指导实际决策，行为可观察/可衡量，可立即用于决策，承认取舍，无矛盾，能区分本团队与其他团队。最低标准：得分≥3.5（如果是全组织范围，目标为4.5+）。
步骤5：交付与推广
展示完成的框架并说明理由（为何选择这些价值观）、提供决策应用示例、制定推广计划（招聘、决策流程、新员工入职、团队会议）和回顾周期（通常每年一次）。确保团队能记住并应用关键要点。

Common Patterns

常见模式

For technical teams:
  • Focus on technical trade-offs (simplicity vs performance, speed vs quality)
  • Make architectural principles explicit
  • Include operational considerations
  • Address technical debt philosophy
For product teams:
  • Center on user/customer value
  • Address feature prioritization philosophy
  • Include quality bar and launch criteria
  • Make product-market fit assumptions explicit
For company-wide values:
  • Keep values aspirational but grounded
  • Include specific behaviors (not just values)
  • Address how values interact (what wins when they conflict?)
  • Make hiring/firing implications clear
For crisis/change:
  • Acknowledge what's changing
  • Re-center on core that remains
  • Be explicit about new priorities
  • Include timeline for transition
针对技术团队：
  • 聚焦技术取舍（简洁性vs性能，速度vs质量）
  • 明确架构原则
  • 包含运维考量
  • 说明技术债务理念
针对产品团队：
  • 围绕用户/客户价值展开
  • 说明功能优先级理念
  • 包含质量标准和发布准则
  • 明确产品市场契合度假设
针对全公司价值观：
  • 价值观既有抱负又接地气
  • 包含具体行为（而非仅价值观表述）
  • 说明价值观冲突时的优先级
  • 明确对招聘/解雇的影响
针对危机/变革场景：
  • 承认正在发生的变化
  • 重新聚焦不变的核心
  • 明确新的优先级
  • 包含过渡时间表

Guardrails

约束准则

Do:
  • Make values specific and distinctive (not generic)
  • Include concrete behaviors and examples
  • Acknowledge trade-offs (what you're NOT optimizing for)
  • Test values against real decisions
  • Keep it concise (1-2 pages max)
  • Make it memorable (people should be able to recall key points)
  • Involve the team in creating it (not top-down)
Don't:
  • Use corporate jargon or buzzwords
  • Make it so generic it could apply to any company
  • Create laundry list of every good quality
  • Ignore tensions between values
  • Make it purely aspirational (need concrete behaviors)
  • Set it and forget it (values should evolve)
  • Weaponize values to shut down dissent
建议：
  • 让价值观具体且独特（而非通用表述）
  • 包含具体行为和示例
  • 承认取舍（明确不优先优化的方向）
  • 用实际决策验证价值观
  • 保持简洁（最多1-2页）
  • 便于记忆（人们应能记住关键要点）
  • 让团队参与共创（而非自上而下制定）
禁忌：
  • 使用企业行话或流行语
  • 表述过于通用，适用于任何公司
  • 罗列所有优秀品质
  • 忽略价值观之间的矛盾
  • 仅停留在抱负层面（需要具体行为）
  • 制定后就置之不理（价值观应随时间演变）
  • 将价值观作为压制异议的工具

Quick Reference

快速参考

  • Standard template: 
    resources/template.md
  • Scaling/complex cases: 
    resources/methodology.md
  • Examples: 
    resources/examples/engineering-team.md
    , 
    resources/examples/product-vision.md
    , 
    resources/examples/company-values.md
  • Quality rubric: 
    resources/evaluators/rubric_alignment_values_north_star.json
Output naming: 
alignment-values-north-star.md
or 
{team-name}-alignment.md
  • 标准模板：
    resources/template.md
  • 扩张/复杂场景：
    resources/methodology.md
  • 示例：
    resources/examples/engineering-team.md
    , 
    resources/examples/product-vision.md
    , 
    resources/examples/company-values.md
  • 质量评估标准：
    resources/evaluators/rubric_alignment_values_north_star.json
输出命名：
alignment-values-north-star.md
或 
{team-name}-alignment.md