Explaining Validation
Posted: Wed Mar 01, 2006 1:25 pm
Posted by ""Timothy Quinn"" <tdquinn@MIT.EDU>
I have two very specific questions for the practitioners among you. Before I pose them, here is the setup:
In the past three weeks, I have been asked on several occasions how we ""validate"" our models when they are built from ""subjective"" accounts of how the system works (i.e., on expert opinion). Jay Forrester, in Industrial Dynamics, wrote,
""Any 'objective' model-validation procedure rests eventually at some lower level on a judgment or faith that either the procedure or its goals are acceptable without objective proof."" (Forrester 1961, p. 123)
I take these judgments and faith to be the intuition or common-sense knowledge of a model's critic. For example, we know that physical inventory cannot go negative, or more workers have a higher work completion rate than fewer (unless you reach the nonlinear too-many-cooks regime). Therefore, John Sterman, in Business Dynamics, concludes,
""Validation is.intrinsically social. The goal of modeling, and of scientific endeavor more generally, is to build shared understanding that provides insight into the world and helps solve important problems. Modeling is therefore inevitably a process of communication and persuasion among modelers, clients, and other affected parties. Each person ultimately judges the quality and appropriateness of any model using his or her own criteria."" (Sterman 2000, p.850)
To restate, validation is building shared understanding of
(1) the problem,
(2) how the model simplifies the real world in favor of achieving a purpose, and
(3) the appropriateness of those simplifications for the purpose.
I have struggled to make a compelling case for model ""validity"" when my potential critic's attention span is limited to a few minutes only. I cannot take him or her equation-by-equation and explain the empirical or common-sense justification for each.
Questions:
(1) Is there a quick way, possibly a good analogy, to communicate the point that validation is about confidence in a model's simplifications of reality for a specific purpose? I am looking for something akin to the bathtub analogy so often used for explaining stocks and flows to a lay audience.
Here is my best failed attempt: Imagine your goal is to cross a ford without getting your feet wet. Can you do it? Only by demonstrating that there exists a sequence of stepping stones, each within one stride of the next, spanning the river. If we agree on the existence of each hop, then you must concede the goal is possible.
The reason this analogy fails is that the goal is achieved by cutting it into sequential pieces, each of which must lead to the next. In contrast, from uncontroversial pieces, SD models can produce surprising and counterintuitive results.
(2) What published paper best exemplifies how a model's formulations should be justified, based both on tests of intended rationality, ""common knowledge"" reality constraints (e.g., conservation of mass), and expert opinion?
Thanks,
Tim Quinn
~~~~~~~~~
MIT Sloan School of Management
System Dynamics Group
Posted by ""Timothy Quinn"" <tdquinn@MIT.EDU>
posting date Tue, 28 Feb 2006 10:19:17 -0600
I have two very specific questions for the practitioners among you. Before I pose them, here is the setup:
In the past three weeks, I have been asked on several occasions how we ""validate"" our models when they are built from ""subjective"" accounts of how the system works (i.e., on expert opinion). Jay Forrester, in Industrial Dynamics, wrote,
""Any 'objective' model-validation procedure rests eventually at some lower level on a judgment or faith that either the procedure or its goals are acceptable without objective proof."" (Forrester 1961, p. 123)
I take these judgments and faith to be the intuition or common-sense knowledge of a model's critic. For example, we know that physical inventory cannot go negative, or more workers have a higher work completion rate than fewer (unless you reach the nonlinear too-many-cooks regime). Therefore, John Sterman, in Business Dynamics, concludes,
""Validation is.intrinsically social. The goal of modeling, and of scientific endeavor more generally, is to build shared understanding that provides insight into the world and helps solve important problems. Modeling is therefore inevitably a process of communication and persuasion among modelers, clients, and other affected parties. Each person ultimately judges the quality and appropriateness of any model using his or her own criteria."" (Sterman 2000, p.850)
To restate, validation is building shared understanding of
(1) the problem,
(2) how the model simplifies the real world in favor of achieving a purpose, and
(3) the appropriateness of those simplifications for the purpose.
I have struggled to make a compelling case for model ""validity"" when my potential critic's attention span is limited to a few minutes only. I cannot take him or her equation-by-equation and explain the empirical or common-sense justification for each.
Questions:
(1) Is there a quick way, possibly a good analogy, to communicate the point that validation is about confidence in a model's simplifications of reality for a specific purpose? I am looking for something akin to the bathtub analogy so often used for explaining stocks and flows to a lay audience.
Here is my best failed attempt: Imagine your goal is to cross a ford without getting your feet wet. Can you do it? Only by demonstrating that there exists a sequence of stepping stones, each within one stride of the next, spanning the river. If we agree on the existence of each hop, then you must concede the goal is possible.
The reason this analogy fails is that the goal is achieved by cutting it into sequential pieces, each of which must lead to the next. In contrast, from uncontroversial pieces, SD models can produce surprising and counterintuitive results.
(2) What published paper best exemplifies how a model's formulations should be justified, based both on tests of intended rationality, ""common knowledge"" reality constraints (e.g., conservation of mass), and expert opinion?
Thanks,
Tim Quinn
~~~~~~~~~
MIT Sloan School of Management
System Dynamics Group
Posted by ""Timothy Quinn"" <tdquinn@MIT.EDU>
posting date Tue, 28 Feb 2006 10:19:17 -0600