DGB 1: Help Systems and Troubleshooting

← Digital Literacy – Year 1

Help systems provide support when users need to understand a function or solve a technical problem. Good troubleshooting begins by describing the problem clearly, reading available information and changing one thing at a time rather than trying random solutions.

Curriculum reference

Area	Classification
Competence area	Action
Focus	Using help systems to solve problems
Competence	Use built-in and external help resources systematically and safely to solve simple technical problems.

Learning objectives

Students can:

explain what a help system is;
distinguish help menus, search fields, tooltips, FAQs, tutorials and error messages;
find an appropriate help function in an application;
describe a technical problem in a few clear words;
formulate suitable search terms using the problem, program and error message;
follow step-by-step instructions carefully and in order;
test one change at a time and observe the result;
distinguish trustworthy help resources from risky download or scam offers;
document a successful solution briefly;
recognise when support from a teacher, administrator or another responsible person is required.

Learning content

What are help systems?

Help systems are support resources in programs, operating systems or online services. They explain functions or help users deal with errors. They include built-in help pages, search fields, question-mark icons, tooltips, FAQs, assistants and tutorials.

In some programs the F1 key opens help, while in others it does not. It is therefore more important to understand the idea of built-in help than to memorise a single key.

Tooltips and short hints

When the mouse pointer is placed over an icon, many programs display a short explanatory text. These tooltips describe the function of a button without requiring a long manual to be opened.

Information boxes, highlights and short hints directly in an interface can also be part of a help system.

Read error messages

An error message is not only an obstacle; it is often an important clue. Before closing it, read the text. The program name, error code or exact wording may later help when searching for a solution.

Personal data, passwords or secret keys must not be copied into public forums or search engines.

Describe the problem clearly

The statement “It doesn't work” provides little useful information. A clearer description might be: “In Writer, the file cannot be exported as a PDF; during export the following message appears: …”.

A useful problem description answers: What was I trying to do? What actually happened? What message appeared? When did the problem begin? What have I already checked?

Work systematically

A simple troubleshooting process can be:

Describe the problem precisely.
Read the error message.
Check obvious basics such as connection, file, volume or selected device.
Search the built-in help.
If necessary, search a trustworthy source using suitable terms.
Try one understandable proposed change.
Test the result.
Undo the change if it did not help and this is possible.
Document the solution or ask the responsible person for support.

Changing several unknown settings at the same time makes troubleshooting more difficult.

Choose useful search terms

Useful help searches combine the program or device, the intended function and the symptom. An exact error message can be placed in quotation marks if it contains no personal information.

For example, `Windows printer queue paused` is more informative than `printer does not work`.

Assess help resources

Not every instruction on the internet is correct or current. Official documentation, recognised educational resources and sources with an identifiable author or provider are generally easier to assess.

Be cautious with pages that demand unknown software as the “solution”, ask users to disable security functions without explanation or request passwords or payment information.

When should you ask for help?

Permissions on school devices may be intentionally restricted. Administrator rights, security software and network settings should not be bypassed. If a solution requires such rights or could put data at risk, the responsible teacher or IT administration should be consulted.

Independent problem-solving also means recognising one's own limits.

Document solutions

A short troubleshooting record containing the problem, cause, solution steps and result can save time later. In a team, it can also help others solve the same problem more quickly.

Only necessary technical information should be recorded, never passwords or private data.

Classroom activities

Find a help function

In a familiar school program, an unfamiliar function is to be found using built-in help.

Task: Search, for example, for “insert image”, “line spacing” or “save as PDF” and follow the instructions using a practice file.

Expected outcome: Independent use of built-in help.

Analyse an error message

A prepared, harmless error message is examined.

Task: Identify the program name, error clue and important keywords. Use them to formulate a precise help search.

Expected outcome: Turning an error message into a useful search query.

Improve a help search

Task: Replace vague searches such as “computer broken” with queries containing the program or device, the desired action and a clear symptom.

Follow a troubleshooting path

Task: Work through a prepared technical problem one step at a time. Record each check and its result instead of changing several settings at once.

Write a short troubleshooting record

Task: Document the problem, likely cause, solution steps and result of a completed exercise without including passwords or personal data.

Self-check

I can find and use built-in help.
I read error messages before dismissing them.
I can describe a problem clearly.
I can formulate precise search terms for technical help.
I test one change at a time.
I can assess whether a proposed solution is trustworthy and safe.
I know when to ask a responsible person for help.