How to Design a Typing Curriculum: Goals, Practice, and Assessment

By Evan

To design a typing curriculum for adult beginners, start with a task they need to complete, identify the keys and actions it requires, and build practice toward that task. Decide what you will observe when they try again with different text. This gives each lesson a purpose and helps you respond when completing an exercise does not carry over to everyday typing.

This guide is for teachers and course designers planning instruction on a physical keyboard. It develops a contact-card task from an initial observation through four teaching encounters, a later assessment and a completed planning record. The route and learner responses are constructed examples, not a tested Typekute sequence or results from a real learner.

Plan your route with the one-page worksheet.

Start with a task the learner actually needs

Ask what the learner wants to do: fill in a form, send a message, enter a reference number, or work with a document. “Improve typing” leaves too many decisions open. “Enter a name and email address, then correct a typo” identifies skills to teach and suggests an appropriate check.

Define an observable outcome

My example outcome is to enter a supplied contact card accurately, use Shift for capitals, and correct a final-letter typo without deleting the entire entry. The learner can read the card throughout. Composing an email needs a separate observation: choosing words and expressing an idea adds a writing task beyond copying text.

Include functional actions when the task needs them. Northstar’s Basic Computer Skills standards include knowledge of Shift, Enter, Backspace, Delete, arrow keys and Tab. This is a scope reference for adult digital skills, not a prescribed lesson order.

Write the task, conditions and observation together: “Given a new card and the same keyboard, the learner enters its details, checks the result and corrects a typo using the taught action.” You now know what to look for beyond a completion badge.

Identify the learner’s starting point and keyboard

Check what is already comfortable

Ask the learner to enter a familiar name, a short number and a lowercase word at a manageable pace. Observe pauses, key searching, responses to mistakes and use of the screen. Ask what felt difficult instead of diagnosing the cause from speed alone.

If lowercase letters are comfortable but capitals interrupt the task, focus on Shift and its transitions. If most letters require searching, narrow the first activities. If the supplied text is hard to read, adjust that condition before interpreting difficulty as a keyboard problem. Keep a record of the starting task for later comparison.

Make the initial observation change the plan

In my constructed starting record, the learner copies anna lee accurately without help, enters Anna Lee as anna lee, and cannot yet find @. When asked to repair Annx|, they delete the whole word and retype it. The card remains visible; no speed target is imposed.

This record does not say “poor at typing.” It identifies three different teaching needs: case control, symbol entry and a local correction. Retyping shows that the learner can obtain the right word, but not yet that they understand the requested repair. Because lowercase entry is already usable in this example, repeating an entire alphabet course would not address the main gaps first.

For a different learner who searches for A, L and E, keep the same eventual goal but begin with those letters and Space. For someone comfortable with symbols but new to this application, teach the field and cursor behavior rather than adding more symbol drills. The starting observation determines the route; the route should not force every learner to repeat identical preparation.

Declare the layout and device

The worked examples use a physical US QWERTY keyboard with English input. On that layout, @ uses Shift and 2; another layout may need a different combination. Check the actual layout before assigning symbols. A phone’s on-screen keyboard needs different instructions.

Ask about the learner’s usual device and input method, including adapted controls or accessibility tools they use. Build the route around that task and method. A single score does not tell you whether a different technique or input method would suit them.

Turn the outcome into prerequisites

Work backward. Anna Lee needs letters, Space and capitals. [email protected] adds symbols. Correcting a typo needs an understood cursor position and editing action. Introduce these requirements before combining them.

A learner may already know some components; another may need more work before combining them. Unexpectedly adding an unfamiliar symbol makes it hard to tell whether the intended skill or the new requirement caused the difficulty. The route above is a design choice based on these dependencies, not a universal scientific sequence.

Give each practice activity a different job

Give the learner a task, watch what happens, and use that response to choose the next task. The four encounters below are an illustrative arrangement, not a four-session completion promise. An encounter can need another visit; a learner who already demonstrates the action can skip its introductory practice.

Turn an error into a specific revision

Suppose the constructed response in encounter1 is a A A A. The observer sees Shift remain held after the first capital. “Repeat the exercise” is underspecified. Demonstrate the release, return to A a, and have the learner explain the change while doing it. Then return to Anna, where release must occur after its first letter. The recheck asks whether the troublesome transition now happens, not whether the learner completed more screens.

If the output is uppercase but the action was Caps Lock, the text alone cannot establish a Shift objective. Conversely, Caps Lock may be a reasonable method for a task needing a long uppercase label. Teach the method the intended task requires; do not treat a different valid method as failure at all keyboard use. The Shift and editing guide supplies additional action examples.

Choose between a controlled pattern and an application task

The pattern a A a A makes one change easy to inspect, but says little about symbols or word spacing. The name task adds real transitions, but a misspelled name can hide which transition needs attention. Use the pattern to isolate the suspected issue and the name to see whether the action remains usable when combined with familiar letters.

Dhakal and colleagues’ 2018 observational study found that certain letter-pair timings were more predictive of typing speed than letter repetitions. This gives a reason to inspect combinations rather than count isolated entries alone; it does not validate the sequence above. Choose activities by the difficulty they reveal. The exercise-selection guide develops that choice.

Build review and later checks into the route

Reserve a place to return in another session. In Baddeley and Longman’s 1978 experiment, postal workers learned alphanumeric typing on typewriters under four schedules. The once-daily, one-hour group learned most efficiently in training time. This supports considering practice across sessions; it does not identify an ideal short browser-session length.

Revisit capitals during the next suitable session, then use a different contact card. This is a proposed teaching arrangement. Adjust the amount of work around the learner’s circumstances and observed difficulties, rather than turning the experiment’s one-hour condition into a requirement.

Change the text without introducing unlearned requirements

A later card might use Lena Allen and [email protected] if those letters are already taught. Keep the layout and task type comparable. Record changes in help, length and text difficulty: a harder card can affect performance for reasons unrelated to forgetting Shift.

The learner still sees the card, so this is fresh transcription, not free recall. It gives you another observation of the skill in changed text. See repetition, review and fresh text for a routine you can adapt.

Keep the later check comparable enough to interpret

The fresh name is not enough by itself. Keep the same keyboard, visible card, help rule and task instructions. Note that Lena Allen is not identical in length or transitions to Anna Lee; this is a classroom observation, not a controlled estimate of a training effect. If you also switch to a phone, hide the card and introduce a number, you will not know which change accounts for difficulty.

Use a staged change when the real application is broader. First revisit the familiar task with new text; then try it in the actual form. A learner who succeeds in the editor but types into the wrong form field needs application/navigation support. Sending them back to a capital-letter drill would address a different problem. Do not put real personal details into a public exercise; use supplied example data.

Measure the outcome you promised

Typing: speed and errors under stated conditions

Record the text, keyboard, help and timing conditions. If speed matters for the goal, use the same measurement method on comparable tasks. Note mistakes during entry and errors remaining afterward; a speed score cannot show the quality of an email’s content.

Two illustrative attempts both finish with Anna. One enters it correctly immediately; the other enters Annx, presses Backspace and types a. The second includes a mistake and repair. Soukoreff and MacKenzie’s 2003 text-entry metrics paper distinguishes corrected errors from errors left in the text.

Respond to the observation: repeated Shift-transition errors suggest revisiting that transition; accurate entry with frequent help suggests trying with less help. Successful use on a later comparable card supports moving to a broader task. It does not establish competence in every keyboard action.

Editing: text, cursor, selection and actions

Specify the starting state and action. In Annx|, the bar represents the cursor, not a character to type. After Backspace and a, expect Anna|. If the goal is Backspace at the end, this fits. A typo in the middle needs a different task.

Retyping the whole word can produce correct text while leaving the specific editing objective unobserved. Record that distinction without treating the workaround as failure at every aspect of typing.

Use an assessment record that tells you what to teach next

The completed record below is hypothetical. Each row answers a different question, so there is no combined mastery percentage. “Without help” means no location hint or action demonstration during that attempt; the supplied text stays visible and self-correction is allowed.

If the learner needs assistance, record what it was. “Completed with a reminder to release Shift” is more informative than either a bare pass or a bare fail. Try the comparable action without that reminder later. A classroom readiness decision can use these observations, but a claim that this route is effective for a population would need a study of those learners and outcomes.

Check the curriculum before using it

Try the route yourself. Compare instructions with required input, identify unintroduced keys, check that feedback addresses the intended skill, and find the later check. Verify editing in the actual application rather than relying on its title.

An illustrative finding is: “Shift practice contains only uppercase letters, so it cannot check release between cases. Add alternating case, try the revised task, and inspect the feedback.” This identifies a gap and recheck; it does not prove the rewrite improves learning.

Use the lesson audit checklist for a full review, or the course-standards guide to evaluate claims about alignment and certification.

Put your route on one page

Copy this completed worksheet into your planning document and adapt the task, conditions and decisions to your learners. It separates the route’s three outcomes so that a good score in one does not conceal a difficulty in another.

Before adding an activity, identify which cell it serves. If you cannot connect it to the goal or an observation you need, reconsider its place.

Decide what to leave out of the first route

The example deliberately does not begin with every symbol, a speed challenge or selection shortcuts. Those may matter later, but they add requirements that are not needed to establish the immediate contact-card goal. This is a scope decision, not a claim that narrow instruction is always better. If the learner's real task includes a reference number or a multiline note, those requirements belong in a revised route.

There is a tradeoff between an easy-to-observe task and a realistic task. A short visible card keeps reading and composition demands limited; it also leaves original writing unassessed. An editor makes cursor position easy to inspect; it leaves field navigation unassessed. Keep the small task for the question it can answer, then add the broader application rather than pretending one exercise measures both.

Conclude the route with a practical decision: keep demonstrated actions in normal use, isolate recurring difficulty for another teaching encounter, and teach new application requirements explicitly. Do not keep assigning the entire introductory sequence merely because one component still needs attention.

With your worksheet in hand, explore the available Typekute lessons and compare their tasks with the skills you want to practise. Keep editor-specific application in the application where the learner needs it.

References

• Northstar Digital Literacy: Standards. Basic Computer Skills.
• Baddeley, A. D., and Longman, D. J. A. (1978). The Influence of Length and Frequency of Training Session on the Rate of Learning to Type. Ergonomics, 21(8), 627–635. Full-text copy of the original paper.
• Dhakal, V., Feit, A. M., Kristensson, P. O., and Oulasvirta, A. (2018). Observations on Typing from 136 Million Keystrokes. CHI 2018. Author-hosted study page.
• Soukoreff, R. W., and MacKenzie, I. S. (2003). Metrics for Text Entry Research: An Evaluation of MSD and KSPC, and a New Unified Error Metric. CHI 2003.