https://lekb.org/index.php?action=history&feed=atom&title=Design_experiments 2026-04-28T16:12:55Z Revision history for this page on the wiki MediaWiki 1.41.0 https://lekb.org/index.php?title=Design_experiments&diff=117&oldid=prev 2024-02-09T00:10:17Z

<p>1 revision imported</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <tr class="diff-title" lang="en"> <td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 00:10, 9 February 2024</td> </tr><tr><td colspan="2" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div> </td></tr></table>

Drriel https://lekb.org/index.php?title=Design_experiments&diff=116&oldid=prev 2023-06-16T00:52:12Z

<p>Created page with &quot;A &#039;&#039;&#039;design experiment&#039;&#039;&#039; is a <a href="/index.php/Analysis_method" title="Analysis method">method</a> for the continual development and testing of an <a href="/index.php/Educational_product" title="Educational product">educational product</a> to hypothesize, test, and improve the product &#039;&#039;while it is being used&#039;&#039;. Design focuses on &#039;&#039;<a href="/index.php?title=Iterative_Design_Process&amp;action=edit&amp;redlink=1" class="new" title="Iterative Design Process (page does not exist)">iterative cycles</a>&#039;&#039; to continually test and improve (1) the product itself, (2) participation with the product to match expectations, and (3) <a href="/index.php/Learning_objectives_and_outcomes" title="Learning objectives and outcomes">achievement and outcomes</a> from the product....&quot;</p> <p><b>New page</b></p><div>A &#039;&#039;&#039;design experiment&#039;&#039;&#039; is a [[Analysis method|method]] for the continual development and testing of an [[educational product]] to hypothesize, test, and improve the product &#039;&#039;while it is being used&#039;&#039;. Design focuses on &#039;&#039;[[Iterative Design Process|iterative cycles]]&#039;&#039; to continually test and improve (1) the product itself, (2) participation with the product to match expectations, and (3) [[Learning objectives and outcomes|achievement and outcomes]] from the product.<br /> <br /> == Definition ==<br /> &#039;&#039;&#039;A design experiment&#039;&#039;&#039; is a [[Analysis method|research methodology]] that uses an actual educational product to test [[Learning theory|theory]], hypothesize how things work, and investigate how and why people use the product to achieve the desired goals. <br /> <br /> In a design experiment, the product or [[learning environment]] is continually modified or &#039;&#039;iteratively changed&#039;&#039; to see how minor changes to the product subsequently alter the [[Behavior of the learner (KAB)|behaviors]], [[Attitudes and affect of the learner (KAB)|attitudes]], and structure of the experience. Designers and researchers ask [[Research question|research questions]] related to how and why certain [[Design feature|design features]] lead to different interactions by participants.<br /> <br /> == Additional Information ==<br /> In a design experiment, the design team makes hypotheses as to why they think that elements of design may influencing how people interact and learn with the product. These hypotheses typically examine (1) the specified procedures of the learning experience, (2) the design specifications of media and technology, or (3) the look and feel of the learning environment. By making small changes to any of these elements &#039;&#039;while the product is being used&#039;&#039;, the design team can see if any changes in [[participation]] occur, as well as [[Learning objectives and outcomes|learning]] if the team uses [[Formative assessment|formative evaluation methods]].<br /> <br /> Participation changes are a primary indicator of how learning might be influenced by changes to the product or environment because a person&#039;s involvement and engagement with the product is the first level of the product having any effect. If a person does not interact with the product, a designer can safely assume that the product had no effect. Furthermore, participation with or use of a product is more readily measurable with today&#039;s [[Analytics, monitoring, and data capture (EdTech)|digital analytics]] tools, especially within digital environments that can capture participation data unobtrusively without bothering the participant to take an assessment or survey.<br /> <br /> As such, investigating [[Usage pattern evaluation|participation levels and patterns]] is a good immediate step and source of evidence for design experiments that are actively being implemented in real world settings. This is especially the case when there is little time for conducting summative assessments after every small change or iteration is made to the product. <br /> <br /> How to conduct design experiments are beyond the scope of this page. However, the initial concepts for a design experiment can be planned if the research team embraces the idea of making multiple small-level changes to the product while it is being used to improve the user experience, as well as test hypotheses as to how and why the product is being used. <br /> <br /> In the education field, projects that are based on design experiments are often called &#039;&#039;&#039;design-based research&#039;&#039;&#039; &#039;&#039;&#039;(DBR)&#039;&#039;&#039;. When using DBR, the entire project is organized around the principles of rapid iterative design and testing hypotheses to generate understandings about how and why people interact the way they do. As such, DBR and design experiments are a useful tool for better understanding how [[Learning theory|learning theories]] work in practice, as well as for refining existing theories and even generating new theories of learning.<br /> <br /> == Tips and Tricks ==<br /> <br /> * Consider how you might have the resources to make small improvements and changes to your [[educational product]] or [[Learning experience|experience]] while it is actively being used. How might you handle this without too much disruption or downtime of the product?<br /> * Think about how you or the design team might generate hypotheses about how and why people are or are not using the product to your level of expectation. Consider the [[Learning theory|learning theories]] that your product uses to predict why people will benefit from its use. Also consider other environmental, psychological, or interpersonal factors that might be arising during the use of your product.<br /> * If you would like to consider using design experiments or DBR, set aside specific times for your team to review the logs and participation levels of the learners so that you may regularly how people are using it at expected levels. During this time, generate questions and hypotheses as to &#039;&#039;why&#039;&#039; people are or are not using features as you would expect them to. Then, consider changes to the environment that might influence a change in participation. <br /> * After learners are done with your product, consider summative assessments that survey or interview them specifically on the changes that were done to the environment while they were using it (as a part of the iterative improvements in the design experiment). It would be particularly useful to ask participants to reveal their perceptions about the change and what they remember from their experience as to how these changes to the product influenced their behavior.<br /> <br /> == Related concepts ==<br /> <br /> * [[Iterative Design Process]]<br /> * [[Research question]]<br /> * [[Analysis method]]<br /> * [[Evaluation and assessment]]<br /> <br /> == Examples ==<br /> None yet - check back soon!<br /> <br /> == External Resources ==<br /> None yet - check back soon!</div>

Drriel