A straw man is a rough prototype.
If you build something out of straw what do you expect to happen to it in the long run? You expect it to collapse or be blown away! A straw man proposal similarly lacks solid foundation, and it too may be blown away under scrutiny. So is a straw man proposal to be avoided?
Not necessarily. A "straw man" can be very useful, as long as people know that what stands before them is indeed a straw man. When you begin a project or start looking into a problem, you often have incomplete information to work with. So you can spend time gathering facts and data until you are ready to build a really strong argument or plan, or, you can get going straight away and jump in with a not-so-complete solution, with the intention of finding a much better one, as you learn more and more.
That's the premise behind building a straw man – creating a first draft for criticism and testing, and then using the feedback you receive to develop a final outcome that is rock solid.
Suppose your revenue is falling and you have to come up with a better sales strategy. Using the straw man idea you might do the following:
In a culture that values being right, the notion of constructing a straw man is difficult to embrace. Why spend time drafting something that, ultimately, isn't going to be used? If you can get past this perception you will be surprised at how useful the technique can be. One of its main advantages is that it forces you to do something. Taking too long to deliberate the merits of an idea or hypothesis can be costly, as you risk never making a decision at all. With a straw man, you force an early, if incomplete, decision. This ensures that a final decision will be reached because doing nothing means accepting a poor plan by default.
Be very careful when you're using a Straw Man approach that people understand what you're doing: The last thing you want is to develop a reputation for "coming up with half-baked ideas." Make sure that your document is clearly labeled as such, and that the people receive it understand what it is.
A straw man is also useful in ensuring that everyone involved has a tangible concept to work from. Otherwise, there is a risk that people are working with different pieces of the whole, different perceptions, and different, unstated assumptions, as they continue to research and discuss aspects of the idea or solution.
The risk of using a straw man proposal is that, by definition, you are jumping to conclusions. Providing you are aware of this risk, you'll challenge, test, and retest the real solution and so use "jumping to a conclusion" as a vehicle to find a better conclusion.
A good technique for checking your solution and assumptions is the Ladder of Inference. Use it to make sure that your final assumptions are valid, rather than "straw man" assumptions that won't stand up to the reality of your working solution.
Impact Analysis is another great approach for determining where the straw man fails to deliver. By looking at the consequences of the proposed action, you are able to see the weak points and create a better plan.
A straw man is a prototype solution to a problem, built on incomplete information and on ideas that have not been fully thought through. Even in this rough state, though, it helps ensure everyone involved has a common understanding of the initial concept.
The point of building the straw man is to knock it down and rebuild something much better. How you do that will depend on circumstances, and on the resources available to you. It is a good place to start, and it is often the push you need to get past decision-making paralysis, which plagues many projects, problems and decisions. By putting together a straw man, you take action and gain momentum to get moving towards a winning solution.
With the Mind Tools Club, you get much, much more than you do here for free.
And we'll give you the 4 workbooks above when you join!
Learn on the move with the free Mind Tools iPhone, iPad and Android Apps. Short bursts of business training ideal for busy people.