A hands-on guide to doing content analysis

Abstract

There is a growing recognition for the important role played by qualitative research and its usefulness in many fields, including the emergency care context in Africa. Novice qualitative researchers are often daunted by the prospect of qualitative data analysis and thus may experience much difficulty in the data analysis process. Our objective with this manuscript is to provide a practical hands-on example of qualitative content analysis to aid novice qualitative researchers in their task.

African relevance

• •Qualitative research is useful to deepen the understanding of the human experience.
• •Novice qualitative researchers may benefit from this hands-on guide to content analysis.
• •Practical tips and data analysis templates are provided to assist in the analysis process.

Introduction

There is a growing recognition for the important role played by qualitative research and its usefulness in many fields, including emergency care research. An increasing number of health researchers are currently opting to use various qualitative research approaches in exploring and describing complex phenomena, providing textual accounts of individuals’ “life worlds”, and giving voice to vulnerable populations our patients so often represent. Many articles and books are available that describe qualitative research methods and provide overviews of content analysis procedures [1], [2], [3], [4], [5], [6], [7], [8], [9], [10]. Some articles include step-by-step directions intended to clarify content analysis methodology. What we have found in our teaching experience is that these directions are indeed very useful. However, qualitative researchers, especially novice researchers, often struggle to understand what is happening on and between steps, i.e., how the steps are taken.

As research supervisors of postgraduate health professionals, we often meet students who present brilliant ideas for qualitative studies that have potential to fill current gaps in the literature. Typically, the suggested studies aim to explore human experience. Research questions exploring human experience are expediently studied through analysing textual data e.g., collected in individual interviews, focus groups, documents, or documented participant observation. When reflecting on the proposed study aim together with the student, we often suggest content analysis methodology as the best fit for the study and the student, especially the novice researcher. The interview data are collected and the content analysis adventure begins. Students soon realise that data based on human experiences are complex, multifaceted and often carry meaning on multiple levels.

For many novice researchers, analysing qualitative data is found to be unexpectedly challenging and time-consuming. As they soon discover, there is no step-wise analysis process that can be applied to the data like a pattern cutter at a textile factory. They may become extremely annoyed and frustrated during the hands-on enterprise of qualitative content analysis.

The novice researcher may lament, “I’ve read all the methodology but don’t really know how to start and exactly what to do with my data!” They grapple with qualitative research terms and concepts, for example; differences between meaning units, codes, categories and themes, and regarding increasing levels of abstraction from raw data to categories or themes. The content analysis adventure may now seem to be a chaotic undertaking. But, life is messy, complex and utterly fascinating. Experiencing chaos during analysis is normal. Good advice for the qualitative researcher is to be open to the complexity in the data and utilise one’s flow of creativity.

Inspired primarily by descriptions of “conventional content analysis” in Hsieh and Shannon [3], “inductive content analysis” in Elo and Kyngäs [5] and “qualitative content analysis of an interview text” in Graneheim and Lundman [1], we have written this paper to help the novice qualitative researcher navigate the uncertainty in-between the steps of qualitative content analysis. We will provide advice and practical tips, as well as data analysis templates, to attempt to ease frustration and hopefully, inspire readers to discover how this exciting methodology contributes to developing a deeper understanding of human experience and our professional contexts.

Overview of qualitative content analysis

Synopsis of content analysis

A common starting point for qualitative content analysis is often transcribed interview texts. The objective in qualitative content analysis is to systematically transform a large amount of text into a highly organised and concise summary of key results. Analysis of the raw data from verbatim transcribed interviews to form categories or themes is a process of further abstraction of data at each step of the analysis; from the manifest and literal content to latent meanings (Fig. 1 and Table 1).

Fig. 1.

Example of analysis leading to higher levels of abstraction; from manifest to latent content.

Table 1.

Glossary of terms as used in this hands-on guide to doing content analysis.^*

Condensation	Condensation is a process of shortening the text while still preserving the core meaning
Code	A code can be thought of as a label; a name that most exactly describes what this particular condensed meaning unit is about. Usually one or two words long
Category	A category is formed by grouping together those codes that are related to each other through their content or context. In other words, codes are organised into a category when they are describing different aspects, similarities or differences, of the text’s content that belong together
	When analysis has led to a plethora of codes, it can be helpful to first assimilate smaller groups of closely related codes in sub-categories. Sub-categories related to each other through their content can then be grouped into categories
	A category answers questions about who, what, when, or where? In other words, categories are an expression of manifest content, i.e., what is visible and obvious in the data
	Category names are factual and short
Theme	A theme can be seen as expressing an underlying meaning, i.e., latent content, found in two or more categories.
	Themes are expressing data on an interpretative (latent) level. A theme answers questions such as why, how, in what way, or by what means?
	A theme is intended to communicate with the reader on both an intellectual and emotional level. Therefore poetic and metaphoric language is well suited in theme names to express underlying meaning
	Theme names are very descriptive and include verbs, adverbs and adjectives

^*More information found in Refs. [1], [2], [3], [5]

The initial step is to read and re-read the interviews to get a sense of the whole, i.e., to gain a general understanding of what your participants are talking about. At this point you may already start to get ideas of what the main points or ideas are that your participants are expressing. Then one needs to start dividing up the text into smaller parts, namely, into meaning units. One then condenses these meaning units further. While doing this, you need to ensure that the core meaning is still retained. The next step is to label condensed meaning units by formulating codes and then grouping these codes into categories. Depending on the study’s aim and quality of the collected data, one may choose categories as the highest level of abstraction for reporting results or you can go further and create themes [1], [2], [3], [5], [8].

Content analysis as a reflective process

You must mould the clay of the data, tapping into your intuition while maintaining a reflective understanding of how your own previous knowledge is influencing your analysis, i.e., your pre-understanding. In qualitative methodology, it is imperative to vigilantly maintain an awareness of one’s pre-understanding so that this does not influence analysis and/or results. This is the difficult balancing task of keeping a firm grip on one’s assumptions, opinions, and personal beliefs, and not letting them unconsciously steer your analysis process while simultaneously, and knowingly, utilising one’s pre-understanding to facilitate a deeper understanding of the data.

Content analysis, as in all qualitative analysis, is a reflective process. There is no “step 1, 2, 3, done!” linear progression in the analysis. This means that identifying and condensing meaning units, coding, and categorising are not one-time events. It is a continuous process of coding and categorising then returning to the raw data to reflect on your initial analysis. Are you still satisfied with the length of meaning units? Do the condensed meaning units and codes still “fit” with each other? Do the codes still fit into this particular category? Typically, a fair amount of adjusting is needed after the first analysis endeavour. For example: a meaning unit might need to be split into two meaning units in order to capture an additional core meaning; a code modified to more closely match the core meaning of the condensed meaning unit; or a category name tweaked to most accurately describe the included codes. In other words, analysis is a flexible reflective process of working and re-working your data that reveals connections and relationships. Once condensed meaning units are coded it is easier to get a bigger picture and see patterns in your codes and organise codes in categories.

Content analysis exercise

The synopsis above is representative of analysis descriptions in many content analysis articles. Although correct, such method descriptions still do not provide much support for the novice researcher during the actual analysis process. Aspiring to provide guidance and direction to support the novice, a practical example of doing the actual work of content analysis is provided in the following sections. This practical example is based on a transcribed interview excerpt that was part of a study that aimed to explore patients’ experiences of being admitted into the emergency centre (Fig. 2).

Fig. 2.

Excerpt from interview text exploring “Patient’s experience of being admitted into the emergency centre”

This content analysis exercise provides instructions, tips, and advice to support the content analysis novice in a) familiarising oneself with the data and the hermeneutic spiral, b) dividing up the text into meaning units and subsequently condensing these meaning units, c) formulating codes, and d) developing categories and themes.

Familiarising oneself with the data and the hermeneutic spiral

An important initial phase in the data analysis process is to read and re-read the transcribed interview while keeping your aim in focus. Write down your initial impressions. Embrace your intuition. What is the text talking about? What stands out? How did you react while reading the text? What message did the text leave you with? In this analysis phase, you are gaining a sense of the text as a whole.

You may ask why this is important. During analysis, you will be breaking down the whole text into smaller parts. Returning to your notes with your initial impressions will help you see if your “parts” analysis is matching up with your first impressions of the “whole” text. Are your initial impressions visible in your analysis of the parts? Perhaps you need to go back and check for different perspectives. This is what is referred to as the hermeneutic spiral or hermeneutic circle. It is the process of comparing the parts to the whole to determine whether impressions of the whole verify the analysis of the parts in all phases of analysis. Each part should reflect the whole and the whole should be reflected in each part. This concept will become clearer as you start working with your data.

Dividing up the text into meaning units and condensing meaning units

You have now read the interview a number of times. Keeping your research aim and question clearly in focus, divide up the text into meaning units. Located meaning units are then condensed further while keeping the central meaning intact (Table 2). The condensation should be a shortened version of the same text that still conveys the essential message of the meaning unit. Sometimes the meaning unit is already so compact that no further condensation is required. Some content analysis sources warn researchers against short meaning units, claiming that this can lead to fragmentation [1]. However, our personal experience as research supervisors has shown us that a greater problem for the novice is basing analysis on meaning units that are too large and include many meanings which are then lost in the condensation process.

Table 2.

Suggestion for how the exemplar interview text can be divided into meaning units and condensed meaning units (condensations are in parentheses).

Meaning units (Condensations)
– Well, ok, where to start, that was a bad day in my life (It was a bad day in my life)
– And it started so much the same as any other day. Right up until I was in that car crash! (Ordinary day until the crash)
– I still have nightmares about the sound of the other car and the lady screaming (Nightmares about sounds of the crash)
– I can’t get the sound out of my head! (Can’t get the sound out of my head)
– it is a crazy place there. Do you know…do you work there? (Emergency Centre is a crazy place)
– Well the people in the ambulance, when they had me in the ambulance they were looking worried, they kept telling me “there was lots of blood here” (Ambulance staff looked worried about all the blood)
– I really remember that. I thought, “Well there is not much I can do” (Thinking that I couldn’t do anything about it)
– Anyway, they seemed to want to get me into the EC in a real hurry. Then pushed my trolley in fast. (Ambulance staff were in a great hurry to get the trolley into EC)
– I was feeling very cold. I think my legs were shaking. (I feel cold and my legs are shaking)
– I think they had cut off my jeans. It was very uncomfortable, (Jeans cut off and very uncomfortable)
– I wasn’t sure if the blanket covered me. I tried to grab the blanket with my hand. (Tried to grab the blanket to cover me)
– They must have given me something, maybe in that drip thing (Must have been given something in a drip)
– because I remember thinking that I should be in pain…. my legs must be sore… they were jammed in the car …but I really can’t remember feeling it (Thinking I should be in pain but can’t remember feeling legs jammed in the car)
– just remember being cold, shaky (Being cold and shaky)
– feeling very alone (Feeling very alone)
– just saw everything moving past me (Only saw things moving past me)
– I really wished my sister was there. She always seems to know what to do. She doesn’t panic, (I wanted my sister who knows what to do and doesn’t panic)
– But there was no one. (There was no one)
– No one spoke to me. (No one spoke to me)
– I wondered if I was invisible. (Was I invisible)
– They pushed me into a big room and there were lots of people there. It looked so busy, lots of noise, phones ringing, people talking loudly (Placed in a big, busy, noisy room)
– And I remember thinking that my sister wouldn’t know how to find me (Thinking my sister wouldn’t find me)
– I tried to tell the ambulance guy that I needed him to please call my sister (Tried to tell ambulance guy I needed him to call my sister)
– … but I had a thing on my face – for air they said before– so no one heard me, (with this thing on my face no one heard me)
– No one seemed to be looking at my face. (No one looked at my face)
– They pushed me into the middle of the room and then walked away. They just left me (Pushed me to the middle of the room, walked away, left me)
– And I am not sure what everyone was doing (I didn’t know what they were doing)
– They seemed to be rushing around (They were rushing about)
– … but no one spoke to me. (No one spoke to me)
– Suddenly someone grabbed my leg, (Suddenly someone grabbed my leg)
– I got such a fright (I got a fright)
– they didn’t say anything to me… (Saying nothing to me)
– just poked my leg. (They poked my leg)
– I remember screaming. (I screamed)
– I remember that pain! (I remember the pain)

Formulating codes

The next step is to develop codes that are descriptive labels for the condensed meaning units (Table 3). Codes concisely describe the condensed meaning unit and are tools to help researchers reflect on the data in new ways. Codes make it easier to identify connections between meaning units. At this stage of analysis you are still keeping very close to your data with very limited interpretation of content. You may adjust, re-do, re-think, and re-code until you get to the point where you are satisfied that your choices are reasonable. Just as in the initial phase of getting to know your data as a whole, it is also good to write notes during coding on your impressions and reactions to the text.

Table 3.

Suggestions for coding of condensed meaning units.

Meaning units condensations	Codes
It was a bad day in my life	The crash
Ordinary day until the crash	The crash
Nightmares about the sounds of the crash	The crash
Can’t get the sound out of my head	The crash
Emergency Centre is a crazy place	Emergency Centre is crazy
Ambulance staff looked worried about all the blood	In the ambulance
I couldn’t do anything about it	?*
Ambulance staff were in a great hurry to get the trolley into EC	Staff in a hurry
I feel cold and my legs are shaking	Cold and shaky
Jeans cut off and very uncomfortable	Feeling exposed
Tried to grab the blanket to cover me	Feeling exposed
Must have been given something in a drip	In the ambulance
Thinking I should be in pain but can’t remember feeling legs jammed in the car	In the ambulance
Being cold and shaky	Cold and shaky
Feeling very alone	Feeling alone
Only saw things moving past me	Emergency Centre is busy
I wanted my sister who knows what to do and doesn’t panic	Wanting support
There was no one	Feeling alone
No one spoke to me	Not spoken to
Was I invisible	Feeling invisible
A big, busy, noisy room	Emergency Centre is noisy
Thinking my sister wouldn’t find me	?**
Tried to tell ambulance guy I needed him to call my sister	Wanting help
With this thing on my face no one heard me	Not heard
No one looked at my face	Not looked at
Pushed me to the middle of the room, walked away, left me	Left alone
I didn’t know what they were doing	Unsure
They were rushing about	Staff in a hurry
No one spoke to me	Not spoken to
Suddenly someone grabbed my leg	Staff actions
I got a fright	Frightened
Saying nothing to me	Not spoken to
They poked my leg	Staff actions
I screamed	Pain
I remember the pain	Pain

^*Feeling helpless? Resigned, Powerless? “In god’s hands”? What do you think?

^**Worried? Feeling lost? Distraught? What do you think?

Developing categories and themes

The next step is to sort codes into categories that answer the questions who, what, when or where? One does this by comparing codes and appraising them to determine which codes seem to belong together, thereby forming a category. In other words, a category consists of codes that appear to deal with the same issue, i.e., manifest content visible in the data with limited interpretation on the part of the researcher. Category names are most often short and factual sounding.

In data that is rich with latent meaning, analysis can be carried on to create themes. In our practical example, we have continued the process of abstracting data to a higher level, from category to theme level, and developed three themes as well as an overarching theme (Table 4). Themes express underlying meaning, i.e., latent content, and are formed by grouping two or more categories together. Themes are answering questions such as why, how, in what way or by what means? Therefore, theme names include verbs, adverbs and adjectives and are very descriptive or even poetic.

Table 4.

Suggestion for organisation of coded meaning units into categories and themes.

Overarching theme: THE EMERGENCY CENTRE THROUGH PATIENTS’ EYES – ALONE AND COLD IN CHAOS
Theme: Reliving the pre-hospital experience
Condensations	Codes		Categories
It was a bad day in my life	The crash		Reliving the crash
Ordinary day until the crash	The crash
Nightmares about the sounds of the crash	The crash
Can’t get the sound out of my head	The crash
Ambulance staff looked worried about all the blood	In the ambulance		Reliving the rescue
Must have been given something in a drip	In the ambulance
Thinking I should be in pain but can’t remember feeling legs jammed in the car	In the ambulance
Theme: Not a person, just a body in the hectic EC
Condensations		Codes		Categories
EC is a crazy place		Emergency Centre is crazy		Emergency Centre is a crazy, noisy, environment
Only saw things moving past me		Emergency Centre is busy
A big, busy noisy room		Emergency Centre is noisy
Ambulance staff were in a great hurry to get the trolley into EC		Staff in a hurry		Staff actions and non-actions
They were rushing about		Staff in a hurry
Pushed me to the middle of the room, walked away, left me		Left alone
No one spoke to me		Not spoken to
No one spoke to me		Not spoken to
Saying nothing to me		Not spoken to
Suddenly someone grabbed my leg		Staff actions
They poked my leg		Staff actions
No one looked at my face		Not looked at
With this thing on my face no one heard me		Not heard
I wanted my sister who knows what to do and doesn’t panic		Wanting support		Unmet needs
Tried to tell ambulance guy I needed him to call my sister		Wanting help
Theme: Invisible and alone inside the pain of a broken body
Condensations		Codes		Categories
I feel cold and my legs are shaking		Cold and shaky		Physical responses
Being cold and shaky		Cold and shaky
I remember the pain		Pain
I screamed		Pain
I couldn’t do anything about it		Feeling helpless		Emotional responses
Pants cut off and very uncomfortable		Feeling exposed
Tried to grab the blanket to cover me		Feeling exposed
Was I invisible		Feeling invisible
There was no one,		Feeling alone
Feeling very alone		Feeling alone
I didn’t know what they were doing		Unsure
Thinking my sister wouldn’t find me		Feeling lost
I got a fright		Frightened

Some reflections and helpful tips

Understand your pre-understandings

While conducting qualitative research, it is paramount that the researcher maintains a vigilance of non-bias during analysis. In other words, did you remain aware of your pre-understandings, i.e., your own personal assumptions, professional background, and previous experiences and knowledge? For example, did you zero in on particular aspects of the interview on account of your profession (as an emergency doctor, emergency nurse, pre-hospital professional, etc.)? Did you assume the patient’s gender? Did your assumptions affect your analysis? How about aspects of culpability; did you assume that this patient was at fault or that this patient was a victim in the crash? Did this affect how you analysed the text?

Staying aware of one’s pre-understandings is exactly as difficult as it sounds. But, it is possible and it is requisite. Focus on putting yourself and your pre-understandings in a holding pattern while you approach your data with an openness and expectation of finding new perspectives. That is the key: expect the new and be prepared to be surprised. If something in your data feels unusual, is different from what you know, atypical, or even odd – don’t by-pass it as “wrong”. Your reactions and intuitive responses are letting you know that here is something to pay extra attention to, besides the more comfortable condensing and coding of more easily recognisable meaning units.

Use your intuition

Intuition is a great asset in qualitative analysis and not to be dismissed as “unscientific”. Intuition results from tacit knowledge. Just as tacit knowledge is a hallmark of great clinicians [11], [12]; it is also an invaluable tool in analysis work [13]. Literally, take note of your gut reactions and intuitive guidance and remember to write these down! These notes often form a framework of possible avenues for further analysis and are especially helpful as you lift the analysis to higher levels of abstraction; from meaning units to condensed meaning units, to codes, to categories and then to the highest level of abstraction in content analysis, themes.

Aspects of coding and categorising hard to place data

All too often, the novice gets overwhelmed by interview material that deals with the general subject matter of the interview, but doesn’t seem to answer the research question. Don’t be too quick to consider such text as off topic or dross [6]. There is often data that, although not seeming to match the study aim precisely, is still important for illuminating the problem area. This can be seen in our practical example about exploring patients’ experiences of being admitted into the emergency centre. Initially the participant is describing the accident itself. While not directly answering the research question, the description is important for understanding the context of the experience of being admitted into the emergency centre. It is very common that participants will “begin at the beginning” and prologue their narratives in order to create a context that sets the scene. This type of contextual data is vital for gaining a deepened understanding of participants’ experiences.

In our practical example, the participant begins by describing the crash and the rescue, i.e., experiences leading up to and prior to admission to the emergency centre. That is why we have chosen in our analysis to code the condensed meaning unit “Ambulance staff looked worried about all the blood” as “In the ambulance” and place it in the category “Reliving the rescue”. We did not choose to include this meaning unit in the categories specifically about admission to the emergency centre itself. Do you agree with our coding choice? Would you have chosen differently?

Another common problem for the novice is deciding how to code condensed meaning units when the unit can be labelled in several different ways. At this point researchers usually groan and wish they had thought to ask one of those classic follow-up questions like “Can you tell me a little bit more about that?” We have examples of two such coding conundrums in the exemplar, as can be seen in Table 3 (codes we conferred on) and Table 4 (codes we reached consensus on). Do you agree with our choices or would you have chosen different codes? Our best advice is to go back to your impressions of the whole and lean into your intuition when choosing codes that are most reasonable and best fit your data.

A typical problem area during categorisation, especially for the novice researcher, is overlap between content in more than one initial category, i.e., codes included in one category also seem to be a fit for another category. Overlap between initial categories is very likely an indication that the jump from code to category was too big, a problem not uncommon when the data is voluminous and/or very complex. In such cases, it can be helpful to first sort codes into narrower categories, so-called subcategories. Subcategories can then be reviewed for possibilities of further aggregation into categories. In the case of a problematic coding, it is advantageous to return to the meaning unit and check if the meaning unit itself fits the category or if you need to reconsider your preliminary coding.

It is not uncommon to be faced by thorny problems such as these during coding and categorisation. Here we would like to reiterate how valuable it is to have fellow researchers with whom you can discuss and reflect together with, in order to reach consensus on the best way forward in your data analysis. It is really advantageous to compare your analysis with meaning units, condensations, coding and categorisations done by another researcher on the same text. Have you identified the same meaning units? Do you agree on coding? See similar patterns in the data? Concur on categories? Sometimes referred to as “researcher triangulation,” this is actually a key element in qualitative analysis and an important component when striving to ensure trustworthiness in your study [14]. Qualitative research is about seeking out variations and not controlling variables, as in quantitative research. Collaborating with others during analysis lets you tap into multiple perspectives and often makes it easier to see variations in the data, thereby enhancing the quality of your results as well as contributing to the rigor of your study. It is important to note that it is not necessary to force consensus in the findings but one can embrace these variations in interpretation and use that to capture the richness in the data.

Yet there are times when neither openness, pre-understanding, intuition, nor researcher triangulation does the job; for example, when analysing an interview and one is simply confused on how to code certain meaning units. At such times, there are a variety of options. A good starting place is to re-read all the interviews through the lens of this specific issue and actively search for other similar types of meaning units you might have missed. Another way to handle this is to conduct further interviews with specific queries that hopefully shed light on the issue. A third option is to have a follow-up interview with the same person and ask them to explain.

Additional tips

It is important to remember that in a typical project there are several interviews to analyse. Codes found in a single interview serve as a starting point as you then work through the remaining interviews coding all material. Form your categories and themes when all project interviews have been coded.

When submitting an article with your study results, it is a good idea to create a table or figure providing a few key examples of how you progressed from the raw data of meaning units, to condensed meaning units, coding, categorisation, and, if included, themes. Providing such a table or figure supports the rigor of your study [1] and is an element greatly appreciated by reviewers and research consumers.

During the analysis process, it can be advantageous to write down your research aim and questions on a sheet of paper that you keep nearby as you work. Frequently referring to your aim can help you keep focused and on track during analysis. Many find it helpful to colour code their transcriptions and write notes in the margins.

Having access to qualitative analysis software can be greatly helpful in organising and retrieving analysed data. Just remember, a computer does not analyse the data. As Jennings [15] has stated, “… it is ‘peopleware,’ not software, that analyses.” A major drawback is that qualitative analysis software can be prohibitively expensive. One way forward is to use table templates such as we have used in this article. (Three analysis templates, Templates A, B, and C, are provided as supplementary online material). Additionally, the “find” function in word processing programmes such as Microsoft Word (Redmond, WA USA) facilitates locating key words, e.g., in transcribed interviews, meaning units, and codes.

Lessons learnt/key points

From our experience with content analysis we have learnt a number of important lessons that may be useful for the novice researcher. They are:

• •A method description is a guideline supporting analysis and trustworthiness. Don’t get caught up too rigidly following steps. Reflexivity and flexibility are just as important. Remember that a method description is a tool helping you in the process of making sense of your data by reducing a large amount of text to distil key results.
• •It is important to maintain a vigilant awareness of one’s own pre-understandings in order to avoid bias during analysis and in results.
• •Use and trust your own intuition during the analysis process.
• •If possible, discuss and reflect together with other researchers who have analysed the same data. Be open and receptive to new perspectives.
• •Understand that it is going to take time. Even if you are quite experienced, each set of data is different and all require time to analyse. Don’t expect to have all the data analysis done over a weekend. It may take weeks. You need time to think, reflect and then review your analysis.
• •Keep reminding yourself how excited you have felt about this area of research and how interesting it is. Embrace it with enthusiasm!
• •Let it be chaotic – have faith that some sense will start to surface. Don’t be afraid and think you will never get to the end – you will… eventually!