Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
marine_colab:what_is_an_experiment [2015-05-08 10:19] majamarine_colab:what_is_an_experiment [2015-08-19 10:15] (current) nik
Line 4: Line 4:
  
 An experiment can be seen as a structured method for collecting evidence to test a hypothesis. The process of designing a good experiment involves reducing  unknowns and establishing a clear relationship between the hypothesis and any expected results. is there a causal relationship that can be established between the initial conditions and the result? does the collected data actually support (or refute) the hypothesis? is there enough data to draw a conclusion? are there other factors effecting the outcome?  An experiment can be seen as a structured method for collecting evidence to test a hypothesis. The process of designing a good experiment involves reducing  unknowns and establishing a clear relationship between the hypothesis and any expected results. is there a causal relationship that can be established between the initial conditions and the result? does the collected data actually support (or refute) the hypothesis? is there enough data to draw a conclusion? are there other factors effecting the outcome? 
 +
  
 [[http://labcraft.co/|From Labcraft]] on experimentation: [[http://labcraft.co/|From Labcraft]] on experimentation:
Line 14: Line 15:
 [[http://labcraft.co/|From Labcraft]] on lessons learned about experimenting: [[http://labcraft.co/|From Labcraft]] on lessons learned about experimenting:
 <blockquote> <blockquote>
-**Know what you’re trying to discover**. There’s a lot to be said for insights that emerge from pilots, and even more to be said about being open to being surprised. But our experience suggests that our efforts are best served when we define from the outset what we hope to learn from a pilot or trial.\\ +**Know what you’re trying to discover**. There’s a lot to be said for insights that emerge from pilots, and even more to be said about being open to being surprised. But our experience suggests that our efforts are best served when we define from the outset what we hope to learn from a pilot or trial. 
-**If it isn’t working, stop doing it**. This may sound obvious, but continuing on with something when it’s clearly not working happens more often than you might think in almost every type of organization. One of the key aspects of rapid-cycle prototyping is that you simply stop doing something when you realize it’s not working, learn from that, and move on.\\ + 
-**Don’t take it personally**. Labs take risks, so failure will happen. As much as we fetishize failure in social innovation, it can still hurt when it happens. Make sure the culture in your organization genuinely supports the notion that things won’t always work, and backs up the individuals who lead experiments.\\+**If it isn’t working, stop doing it**. This may sound obvious, but continuing on with something when it’s clearly not working happens more often than you might think in almost every type of organization. One of the key aspects of rapid-cycle prototyping is that you simply stop doing something when you realize it’s not working, learn from that, and move on. 
 + 
 +**Don’t take it personally**. Labs take risks, so failure will happen. As much as we fetishize failure in social innovation, it can still hurt when it happens. Make sure the culture in your organization genuinely supports the notion that things won’t always work, and backs up the individuals who lead experiments. 
 **Be strict about learning**. Experimentation isn’t a substitute for deeper learning. There’s no point in failing for the sake of it. It’s crucial that no matter how much you may want to forget a failed experiment, you reflect after every activity that went wrong on what went well, what didn’t, and what you’d do differently. -pp 96</blockquote> **Be strict about learning**. Experimentation isn’t a substitute for deeper learning. There’s no point in failing for the sake of it. It’s crucial that no matter how much you may want to forget a failed experiment, you reflect after every activity that went wrong on what went well, what didn’t, and what you’d do differently. -pp 96</blockquote>
- + 
 +Venkatesh Rao on [[http://www.ribbonfarm.com/2015/08/18/extraordinary-laboratories/#more-5096|Extraordinary Laboratories]] 
 + <blockquote> 
 +Civilization is the world we build within these extraordinary laboratories. A contingent state of affairs that is only stable to the extent that the truths it is built on are sufficiently sequestered. Understood this way, all of civilization is one giant laboratory instrument, poking at the unknown. 
 +</blockquote> 
 On unstructured tinkering and statistical validity... On unstructured tinkering and statistical validity...
   * https://en.wikipedia.org/wiki/Quasi-experiment   * https://en.wikipedia.org/wiki/Quasi-experiment
Line 31: Line 40:
  
  
-How can we frame a feasabulity study, or pilot project as an experiment? How does it help?+How can we frame a feasibility study, or pilot project as an experiment? Is it more, or less than an existence proof? How does it help?
  
 Replicability [...] Replicability [...]
  • marine_colab/what_is_an_experiment.1431080381.txt.gz
  • Last modified: 2015-05-08 10:19
  • by maja