Stop Setting Goals Your Team Can't Control

Every January, teams around the world sit down and set goals. By March, most of those goals are forgotten, irrelevant, or quietly abandoned. Not because the team failed — but because the goals were set up to fail from the start.

After 15 years of coaching teams at companies like Visa and LogMeIn, I've seen the same mistake over and over: teams set goals they can't actually control.

The Outcome Trap

"Increase revenue by 20%." "Reduce churn to under 5%." "Achieve a Net Promoter Score of 60."

These sound great in a board meeting. But they're terrible team goals. Why? Because outcomes depend on factors outside the team's control — market conditions, competitor moves, customer behavior, decisions made by other departments.

When a team's goals are outcomes they can't control, they experience one of two things:

1. Learned helplessness: "Why bother? We can't control this anyway."
2. Gaming: People optimize for the metric instead of the actual result. Churn goes down because someone changed the calculation. NPS goes up because surveys only go to happy customers.

Neither is what you want.

The Input Framework

The alternative is deceptively simple: set goals around inputs, not outcomes.

An input is something the team can directly control. It's the lever they pull, the action they take, the behavior they commit to. The outcome is what happens as a result — but it's not the goal itself.

Here's what this looks like in practice:

| Outcome (Don't Goal This) | Input Goal (Goal This Instead) | |---|---| | Increase revenue by 20% | Ship 3 new features per quarter that address top customer requests | | Reduce churn to 5% | Conduct exit interviews with 100% of churned customers and implement top 3 findings monthly | | NPS of 60 | Respond to every support ticket within 4 hours; follow up on every detractor score within 24 hours |

The team can control whether they ship 3 features. They can't control whether revenue goes up. But if they consistently do the right inputs, the outcomes tend to follow.

Making It Work

Three principles make input goals effective:

1. The Team Chooses Their Inputs

Leaders set the desired outcome. The team decides which inputs they believe will drive that outcome. This creates ownership and leverages the team's expertise about what actually moves the needle in their domain.

2. Weekly Check-ins, Monthly Recalibration

Input goals need short feedback loops. Every week: "Did we do what we said we'd do?" Every month: "Are these inputs actually moving the outcome? Do we need to adjust?"

This is where most goal-setting frameworks fall apart. They set goals in January and review in December. That's not goal-setting — that's wishful thinking with a deadline.

3. Celebrate the Inputs, Learn from the Outcomes

If the team hit their input goals but the outcome didn't move, that's not a failure — that's learning. It means the team executed well, and now they have data to choose better inputs next cycle.

This subtle shift — celebrating consistent execution rather than lucky outcomes — fundamentally changes team culture. People stop playing it safe and start experimenting. They stop hiding missed targets and start sharing what they learned.

The Connection to Automation

Here's where my two worlds collide: automation is often the most powerful tool for executing input goals consistently.

If your input goal is "respond to every ticket within 4 hours," automation can route, prioritize, and escalate tickets to make that achievable. If your input goal is "follow up with every lead within 24 hours," automation can make it impossible to forget.

Automation turns aspirational inputs into systematic ones. And systematic inputs drive reliable outcomes.

The goals aren't the hard part. Knowing what to do with the time, attention, and energy you free up — that's where real performance lives.