Problem Solving IV — Problem Management
Problem management and implementation
To round out our series we take a look at some of the different techniques to make sure your problem solutions are actually implemented and not left as a recommendation in an email or memo — a game changing solution that fails to live up to its potential.
So how to choose the project management technique to use? If you have a known problem with a know solution, the tried and tested waterfall /gantt technique will do well. For a know problem with an unknown solution you want to apply a more iterative style such as Agile / Scrum, kanban or a design sprint. Finally if you have an unknown problem with and unknown solution then you need very iterative approach such as rapid learning cycles, design thinking or lean startup. The figure below highlights how some of these different style interact at different phases of problem solution. Also a good summary of the methodologies here
Applying the wrong project management style will see you waste significant time and effort on paperwork and planning that is meaningless. Laying out a 12 month gantt chart for a project where you can’t even outline the problem statement clearly is a poor use of your time!
Also worth mentioning the approach we all default to — the “Ad Hoc” project management style. When following this you don’t really make any plans and just wing it as you go. On many simple problems this works just fine — no point going to more effort than you need to!
For some light relief to close have a look at the 7 habits of highly defective projects.
# Reference — Geert Cl aes— When, which … Design Thinking, Lean, Design Sprint, Agile?
