23rd May 2012

Network Dictionary – Backward Planning

I recently observed some documentation outlining the “Forward Planning” process. Lets just put the tautology to one side and realise that if Forward Planning exists, then by extension “Backward Planning” must also exist. But what could Backward Planning be ?

It can’t be the operational documentation, or the handover process. I’ve struggled to make sense of this.

After much thought, I’ve decided that Backward Planning must be the activity that occurs when reviewing the Forward Plan. That is, reviewing design documents, strategy papers, business cases, product options etc etc must be backward planning

And that is what is in my calendar from now on.

This post is copyright of Thropos Ltd ©2008-2011 at Etherealmind.com - contact | email: greg.ferro@packetpushers.net - twitter: @etherealmind | All rights reserved
About Greg Ferro

Greg Ferro is a Network Engineer/Architect, mostly focussed on Data Centre, Security Infrastructure, and recently Virtualization. He has over 20 years in IT, in wide range of employers working as a freelance consultant including Finance, Service Providers and Online Companies. He is CCIE#6920 and has a few ideas about the world, but not enough to really count.

He is a host on the Packet Pushers Podcast, blogger at EtherealMind.com and on Twitter @etherealmind and Google Plus

  • Joe

    I’ve always seen Backwards Planning as “It’s been running for years, do you think we should document it?”

    Also known as build first, plan later.