Re: [mpowr] Experiment design
John C Klensin <john@jck.com> Tue, 13 January 2004 14:32 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13987 for <mpowr-archive@odin.ietf.org>; Tue, 13 Jan 2004 09:32:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgPam-00072R-GN for mpowr-archive@odin.ietf.org; Tue, 13 Jan 2004 09:32:29 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0DEWSAx027049 for mpowr-archive@odin.ietf.org; Tue, 13 Jan 2004 09:32:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgPam-00072C-Ae for mpowr-web-archive@optimus.ietf.org; Tue, 13 Jan 2004 09:32:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13958 for <mpowr-web-archive@ietf.org>; Tue, 13 Jan 2004 09:32:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgPaj-0001nk-00 for mpowr-web-archive@ietf.org; Tue, 13 Jan 2004 09:32:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgPYu-0001kT-00 for mpowr-web-archive@ietf.org; Tue, 13 Jan 2004 09:30:33 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AgPYO-0001hM-00 for mpowr-web-archive@ietf.org; Tue, 13 Jan 2004 09:30:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgPYO-0006xr-Qf; Tue, 13 Jan 2004 09:30:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgOj2-0005MW-UR for mpowr@optimus.ietf.org; Tue, 13 Jan 2004 08:36:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11992 for <mpowr@ietf.org>; Tue, 13 Jan 2004 08:36:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgOj1-0006i5-00 for mpowr@ietf.org; Tue, 13 Jan 2004 08:36:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgOh5-0006ZL-00 for mpowr@ietf.org; Tue, 13 Jan 2004 08:34:55 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx with esmtp (Exim 4.12) id 1AgOgF-0006R0-00 for mpowr@ietf.org; Tue, 13 Jan 2004 08:34:03 -0500
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.10) id 1AgOgC-0008kS-00; Tue, 13 Jan 2004 08:34:00 -0500
Date: Tue, 13 Jan 2004 08:34:00 -0500
From: John C Klensin <john@jck.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, Pekka Savola <pekkas@netcore.fi>
cc: mpowr@ietf.org
Subject: Re: [mpowr] Experiment design
Message-ID: <85701622.1073982840@scan.jck.com>
In-Reply-To: <2089172591.1073661950@localhost>
References: <Pine.LNX.4.44.0401091953270.1018-100000@netcore.fi> <Pine.BSF.4.58.0401091320370.62437@measurement-factory.com> <2089172591.1073661950@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: mpowr-admin@ietf.org
Errors-To: mpowr-admin@ietf.org
X-BeenThere: mpowr@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>, <mailto:mpowr-request@ietf.org?subject=unsubscribe>
List-Id: Management Positions -- Oversight, Work and Results <mpowr.ietf.org>
List-Post: <mailto:mpowr@ietf.org>
List-Help: <mailto:mpowr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>, <mailto:mpowr-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Harald, --On Friday, 09 January, 2004 15:25 -0800 Harald Tveit Alvestrand <harald@alvestrand.no> wrote: > When I think of running an experiment, I think of something > like: > > - Define the ruleset we want to test > - Declare that from March 1(?), in all WGs with the first > letter from A to K, the new ruleset applies; in WGs from L to > Z, the old rule of IESG decision applies. > - At the end of 3 (or 6) months, the WG chairs get asked: > - Did you remove anyone from the list? > - Was there a time when you wanted to remove a person from > the > list, but did not? > - Was there a time when you removed someone from the list, > and > afterwards decided that you made the wrong decision? > > That should give us some real data - or some real data saying > that this isn't a problem...... I'd add two things to your list, which I consider fairly important: (1) A request to the WG participants for input on whether they feel happier or unhappier with the changes in place, with "happier" specifically focused on "feel that the WG is more effective", "feel that it is easier to contribute", "feel that the S/N ratio in the WG's discussions is better", etc., and "unhappier" including the opposite of these. We shouldn't just be asking the Chairs about impacts. (2) A mechanism for early discontinuance of the "experiment" if there are severe and obvious consequences. While I personally think that is unlikely, if the process led to a lot of appeals with which the IESG agreed, it would be time to immediately stop, and either give it up or readjust the rules in some fashion. Using the mailing list management situation as an example, I would consider "fewer disruptions than before and an improved S/N ratio" to make the procedural change a wild success. But it would give zero data under your proposal and, indeed, under that proposal as written, might convince people that there was no problem, since no one was removed nor was there the strong temptation to remove anyone. Similarly, I would consider "warned someone in private and they decided to behave, where previous warnings had been unheeded" to be a sign of huge success, and your list of questions is unlikely to capture that one either. john <tirade> p.s. To anyone inclined to raise the "it isn't really an experiment, since there is no design control group and no placebo" argument, please give it a rest. I am _not_ singling anyone out here -- that comment is made by someone, usually someone different, every time someone uses the word "experiment" around the IETF. Virtually any experiment (e.g., a change in the rules with a monitored and evaluated outcome) on a social/behavioral system requires working with the subjective evaluations of participants and/or observers as to what happened. If you exclude anything that is not subject to a carefully managed cross-plot or split-plot design, or even everything on which no exogeneous variates can unexpectedly occur in the system, then there are no experiments except in agriculture, and fewer of those than is generally believed. In more careful designs than I am suggesting above (because I don't think the design and implementation time is justified), there are sometimes-complex techniques to lay a basis for comparing pre- and post-test opinions but they still don't involve design control groups or placebo controls. The latter, in their purest form, are applicable only if _all_ variation not measured by the experiment can be excluded and that is, in practice, nearly impossible (double-blind placebo-based tests are just intended to minimize the most obvious causes). If you need some really good examples from the "experimental" literature, read some of the papers evaluating treatments the claim to reduce perceived pain levels. Then, for a change in pace, read Wittgenstein's discussions on how someone accurately communicates levels of pain to someone else. I try to discourage my statistician colleagues who are not trained in network design from doing their own networks, and believe that this community should return the favor. </tirade> _______________________________________________ mpowr mailing list mpowr@ietf.org https://www1.ietf.org/mailman/listinfo/mpowr
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Partain (LI/EAB)
- [mpowr] SUMMARY: Mailing List Management Discussi… Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Pekka Savola
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Joel M. Halpern
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Meyer
- RE: [mpowr] SUMMARY: Mailing List Management Disc… Robert Snively
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Meyer
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Pekka Savola
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Meyer
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Melinda Shore
- [mpowr] Gauging consensus during disruptions Alex Rousskov
- [mpowr] Re: Gauging consensus during disruptions Melinda Shore
- Re: [mpowr] Re: Gauging consensus during disrupti… Dave Crocker
- [mpowr] Re: Gauging consensus during disruptions Alex Rousskov
- [mpowr] Re: Gauging consensus during disruptions James Kempf
- [mpowr] Experiment design Harald Tveit Alvestrand
- Re: [mpowr] Experiment design Alex Rousskov
- [mpowr] Re: Experiment design Pekka Savola
- clarifications Re: [mpowr] SUMMARY: Mailing List … Alex Conta
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Conta
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] Re: Gauging consensus during disrupti… Alex Conta
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Conta
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Conta
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Eric Rosen
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Spencer Dawkins
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- [mpowr] Getting Bad Ideas to Fail Early Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Alex Rousskov
- [mpowr] Re: Getting Bad Ideas to Fail Early James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Partain (LI/EAB)
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Alex Rousskov
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Meyer
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Meyer
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain (LI/EAB)
- Re: [mpowr] Experiment design John C Klensin
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James M Galvin
- Re: [mpowr] Experiment design Spencer Dawkins
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Mark Allman
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Spencer Dawkins
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain (LI/EAB)
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain (LI/EAB)
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early James Kempf
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Mark Allman
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Spencer Dawkins
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Spencer Dawkins