Opportunity Cost Minimization by coowoolf/insighthunt-skills
npx skills add https://github.com/coowoolf/insighthunt-skills --skill 'Opportunity Cost Minimization'"你应该停止做那些仅仅能带来正向投资回报的工作,开始专注于那些能最小化机会成本的工作。" — Shreyas Doshi
在高杠杆率的职位中,存在无数具有正向投资回报的任务。专注于投资回报率会导致选择那些小而快的胜利。相反,应专注于最小化机会成本——选择时间最佳可能的用途,而不仅仅是好的用途。
影响
投资回报率 = ─────────
时间
这个公式鼓励: ❌ 快速、微小的事情(减少分母) ❌ 不产生复合效应的轻松胜利 ❌ 避免困难但高影响力的工作
投资回报率公式鼓励做快速、微小的事情,而不是困难、重大的事情。
使用类似以下的框架:
提问:"这是时间的最佳利用方式吗?" 而不是:"这是时间的良好利用方式吗?"
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
步骤 1:列出所有候选项目
步骤 2:计算朴素的投资回报率
└── "快速胜利:2周内获得2倍回报 = 1.0 投资回报率"
└── "战略性押注:6个月内获得10倍回报 = 0.83 投资回报率"
步骤 3:提出机会成本问题
└── "如果我们做快速胜利,我们就不会做战略性押注"
└── "不做战略性押注的成本是什么?"
步骤 4:评估两年影响
└── 快速胜利:通常会被遗忘
└── 战略性押注:随时间产生复合效应
步骤 5:强制分配
└── 规定路线图的 X% = 战略性押注
└── 不要让快速胜利消耗100%的资源
❌ 因为易于证明合理性而优先考虑"快速胜利" ❌ 通过已发布功能的数量来衡量团队产出 ❌ 忽视那些需要更长时间线的困难战略性押注
在 Stripe,Shreyas 将重点从小的渐进式修复(正向投资回报率)转移到对市场支付系统(Connect)进行一次大规模、令人望而生畏的重构,因为不这样做的机会成本是巨大的。
来源:Shreyas Doshi, Lenny's Podcast
每周安装量
0
代码仓库
GitHub 星标数
2
首次出现时间
1970年1月1日
安全审计
"You should stop doing work that simply provides a positive return on investment and start focusing on work that minimizes opportunity cost." — Shreyas Doshi
In high-leverage roles, there are infinite tasks with positive ROI. Focusing on ROI leads to picking small, quick wins. Instead, focus on minimizing opportunity cost —choosing the best possible use of time, not just a good one.
Impact
ROI = ─────────
Time
The formula incentivizes:
❌ Quick, small things (reduce denominator)
❌ Easy wins that don't compound
❌ Avoiding hard, high-impact work
ROI formula incentivizes doing quick, small things rather than hard, big things.
Use a framework like:
Ask: "Is this the optimal use of time?" NOT: "Is this a good use of time?"
STEP 1: List All Candidate Projects
STEP 2: Calculate Naive ROI
└── "Quick win: 2x return in 2 weeks = 1.0 ROI"
└── "Strategic bet: 10x return in 6 months = 0.83 ROI"
STEP 3: Ask Opportunity Cost Question
└── "If we do the quick win, we WON'T do the strategic bet"
└── "What's the cost of NOT doing the strategic bet?"
STEP 4: Evaluate 2-Year Impact
└── Quick wins: Often forgotten
└── Strategic bets: Compound over time
STEP 5: Force Allocation
└── Mandate X% of roadmap = strategic bets
└── Don't let quick wins consume 100%
❌ Prioritizing "quick wins" because they're easy to justify
❌ Measuring team output by number of shipped features
❌ Neglecting difficult strategic bets that require longer timelines
At Stripe, Shreyas shifted focus from small incremental fixes (positive ROI) to a massive, scary refactor of marketplace payments (Connect) because the opportunity cost of not doing it was huge.
Source: Shreyas Doshi, Lenny's Podcast
Weekly Installs
0
Repository
GitHub Stars
2
First Seen
Jan 1, 1970
Security Audits
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 周安装