My two most recent posts focused on my passion for engaging K-12 learners and my beliefs that Flow Theory might be a way to better engage them. While time and research may reveal that Flow Theory is a Most Valuable Player in planning K-12 instruction, the MVP in the title of this post refers to a different MVP - the Minimum Viable Product. According to Eric Ries, the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. Another way that Ries defines the minimum viable product is as the smallest thing you can build that lets you quickly make it around the build/measure/learn loop. This blog post is about the minimum viable product (MVP) for Flow Learning.
The minimum viable product for Flow Learning is presenting the application of Flow Theory to students and teachers in the field to see if they have a need or interest in the product. I have already done this to a small sample of teachers and students, and the results are presented in my previous blog post. Presenting these ideas allowed me to test my ideas in the smallest format that could still provide me with valuable feedback for learning. What I learned from this step of the feedback loop is detailed in my previous blog post, so I want to focus on the next step in this blog post.
The next step will be to take what I learned from the results mentioned above and use them to modify my ideas to create a theory-based framework for Flow Theory that can be immediately applied to planning K-12 learning units or modules. One of the challenges to creating this MVP would be making the framework applicable to a K-12 instructional unit. In order for the application of Flow Theory to work effectively, teachers or curriculum designers would need a tool that allows them create a list of activities that will personalize learning to their students, so that students’ learning activities match their ability levels (see the image below from a previous post). The best tool for this is likely a learning management system (LMS) such as Canvas, but then students will also need to have devices that allow them to access content on the LMS. Instead of looking to create a context in which I need to add device access and LMS access for all students, it would be best to measure Flow Learning in a context that already has one-to-one devices and utilizes an LMS. I would also want to test my MVP with a small group of students and teachers so that I can get to know them well enough to understand how Flow Learning can best meet their individual learning and pedagogical needs.
Selling Flow Learning in the Bazaar
Because the idea of implementing Flow Theory depends on meeting the needs of many different users, i.e., students and teachers in different contexts, one of the methods for developing the theory-based framework is to work out its development using the bazaar model made famous by Linus Torvalds in developing Linux. In reading Raymond’s (2000) The Cathedral and the Bazaar (CatB), I discovered many useful tips in how to make the process of testing the MVP effective and beneficial. One of the most important lessons I learned from CatB is that developers “don’t really understand the problem until after the first time [they] implement a solution. The second time, maybe [they] know enough to do it right. So if [they] want to get it right, [they should] be ready to start over at least once.” This idea enforces the need to get the MVP to consumers quickly so I can learn more about the problem I am really trying to solve.
The next idea from CatB that will influence how I test and develop Flow Learning is to treat users as co-developers because doing so comes with many benefits. First, when developers treat their users as co-developers then users can assist in creating rapid improvements for the MVP. Second, incorporating more users in the development process helps in finding more ways and different ways to tease out problems with the product. Third, CatB suggests that if early testers of a product are treated as a developer’s best resource, they will become the developer’s best resource. Teachers have such little time to begin with, so I need to make sure that any time they offer to give me is valued as well as their opinions. Doing so will allow teachers and their students to provide valuable input in redesigning and updating the MVP. Lastly, in valuing beta-testers I will also benefit from their good ideas. According to Raymond (2000), “the next best thing to having good ideas is recognizing good ideas from your users [and] sometimes the latter is better.”
In an earlier post, I stated that in order test my theories on the usefulness of Flow Theory to K-12 instruction, I needed to test my ideas with others. Upon doing so, I have found that there is demand for a program that helps implement Flow Theory into K-12 classrooms. The next step in testing Flow Theory in the classroom is to create a minimum viable product. With such a product, I can allow users to test the product and provide me with feedback. Such feedback can be used to improve the product for re-implementation and testing. One of the keys to product development is to quickly complete the feedback loop. Choosing testers who can provide valuable feedback will help make quick improvements to the product, as well as help identify the problems that need to be solved both by and within the product. Developing the MVP is the next step towards discovering how components of Flow Theory, e.g., matching difficulty of skill and providing frequent feedback, affect a student’s learning.
This blog presents thoughts that Cecil has concerning current projects, as well as musings that he wants to get out for future projects. For questions or comments on his posts, please go to his Contact page.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.