S7.01 - Design_science_research
S7.01 ? Design science research
flowchart LR
A[High-level AI governance principles] --> B[Need for operational oversight]
A2[Descriptive or policy-only approaches] --> B
B --> C[RAIDT
Run-level evidence framework]
C --> D[[Design science research
Artefact logic for RAIDT]]
D --> E[Run-level evidence]
E --> F[Evidence pack]
E --> G[RAIDT score profile]
F --> H[Reviewer reconstruction]
G --> I[Governance readiness]
D --> J[Organisational learning]
D --> K[Policy alignment]
L[Healthcare]
M[Public services]
N[Finance]
O[Education]
P[Templates, logging, dashboards]
L --> D
M --> D
N --> D
O --> D
P --> D? Star S7 - Academic Theory and Design Logic
Star context: Positions RAIDT within Academic Theory and Design Logic by showing that RAIDT is not only a descriptive account of GenAI governance, but a designed and evaluable governance artefact intended to solve a real organisational problem through run-level evidence and structured assessment.
Academic picture
Definition / background
Design science research is a research tradition, especially prominent in Information Systems, that seeks to address important real-world problems by designing, justifying, and evaluating artefacts. Those artefacts may be models, methods, constructs, decision procedures, frameworks, or socio-technical arrangements rather than only software applications. The central idea is pragmatic but academically rigorous: knowledge is produced not only by describing or explaining the world, but also by designing an intervention that improves it and by learning from how that intervention performs.
In RAIDT, design science research matters because the governance problem is not solved by description alone. Organisations do not merely need a theory saying that GenAI should be responsible, auditable, interpretable, dependable, and traceable. They need a usable governance artefact that structures evidence at the level of a run, produces a reviewable evidence pack, and generates a score profile that supports oversight, comparison, and improvement. RAIDT therefore fits design science research because it is intentionally constructed to solve a practical governance problem while also contributing conceptual and methodological knowledge.
This distinguishes design science research from several nearby ideas. It is not the same as a purely explanatory theory, whose primary goal is to account for observed phenomena. It is not the same as routine system development, because its purpose is scholarly contribution through justified design and evaluation. It is also not simply a compliance checklist, because the artefact must embody defensible design logic about what evidence should exist, why it matters, and how that evidence supports governance decisions. In RAIDT, design science research provides the overarching logic that connects conceptual design to operational governance.
The concept belongs inside RAIDT because RAIDT is best understood as a designed governance artefact for the era of generative AI. It defines the run as the unit of governance, specifies what evidence should be collected, and translates that evidence into practical outputs that organisations can inspect and contest. That is precisely the kind of problem-solution orientation that design science research is intended to support.
Why this concept matters
Design science research matters because it gives RAIDT a defensible answer to the question, ?Why build this framework in this form?? Without that answer, RAIDT could be misread as an arbitrary model, a loose conceptual taxonomy, or a policy aspiration without an operational core. Design science research clarifies that RAIDT exists because organisations face a concrete governance problem: they must make GenAI use reviewable at the level where work is actually performed.
The concept also prevents a common confusion between principles and mechanisms. Many governance discussions stop at desirable values, but design science research pushes the project toward artefact logic, use context, evaluation, and improvement. That shift matters in GenAI governance because risks often emerge in specific runs, prompts, settings, user roles, data conditions, and task contexts. A design-science framing therefore justifies why RAIDT focuses on run-level evidence rather than only policy-level statements.
If this concept were missing, RAIDT would be easier to dismiss as either too theoretical for practitioners or too applied for theory-building audiences. Design science research avoids that false split by showing that a well-designed artefact can itself be a scholarly contribution while also delivering practical governance value.
Key idea: Design science research matters in RAIDT because it justifies building a governance artefact that turns abstract AI principles into reviewable run-level evidence and operational assessment.
What this item explains
- Why RAIDT is framed as a designed governance artefact rather than only a descriptive theory.
- Why run-level evidence, evidence packs, and score profiles are legitimate design outputs in a research contribution.
- How RAIDT links practical problem-solving with academic rigour in Information Systems and organisational governance.
- Why governance for generative AI requires a structured artefact and not only narrative guidance.
- How evaluation and refinement become part of the contribution, rather than an afterthought.
Practical example / likely audience question
Audience question
Why describe RAIDT as design science research rather than simply calling it an AI governance framework or an Information Systems theory?
Answer
The concern behind this question is usually that design science research may sound like an unnecessary label, or that it implies RAIDT must be a software tool to qualify. The direct answer is that RAIDT is called design science research because its core contribution is the design of a governance artefact intended to solve a practical problem: how to make individual GenAI uses inspectable, assessable, and improvable in organisational work.
A generic governance framework might list principles, controls, or policy recommendations. A purely explanatory theory might clarify causes, mechanisms, or outcomes. RAIDT goes further by specifying a concrete governance object: the run-level evidence pack and associated score profile. For example, if a public-sector team uses a GenAI assistant to draft citizen communications, RAIDT asks what evidence should exist for that run, how it should be reviewed, and how the organisation should interpret strengths and weaknesses across the five pillars. That is an artefact-centred, problem-solving contribution, which is exactly why design science research is the right positioning.
RAIDT handles this better than a generic AI governance approach because it does not stop at saying organisations should be accountable. It gives them a designed structure for evidencing accountability in context. That move from aspiration to artefact is the essential design-science step.
Practical example in RAIDT terms
Consider a healthcare setting where a hospital team uses a generative AI system to draft discharge-summary explanations for patients. The GenAI use case is helpful because it can improve speed and clarity, but the run-level issue is that each generated output depends on prompt wording, patient context, model configuration, source materials, human review, and final sign-off.
In RAIDT terms, the organisation would need evidence showing who initiated the run, what task was intended, what context and source materials were used, which model and settings were active, what output was produced, what human checks were applied, and what revisions were made before the summary reached the patient. Responsibility is affected because staff roles and sign-off obligations must be clear. Auditability is affected because the organisation must be able to reconstruct the decision path. Interpretability is affected because clinicians must understand why the output is acceptable or problematic. Dependability is affected because the organisation needs confidence that the process performs consistently. Traceability is affected because inputs, outputs, versions, and review steps must be connected.
Design science research improves governance readiness here because it explains why RAIDT should be designed as a practical artefact for capturing, organising, and assessing this evidence. Without that design logic, the hospital may have policy statements about safe AI but still lack a repeatable way to examine what actually happened in a specific discharge-summary run.
Detailed link to RAIDT
Design science research links to RAIDT in four ways.
First, it explains RAIDT's core identity as a purposeful governance artefact designed to address the practical problem of governing generative AI in organisational work.
Second, it supports the choice of the run as the unit of analysis and intervention, because governance becomes meaningful when evidence is attached to specific uses rather than to abstract system claims.
Third, it justifies the creation of structured outputs such as the run-level evidence pack and five-pillar score profile as designed objects that support evaluation and comparison.
Fourth, it strengthens reviewability, contestability, audit readiness, and organisational learning by making the framework inspectable, improvable, and defensible as an intervention rather than only a concept.
Design science research ? Run-level evidence ? Evidence pack ? RAIDT score profile ? Governance readiness
That chain matters because it shows how an academic design logic becomes an operational governance pathway. Design science research is the reason RAIDT can claim both scholarly relevance and practical utility.
Link to the five RAIDT pillars
Responsibility
Design science research supports Responsibility by requiring RAIDT to be intentionally oriented toward a meaningful organisational problem with clear roles, purposes, and decision consequences.
Example evidence / implication:
- The artefact should specify who is accountable for initiating, reviewing, approving, and contesting a run.
- The framework should make explicit which governance responsibilities are assigned to users, managers, reviewers, and system owners.
Auditability
Design science research strongly supports Auditability because designed artefacts must be inspectable and evaluable. In RAIDT, that means the framework should generate evidence that enables retrospective review of what happened and why.
Example evidence / implication:
- A run should leave a reconstructable record of prompts, sources, outputs, review actions, and sign-off decisions.
- The evidence pack should be designed so that an internal reviewer or auditor can examine governance quality without relying on memory or informal explanation.
Interpretability
Design science research supports Interpretability by requiring the rationale of the artefact to be explainable. In RAIDT, the categories of evidence and scoring should be understandable to those using or scrutinising the framework.
Example evidence / implication:
- The scoring logic should be explainable in ordinary governance language rather than hidden behind opaque labels.
- Reviewers should be able to understand why a run scored strongly or weakly on a particular pillar.
Dependability
Design science research supports Dependability because an artefact must perform consistently enough to be useful. RAIDT therefore needs stable design logic, repeatable review processes, and evidence structures that work across comparable contexts.
Example evidence / implication:
- Similar runs should be assessed in a reasonably consistent way when the same rubric and evidence requirements are applied.
- The framework should support refinement when evaluation shows inconsistency, ambiguity, or weak governance outcomes.
Traceability
Design science research supports Traceability by requiring explicit links between design choices, evidence categories, organisational context, and resulting assessments. In RAIDT, this is central rather than optional.
Example evidence / implication:
- The evidence pack should connect run inputs, system configuration, outputs, review actions, and final governance conclusions.
- Changes to templates, scoring logic, or evidence requirements should be traceable as part of artefact evolution.
Design science research affects all five pillars, but it is especially strong in Auditability, Traceability, and Dependability because those pillars depend most visibly on the existence of a well-designed and evaluable governance artefact.
Why this item is more than a generic concept
In general AI governance, design science research may simply mean that a researcher built or proposed a useful governance model. In RAIDT, it means something more operational and more disciplined: the governance model is explicitly designed around the run, implemented through evidence structures, and assessed through outputs that can be reviewed, contested, and improved.
The RAIDT meaning is therefore more operational because it is tied to run-level evidence. The contribution is not just that a governance idea exists. The contribution is that the idea has been shaped into a practical artefact with identifiable components, intended uses, evaluable outputs, and a clear pathway to organisational readiness.
Common misunderstanding
Misunderstanding
Design science research means building a software application, so a conceptual governance framework like RAIDT cannot really qualify.
Correction
This is too narrow. Design science research is about designing and evaluating artefacts that solve important problems, and those artefacts can include methods, models, frameworks, and governance structures as well as software. RAIDT qualifies because it specifies a practical governance artefact centred on run-level evidence, evidence packs, and scoring logic.
A useful example is a scoring rubric used in safety-critical review. The rubric may exist as a document, template, workflow, or dashboard, but its research value lies in the design logic it embodies and the problem it helps solve. In the same way, RAIDT is not disqualified if parts of it are conceptual. What matters is that it is intentionally designed, operationally meaningful, and open to evaluation in use.
Boundary and limitation
Design science research does not by itself prove that RAIDT is universally effective, complete, or superior in every governance context. It does not remove the need for empirical validation, sector-specific adaptation, institutional judgement, or ongoing revision as models, regulations, and work practices change. A design-science framing can justify why the artefact exists and how it should be evaluated, but it cannot substitute for careful evidence about how well the artefact performs in practice.
There is also a boundary around abstraction. If RAIDT remains too general, the artefact risks becoming another high-level framework. If it becomes too rigid, it may fail to travel across sectors or task types. RAIDT handles this limitation by anchoring the artefact at the run level while allowing evidence requirements, review thresholds, and implementation mechanisms to be adapted to context.
Implementation levels
Manual implementation
A researcher or small team can apply design science research manually by defining the RAIDT artefact, specifying run-level evidence fields, using templates to assemble evidence packs, and applying a human-reviewed scoring rubric to selected cases.
Semi-automated implementation
Semi-automated implementation can use structured metadata capture, templated evidence forms, logging conventions, and review dashboards that help assemble evidence packs and pre-populate parts of the score profile while keeping human judgement in the loop.
Fully automated implementation
At scale, a platform or governance pipeline can operationalise the design-science logic by integrating orchestration layers, prompt wrappers, event logging, version control, automated evidence capture, and dashboarded scoring support so that each run generates a reconstructable governance record with minimal manual effort.
Practical use in the RAIDT project
Within the RAIDT project, design science research is especially useful for positioning and defence. In Paper 08 Foundations, it helps justify why RAIDT is a designed governance artefact rather than only a conceptual map of desirable principles. In Paper 09 Empirical Validation, it supports the expectation that the artefact should be tested against real or simulated runs to see whether it improves reviewability, consistency, and governance decision quality. In Paper 10 Policy Pathways, it helps explain how a research artefact can inform organisational policy without collapsing into policy language alone.
The concept is also useful in sector playbooks, evidence-pack design, scoring-rubric explanation, and supervision or viva discussion. It gives a direct answer when a reviewer asks what kind of contribution RAIDT is making: RAIDT is a design-science contribution because it creates and justifies a practical governance artefact for responsible use of generative AI.
Key audience questions to prepare for
Q1. Why is design science research a better fit for RAIDT than a purely descriptive theory?
Because RAIDT is intended to solve a practical governance problem by specifying a usable artefact. A descriptive theory can explain why governance problems occur, but RAIDT also needs to define what evidence should be gathered and how governance quality should be assessed.
Q2. Does calling RAIDT design science research weaken its theoretical contribution?
No. It clarifies the type of contribution. Theoretical value still exists in the constructs, mechanisms, boundaries, and evaluation logic, but those are organised around an artefact designed to improve practice.
Q3. What is the artefact in RAIDT?
The artefact is not only a document or tool. It is the designed governance arrangement consisting of the run concept, evidence requirements, evidence pack structure, five-pillar score profile, and review logic that connects them.
Q4. Why is run-level focus important to the design-science claim?
Because it shows that the artefact is built around the real point at which governance evidence is needed. The run is where prompts, context, outputs, human judgement, and risk conditions come together in a form that can be reviewed.
Q5. How would you defend RAIDT against the criticism that it is just a checklist?
A checklist merely enumerates items to tick off. RAIDT, framed through design science research, provides a structured governance artefact with design logic, evidence relationships, assessment outputs, and a pathway to evaluation and organisational learning.
Suggested citation concepts to support this item
- design science research in Information Systems
- design science research artefact evaluation
- design science research for governance frameworks
- design theory and artefact design in IS
- problem-centred design science research
- evaluable governance artefacts for AI
- socio-technical artefacts in organisational governance
- run-level accountability in generative AI systems
- evidence-based AI governance frameworks
- operationalising AI governance through design artefacts
Short explanation for presentation
Design science research is the logic that explains why RAIDT is more than a descriptive framework for AI governance. It treats RAIDT as a designed artefact intended to solve a practical organisational problem: how to govern individual uses of generative AI in a way that is reviewable, contestable, and auditable. In RAIDT, that artefact takes the form of run-level evidence requirements, an evidence pack, and a five-pillar score profile. This matters because organisations do not only need principles; they need a usable method for inspecting what happened in a specific GenAI run and assessing whether governance expectations were met. Positioning RAIDT as design science research therefore strengthens both the scholarly argument and the practical value of the project.
One-line takeaway
Design science research is the artefact-centred research logic behind RAIDT because RAIDT turns abstract GenAI governance principles into run-level evidence, structured assessment, and practical governance readiness.
Mentioned in reference-paper summaries (5)
Paper summaries live in Port/93-References/pdf_summaries/. Each file listed below contains the key term at least once.
REF-049__Herath-2025.mdREF-108__Tuunanen-2024.mdREF-112__Venable-2016.mdUNM-013__codex_oa_10.1057_ejis.2014.36.mdUNM-021__codex_oa_10.25300_MISQ_2023_16700.md