From Reactive Planning Model to Natural Planning Model

Natural Planning Model

Reactive Planning Model


## Notes

- *It's a situation where a group of people meets to think about a problem and try to have as many ideas as possible.*

  - They should be able to think about as many spontaneous ideas as possible.

- Brainstorming keys:

  - **Go for quantity, not quality**: keep the thinking expansive. The group should have as many ideas as possible, not worrying about the quality. Sometimes you'll realize what's a good idea only later on.

  - **Don't judge, challenge, evaluate, or criticize**: this rule keeps the creative process of generating and extending new ideas. By keeping this rule, the participants will feel free to generate unusual ideas. Wild ideas should be encouraged.

  - **Put analysis and organization in the background**: these activities should not be the driver of the brainstorming. Worrying about structuring the ideas may block the creative process. Just make sure to grab all and keep going until you get as many ideas as the group want.

- It's important that brainstorming is part of the overall context of the planning process.
  - It should not be seen as a single activity and the group is just doing it for its own sake. If this happens, it can seem trite.

## References

- [Wikipedia. Brainstorming](https://en.wikipedia.org/wiki/Brainstorming)

- [David Allen. Getting Things Done](/books/getting-things-done)

## Backlinks
- [From Reactive Planning Model to Natural Planning Model](/articles/from-reactive-planning-model-to-natural-planning-model)
- [Natural Planning Model](/zettelkasten/natural-planning-model)
- [Reactive Planning Model](/zettelkasten/reactive-planning-model)

Brainstorming


## Notes

- Method to solve problems without discussion.
  - Replace all open and unstructured discussions with a clear solving problem process.
- Methods like brainstorm have discussions in which may cause a problem like:
  - Discussions that losing focus and don't solve the problem.
  - Very long talks that left the team very fatigued.
  - The one with the higher voice may impose his/her ideas.
  - People may sabotage each other to promote his/her "good" idea.
- Supplies (the colors can be changed):
  - Rectangular post-its (yellow).
  - 2 two different color post-its (blue and pink).
  - Voting dots, two different colors (red and green).
  - Sharpies.
  - A timer that clearly shows the remaining time.
- Choose a moderator.
  - He/she can join in on the process but must focus on making sure no discussions break out.
  - Has to keep time.
- The method:

  1. Write the problems.
     - No discussion.
     - 7 minutes.
     - Everybody writes all the challenges, annoyances, mistakes, problems without discussion. Can be anything.
     - Write in blue squared post-its.
  2. Present the problems.
     - The moderator selects one person to present each of his/her problems and stick them to the surface.
     - Nobody else in the team is allowed to speak.
     - Each person has 4 minutes.
  3. Select problems to solve.
     - 6 minutes.
     - The moderator gives two voting red dots to each member of the team.
     - They can vote on their posts.
     - They can put two votes on the same post.
     - After voting, the moderator arranges the posts in order of priority.
  4. Reframe/rewrite the problems as standardized challenges.
     - 6 minutes.
     - Reformat problems to standardized "How might we...".
     - Focus only on the prioritized problems (most voted).
     - Rewrite in a way that makes the problem solvable and standardized.
       - For instance, instead of "I have no idea what's going on project X", rewrite as "How might we make sure everyone stays in the loop with all running projects".
  5. Produce solutions.
     - The top-left-most voted problem is chosen.
       - If there are two most voted problem just pick the most left one.
     - Each team member has 7 minutes to produce as many solutions as possible on pink squared posts-its.
     - No discussions.
     - **Aim quantity over quality.**
     - Stick the pink squared post-its on the surface.
  6. Vote on solutions.
     - 10 minutes.
     - The moderator gives six green voting dots to each team member.
     - Each member votes on the solutions they think would best solve the problem.
  7. Prioritize solutions
     - 30 seconds.
     - The team arrange the solutions list.
     - Ignore the solutions with less than two votes.
  8. Decide what to execute on.
     - 10 minutes.
     - Put the solutions in a graphic Impact x Effort.
     - Choose the solution with higher impact and less effort, even if it isn't the most voted one.
  9. Turn solutions into actionable tasks.
     - 5 minutes.
     - The moderator takes the selected solution of the previous step.
     - Each member writes actionable solutions on the rectangular yellow post-its.
       - Actionable means something that can be executed in a time frame (1 or 2 weeks).
  10. Execute the actionable tasks.

- What about that great idea that was not selected?
  - **Here good ideas don't matter, executing and testing is what matters.**

## References

- [Lightning Decision Jam — Solve Problems Without Discussion](https://medium.muz.li/a-super-simple-exercise-for-solving-almost-any-product-design-challenge-f9e6c0019d7d)


#problem-solving

Brainstorming

Lightning Decision Jam