|
|
| Line 1: |
Line 1: |
| | ; [[Rationale]] : Why do these guidelines exist. | | ; [[Rationale]] : Why do these guidelines exist. |
| − |
| |
| − | == The Idea ==
| |
| − |
| |
| − | Track and document PDP projects in a lightweight and uniform fashion.
| |
| − |
| |
| − | == Background ==
| |
| − |
| |
| − | The PDP group executes a rather large number of projects. The projects are started in various ways. Alignment with the PDP strategy, cost/benefit analysis, and alignment with other running PDP projects, is carried out in an ad-hoc fashion if at all. The progress, completion, and result of projects is often not documented.
| |
| − |
| |
| − | == How it works ==
| |
| − |
| |
| − |
| |
| − | 2. Background. What conditions have arisen that led you to this recommendation? Only include information that everyone agrees upon in the Background - this is the basis for discussion, so it needs to be non-debatable.
| |
| − | 3. How it Works. The details. In addition to How, also What, Who, When, Where.
| |
| − | 4. Key Benefits. This is the "Why?" There are usually three benefits: the recommended action is on strategy, already proven (e.g. in test market or in another business unit), and will be profitable. You can think of these three in terms of the old Total Quality mantra of "doing right things right." The first (on strategy) means you're doing the right thing. The second and third mean you're doing things the right way, because you're being effective (proven to work) and efficient (profitable).
| |
| − | 5. Next Steps. Who has to do what and by when for this to happen?
| |
