What Is Planning? Start With the Question the Proposal Has to Answer

The first time somebody asks you to write a proposal, the blank document can make the work look like a question of format. Gil Yeong-ro’s What Is Planning? begins earlier, with the words you will use and the decision you are asking someone to make. I read it as a reference to keep near the document, not as a form to copy.

Say What the Words Mean Before You Use Them

A team can agree that it has a problem and still be talking about different things. Gil distinguishes a condition you want to change from the particular points that may explain it. He separates the purpose of a project, the reason to do it, from a target you can later check. In his vocabulary, planning chooses a direction and a way forward, while an implementation plan works out how to act.

The book spends time on definitions because a word has to do work in the proposal. A general definition gives you a shared starting point. An operational definition says what counts for this project and how people will recognize it when they see it. If the team cannot tell what an improvement would look like, it is still too early to write that it will improve.

Build an Argument Out of Evidence

Gil asks the planner to distinguish background, the state of affairs and evidence about causes. A good proposal makes it possible to see which statements were observed and which conclusions were inferred. A pattern may point to a cause, but the explanation still has to survive scrutiny.

The book uses a pyramid to organize findings. At each level, “So what?” asks what follows from the material below, and “Why so?” asks what supports the statement above. Across a level, the familiar MECE principle asks whether the categories overlap and whether they cover what you need to consider. Both checks are easier to do with a few good observations than with a pile of loosely related facts.

When the Problem Is Known

First decide the direction. What changed, whom does it affect and why act now? Then analyze the need by sorting out what is happening and what might explain it. Finally state the task, propose a response and describe what the situation should look like if the response works. A short title that includes the purpose and scope can help keep the proposal from drifting.

At that point, the overall concept needs to give direction to the smaller parts. If a proposed activity does not help the concept become real, the activity needs an explanation or a different place. The book turns this into questions you can ask while revising.

When You Still Need to Test a Hypothesis

For a new undertaking with sparse information, Gil suggests starting with a question and mapping the possible causes or solutions in an issue tree. Branches can be tested through experiments, discussion or analysis. The Korean review looks at Admiral Yi Sun-sin’s naval tactics as an illustration of how a planner might work from evidence toward a decision.

The book also suggests saving ideas with a 5W1H grid: what, how, who, why, when and where. The rows can be markets, customers, products and distribution. Keep the cost and the method in view under how. When logical analysis has left you without a plausible answer, the brainstorming chapter gives you a way to widen the set of options.

Get From the Proposal to the Schedule

A Gantt chart can show when activities start and finish. A PERT chart can make it easier to see which work depends on other work. Either way, dates only help when you know who is doing what and where a delay would change the rest of the project. Gil leaves time in the plan for what might go wrong.

I cannot learn to plan a project by reading one book. I can use this one to work out why the next proposal is hard to finish. Sometimes what is missing is a definition. Sometimes it is a piece of evidence. Sometimes I have been trying to answer the wrong question.