Comments on: Management-as-Determining? http://www.reformingprojectmanagement.com/2002/10/30/22/ The magazine for the project age Fri, 04 Jul 2008 13:45:08 +0000 http://wordpress.org/?v=2.0.5 by: Buck http://www.reformingprojectmanagement.com/2002/10/30/22/#comment-400 Wed, 31 Dec 1969 16:00:00 +0000 http://www.reformingprojectmanagement.com/2002/10/30/22/#comment-400 Hi, I would just like to comment on one of your last sentences, >Better (much better) is to add detail no sooner than it is needed (acting a the last responsible moment) taking advantage of what is revealed and learned. Sometimes, it`s hard to pinpoint the last responsible moment and sometimes you have to stake your claim early in a project otherwise you have a repeated discussion on decisions you make later in the project. Imagine an IT project where you state that the language of choice is xyz for the apropriate reasons... Now if you state this early in a project, all involved can get accustomed to the thought and in the end they will follow. Now if you decide on such a vital detail in the middle of a project this decision might be exploited for various targets like e.g. an excuse why the project is late... And you might get into repeated arguments when you least need them (in the middle of a running project) So it`s a tough call to make this last responsible moment... Even though I like the concept, I find it hard to implement. Bye Buck Hi,
I would just like to comment on one of your last sentences,
>Better (much better) is to add detail no sooner than it is needed (acting a the last responsible moment) taking advantage of what is revealed and learned.

Sometimes, it`s hard to pinpoint the last responsible moment and sometimes you have to stake your claim early in a project otherwise you have a repeated discussion on decisions you make later in the project.

Imagine an IT project where you state that the language of choice is xyz for the apropriate reasons…
Now if you state this early in a project, all involved can get accustomed to the thought and in the end they will follow.
Now if you decide on such a vital detail in the middle of a project this decision might be exploited for various targets like e.g. an excuse why the project is late…
And you might get into repeated arguments when you least need them (in the middle of a running project)
So it`s a tough call to make this last responsible moment…
Even though I like the concept, I find it hard to implement.

Bye

Buck

]]> by: Mary Poppendieck http://www.reformingprojectmanagement.com/2002/10/30/22/#comment-401 Wed, 31 Dec 1969 16:00:00 +0000 http://www.reformingprojectmanagement.com/2002/10/30/22/#comment-401 A set-based design concept can be very useful for thinking about when to make decisions. Delaying decisions is the equivalent of maintaining options, a very find economic approach to business. In design, one maintains options by defining the constraints of choices, rather than making a choice and iterating on it. As time progresses and more knowledge is gained, the constraints are narrowed. This is the way Toyota designs cars. Of course, a fine sense of timing is required to know when decisions have to be made, but my observation is that we have a great tendency to want to ‘lock in’ decisions as soon as possible, while the bias to make them as late as possible tends to be counter to our ‘culture’. A set-based design concept can be very useful for thinking about when to make decisions. Delaying decisions is the equivalent of maintaining options, a very find economic approach to business. In design, one maintains options by defining the constraints of choices, rather than making a choice and iterating on it. As time progresses and more knowledge is gained, the constraints are narrowed. This is the way Toyota designs cars. Of course, a fine sense of timing is required to know when decisions have to be made, but my observation is that we have a great tendency to want to ‘lock in’ decisions as soon as possible, while the bias to make them as late as possible tends to be counter to our ‘culture’.

]]> by: Mary Poppendieck http://www.reformingprojectmanagement.com/2002/10/30/22/#comment-402 Wed, 31 Dec 1969 16:00:00 +0000 http://www.reformingprojectmanagement.com/2002/10/30/22/#comment-402 I like to divide planning into two types: 1. Plan to Learn 2. Plan to Execute The first type of planning is good. The second type of planning has a great tendency to make decisions before their time. It is the failure to keep options open, even when there is little cost to doing so, that makes ‘planning to execute’ ineffective in a changing environment. I like to divide planning into two types:

1. Plan to Learn

2. Plan to Execute

The first type of planning is good. The second type of planning has a great tendency to make decisions before their time. It is the failure to keep options open, even when there is little cost to doing so, that makes ‘planning to execute’ ineffective in a changing environment.

]]> by: Buck http://www.reformingprojectmanagement.com/2002/10/30/22/#comment-403 Wed, 31 Dec 1969 16:00:00 +0000 http://www.reformingprojectmanagement.com/2002/10/30/22/#comment-403 Hi Hal, >proneness to naivete. I don`t think it to naiive only sometimes you just have to adapt to your environment and if you are in a rough environment you have to adapt, sometimes... I always have to take that into account when I´m writing PM Handbooks for different companies. Depending on the whole interpersonal chemistry that is current in a company I sometimes have to spell out every step right down to the smallest detail, including escalation chains and sometimes it`s ok to wrap it all up in 10 pages... It´s a strange world out there ;-) Bye Buck P.S. I like the anagramm, although I haven`t found the solution yet... Hi Hal,
>proneness to naivete.
I don`t think it to naiive
only sometimes you just have to adapt to your environment and if you are in
a rough environment you have to adapt, sometimes…
I always have to take that into account when I´m writing PM Handbooks for different companies.
Depending on the whole interpersonal chemistry that is current in a company
I sometimes have to spell out every step right down to the smallest detail, including escalation chains and sometimes it`s ok to wrap it all up in 10 pages…
It´s a strange world out there ;-)

Bye

Buck

P.S. I like the anagramm, although I haven`t found the solution yet…

]]>