Uploaded December 2014 | Updated November 2026, 1 day ago
In this video, I conclude my discussion about some of the things I do to prepare for a new tutorial series.
Here's an overall summary of the process, based on both this video and the last one:
- Have a clear initial goal, and a map of what you need to do to achieve it. (Doesn't have to be a physical map; it can just be a mental map of what's needed to get there)
- Start testing parts of your goal for feasibility. If they're too cumbersome or far-reaching, you may need to rethink your goal.
- Once you've tested "enough," start creating a tentative architecture for how everything is going to fit together. (The architecture can be a traditional code architecture if it's a programming topic, but it can also just be a mental "big picture" of how all the parts of your goal fit together, interact, and affect one another)
- Test the architecture. Does it actually work? Do things fit together differently than you initially thought?
- Using the architecture, start figuring out new parts of the goal. This should be relatively easy, since you're mostly seeing how the new things fit in the existing architecture. In other words, adding something to an existing an idea is easier than figuring out a new idea.
- See if the architecture still works. If some things aren't working out too well, you may need to rethink and adapt it a bit.
- Repeat the previous 2 steps until the goal is completed.
In this video, I conclude my discussion about some of the things I do to prepare for a new tutorial series.
Here's an overall summary of the process, based on both this video and the last one:
- Have a clear initial goal, and a map of what you need to do to achieve it. (Doesn't have to be a physical map; it can just be a mental map of what's needed to get there)
- Start testing parts of your goal for feasibility. If they're too cumbersome or far-reaching, you may need to rethink your goal.
- Once you've tested "enough," start creating a tentative architecture for how everything is going to fit together. (The architecture can be a traditional code architecture if it's a programming topic, but it can also just be a mental "big picture" of how all the parts of your goal fit together, interact, and affect one another)
- Test the architecture. Does it actually work? Do things fit together differently than you initially thought?
- Using the architecture, start figuring out new parts of the goal. This should be relatively easy, since you're mostly seeing how the new things fit in the existing architecture. In other words, adding something to an existing an idea is easier than figuring out a new idea.
- See if the architecture still works. If some things aren't working out too well, you may need to rethink and adapt it a bit.
- Repeat the previous 2 steps until the goal is completed.










