Tasks for Each Phase in the Plan
A sequence of top-level tasks for executing each phase of the 3-Phase Project Plan model is laid out here as a template for planning purposes. Again, it is a PARADIGM, not a cook book recipe, so apply it with discernment. If some tasks in the template serve the needs of your project, use them. If some do not, discard them. If you need tasks not in the template, create them.
The tasks in each phase of the model are based on the four-step Solution Search Path (SSP) described elsewhere on this site. If you need to, go read that material before proceeding here.
The project begins with recognition of a serious problem in the real world that calls for a solution. We’ll call that PROBLEM A. Wisely, the people who initiate the project recognize that jumping right into PROBLEM A without adequate preparation would be a very bad idea. PROBLEM A needs a competent Solution-Discovery process, and creating that process itself is a job requiring adequate preparation. This indicates the necessity for a chain of developing-a-process for developing-a-process for doing solution-discovery, hence the three-phase project plan paradigm. The Muddle Buster admits that this chain of process development activities seems complicated, but it is necessary to produce a competent process when the issue is complex.
This three-phase process-development chain, as described here in words, can be confusing. If you find that so, first go to the branch on The Three-Phase CSD Project Paradigm, where the the chain of project phases is depicted graphically.
As described here, the three-phase project chain assumes the project is starting from scratch. There is no organization in place to do the project, no organizational infrastructure to support the project, no legacy of similar project experience to apply. There are only the few people, maybe only one, who recognize the need to address PROBLEM A as they see it, and have the confidence that a project to find a solution is feasible.
Phase 1
Organize the project team. Then create the process-development methodology for use in Phase 2 to design a Solution-Discovery Process to work PROBLEM A in Phase 3.
Task 1.1
Pull together a lean, mean and process-oriented team that can focus on creating the process-development methodology to be used in the next Phase. These are people who understand that a good product demands that a good process be in place to deliver that product.
Task 1.2
Agree on the details of problem definition for Phase 1, which is “What is the process-development methodology, organization and plan to be used in Phase 2 to create the Solution-Discovery Process to solve PROBLEM A in Phase 3?”
Task 1.3
Identify the stakeholders for Phase 1. These are the people who are concerned about finding a good Solution-Discovery Process for PROBLEM A, but not yet about working PROBLEM A itself. They know that getting that good Solution-Discovery Process for PROBLEM A means first setting up a process-development methodology in Phase 1 which is used in Phase 2 to create the Solution-Discovery Process for PROBLEM A in Phase 3.
Stakeholders in Phase 1 might also include, on the negative side, people who don’t want PROBLEM A to be solved at all, for whatever reason.
If, unlikely though it may be, this group of all stakeholders is large and varied, help them organize into sub-groups that share common interests, for the purpose of participating efficiently in the job at hand.
Task 1.4
Find out what the stakeholder interests, concerns, values, priorities and aspirations are about setting up a good process-development methodology for use in Phase 2 (got that?). Compile all this data and check it out with the stakeholders.
Task 1.5
Convert the stakeholder data from Task 1.4 into a Definition of Success for a good process-development methodology to use in Phase 2, where the job is to create a Solution-Discovery process for Phase 3. This Definition of Success contains all the qualities of outcome expected from the process-development used in Phase 2, as important to all the various stakeholders. Again, check it out with the stakeholders for Phase 1.
Task 1.6
Set up a method for searching out good solution options for process-development in Phase 2, and check it out with the stakeholders.
Task 1.7
Using this search method with creative input and review from the stakeholders, generate a menu of solution options for process-development in Phase 2. That is, how will design of a Solution-Discovery process for use in Phase 3 be done in Phase 2?
Task 1.8
Set up a method for evaluating the solution options in the menu coming out of Task 1.7. Apply the qualities of outcome from the Definition of Success (Task 1.5) as the selection criteria.
Task 1.9
Implement the process design methodology created through steps 3 through 10 to find the preferred process-development methodology to be used in Phase 2 to create the Solution-Discovery process for Phase 3.
Once again, we ask, does this Task Plan for Phase 3 need to be so elaborate? That depends on the size and complexity of the organization to do the project. For a small project with a close-knit project team, simply calling the project start-up team together for one or two meetings will be sufficient to satisfy the needs of Phase 1. That can often happen within the first few days of the project’s life.
On the other hand, for a large complex project involving many independent agencies (governmental, commercial and NGOs), each with a strong organizational identity and agenda, it is prudent to proceed carefully and thoroughly. In that case a formal plan for Phase 1 is called for, with each task planned in detail, full stakeholder engagement emphasized, and reports written to record the proceedings and decisions of each task.
Remembering that CSD is a paradigm, not a cookbook, the essential idea is to understand the intent of each task in Phase 1 and fulfill that intent in the most expeditious and appropriate manner
Phase 2
Develop a Solution-Discovery Process to work PROBLEM A in Phase 3.
Task 2.1
Expand and reorganize the project core team for executing Phase 2. More people with expertise in designing the Solution-Discovery process may be needed, and the project organization will be faced with different tasks. Again, bring in process-oriented people, recognizing that the stage is not yet set to go to work directly on PROBLEM A.
Task 2.2
Agree on the details of problem definition for Phase 2, which is “What is the Solution-Discovery Process, organization and plan to work PROBLEM A?”
Task 2.3
Check whether more stakeholders concerned with process quality need to be brought into the project.
Task 2.4
Integrate the new stakeholders into sub-groups that share common interests, for the purpose of participating efficiently in the job at hand, as were set up under Task 1.3.
Task 2.5
Find out what the stakeholder interests, concerns, values, priorities and aspirations are about the process for creating the Solution-Discovery process for Phase 3. Compile all this data and check it out with the stakeholders
Task 2.6
Convert the stakeholder data from Task 2.5 into a Definition of Success for a good Solution-Discovery process to work PROBLEM A in Phase 3. This Definition of Success contains all the qualities of outcome resulting from having a good Solution-Discovery process, as important to all the various stakeholders. Again, check it out with the stakeholders for Phase 2.
Task 2.7
Set up a method for searching out good solution options for doing Solution-Discovery on PROBLEM A, and check it out with the stakeholders.
Task 2.8
Using this search method with creative input and review from the stakeholders, generate a menu of solution options for Solution-Discovery in Phase 3.
Task 2.9
Set up a method for evaluating the solution options in the menu. Apply the qualities of outcome from the Definition of Success (Task 2.6) as the selection criteria.
Task 2.10
Implement the process design methodology created through steps 3 through 10 to find the Solution-Discovery process to be used in Phase 3 to solve PROBLEM A.
Phase 3
Apply the Solution-Discovery Process from Phase 2 to work PROBLEM A in Phase 3.
Task 3.1
Reorganize the project core team for Phase 3. Now bring in people who are concerned with solving Prob A itself. Establish organization to use the Solution-Discovery process as developed in Phase 2 for solving PROBLEM A.
Task 3.2
Agree on the definition of PROBLEM A, the issue that kicked off this whole project. Although that was first done at the beginning of Phase 1, new knowledge about that problem has doubtless emerged in the course of the project so far, and that needs to be addressed.
Task 3.3
Identify the stakeholders in PROBLEM A, both new ones and carry-overs from previous phases. These are the people who are concerned about the good outcomes when PROBLEM A is solved, and perhaps also people who don’t want PROBLEM A to be solved at all, for whatever reason.
Task 3.2
Help the stakeholders form into sub-groups that share common interests, for the purpose of participating efficiently in the job at hand.
Task 3.3
Find out what stakeholder interests, concerns, values, priorities and aspirations are for the outcome when PROBLEM A is solved. Compile all this data and check it out with the stakeholders. share common interests, for the purpose of participating efficiently in working PROBLEM A.
Task 3.4
Convert the stakeholder data from Task 3.3 into a Definition of Success for PROBLEM A which contains all the qualities of outcome that will result from a good solution to PROBLEM A. Again, check it out with the stakeholders in PROBLEM A to be sure everybody’s concerns are in the mix.
Task 3.5
Set up a method for searching out good solution options for PROBLEM A, and check it out with the stakeholders.
Task 3.6
Using this search method with creative input and review from the stakeholders, generate a menu of solution options for PROBLEM A.
Task 3.7
Set up a method for evaluating the solution options in the menu. Apply the qualities of outcome from the Definition of Success from Task 3.4 as the selection criteria.
Task 3.8
Execute the Solution-Discovery process created through Tasks 3.3 through 3.7 to work PROBLEM A.
Task 3.9
Implement the solution you have discovered. DONE!