Thoughts about theorizing from ADR and DR

1. Theorizing in Design Research
Matti Rossi
Aalto University School of Economics
Sandeep Purao
Penn State University
Maung Sein
Agder University

2. Contents
• Why theorizing from DR at all?
• What has been said before
• How one can theorize from from DR?
9/23/2012
2
2

3. What theory is not?
(Sutton and Staw, 1995)
• References are not theory
• Data are not theory
• Lists of variables and constructs are not theory
• Diagrams are not theory
• Hypotheses (or predictions) are not theory
3

4. Theory according Nunamaker et al.
Different types of theory building:
• Declare the “truth”
– e.g. Dijkstra’s ”Go to statement considered harmful”
CACM, 1968
• Formulate a concept (i.e. a framework)
– e.g. Relational model
• Construct a method
– e.g. Parnas on modularity
• Develop a theory
– e.g. Halstead’s Software Science
4

5. Theory of theories
(Gregor, 2006)
• Theory for analysing and describing
• Theory for explaining
• Theory for predicting
• Theory for explaining and predicting
• Theory for design and action (design theory)
5

6. IS Design Theory
(Walls et al, 1992)
Kernel Meta- Meta- Testable
Theory Require- Design (product)
ments hypotheses
Kernel Design Testable
Theory Method (process)
hypotheses
6

7. Walls, Widmeyer and El-Sawy 2004
-
7

8. Kuechler and Vaishnavi (2008) on levels of
theories
9/23/2012
8
8

9. Generalizing from ADR
Design Theory Level 4
Design
Principles
Class of Class of
Problems
Level 3 Solutions
Level 1 Level 2
Design Solution(s) as
Problem(s) process artifact in use
9

10. Modifying (kernel) theory through ADR
Level 3:
Kernel modifying
Theory
theory
Class of
Problems Class of
Solutions
Level 1 Level 2
Design Solution(s) as
Problem(s) process artifact in use
10

11. Conclusions
• Theorizing is vital for design research to mature
– We should see the designs as tests of the kernel and/or design
theories
• There are different forms of theorizing
• There are different theoretical contributions
• Not everyone has to come up with a full design theory
– The goal should be always to develop at least design principles
9/23/2012
11
11

12. 12

13. Contact Information
Matti Rossi
Helsinki School of Economics
P.O. Box 1210
FIN-00101 Helsinki
Finland
Email: matti.rossi@hse.fi
Phone: +358-9-43138996
Fax : +358-9-43138777
http://www.hse.fi/EN/HKI/R/Matti.Rossi/1_ContactInfo.htm
IM: Matti_Rossi@msn.com
13
13