1 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
Jason Yip argues that focusing on labour costs can distract teams from what truly matters in product development: the cost of delay. He illustrates this with a scenario where a costly meeting could be justified if it leads to faster decision-making and better outcomes.
If you do, here's more
Jason Yip argues that focusing on labor costs in product development can lead teams astray. He uses a scenario where a company holds a full-day workshop with 100 people, each costing around $400,000 annually, which totals $160,000 for the meeting. He highlights that while the expense seems high, the real issue is not the cost itself but whether the meeting is structured to achieve its goals efficiently. If a meeting can replace a month of delayed decision-making, the potential costs of inaction are far greater—about $1 million per month in this case.
Yip emphasizes that if labor costs dominate the conversation, teams might be prioritizing the wrong metrics. Instead of fixating on hourly rates, businesses should concentrate on the cost of delaying product releases and the overall value of their time. The takeaway is clear: effective meetings and decision-making structures should take precedence over labor cost concerns. Focusing on outcomes rather than costs can lead to better product development decisions.
Questions about this article
No questions yet.