Video Tutorial: Using memos at project begin.
"Memos and diagrams are more than just repositories of thoughts. They are working and living documents. When an analyst sits down to write a memo or do a diagram, a certain degree of analysis occurs. The very act of writing memos and doing diagrams forces the analyst to think about the data. And it is in thinking that analysis occurs" (Corbin & Strauss: 118).
"Writing is thinking. It is natural to believe that you need to be clear in your mind what you are trying to express first before you can write it down. However, most of the time, the opposite is true. You may think you have a clear idea, but it is only when you write it down that you can be certain that you do (or sadly, sometimes, that you do not)" (Gibbs, 2005).
As you see from the above quotes, memos is an important task in every phase of the qualitative analysis process. Much of the analysis 'happens' when you write down your findings, not by clicking buttons in the software.
The ideas captured in memos are often the pieces of a puzzle that are later put together in the phase of report writing.
Theory-building, often associated with building networks, also involves writing memos.
Memos in ATLAS.ti can be just a text on its own, or can be linked to other entities like quotations, codes, or other memos.
Memos can contain a project description
You can list all research questions in a memo.
You can use memos to write a research diary.
You can use one memo as to do list.
Memos can be used as a bulletin board to exchange information between team members.
You can store definitions, findings or theories from relevant literature in one or more memos.
You can write up your analysis using memos. Those memos will be the building blocks for your research report.
Memos can also be assigned as documents, if you want to code them. See Using Memos as Document .
From a methodological point of view comments are also memos in the sense that comments are also places for thinking and writing.
In technical terms, in ATLAS.ti there is a distinction between comments and memos, as comments exclusively belong to one entity. For example, the document comment is part of the document; a code comment belongs to a particular code and is usually a definition for this code. A quotation comment contains notes or interpretations about the quotation it belongs to.
Comments are not displayed in browsers separately from the entity to which they are attached.
ATLAS.ti memos in comparison
- can be freestanding, or they can be linked to other entities.
- You can write a comment for a memo, for example: use this memo for section 2 in chapter 4 in my thesis.
Below some ideas are listed for what you can use comments:
- project description
- Meta information about a document: source, where and how you found or generated it
- Interview protocols
Information about a respondent like gender, age, profession etc., are best handled by document groups. There is no need to write this type of information into the comment field.
- interpretations that only concern a specific data segment
- ideas how a quotation might be related to another quotation
- summaries for what you hear or see in the multimedia quotation
- interpretations of image quotations
- notes on a geo position
- first ideas what you mean by a code
- a code definition
- a coding rule, especially when working in a team
- an example of what kind of data can be coded with this code
- summary of coded segments
- note to yourself where you want to use the memo in a report
- comments from supervisors or team members
- links to or notes about relevant literature
- description of the network
- idea how you want to develop it further
- Explaining why the two entities are linked in a specific way.
Code names are (or should be) succinct, dense descriptors for concepts emerging during the stage of closely studying the data. They often reduce complex findings to crisp placeholders and/or theoretically relevant concepts.
Beginners often stuff lengthy treatises into a code name, blurring the distinction between codes, comments, and memos and thereby mistaking codes for their more appropriate siblings.
If you find yourself using more than a few words as a code label, consider making use of the quotation name or comment. See Working with Quotations, or write more extensive thoughts about a code as code comment.
Like codes, memos have names. These names, or titles, are used for displaying memos in browsers, and help to find specific memos.
Just like code names, a memo's title should be short and concise. Don't confuse the name with its content! The purpose is to fill the memo with content, which is a longer text that goes beyond just describing the memo title. If all what you want to write in the memo fits into the title, use a quotation comment instead.
Corbin, Juliet and Strauss, Anselm (2008). Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory (3rd and 4th ed.). Thousand Oaks, CA: Sage.
Gibbs, Graham (2005). Writing as analysis. Online QDA.