The theory chapter forms the conceptual backbone of an academic thesis. It defines key concepts, introduces relevant models and theories, and develops a line of argument from which the research question and, where applicable, hypotheses follow logically. In Information Systems, the theory chapter plays a particularly important role because this field typically integrates technical, organizational, and individual perspectives.
1. Purpose of the Theory Chapter in Information Systems
The theory chapter explains the conceptual and theoretical frame of reference within which the study is situated. It clarifies which concepts are used, how they relate to one another, and which theoretical assumptions and empirical findings the study builds on. In this sense, the theory chapter is explicitly more than a list of citations and clearly distinct from a mere “literature collection.”
For readers, the theory chapter makes visible which perspective the thesis adopts on its subject. In Information Systems, this may, for example, be a user‑oriented perspective (e. g., system acceptance), an organizational perspective (e. g., digital transformation processes), or a process‑ or technology‑oriented perspective (e. g., system architectures, data flows). The theory chapter thus lays out the intellectual foundations on which empirical analyses or design‑oriented artefacts build (see also Research Methods).
2. Literature Review vs. Theory Chapter
In practice, there is often little distinction between a general literature review and a deliberately constructed theory chapter. A literature review primarily serves to provide a structured summary of the existing state of research: Which studies exist, when were they conducted, which methods were used, and what were the main findings (see also the guidance on Literature Research)?
A theory chapter goes beyond this. It typically:
- identifies and defines the core concepts,
- embeds these concepts in one or more theoretical frameworks, and
- translates them into a coherent line of argument that leads toward the research question.
In empirical theses, literature review and theory chapter are often combined in a single chapter. In such cases, it is helpful to make it clear within the chapter when you are mainly reporting the state of the art and when you are actively developing the theoretical framing and argumentation based on that literature. The goal is not only to know the existing work, but to understand which model or combination of concepts underpins your own study.
3. Clarifying key concepts and constructs
A major task of the theory chapter is to clarify the central concepts and theoretical constructs. In Information Systems, these often include notions such as usage intention, system quality, user satisfaction, digital transformation, acceptance, trust, transparency, or data quality. Depending on the topic, additional domain‑specific concepts may come into play, for example in e‑government, health IT, or Industry 4.0.
When working with concepts, several aspects are particularly important:
- Relevant definitions from the academic literature should be identified systematically.
- It must be decided which definition is most appropriate for the specific object of study, or how different definitions can be meaningfully combined.
- Where concepts overlap, clear distinctions are needed to avoid ambiguity.
Definitions should not simply be quoted; they should be briefly interpreted and justified. Why is a particular definition suitable for your research object, and how does it support answering the research question? This interpretive step prevents the theory chapter from degenerating into a mere string of definitions. See also the notes on Research Question and Research Gap in Information Systems.
4. Typical Ways of Structuring a Theory Chapter
Theory chapters in Information Systems can be structured in different ways. Common patterns include:
Structure by constructs
The chapter is organized around the central theoretical constructs (e. g., “system quality,” “information quality,” “service quality,” “usage behavior”). For each construct, you present definitions, key relationships, and selected empirical findings.
Structure by theoretical perspectives or models
The focus here is on the core theories underpinning the thesis, such as the Technology Acceptance Model (TAM), UTAUT, the DeLone and McLean IS Success Model, or theories of organizational change. You explain how these theories shape the way you look at the phenomenon and which assumptions they imply.
Structure by thematic blocks
In this variant, the structure follows subtopics within the domain (e. g., “digital platforms and business models,” “governance of digital infrastructures,” “end‑user usage behavior”). Within each block, concepts, models, and empirical findings are combined and related to each other.
The choice of structure depends on the topic and the research question. The crucial point is that the structure is transparent for readers and clearly oriented toward the research question. Section headings should already signal how the argument unfolds step by step.
5. Building a Line of Argument
The theory chapter is not only about presenting existing knowledge. Its main task is to build a coherent line of argument. By the end of the chapter, it should be clear why certain concepts and relationships are at the core of the study.
A possible approach includes:
- starting with fundamental concepts and the overarching theoretical lens,
- highlighting the factors that previous studies have identified as relevant,
- identifying ambiguities, contradictions, or open questions in the literature,
- deriving the specific relationships or mechanisms that the thesis will examine in more detail.
In quantitative studies, this line of argument often culminates in the formulation of hypotheses or propositions. In qualitative or design‑oriented work, it serves to theoretically justify the analytic focus and the selection of concepts for data collection and analysis.
6. Hypotheses and conceptual models
In hypothesis‑driven studies, the theory chapter provides the basis for deriving hypotheses. Drawing on existing theories and empirical findings, you develop a conceptual model in which the relationships between the key constructs are made explicit.
Typical steps include:
- identifying the main independent variables (influencing factors) and dependent variables (outcomes),
- discussing how these variables are related according to the literature,
- formulating hypotheses that specify these relationships for your study,
- visualizing the relationships in a simple conceptual model (e. g., a path diagram with constructs and directional links).
In Information Systems, such models frequently build on established approaches, such as TAM or UTAUT in acceptance studies or the IS Success Model for evaluating information systems. It should be transparent where existing models are adopted, adapted, or extended. A more detailed discussion of typical methodological settings used to test these models can be found under Research Methods.
7. Dealing with Contradictory Studies
In many research areas, you will find studies that report divergent or even contradictory results. A reflective theory chapter does not ignore these differences; instead, it addresses them explicitly.
A constructive way of handling contradictions includes:
- presenting conflicting findings on a given relationship side by side,
- discussing possible reasons for discrepancies (e. g., different contexts, samples, measurement instruments, or theoretical lenses),
- formulating open questions that arise from these inconsistencies.
These considerations feed directly into the research gap. If it is unclear under which conditions certain relationships hold, your thesis can position itself precisely in this space (see also Research Question and Research Gap in Information Systems).
8. Common Pitfalls in Theory Chapters
In practice, several recurring problems can be observed in theory chapters:
- The text remains at the level of article‑by‑article summaries, without developing an own structure or evaluation.
- Key concepts are used inconsistently or not clearly distinguished from one another.
- The link to the research question remains vague; it is unclear why some concepts are discussed in depth while others are ignored.
- Hypotheses appear at the end of the chapter without a clearly traceable derivation from the preceding theory.
- Central parts of the theory chapter are later repeated in the results or discussion chapters in almost the same form.
Such issues can be reduced if, during the writing process, you consistently check whether each section contributes visibly to the overarching research question and whether the line from literature to your own study remains clear.
9. Short Checklist for Your Theory Chapter
The following checklist can support the final review of the theory chapter:
- Are all central concepts and constructs defined and clearly distinguished from each other?
- Is it clear which theoretical models or perspectives the thesis relies on?
- Is it transparent why certain concepts are in focus and others deliberately left aside?
- Does the text build a line of argument that leads to the research question and, where applicable, to hypotheses?
- Are contradictory findings from the literature acknowledged and reflected?
- Can a simple conceptual model be derived from the theory chapter that structures the study?
If you can answer most of these questions in the affirmative, this is a strong indication that your theory chapter is conceptually sound and provides a solid foundation for the methodological implementation and subsequent analysis.
As a next step, it is advisable to align the theoretical framework with the chosen research methods and to ensure that the research question, theory chapter, and methodology are consistent with one another (see Research Methods and the guidance under Theses - Outline).