Tag Archives: milestones

Planning, Goals and Objectives

From the Ask Tom mailbag –

Question:
My role has expanded recently and as a manager, I am expected to participate in our annual goal setting exercise, including setting expectations for my team. How would you suggest I approach this task? I recognize that communicating context is critical.

Response:
Congratulations. Welcome to your new role. Goal setting is actually the second step, not the first in your organizations annual planning exercise. Before you can set goals for yourself and expectations for your team, you have to understand where the organization is going. That always starts at the top of the organization, and, it appears you are now part of that circle.

  • S-V – Business Unit President, goals and objectives, 5-10 years, mission, vision.
  • S-IV – Executive Managers, goals and objectives, 2-5 years, multi-system integration.
  • S-III – Manager, goals and objectives, 1-2 years, single system, single critical path.
  • S-II – Supervisor, goals and objectives, 3-12 months, implementation, execution.
  • S-I – Production, goals and objectives, 1 day-3 months, production.
  • Each layer in the organization should be thinking about, and asking questions related to context at the next level up. It all starts at the top with Mission, Vision. I hold the Business Unit President accountable for leading that discussion, arriving at and defining some conclusions. Then, toward that Mission, Vision, each layer begins to grapple with defining the tasks and activities (the work) including stated targets for each objective.

    The approach, for you, will be to get your arms around the way your company expresses itself in these cascading sets of goals and objectives. Some companies are very formal, some informal, some are loose. Speak directly with your immediate manager.

    • How did the process go last year?
    • How were the results of last year’s process stated, or published?
    • Can you get a copy of last year’s planning output?
    • Is there a schedule for this year’s planning?
    • What preparation do most managers complete prior to the planning process?
    • What data needs to be gathered?
    • Specifically, what formal documentation do you need to produce, as a new manager in your company?
    • Does your planning need to coordinate with anyone else’s plan?
    • Does your plan need to include budget and costs?
    • What has changed during the past 12 months? In your market? In your company? In your department? With your team?
    • What changes in the future do you need to be aware of that might impact your plan?
    • How will the elements of your plan need to be broken down and communicated to your team?
    • When will your plan need to be communicated to your team?
    • What feedback from your team will you need to collect in the preparation of your plan?
    • What milestones will you track (key performance indicators) to make sure your plan stays on track?
    • How often will you review those milestones with your manager?

    That’s probably enough for now.

What is Your Intention?

It’s January, annual reflection time. What are your intentions for the year?

More important than the ideas of your intentions, how will you make them more effective as guideposts, milestones, motivation and internal encouragement?

What is the form of your intentions? Like New Year’s resolutions that are forgotten, intentions can easily fade.

  • Define your intentions in written form.
  • Read your intentions out loud, in private.
  • Say your intentions out loud, in front of a group of people.
  • Give that group permission to hold you accountable.
  • Post your intention somewhere public, where you see it every day, where others see it every day.

You can start with a 3×5 card taped to your mirror.

To Kill A Project

Apoplectic, enraged, irate, spitting mad. That described how Theo felt during his brief encounter with Brad. Two weeks ago, they sat in a delegation meeting, everything according to plan. But here they were, three hours to deadline and the project had not been started. Theo’s ears rang as Brad defended himself, “But you never came by to check on the project, I thought it wasn’t important anymore. So, I never started it. You should have said something.”

Lack of follow-up kills projects. In the chaos of the impending deadline, the manager gets caught up, personally starts, works and finishes the project, often with the team standing by, watching.

One small change dramatically changes the way this delegation plays out.

Follow-up. Schedule not one, not two, but, three or four quick follow-up meetings to ensure the project is on track. Segment the project, and schedule the follow-up meetings right up front, in the planning stages of the project. Check-ins are more likely to happen if they are on the calendar.

What Went Wrong?

From the Ask Tom mailbag:

Question:

We had a deliverable and the engineers on the project came in 3 days late. They finished the project and the quality was solid, so we want to acknowledge their success AND we also want to understand why they didn’t deliver on time. Extra hours were not put in near the end of the project to meet the delivery date. We struggle with acknowledging success when they are simply just doing what they were hired to do.

Response:

It really doesn’t matter what you, as the manager, think. The only thing that matters is what your engineers think. Based on your description, time sensitivity, or sense of urgency was not top of mind.

Project effectiveness, in this case is mixed. While the technical side may have been solidly constructed, the client may have lost several thousand dollars per day because of the delay. Many construction contracts contain liquidated damages for failure to meet deadlines. Most construction litigation is based around damages due to delay-claims. So, time is important, in many cases, critical. However, for some construction related accidents, you may want to visit a site like https://www.pacificattorneygroup.com/construction-accidents/ if you need legal experts who can provide guidance on navigating the legal process, filing claims, and protecting your rights under California labor laws.

At the conclusion of every major project, I always insist on a post postmortem meeting to review the following questions:

  • What did we expect?
  • What did we do well?
  • What went wrong?
  • What can we do next time to prevent this from going wrong?

These questions would allow your engineers to pat themselves on the back for things done well and give them the opportunity to address real issues of underperformance.

On an extended project, I use these same questions at interim checkpoints.

  • What do we expect?
  • What are we doing well?
  • What is going wrong, what is beginning to slip?
  • What corrective action do we need to take, now, to get back on course?

Expecting engineers to call their own meeting to ask these questions will never happen. That is your responsibility, as the manager. Remember, what you think doesn’t matter. What matters is what your engineers think. -Tom