Get excited - You don't need to borrow your nephew's ADD medicine, but stay PUMPED throughout the lesson. If it takes a 5-Hour Energy or XL coffee from Dunkin Donuts to do that, go for it. America runs on Dunkin. Good teachers have the energy to teach!
Do over's - If you don't like what you recorded, just start back a few minutes. If you found yourself rambling on about the correct pronounciation of a technical term, just stop recording and edit that out.
Take a break - No one will know if you pause the screencapture software and pee. Or if you sleep for 8 hours and start back again where you left off. Just listen to what you previously recorded so your train-of-thought is consistent, then continue recording.
Combine lots of videos - Your tutorial might end up being 10-20 short videos that need combining together. Unless you are the greatest, most flawless instructor ever, it is doubtful you'll have made a decent tutorial on one take. If you're on the Mac, in Application > Utilities you can find the original (better) version of Quicktime Player 7. You should be able to combine videos by simply selecting all, copying, then pasting. Then you can save the video as a self contained file of everything.
Use notes, not scripts - Reading off a script like a robot is not the CartoonSmart way. Pretend you are teaching a friend.
Notes on the otherhand are a great idea. For example, if you have two monitors and you're teaching a programming tutorial, put the code you are going to teach on the second monitor. It's like a cheat sheet!
Type code. Don't paste it - Unless it's code you've already taught and explained, just type it out. Typing code gives you time to explain, and often times will make you explain things better than if you just pasted in an entire line of code.
Test often - Testing a programming tutorial is key. It gives the student a moment to breath and correct errors. Plus you'll catch any mistakes or typos you made (see below for more on that)
Oops, you made a mistake - Mistakes will happen in a tutorial. Some mistakes are funny if they don't take more than a few seconds to correct and can be used to demonstrate a common error that the student will also run into. Bad mistakes, meaning ones you need to edit out and go back and record again, are ones that involve a lot of backtracking on your part. Because if you have to go back a minute or so in a tutorial, that probably means the student will have lost double or triple that amount of time because they work far slower than you teach.
For you creative types - Like you artists (or arteests). For the less-talented, watching truly talented people draw is like listening to a musician play their instrument. So don't assume you have nothing to teach. Make a masterpiece and talk your way through it. I've seen way too many YouTube videos of talented artists time-lapse an hour or more of work into a 3 minute video that goes by way too fast to understand what they are doing. Those videos suck. Be brave, show your art, have fun, and don't be shy.