The Distinction Between Design and Planning
I decided to have a look at the Army's newcounterinsurgency field manual (issued jointly with the Marine Corps). There is much of interest, but I have to say, after reading through the 282 pages, what most intrigued me was the careful distinction drawn between design and planning.
The manual summarizes the distinction as that between problem-setting and problem-solving. Design "inquires into the nature of a problem to conceive a framework for solving that problem." Planning "applies established procedures to solve a largely understood problem within an accepted framework."
In a nutshell (somewhat adapted):
Design: Problem-setting.
Planning: Problem-solving.
Design: Conceptual, so start with a "blank sheet."
Planning: Physical and detailed.
Design: Questions assumptions and methods.
Planning: Follows best-practice procedures.
Design: Develops understanding.
Planning: Develops products.
Design: Paradigm-setting.
Planning: Paradigm-accepting.
Design: Complemens planning, preparation, execution, and assessment.
Planning: Structures activity by establishing patterns and templates.
Design: Leader-driven dialogue.
Planning: Staff-centered process.
It is important to recognize that design and planning fall along a continuum — there is no bright line between them. On the other hand, you do need to determine upfront whether a particular situation requires starting at the design end of the spectrum.
A further key point is that design is iterative. As decision-makers gather further information and experience, they learn and adapt, a strong theme throughout the manual.
Labels: Critical thinking, Innovation, Strategy, Systems thinking
posted by Karen Nelson @ 11:30 PM
<< Home