The Agent Skills Directory
npx skills add https://smithery.ai/skills/coowoolf/culture-as-product-operating-system"每个公司都在打造两个产品:一个是为客户打造的产品,另一个是为团队打造的产品。后者就是文化。" — Dharmesh Shah
将公司文化视为你为员工(你的客户)打造的 "产品"。正如你不会冻结产品代码一样,你也不应冻结文化。
┌─────────────────────────────────────────────────────┐
│ 文化即产品操作系统 │
├─────────────────────────────────────────────────────┤
│ 输入: 员工反馈 (NPS 调查) │
│ ↓ │
│ 分类: 识别文化中的 "缺陷" │
│ ↓ │
│ 决策: 修复或标记为 "按设计运行" │
│ ↓ │
│ 输出: 更新后的文化实践 │
├─────────────────────────────────────────────────────┤
│ 联邦法律: 不可协商的核心价值观 │
│ 州法律: 团队特定的调整 │
└─────────────────────────────────────────────────────┘
定量(0-10分)和定性(为什么?)地衡量满意度。
将文化方面的投诉视为产品中的 "缺陷"。公开承认它们。
承诺修复有效的缺陷,或者明确声明 "它按设计运行"(例如,"是的,透明度有时会让人不适,但这是一个特性,而非缺陷")。
STEP 1: 定期测量
└── 季度 eNPS 调查
└── 匿名反馈渠道
STEP 2: 全员会议上分类处理
└── "以下是你们报告的缺陷..."
└── 公开承认以建立信任
STEP 3: 对每个缺陷进行分类
└── 将修复: 确定优先级和时间表
└── 不予修复: 解释为何这是有意为之
└── 功能请求: 添加到待办事项
STEP 4: 发布更新
└── 像发布产品一样宣布文化变更
└── 在下一次调查中衡量影响
❌ 认为目标是 保持 文化(实际是 发展 文化)
❌ 因为 "文化无法改变" 而忽视反馈
❌ 将所有事情都定为 "联邦法律"(不给团队自主权)
HubSpot 的透明度政策(让每个人成为 "内部人士")是一项联邦法律,但随着公司规模扩大,座位安排从抽签制演变为基于团队制。
来源: Dharmesh Shah, Lenny's Podcast
每周安装次数
–
来源
首次出现
–
"Every company builds two products: one is the product they build for their customers, and the other is a product they build for their team. That's what culture is." — Dharmesh Shah
Treat company culture as the "product" you build for employees (your customers). Just as you wouldn't freeze code on a product, you shouldn't freeze culture.
┌─────────────────────────────────────────────────────┐
│ CULTURE-AS-PRODUCT OS │
├─────────────────────────────────────────────────────┤
│ INPUT: Employee Feedback (NPS surveys) │
│ ↓ │
│ TRIAGE: Identify "bugs" in the culture │
│ ↓ │
│ DECISION: Fix or mark "Works as Designed" │
│ ↓ │
│ OUTPUT: Updated cultural practices │
├─────────────────────────────────────────────────────┤
│ FEDERAL LAWS: Non-negotiable core values │
│ STATE LAWS: Team-specific adaptations │
└─────────────────────────────────────────────────────┘
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
Measure satisfaction quantitatively (0-10) and qualitatively (Why?).
Treat cultural complaints as "bugs" in the product. Acknowledge them publicly.
Commit to fixing valid bugs, OR explicitly state "It works as designed" (e.g., "Yes, transparency is uncomfortable, but it's a feature, not a bug").
STEP 1: Measure Regularly
└── Quarterly eNPS surveys
└── Anonymous feedback channels
STEP 2: Triage at All-Hands
└── "Here are the bugs you reported..."
└── Public acknowledgment builds trust
STEP 3: Categorize Each Bug
└── Will Fix: Prioritize and timeline
└── Won't Fix: Explain why it's intentional
└── Feature Request: Add to backlog
STEP 4: Ship Updates
└── Announce culture changes like product releases
└── Measure impact in next survey
❌ Thinking the job is to preserve culture (it's to evolve it)
❌ Ignoring feedback because "culture can't be changed"
❌ Making everything a "Federal Law" (no team autonomy)
HubSpot's transparency policy (making everyone an "insider") was a Federal Law, but seating arrangements evolved from lottery-based to team-based as the company scaled.
Source: Dharmesh Shah, Lenny's Podcast
Weekly Installs
–
Source
First Seen
–
站立会议模板:敏捷开发每日站会指南与工具(含远程团队异步模板)
10,500 周安装