One of the things that enabled the software revolution is the speed of iteration. When your product is made of code, you just type a few new characters, and your changes are live.
If you were designing a new tv, for example, you might have to submit design specifications to a factory overseas, wait two weeks for production and a month for shipping. Once the prototype arrives at your office and you discover what tweaks need to be made, you enter another 6 week process of waiting for the next iteration.
Similarly, when you’re piloting a new curriculum for a school, you get to test it once per year. If you’re lucky, you can try once per semester, but either way, you’re stuck waiting for the next period of time to try out a new idea.
The feedback to time ratio in education and manufacturing is small, especially when compared to that of software. You want to get as much feedback in as little time.
When the team from Google Ventures developed a process to help companies innovate, they knew they wanted to be able to iterate quickly. This led them to hosting 5 day sprints. Their experiences would be contained in a set amount of time, and then they could debrief and tweak to prepare for the next one. This means they’re getting in 4 iterations every month! By the end of the year they could have done 40+ iterations. An experienced teacher might not get 40+ iterations of a class in their life.
Iterate more. Especially when you’re young and new. Get feedback quickly and try again soon.