This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Management & Leadership

The Dark Side of Input Metrics

Input metrics can be helpful to track progress toward long-term goals, but they can cause issues if not used carefully. They might make people act in ways you didn’t expect, limit creativity, and lead to micromanaging.

Darth Vader as a Chart cartoon

When used for measuring performance, these metrics can push people to focus only on meeting the specific inputs, not the bigger picture. Imagine that one of your input metrics for a health improvement plan is "have a salad as a meal three times per week." Someone driven by the desire to fulfill the metric adds a small salad as a fourth meal but compensates by indulging in fast food and sweets for the remaining meals. Or they might eat dishes they can call salads but lacking in nutritional value—turning chili cheese fries into a questionable interpretation of a potato salad.

Even if you don’t directly judge someone’s performance based on these metrics, just focusing on them can stifle creativity. Input metrics tell you exactly what to do, and people can feel pressured to do only that instead of finding other, maybe better, ways to reach the real goal. If the goal is to eat a salad every day, you might miss out on discovering other healthy meals that are better options for you. The checklist says to eat a salad, so that’s what you do.

Both of these problems happen because the focus shifts from what you want to achieve to what you have to do. An input metric tells you "do this" instead of "achieve this."

If you’re going to use input metrics, you need to ensure that they also capture the intent and not just the activity. The intent of eating a salad three times a week is to replace some unhealthy meals with healthier ones. The real goal isn’t to eat things called salad. Eating salad was a proxy measurement in your quest to improve your nutrition and lose weight. You need to keep the end goal in sight and connect it to the input metric.

There’s an old joke about a cook who always cuts off the end of a roast before cooking it. When asked why, he says his mom did it that way. When they ask his mom, she says her mom did it that way. Finally, they ask Grandma, and she reveals it was because the butcher only sold roasts that were too big for her oven.

"We do it this way because we’ve always done it this way" is a hard habit to break in an organization. Input metrics risk becoming company rules. If they aren’t always linked back to the purpose, you’ll start to get people performing the activity even when it no longer serves the goal.

The third way input metrics can become harmful is when they are set outside of the team. The people doing the work must be the ones that choose which inputs to measure. An input metric is "do this" instead of "achieve this." When they’re set by a manager, that’s micromanagement.

Input metrics are only helpful when they’re chosen by the people doing the work. They’re only useful when they’re used as a way to predict progress toward future outcomes. If they are used in any other way, they can slow down progress and stop creativity.

Recently Written

Your OKR Cascade is Breaking Your Strategy
Aug 1: Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here's what works better than the waterfall approach.
Your Prioritization Problem Is a Strategy Problem
Jul 23: Most teams struggle with prioritization because they're trying to optimize for everything at once. The real problem isn't having too many options—it's not having a clear strategy to choose between them. Without strategy, every decision feels equally important. With strategy, most decisions become obvious.
Behind schedule
Jul 21: Your team is 6 weeks late and still missing features. The solution isn't working harder—it's accepting that your deadlines were fake all along. Ship what you have. Cut ruthlessly. Stop letting "one more day" turn into one more month.
VC’s Future Lies In Building Winners
Jun 21: AI and megafunds are about to kill the traditional venture model, forcing smaller VCs to stop hunting for hidden gems and start rolling up their sleeves to fix broken companies instead.
Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.

Older...

What I'm Reading