I agree with what you’ve said; general charactaristics that make a poor planner are pretty much the same as those that make a poor project manager, accountant or chemist. These run pretty much along the lines of the list below
Doesn’t spend sufficient time or effort doing the job he’s paid for;
Antagonises or patronises the people he has to work with;
Doesn’t give straight answers to straight questions;
When asked for an explanation, either becomes evasive or spouts a complete load of horse puckey;
Imagines that software and paperwork will do the planning for him;
Has an overinflated opinion of his own intelligence and abilities;
Is unable to accept criticism;
Has preconceived ideas about people based on stereotypes of race or nationality;
Is unable to admit it when he doesn’t know something;
Wastes people’s time with trivia and irrelevances;
Not everything, of course, but maybe it’ll do as a start.
when I saw the thread title in CAPS I initially though that this was another Charlie thread :)
There are several discussions on the other sub-forums about this subject, from different angles. Some make interesting reading, some descend into rants. My opinion on your question;
A bad planner may be Arrogant, believing that he or she knows how to organise and execute the works more effectively than the executers. It really doesnt matter, even if he or she is correct in their assumption because the planner is not the one who executes the project.
Conversely, a bad planner may be too timid or lacking in project specific knowledge to communicate with the executors and management regarding expectations and acheivability. Such a planner will tend to stretch (or more accurately compress) the acheivable to match the expectations handed down. A bad plan will result.
In both cases, such planners will tend to work in an ivory tower, isolating themselves from the executors
Thus, I believe that a planner needs a balance between the ability to debate with others (both executors and management) and the willingness to listen to them.
Further, Id say that, both in relation to the above and to the generation of the output, a planner must essentially be an excellent communicator. Bad communicators never make good planners in my experience. Thankfully, communication skills are not genetic and can be learned.
Finally, the best plans are the ones that have been thoroughly bathed in constructive criticism by the management but more importantly the executors. This will temper the plan, as well as effectively involving the executors in the process (horrible phrase, but "buying in" is still the best I can think of). Thus an ability to take criticism on the chin is a real asset, as is the ability to recognise constructive criticism from sniping and ignore the latter without heckles raised. This is probably my weak point but I have a decent boss who I trust to recognise the sniping as it happens (and there is a lot of it) so I dont need to defend myself against it ... at least thats what I tell myself!
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
James,
I agree with what you’ve said; general charactaristics that make a poor planner are pretty much the same as those that make a poor project manager, accountant or chemist. These run pretty much along the lines of the list below
Not everything, of course, but maybe it’ll do as a start.
Chris Oggham
when I saw the thread title in CAPS I initially though that this was another Charlie thread :)
There are several discussions on the other sub-forums about this subject, from different angles. Some make interesting reading, some descend into rants. My opinion on your question;
A bad planner may be Arrogant, believing that he or she knows how to organise and execute the works more effectively than the executers. It really doesnt matter, even if he or she is correct in their assumption because the planner is not the one who executes the project.
Conversely, a bad planner may be too timid or lacking in project specific knowledge to communicate with the executors and management regarding expectations and acheivability. Such a planner will tend to stretch (or more accurately compress) the acheivable to match the expectations handed down. A bad plan will result.
In both cases, such planners will tend to work in an ivory tower, isolating themselves from the executors
Thus, I believe that a planner needs a balance between the ability to debate with others (both executors and management) and the willingness to listen to them.
Further, Id say that, both in relation to the above and to the generation of the output, a planner must essentially be an excellent communicator. Bad communicators never make good planners in my experience. Thankfully, communication skills are not genetic and can be learned.
Finally, the best plans are the ones that have been thoroughly bathed in constructive criticism by the management but more importantly the executors. This will temper the plan, as well as effectively involving the executors in the process (horrible phrase, but "buying in" is still the best I can think of). Thus an ability to take criticism on the chin is a real asset, as is the ability to recognise constructive criticism from sniping and ignore the latter without heckles raised. This is probably my weak point but I have a decent boss who I trust to recognise the sniping as it happens (and there is a lot of it) so I dont need to defend myself against it ... at least thats what I tell myself!