For the last couple of days, I was attending a workshop on Project Management (yes you heard it right). I wanted to brush up my PM knowledge after working as a “consultant” for few years, and also look at the new dimension of effective PM using systematic thinking methods, especially simple TRIZ tools. I set my expectation before attending this program that the Project Management Body of Knowledge would have embraced something different to say the PM BOK (Body of Knowledge) is evolving, and the session is going to teach me something new, such as using techniques for effective Project Planning. Unfortunately, it was nowhere close to my expectation.
In the last couple of years we have witnessed the increasing complexity of uncertainty in the existence of a business, collective social knowledge for a consumer to change the business decisions of a company within the span of a dusk and a dawn, and finally how has it impacted the people delivering innovative solution, questioning their own “existence” on a project in the helm of these external developments. Naturally, these super-system developments have the undulate effect in a Project Management activity, and without doing something new, I think Project Management will still be the most challenging activity with a success ratio ticking to the top of % charts.
Considering this “evolution gap” in the PM BoK viz-a-viz the external business scenario, I was trying to conceive the concepts to make a Project Manager's life simple during the workshop. Major part of the “PM thinking” has been involved in planning and monitoring; in the true sense of today, Planning and Firefighting. Despite a good Project Plan, PM’s are in the firefighting mode in at least 80% of the projects being executed today.
Let’s look at the planning; when and where do we start planning a project is highly dependent on the context. The context of the services offered by your company, the context of your customer business needs, the context of your people involved in, and most factually, after the contract signing. I think we aren’t late to start a project plan after signing the contract, but what could have happened by then is the amount of relevant project information transacted before the contract signing is no longer within the reach of a PM, and even if they are, mostly ambiguous. As a PM you have a clean canvas and start from there. How effective the planning could then be?
Most often, the project planning concentrates on the execution model of “what I know I know” perspective. “What I know I don’t know” and “what I don’t know I don’t know (or have no clue about it” are the place holders in your assumptions and dependencies, and the success of your project may be decided by that.
Is there a way to identify “what we do not know well” for a PM during the planning stage? Apart from seeking inputs from your surroundings (people and artificats around you, if any), what should be your thinking model? I have often heard that a Good Project Manager is someone who knows that s/he can not predict the future. I think a good PM toady should not only assume that the future is unpredictable, but also identify the plane of unpredictability and direction of the evolution from today to the future. Unfortunately, we are too busy to think outside that “project” box and writing a project plan with what we know, and think about the operational activities and outcomes.

You can also download this as a PDF version (to read the questions inside the windows) from TRIZ Community discussion forum
hereSo, this is what I’m experimenting now, using a 1-2 (actually 12) Windows of thinking for Project Planning, a simple, systematic thinking technique to look at the plane of unpredictability of a project.
(You don’t necessarily need a “Window” for Project Planning, because in this stage (planning) of a project you don’t even have a “foundation” ready :).
So, you have noticed the above 12 windows have nothing but questions. May be, ’Q’ is the ‘P’- lanning, if you have questions, you have the answers, or someone, somewhere will or have the answers for your questions. Any problem related to any project is that there were only “Answers” before we started the project, and no Questions. Do you really need the above 12 windows to ask questions? Well, believe me, we need. As an adult, we don’t really like questions, and if at all we ask questions, we mostly ask questions for TODAY.
The above lists of questions are certainly nowhere close to the actual number of questions a PM should ask. If you have the context of your project in the “System-Present”, you have the right question for PAST, PRESENT, and indeed FUTRE. Do your thinking and let me know what window you as a PM would like to OPEN/CLOSE?