Goals, goals, goals.

All goals are arbitrary, but some are more arbitrary than others.

When your company treats goals like they’re not arbitrary, welcome to the US industrial complex.

What happens if you meet your year-end goals in June? Can you take off the rest of the year?

What happens if at year-end you meet only your mid-year goals? Can you retroactively declare your goals unreasonable?

What happens if at the start of the year you declare your year-end goals are unreasonable? Can you really know they’re unreasonable?

You can’t know a project’s completion date before the project is defined.  That’s a rule.

Why does the strategic planning process demand due dates for projects that are yet to be defined?

The ideal future state may be ideal, but it will never be real.

When the work hasn’t been done before, you can’t know when you’ll be done.

When you don’t know when the work will be done, any due date will do.

A project’s completion date should be governed by the work content, not someone’s year-end bonus.

Resources and progress are joined at the hip.  You can’t have one without the other.

If you are responsible for the work, you should be responsible for setting the completion date.

Goals are real, but they’re not really real.

“Arbitrary limitations II” by Marcin Wichary is licensed under CC BY 2.0

Comments are closed.

Mike Shipulski Mike Shipulski
Subscribe via Email

Enter your email address:

Delivered by FeedBurner

Archives