Goals ► Priorities ► Outcomes ► Initiatives

Do your organizational goals sound something like this: Foster talent by building a culture that maximizes opportunities for growth. Sounds nice, right? But how would you measure that? How would you know when you’ve achieved it? The truth is, it would be next to impossible. Whether you’re creating goals at an organizational level or at an operational level, here are some tips for improving them so that you can demonstrate their achievement.

Describe the outcome.
The trick is to describe the result you hope to achieve rather than the activity. Measuring an activity can result in meaningless metrics. (It is also wise to stay away from words and phrases that cannot be measured such as maximize or more efficient.) Here’s a possibility: Growth and innovation will increase through training, mentoring, and creating time buffers around scheduled projects.

Studies have shown that goal specificity and level of difficulty have a direct impact on employee performance: Goals that are specific and challenging (but not unreasonable) lead to better performance by motivating employees.

Create line of sight.

Just as important, a clear line of sight should exist between corporate objectives and the goals set at the operational level—employees should be able to grasp their roles’ importance in the larger picture. In order to achieve this, it is helpful to include different levels of the organization in developing the goals to ensure consensus, cooperation, and realistic goal-setting.

Define the measure.

Once your goals have been determined, you will be able to think about how you will measure the outcome.

• What are we trying to achieve?
• What behavior are we hoping to encourage? (Key Performance Indictors)
• What will success look like?

Performance measures should be as explicit as your goals, and answer the following:

• What change is being measured?
• How will the change be quantified (generally a number or percentage of something)
• What is the starting point or baseline measure?
• What is the target performance? By when?

It is an old saying but true: you cannot manage what you do not measure. Measuring tracks the specific activities and conditions necessary to support your goals and provides the means by which you communicate to the organization what is important. Measuring also presents the opportunity to identify problem areas and affords employees the ability to monitor their performance and see themselves comparatively. It is therefore vital that you measure the correct things—not the easy things because they exist or because you’ve measured them before—the right things. If your goals have been delineated with specificity and the outcomes you wish to achieve are clear, chances are you will know what they are.

Now the truth is if you start with a structural reorganization, it’s like going on a crash diet. Everybody knows the naughty non-foods you can cut out, just like everybody knows which low-performers could be eliminated or how work could be shuffled around to immediate effect. So you lose a few pounds by cutting out “empty calories” and get rid of some of the obvious encumbrances at work—a quick fix that’s very gratifying. But what happens after that? Usually all the weight comes right back (and then some) and the reorganization doesn’t really change a thing—everything reverts to the way it was. Why? Because the underlying behaviors are still the same.

A diet that relies on simply cutting calories is bound to plateau or fail because there’s considerably more to maintaining a healthy weight and body that includes exercise, eating complex carbohydrates, drinking plenty of water and getting plenty of rest. It is a lifestyle change. Likewise, restructuring an organization is much more complex than focusing solely on getting rid of problematic players or reshuffling the team. The key to sustainable organizational change is to look at the organization holistically and to define the operating model and its various components: roles, processes, governance, sourcing, services, and then structure, and how these are interconnected and measured. Are the right people in the right roles? Are there processes that could be simplified, platforms that could be shared? What does the Business want from you in terms of capabilities and services? What are your differentiating (core) activities that would be at risk if anyone else performed them? What core activities do you monitor and measure?

Whenever we have a client who wants to start with a structural reorganization, we encourage them first to map their capabilities to their services and then to identify those services that are differentiating (core) that would be at risk if someone else (i.e., a contractor or vendor) performed them. Once you know what is core and what is non-core, then you can begin to understand where staff spends most of their time. What we often see is that the majority of the organization is bogged down supporting non-core activities, e.g., enhancement, maintenance, and support. They are held hostage to these activities because they are the only ones who know how the processes work and their managers have come to rely on them. Usually people inherit processes and, as a consequence, documentation is scant or non-existent. This lack of documentation is another reason resources remain where they are rather than shift to new core activities/services.

Changing structure won’t change the fact that the most of the organization is performing non-core work instead of focusing on perfecting the services that are core to IT and your company. Evaluating what’s core and non-core is often the best way to demonstrate why changing the structure or moving the parts isn’t the answer.

Has your organization ever attempted a reorg before understanding the underlying issues? How did it turn out?