1.5: A guide for the reader

This book has an extremely simple structure. There are five chapters — an introduction (this chapter), a short concluding chapter (chapter 5) and three very long chapters in the middle. In chapter 2 we start with a rather simple explanation of the capability approach, and then present a more detailed account of capability theories, focusing in particular on their structure and properties. I will present the capability approach by describing it as having a modular structure — whereby each specific capability theory combines the core elements of the non-optional module with a range of non-core modules. This way of looking at the capability approach helps those who want to apply the capability approach to a particular question or problem to see clearly which elements are needed for such an application; it also makes it very clear that the capability approach can be specified in diverse ways. One could see chapter 2 as trying to provide the anatomy of the capability approach — to try to see behind its skin, to detect what its various organs are, how they interact and which ones are essential, whereas others may be more tangential.

In chapter 3 we discuss further details and try to clear up some misunderstandings. The capability approach is a field that is notoriously prone to misunderstandings, in part because of its interdisciplinary nature, but also because the terminology differs somewhat between different authors. Chapter 3 tries to present the literature as neutrally as possible and describes how it has been evolving.

Chapter 4 then zooms in on a range of critiques that have been made of the capability approach, such as the argument that it is too individualistic, or that it cannot properly account for power. In this chapter, my own voice will be more prominent, as I will engage with these claims, agreeing with some of them (and, as philosophers do, giving reasons why I agree), but also arguing against some other critiques. Here, it will become clear what the value is of the distinction between the general capability approach and more specific capability theories, which I introduced elsewhere (Robeyns 2016b) and explain again in section 2.3. As it turns out, some of the critiques are valid against particular capability theories, but make no sense against the capability approach in general. I hope that the adoption of this distinction between capability theories or applications on the one hand, and capability approach on the other, will clear the capability literature of many confusing and unnecessary criticisms, so that we can devote our energy to those that are powerful and with which we need to engage. Moreover, let us not forget that the capability approach is a tool and not an end in itself; we should master it as well as we can, perhaps also as efficiently as we can, and then move on to use it in the work that really matters.