Design-Experiment-Capture: Close Your Knowledge...

Design-Experiment-Capture

Even the best of us will devolve into Build-Test-Fix cycles when there is no structure to the learning phases of our projects. It's our default way of working when we're trying to bring something new into existence. We give the idea a try, and then we start refining it until it works.

But it's not a very efficient way to learn, because we're doggedly pursuing one path instead of looking for alternatives.  Eric Ries attempted to improve on Build-Test-Fix with Build-Measure-Learn, which at least frames each build as a learning experiment, and it's not a bad alternative for software / IT products that can be build from the beginning.

But if we're working in the physical world, then we may have a lot to learn before we can build anything.  And building a full physical prototype may not be the most effective way to learn.  In that environment, we need to be a lot more careful about the experiments that we run.

This week's Knowledge Brief describes the three steps we need to close Knowledge Gaps:  Design an experiment, run the Experiment and then Capture the things you learned.

Key Takeaways

  • Build-Test-Fix mode is our default mode for product development - it’s the most intuitive process even though it does not lead to good results and takes a long time.
  • Design-Experiment-Capture summarizes the process for closing a Knowledge Gap scientifically and permanently.
  • LAMDA and other problem-solving methods based on the Scientific Method can enrich this process to build better experimental designs.

 

Design-Experiment-Capture: Close Your Knowledge Gaps Scientifically and Permanently

Design-Experiment-Capture-Letter.pdf

Design-Experiment-Capture-Tabloid.pdf

 

 

This Knowledge Brief may be freely distributed without modifications in its original PDF form, including all authorship, copyright and contact information. Other uses require our explicit permission.

 

posted Jul 5, 12:58 am (746 days ago)