Mapping the logic of an argument helps you simplify complicated logic links and dependencies and spot unexpected gaps. It is useful at any stage of a project.
Use this to...
- Identify faulty logic.
- Spot logic leaps, gaps, or missing links.
- Root out incorrect dependencies.
- Safely challenge emotional arguments.
And finally! Logic Mapping works at any time during a sprint, but try it right before making a final decision – it can help you spot links between your evidence, assumptions and conclusions.
Watch out for...
Assume nothing! Your argument is only as strong as your assumptions, so why not do a Key Assumptions Check first and really put your logic through its paces?
- As a group listen to the different perspectives and study the data that supports them. Leverage the diversity of the group.
- Write down the main points of logic that underpin your argument against the discovery theme. Each one should include:
- A key argument
- A deduction
- A conclusion
- Group together similar themes and noticing any linking arguments or dependencies. Challenge each other during this process.
- Give each cluster a name. Are there are any imposters that shouldn’t be there?
- Draw two diagrams: one with the key points of the argument and the other for critical logic and issues. Iterate though as a group. This should be a slow methodical process.
- If your logic is flawed, discuss what must be done to correct it. What extra data do you need to fill gaps?