5. Transdisciplinary Interpretivism & Constructivism

Two paradigms that meet on the question of meaning

Where positivism and post-positivism aim at a reality "out there," interpretivism and constructivism shift the focus to meaning and how meaning is made.

• Interpretivism holds that human action is meaningful action — it can't be understood without understanding how the actor frames the situation. The researcher's task is to interpret the meanings actors bring, in their context.
• Constructivism goes further: knowledge is co-constructed in the research encounter. The researcher's subjectivity isn't a contamination of the data; it is constitutive of what the data even is.

The distinction is subtle but real. An interpretivist study tries to render lived meaning faithfully; the researcher is a careful observer of meaning that's "there." A constructivist study acknowledges that the meaning surfaced through interview, focus group, or ethnography is jointly produced by participant and researcher. Both are legitimate; they have different methodological implications.

Why this matters for transdisciplinary work

Wicked problems involve contested meanings. Vaccine hesitancy, for example, isn't only a behavior; it's a stance built from layered meanings — about authority, family, community, identity. A study that only measures hesitancy as a yes/no item produces a thin description. Interpretive and constructivist work supplies the depth.

The transdisciplinary move is to combine paradigms intentionally. A study might use post-positivist methods to estimate hesitancy prevalence and interpretivist methods to understand its meaning. The point is not to pick one paradigm; it is to know which paradigm is operating where, and to defend the choice.

Building a conceptual framework

A conceptual framework is a visual or written representation of the constructs you're working with and the relationships among them. It is not a literature review; it is a commitment about how you see the problem.

A useful transdisciplinary framework:

• Spans at least two disciplines' concepts
• Marks relationships explicitly with arrows or links
• Names where disciplines disagree about how a relationship works
• Includes at least one non-academic concept (community-named construct, lived-experience category)
• Is iterative — drawn, then redrawn as the project learns

The most common failure mode is a framework that's drawn once and frozen. A framework you don't update isn't an instrument; it's a logo. Plan from the start to redraw it at least twice during the project, and treat the redraws as analytic milestones.

Theoretical tensions as features, not bugs

When you combine frameworks across disciplines, they will sometimes pull in opposite directions. A psychological framework emphasizes individual agency; a sociological framework emphasizes structural constraint. Both are usually true, and the tension between them is where the interesting analytic work happens.

A common temptation is to collapse the tension — to declare one framework "primary" and treat the other as background. This produces clean writing and shallow analysis. Better: hold both, track where each illuminates the data, and make the tension explicit in your write-up.

Example. A study of medication adherence might pair a psychological framework (self-efficacy, perceived control) with a structural framework (medication cost, pharmacy access). The tension sits at the question "where is the locus of responsibility?" A study that doesn't resolve this tension prematurely will produce more honest and more actionable findings than one that picks a side.

Visual mapping as analytic practice

Externalizing your conceptual framework on paper or whiteboard is itself an analytic move. It forces decisions you can otherwise leave fuzzy: which concept is upstream of which, which relationships are reciprocal, which terms you're using interchangeably without realizing it.

Practical patterns:

• Draw the framework before you write the methods section
• Annotate arrows with the strength and direction of relationship
• Mark unknowns with question marks rather than glossing
• Redraw after each major data-collection round
• Keep dated copies — the trajectory of the framework is part of the audit trail

When a team co-authors a framework, the divergent versions are themselves data about how team members are framing the work.

"Living" frameworks

A framework that evolves with the project does several things at once:

• It records the team's evolving understanding (history)
• It surfaces points where disciplines disagree (analytic provocation)
• It guides what data to collect next (operational tool)
• It generates predictions and tests them (research instrument)

The framework you submit with the proposal is rarely the framework you publish with. That isn't a failure of planning; it's the point. A static framework usually means the research didn't learn anything its team didn't already know.

A worked example

A team studying maternal mental health in a refugee community might begin with two frameworks: a clinical framework (depression as an individual disorder, screened via PHQ-9) and an anthropological framework (distress as relational, expressed through idioms of loss and displacement).

In v1 of the conceptual framework, these are kept separate. The clinical box has PHQ scores and biomarkers; the anthropological box has idioms of distress and narrative themes. There's a tentative arrow between them labeled "?".

After 20 interviews, v2 of the framework has reorganized. The arrow has resolved into multiple specific links: certain idioms predict elevated PHQ scores, but not all; some PHQ-elevated individuals don't use the clinical idioms at all, while others use them metaphorically. The framework now has three overlapping zones, and the tension between clinical and anthropological framing has become an analytic object in its own right.

By v3, after analysis, the framework has produced a falsifiable claim: that screening with PHQ-9 alone systematically under-detects distress in this community when the idioms of relational loss aren't elicited. That claim is the study's contribution, and it would not have appeared without holding both frameworks in productive tension.

Closing

Interpretivism interprets situated meaning. Constructivism adds that meaning is co-produced in the research encounter. Conceptual frameworks should span disciplines, evolve with the project, and treat theoretical tensions as features, not bugs. Visual mapping externalizes thinking and makes tensions visible.

Next: Module 2 begins with the Research Design Ecosystem — how to search across disciplines and integrate evidence forms beyond academic publication.