One key, then the next, in an even beat. Eyes on the screen.
The big ideaFixing a mistake costs more than a slow key. Speed grows by itself later.
How it works
Slow and right beats fast and fixing. A mistake costs more than a slow key.
To fix one slip you stop, go back, erase it and type it again. That is a lot of extra steps for one little slip.
Find a pace that is slow and steady. Press one key, then the next, in an even beat, with your eyes on the screen.
Let each finger land before the next. Speed is not something to chase.
What one slip costs.
Example 1: Type salad slowly
Look at the screen, not at the keys.
Type s, then a, then l, then a, then d, one key after another.
Let each finger land before the next.
Nothing to fix.
Salad uses S, A, L and D.
Example 2: Fast and fixing
Hit the keys as hard and fast as you can.
Letters go missing, doubled or out of order.
Stop, go back, erase and type again, again and again.
The card takes far longer than it would have done slowly.
Example 3: A steady beat
Press one key, then the next, in an even beat.
Keep your eyes on the screen.
If a key is off, tap backspace, and carry on slowly.
Words to know
steady
Even and calm, one key after another.
muddle
A mess of missing, doubled or out-of-order letters.
pace
How fast or slow you type.
Watch out
Hitting the keys hard and fast makes more slips, and fixing them costs more.
Looking at the keys instead of the screen lets slips hide.
Do not chase speed. Careful, steady keys are the goal.
Backspace is for a key that is off. A slow pace needs it less.
Try it
Which costs more, a slow key or fixing a mistake?
What is the best beat while you learn?
Do fast fingers never make mistakes?
Where do your eyes go while you type?
Answers: 1. Fixing a mistake · 2. A slow, steady beat · 3. No · 4. On the screen
Try at homeNext time you type something, go slowly with your eyes on the screen. Count how few times you need backspace, because slow and right wins.
For grown-upsPraise careful, steady typing and the number of lines with nothing to fix; never count words or time them, and let your child decide how many times they needed backspace.
Open these notes on screenScan the code, or go to tutorpip.com.