frontier-of-understanding-(ncts) by coowoolf/insighthunt-skills
npx skills add https://github.com/coowoolf/insighthunt-skills --skill 'Frontier of Understanding (NCTs)'"如果你不知道如何改变某个特定指标,那么正确的目标应该是设定一个目标来增进你的理解,而不是去改变那个指标。" — Ravi Mehta
团队不应盲目关注结果,而应识别他们的 "理解前沿"。如果驱动因素未知,目标应是"理解风险"(学习);如果已知,目标可以是"执行风险"(行动)或"战略风险"(结果)。
┌─────────────────────────────────────────────────────────┐
│ UNDERSTANDING RISK │
│ "We don't know the levers" │
│ → Goal = Insight / Learning │
├─────────────────────────────────────────────────────────┤
│ DEPENDENCY RISK │
│ "We know levers but lack tools/resources" │
│ → Goal = Unblock dependencies │
├─────────────────────────────────────────────────────────┤
│ EXECUTION RISK │
│ "We have the tools" │
│ → Goal = High velocity / Quality experiments │
├─────────────────────────────────────────────────────────┤
│ STRATEGIC RISK │
│ "We are executing well" │
│ → Goal = Verify hypothesis moves the metric │
└─────────────────────────────────────────────────────────┘
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
STEP 1: Identify Your Frontier
└── Do we know what moves this metric?
└── Have we proven the levers work?
STEP 2: Match Goal to Frontier
└── Unknown levers → Learning goal
└── Known levers → Execution goal
└── Proven levers → Outcome goal
STEP 3: Don't Overcommit
└── If in Understanding phase, don't promise revenue
└── Promise insights instead
STEP 4: Move Along the Frontier
└── Each quarter, advance your understanding
└── Eventually you earn the right to set outcome goals
❌ 在"理解风险"阶段设定 结果目标(如收入)
❌ 为了达到任意设定的目标而"无的放矢"
❌ 认为所有目标 同样容易实现
在 Tinder,数据显示一小部分用户消费很高。他们没有盲目地试图增加收入,而是设定了一个目标去理解 为什么。他们发现这些人并非富人,而是频繁出差者/销售人员。这一洞察最终催生了"Tinder Platinum"。
来源:Ravi Mehta,Tinder 前首席产品官,Lenny's Podcast
每周安装数
0
代码仓库
GitHub 星标数
2
首次出现
Jan 1, 1970
"If you don't understand how to move a particular metric, then the right goal is to set a goal to increase your understanding not to move that metric." — Ravi Mehta
Instead of blindly focusing on outcomes, teams should identify their "Frontier of Understanding." If the levers are unknown, the goal should be "Understanding Risk" (learning); if known, the goal can be "Execution Risk" (doing) or "Strategic Risk" (outcomes).
┌─────────────────────────────────────────────────────────┐
│ UNDERSTANDING RISK │
│ "We don't know the levers" │
│ → Goal = Insight / Learning │
├─────────────────────────────────────────────────────────┤
│ DEPENDENCY RISK │
│ "We know levers but lack tools/resources" │
│ → Goal = Unblock dependencies │
├─────────────────────────────────────────────────────────┤
│ EXECUTION RISK │
│ "We have the tools" │
│ → Goal = High velocity / Quality experiments │
├─────────────────────────────────────────────────────────┤
│ STRATEGIC RISK │
│ "We are executing well" │
│ → Goal = Verify hypothesis moves the metric │
└─────────────────────────────────────────────────────────┘
STEP 1: Identify Your Frontier
└── Do we know what moves this metric?
└── Have we proven the levers work?
STEP 2: Match Goal to Frontier
└── Unknown levers → Learning goal
└── Known levers → Execution goal
└── Proven levers → Outcome goal
STEP 3: Don't Overcommit
└── If in Understanding phase, don't promise revenue
└── Promise insights instead
STEP 4: Move Along the Frontier
└── Each quarter, advance your understanding
└── Eventually you earn the right to set outcome goals
❌ Setting an outcome goal (Revenue) when in "Understanding Risk" phase
❌ "Throwing spaghetti at the wall" to hit arbitrary targets
❌ Treating all goals as equally achievable
At Tinder, data showed high spending from a small group. Instead of blindly trying to grow revenue, they set a goal to understand WHY. They found these weren't rich people, but frequent travelers/salespeople. This insight led to "Tinder Platinum."
Source: Ravi Mehta, Former CPO of Tinder, Lenny's Podcast
Weekly Installs
0
Repository
GitHub Stars
2
First Seen
Jan 1, 1970
Google Workspace CLI 团队负责人技能:自动化站会、任务协调与团队沟通工具
6,100 周安装
OpenAPI 转 TypeScript 工具 - 自动生成 API 接口与类型守卫
563 周安装
数据库模式设计器 - 内置最佳实践,自动生成生产级SQL/NoSQL数据库架构
564 周安装
Rust Unsafe代码检查器 - 安全使用Unsafe Rust的完整指南与最佳实践
564 周安装
.NET并发编程模式指南:async/await、Channels、Akka.NET选择决策树
565 周安装
韩语语法检查器 - 基于国立国语院标准的拼写、空格、语法、标点错误检测与纠正
565 周安装
技能安全扫描器 - 检测Claude技能安全漏洞,防范提示注入与恶意代码
565 周安装