Pages in this section:
All sections:
Most people will probably skip this page, but if you are interested in learning about the basic ideas of causal mapping without using our app at all, but just using a spreadsheet program, read on!
You will learn:
Now we are going to back to the basics of causal mapping. You don’t need Causal Map App, or any other dedicated application, to do causal mapping. You can use Excel or any spreadsheet program.
Causal maps store information about links of causal influence between two or more factors alongside the evidence for each link. We call the chunks of text, for example from interview transcripts, which potentially contain claims about causal connections, “statements”.
Here is an example Excel file, it contains example statements from our standard example file. You can use it to practice manual causal mapping.
There are several tabs, but the only ones you need to change are links and codebook.
The links tab already contains a couple of example links, otherwise known as an edge-list, the starting point for any causal map. The factors in the from_label column affect the factors in the to_label column. For example, the from_label column contains influence factors such as Improved/increased crops which influence the consequence factor in the next column, like Increased income. It is these links that could then displayed in a causal map.
You will notice, in this example, that the columns in the links tab are dropdown lists when you click on the triangles in each cell. These dropdown lists are fed from the labels listed in the codebook tab. So you can change the options available by editing or adding labels in the factors tab. But you can also add new labels simply by typing in the cell.
So to actually do your causal mapping, you need to make sure that the statement_id and statement_text columns in every row in the links tab correspond to a statement_id and text from the statements tab. You might want to start out by copying all of the rows (but just the first two columns) from the statements tab into vacant rows in the links tab. Don’t actually edit anything in the statements tab (or the sources or questions tabs).

The first two columns of the statements tab.
Then,
statement_text column.quote column.from_factor and to_factor labels to show what causal factor did the influencing and what causal factor was influenced. If you want you can use hierarchical and opposites coding just like in the Causal Map app.As you can create several links for one statement, the same statement_id and statement_text can be repeated several times, usually with different quote, from_label and to_label. It doesn’t matter if you have rows in the links table which don’t have any entries in the quote, from_label or to_label columns; they will be ignored when you upload your data to Causal Map.
If you want to create an extra link from an existing statement,

one easy way is to simply copy the row, then right-click on the left-hand border of the Excel sheet around the row where you want to add a new row, and press “insert copied cells”. Remember to change the quote, from_label and to_label for your new link.
You can download the example file play around with it or use it as a template for your own map.
When you’ve done some coding, you can upload the file to Causal Map to visualise it.

The app will also import the additional data from the sources and questions tab so you can do simple and sophisticated visualisations and analyses and apply special filters.
If you later do some more coding in the same Excel file and want to upload the more complete data set, just remember to press Overwrite not Append when you upload.
Also once in excel format, your data becomes compatible with other data visualisation tools like Gephi. If you want to know more about that check out the video below on using the causal map app alongside other data visualisation tools.
Causal mapping using Excel is pretty simple but of course it isn’t as convenient as in a dedicated app.
from_label column, it won’t be suggested as a label in the to_label column, and vice versa. After you’ve done a bit of coding, you’ll probably want to look through the labels you’ve created in these two columns, tidy them up a bit, and add any new labels to the codebook tab so that they will be provided as suggestions as you continue to code.