Lesson 15 · Transdisciplinary Research

15. Transdisciplinary Research Design

26 min

Before you start

  • Lessons 11–14: paradigms, qualitative, quantitative, mixed, integration
  • Comfort articulating what your study is **for**
  • A team or community partner you can co-design with

By the end you'll be able to

  • Define Mode 2 knowledge production
  • Distinguish multi-, inter-, and transdisciplinary research in practice
  • Apply co-production and team-science strategies
  • Recognize when you're doing Mode 1 vs. Mode 2
  • Build accountability structures for transdisciplinary teams

Mode 1 vs. Mode 2 knowledge production

Gibbons and colleagues described two modes of knowledge production:

  • Mode 1 — knowledge produced within disciplinary structures, driven by academic curiosity, validated by peer review, communicated through publication. The classic university model.

  • Mode 2 — knowledge produced in the context of application, transdisciplinary by nature, validated by accountability to multiple stakeholders, communicated through whatever channels reach the actors who'll use it.

Mode 2 isn't "Mode 1 with stakeholder consultation." It's a different production logic. The question, the methods, the standards of rigor, and the outputs are co-determined by academic and non-academic actors. Mode 1 produces papers; Mode 2 produces papers and practice change, policy artifacts, community-owned tools.

Most projects that claim Mode 2 operate in Mode 1 with consultation. The diagnostic question is decision rights: who held them on the research question? On methods? On interpretation? On dissemination?

Multi-, inter-, transdisciplinary in practice

Recall the ladder:

  • Mono-disciplinary — single discipline owns the work
  • Multi-disciplinary — multiple disciplines work in parallel
  • Inter-disciplinary — disciplines integrate concepts and methods
  • Trans-disciplinary — disciplinary integration plus non-academic partners with decision rights

In practice, the ladder is fuzzy and projects move on it during their lifecycle. A project may start multi-disciplinary, become interdisciplinary as concepts integrate, and reach transdisciplinarity only after community partners gain real decision authority.

The point isn't to claim the highest rung; it's to identify accurately where you are. A project that calls itself transdisciplinary but treats community partners as advisors is at most interdisciplinary. Calling it what it is preserves the meaning of "transdisciplinary" for projects that earn it.

Co-production and team science

Team science is the practice of multi-disciplinary or interdisciplinary collaboration. Transdisciplinary team science extends it by including non-academic partners as full team members.

Co-production has several markers:

  • Shared decision rights — non-academic partners can veto or shape research decisions, not only advise
  • Co-defined success criteria — what counts as a successful project includes non-academic outcomes
  • Co-authored or community-controlled outputs — dissemination products belong to all partners
  • Paid roles for non-academic partners — not unpaid advisory boards
  • Iterative role definition — boundaries between academic and non-academic roles soften as the project matures

Without these markers, co-production is rhetorical.

Team science structures

Transdisciplinary teams face coordination challenges mono-disciplinary teams don't. The standard solution is structure:

  • Decision logs — every major decision recorded with who decided, what alternatives were considered, and what non-academic partner concurred
  • Rotating facilitation — meetings facilitated by different team members, including community partners, to interrupt hierarchical defaults
  • Dissent protocols — explicit processes for surfacing and recording disagreement
  • Boundary spanners — designated team members whose role is to translate across academic and community contexts
  • Regular role-clarification sessions — periodic review of who is doing what, with explicit space for renegotiation

Without these structures, transdisciplinary teams default to the dominant cultural pattern — usually the academic hierarchy with community partners as junior participants.

Accountability structures

Transdisciplinary work is accountable to more than the academy. Accountability structures include:

  • Community advisory boards with documented authority on specified decisions
  • Memoranda of understanding that name reciprocal obligations
  • Co-PI structures with both academic and community PIs of equal standing
  • Funder agreements that include community partners as named recipients of resources
  • Outcome agreements that specify community-defined deliverables alongside academic ones

The legal and administrative work is real. Funder structures, university policies, and IRB practices often don't yet accommodate it. Building the accountability scaffolding is part of the transdisciplinary work.

Producing knowledge "in the context of application"

The Mode 2 phrase "in the context of application" is more than a slogan. It means:

  • The research question emerges from application — from a real decision someone needs to make, a real problem someone is facing — not from gaps in the literature
  • The methods are constrained by what's possible in the application setting
  • The findings are interpreted with the application in mind
  • The outputs are designed for the application audience first, the academic audience second

This is uncomfortable for academic researchers trained to start with literature gaps and end with publications. The discipline is to start with the application question and let publication be a downstream byproduct rather than the goal.

When you're in Mode 1 (and that's fine)

Not every project should be Mode 2. Some research questions are appropriately Mode 1: foundational, theoretical, exploratory, distant from immediate application. Calling these projects what they are — Mode 1 — protects the meaning of Mode 2 for projects that actually do it.

The pretense that all research is now Mode 2 dilutes both. Honest naming is the rigor.

A worked example

A team studying community responses to wildfire smoke in a multi-ethnic neighborhood operates in Mode 2:

  • The question came from a community-organized town hall about air-quality concerns, not from a literature gap
  • Methods (air-quality monitoring locations, survey items, qualitative probes) were co-decided with community partners
  • The community advisory board held veto authority on dissemination channels
  • The primary outputs were a community-controlled report, a policy brief delivered to the city council, and an air-quality dashboard for the neighborhood — with academic papers as secondary outputs
  • Two community members were named co-authors on the resulting publications

A Mode 1 version of "the same study" would have started with a literature gap on environmental-justice methodology, collected the same data without community decision rights, and produced a paper as the primary output. Both versions might pass peer review; only one is transdisciplinary.

Closing

Mode 2 is knowledge produced in the context of application, with non-academic stakeholders holding decision rights. The ladder from mono- to transdisciplinary is fuzzy; honest naming protects the meaning. Team science needs structures — decision logs, rotating facilitation, dissent protocols. Accountability extends beyond the academy. Not every project should be Mode 2; pretending otherwise dilutes the term.

Next: Module 4 begins — interpreting statistics in context, contextual inference, and avoiding reductionism.

Common mistakes

These are the traps learners hit most often on this topic. Knowing them in advance is half the fix.

  • Claiming Mode 2 while operating in Mode 1

    Mode 2 produces knowledge in the context of application — outside the academic team and with non-academic stakeholders sharing decisions. A study that only invites stakeholders to comment on a near-final design is Mode 1 with consultation.

  • Letting team science default to the most senior voice

    Team science requires structures that surface dissent: rotating facilitation, blind input on key choices, written disagreement protocols. Without structure, hierarchy wins.

  • Confusing transdisciplinarity with collaboration

    Many people collaborate; few do transdisciplinary work. Transdisciplinary means integrating concepts and epistemic sources, with non-academic partners holding decision rights. Collaboration is necessary; it is not sufficient.

Practice problems

Try each on paper first. Click Show solution only after you've made a real attempt.

  1. Problem 1
    Audit a project as Mode 1, Mode 2, or hybrid. Justify with three concrete features.
    Show solution

    Hybrid is the most honest answer for most projects. The point of the audit is to identify where Mode 2 is real and where it is rhetorical. Decision-rights distribution is the most reliable indicator.

  2. Problem 2
    Design one accountability structure for a transdisciplinary team (e.g., decision log, dissent protocol, rotating facilitation).
    Show solution

    Example: a decision log that records, for each major design decision, who decided, what alternatives were considered, and which non-academic partner concurred. Signed off monthly by both academic and community co-leads.

Practice quiz

  1. Question 1
    Mode 2 knowledge production is best characterized as:
  2. Reflection 2
    Name three structural features that distinguish a transdisciplinary team from a multidisciplinary one.

Lesson 15 recap

  • Mode 2 = knowledge in the context of application, with stakeholders holding decision rights
  • Multi → inter → transdisciplinary is a ladder of integration, not labels
  • Team science needs structures: decision logs, rotating facilitation, dissent protocols
  • Collaboration alone is necessary but not sufficient

Coming next: Lesson 16 — Interpreting Statistics in Context

  • Module 4 begins: interpreting statistics in context
  • Contextual inference and avoiding reductionism
  • Pattern recognition in systems

Saved in your browser only — no account, no server.