4 Responses to “Optimized Planning is Good, not God!”

  1. Jim Ashmore

    Good article.

    One thing I have noticed over the years is that the life span of “The Plan” is getting shorter and shorter. Maybe a better term is “half life” because “The Plan” degrades exponentially rather than linearly. At some point, critical mass is reached where “The Plan” implodes/explodes and must be redone, hence the need to monitor and adjust, quickly.

  2. Trevor Miles

    Hi Jim

    Thanks for the comment. I’m presuming your “Good article” comment is a reference to the title of the blob? Namely that my opinion is good, but not God? ;-) Well, I would agree.

    Yes, half-life is a good way to think of plan accuracy or risk.

    But I can’t state strongly enough that we all need to plan. What confuses me is the effort put into ensuring that the plan is achieved, even to the point of having plan conformance metrics, when it is the plan that is ‘wrong’.

    I want to be very careful here to distinguish between targets/goals and plans. Targets are aspirational and set the direction for an organization. Plans at one level are about how to achieve the goals, but these plans are strategic and more about which markets to enter, which technologies to pursue, etc. I am mostly refering to tactical plans as they relate to supply chains. What is our anticipated demand and how will we align the supply to satisfy the demand.

    And of course we need always to understand the difference between something happening because we did not execute well versus because we did not have the right information (and therefoer the right plan) to start with.

  3. Jim Ashmore

    When I wrote, “good article”, I was referring to the content, not the title. I shared it with my Supply Chain Team.

    Knowing that “The Plan” is inherently in error is not a reason to throw up our hands and not plan on either a strategic or tactical level. We need a guidepost or as I read in a previous post, a range of plans, to operate towards. And, not only do we need to plan, we need to measure performance against that plan and react to significant deviations in demand, supply, resources or time bucket. Not only that, we need to monitor and adjust the buffers in each (demand, supply, resources or time) and determine when they reach critical levels, either high or low while adjusting accordingly.

    This is where most processes fail, even the one I am involved in on a daily basis.

  4. Trevor Miles

    Hi Jim

    My comment about the title was a joke, not meant seriously.

    I agree with everything you write, especially the concepts of guideposts.

    My only quibble, and its a quibble because the result is the same, is your use of the words “we need to measure performance against that plan”. The reason I use different terminology is that this wording implies that the plan is the source of truth against which we need to measure our performance, and I am saying that the plan was never 100% correct anyway.

    How I state it is that what we need to measure is when there is significant deviation of our plan from actuals, because after all the actuals are the “truth”, we just assumed something different would happen. So we need to detect when our assumption are wrong and readjust.

    It is a philisophical point but I think an important one. The one – measure performance against the plan – tries to make reality fit the plan, whereas the other – measure significant deviation of plan to actuals – is more about agility and responsiveness.

Leave a Reply