This is Part 3 and the final installment of a series on Managing by Outcomes. Part 1 introduces the core principles that make this process work. Part 2 discusses how to define outcomes and align your entire organization behind them. Part 3 discusses common challenges and how to prevent them.

In my experience, some teams snap together and consistently hit outcomes, while others work just as hard—or harder—yet always feel like it is three steps forward, two steps back. The difference is rarely effort. It is almost always how the company defines, rolls out, and manages outcomes across the entire system.

In this series, I have introduced the practice of Managing by Outcomes—a way of leading that starts with clearly defined results, aligns the organization around them, and builds simple routines to keep everyone accountable. Done well, it dramatically increases your odds of achieving the goals you set.

But like most good solutions, it can come with new challenges. This article covers eight of the most common issues and how to avoid them.

1) Top-down outcome definition, with no real buy-in.

When leaders dictate outcomes without engaging those involved in executing them, it squelches buy-in. It feels imposed and misses an opportunity to get better information from the people on the ground.

This erodes a sense of ownership and commitment to the outcomes or work. People may be willing to sit back and let someone else do it. Or they might game success instead of working toward genuine results.

Instead, at a minimum, co-design outcomes with direct reports by asking, “What would it take to actually deliver these results?” You will still set direction—but you are letting the people doing the work help shape how it gets done.

2) Misaligned or conflicting outcomes

Sometimes departments or teams pursue outcomes that either do not support each other’s efforts or actively work against each other.

For example, a sales department may have sales goals to hit without guardrails for pricing. So, they cut pricing to increase sales volume. Meanwhile, manufacturing may have margin goals to achieve, but cannot, given how the sales department has cut its pricing.

Neither the sales nor the margin goals are wrong. But in this instance, the way they were structured drove misaligned behaviors.

Before finalizing outcomes, do a quick cross-functional review: “If sales hit its targets this way, how does that impact operations, finance, and service?”

The trick is that these conflicts rarely self-identify as “outcome conflicts.” Instead, they show up as tension between two managers. When two leaders are at odds, ask yourself: Is this a personality issue, or is this the result of ambiguous or conflicting outcomes?

3) Vague or input-focused outcomes (not outcome-focused)

Poorly defined outcomes are one of the most common challenges. In most cases, instead of defining the desired outcomes or results, leaders define what they think is the right method or input. The actual desired results stay ambiguous.

Using a SMART goals framework or a similar approach can help. (See Part 2 of this series for more specific descriptions.)

For example, instead of “Improve culture,” say “Improve voluntary retention of key roles from 80% to 90% over 12 months.”

Once you learn to recognize and set clearly defined outcomes, you will find that your ability to pursue them takes off.

4) No accountability practices

Simply put, ensuring accountability is one of the most powerful practices you can use to drive consistent progress.

When outcomes are well defined, it is very easy and quick to check in on progress. I do this with large teams, and it rarely takes more than a couple of minutes to check in with anyone—because the metrics are clear and easy to report on.

Schedule regular check-ins to verify that progress is being made, evaluate whether guardrails need to be adjusted, and provide coaching, guidance, or support. If you do not, these conversations tend not to happen until a problem becomes apparent. The common tendency is to avoid dealing with it and hope it works itself out. It rarely does—and this sets you up for bigger problems and conflict later.

All of which could have been avoided with clearly defined outcomes and a regular structure for reporting and coaching. Often no more than 15-30 minutes a week per direct report.

5) Weak feedback, coaching, and guidance

Do not use a “pass/fail” approach to accountability check-ins. This is a rich coaching opportunity—to help people grow, to gather input on how your team is doing, and to understand how effectively people are collaborating with each other and across departments.

A simple check-in template can look like:

• A concise report on progress
• What is working well right now
• What is stuck or unclear
• What decisions or support are needed from you

This is not just about accountability or driving progress. It is an opportunity to build your leadership bench—and it requires very little time or effort.

6) Gaming for rewards

In the sales vs. manufacturing scenario described above, it is possible that sales is “gaming” their pursuit of outcomes.

For example, if the team was told, “Sell 10,000 widgets, and you will get your bonus,” it may have been assumed they understood that this needed to be done at a profit and should not harm the rest of the company.

But it is gameable. The sales team can hit the goal and still cost the company. This is where guardrails are crucial. For example: “Sell 10,000 widgets at or above X margin, with no more than Y% of orders requiring rush production.”

The problem is not incentives. It is single-metric rewards that are not designed with the larger system in mind.

7) Capacity, resources, or constraints are ignored

Sometimes we ask individuals or teams to accomplish something they do not have the knowledge, skills, tools, time, budget, or staffing to deliver. In most cases, this happens because growth goals are being pursued without considering the downstream needs and impacts of that growth.

This can be resolved by imagining what success would look like operationally. For example: “If we plan to grow revenue by 30% next year, how many additional technicians, dispatchers, or account managers will that require—and when do we need to hire them?”

In my experience, growth is frequently constrained by not anticipating the changes required to accomplish or sustain it.

8) Tunnel vision on numbers vs. the system

Do not let the tail wag the dog. Managing by Outcomes is a process—it is not the goal or the outcome itself. If the dashboard is green but your customers or employees are telling you there are problems, then there is a problem.

Management can fixate on stated goals instead of asking, “Is this actually working?” The overall process should contribute to a stronger, more effective way of managing and working productively together. Treat the numbers as feedback about the system—not as a grade on the people.

Conclusion

The eight challenges in this article share a common thread: they all stem from skipping the basics. Vague outcomes, skipped check-ins, or goals that were never tested for alignment. These aren’t complicated or time-consuming. They are the result of trying to move too fast.

The solution is simple, it just takes discipline. Define outcomes clearly, build in accountability routines, stay curious when something feels stuck, and keep asking whether the system is actually working.

Do that consistently, and Managing by Outcomes will deliver. It’ll give you a company that moves as you intended it to.

Take good care,

Christian