By the end of this lesson you will be able to
- Write a question that states the goal, system, steps tried and exact error.
- Create a minimal example that shows a problem without extra detail.
- Keep a personal knowledge base of fixes in a simple, searchable form.
- Decide when a problem needs a professional or the official support channel.
Even a good researcher sometimes cannot solve a problem alone. Then the quality of your question decides the quality of the answer. A vague message such as my computer is broken makes a helper guess; a precise one lets them solve it in a minute. In this lesson you will learn to ask well, to keep your own notes so you never solve the same problem twice, and to recognise problems that are better left to a professional.
What a good question contains
A person who answers a question does not see your screen, your history or your thoughts. They only have what you write. A useful question usually has six parts: what you wanted to do (the goal), the system you use (Ubuntu 24.04 or Windows 11, the program and its version), what you did step by step, what you expected, what actually happened with the exact Error message, and what you have already tried. Writing these down often reveals the answer before you send the message.
- My printer does not work, help
- No system or version
- No error text
- No list of what was tried
The helper must guess
- Goal: print a PDF on Ubuntu 24.04
- Printer says Ready, job stays Pending
- Error: Filter failed
- Tried: restart, remove and add again
The helper can act
Read this figure as text
A comparison of a vague question and a precise question about a printer that will not print.
Two columns. Vague question: the text My printer does not work, help. Missing: system, steps, error, what was tried. The result is that the helper must ask many questions or guess. Precise question: I want to print a PDF from Ubuntu 24.04. The printer is listed as Ready, but the job stays Pending. The error in the print queue is Filter failed. I restarted the printer and removed and added it again. What should I check next. The result is that the helper can suggest a specific next step.
- Marker 1: Start with the goal
- Marker 2: Say what you use
- Marker 3: Steps in order
- Marker 4: Exact message
- Marker 5: What failed already
Read this figure as text
A page with a question template listing goal, system, steps, expected, actual and tried.
A page titled Question template. Marker 1 points to Goal: what I wanted to do. Marker 2 points to System: operating system and version, program and version. Marker 3 points to Steps: what I did, in order. Marker 4 points to Expected and Actual: what I thought would happen and what happened, with the exact message. Marker 5 points to Tried: what I already did and what happened.
Make a minimal example
A Minimal example is the smallest thing that still shows the problem. If a spreadsheet formula gives a wrong answer in a workbook of fifty sheets, copy three cells into a new file and check that the problem still appears. If a command fails, show the one command and its exact output, not the whole session. Making a minimal example has two benefits. The helper sees the problem at once, and you often discover the cause yourself, because removing details removes the confusion.
To capture what you see, use a screenshot of the error window or copy the text. Text is better when you can get it, because helpers can search it and quote it. In a terminal, select the text and copy it. On Ubuntu the terminal uses Ctrl+Shift+C to copy; on Windows Terminal, Ctrl+C copies when text is selected. A screenshot is good for windows, dialogs and settings pages.
Keep your own notes
Everyone forgets. Three months from now you will meet the same problem and remember only that you fixed it once. A Personal knowledge base, in the personal sense, is a collection of short notes about problems you solved. It need not be fancy: a folder of text files or a single document is enough. What matters is that you can find a note later. Name each note after the symptom, as you would search for it, and record the date, system, exact error, cause if known, the fix that worked and a link to the source.
- my-fixes
- 00-how-to-write-a-note.txtThe template
- wifi
- 2025-03-02_wifi-connected-no-internet.txt
- printing
- 2025-04-18_printer-job-pending.txt
- email
- 2025-05-07_cannot-send-attachment-too-large.txt
Read this figure as text
A folder tree of notes, with topics and dated note files named after symptoms.
A folder called my-fixes contains four folders. wifi holds a file 2025-03-02_wifi-connected-no-internet.txt. printing holds 2025-04-18_printer-job-pending.txt. email holds 2025-05-07_cannot-send-attachment-too-large.txt. A file called 00-how-to-write-a-note.txt sits at the top and holds the template. Each file is named by date and symptom so it can be found by searching.
Date: 2025-04-18
Symptom: print job stays Pending, nothing prints
System: Ubuntu 24.04, home printer
Exact message: Filter failed
Cause: printer driver was missing after an update
Fix: removed the printer in Settings and added it again, choosing the driver offered
Source: Ubuntu help pages on printing
Note: took 15 minutes. Test page printed.Use the file naming ideas from the earlier lesson, keep the folder inside a place that is backed up, and never write passwords in the notes. If you like, search the folder with your file manager's search or with grep in a terminal, which finds text inside files. Review the notes once in a while and delete what is out of date.
When to stop and get help
Independence does not mean never asking. Some problems are risky or beyond what you can safely test. It is a sign of good judgement to recognise them. Stop and ask a professional, your school or workplace help desk, or the official support channel in these cases.
- Your data may be lost and you have no backup: stop using the drive, because further use can overwrite what could be recovered.
- You suspect your account or computer has been taken over, or you have given a password to a scam: change passwords from a safe device, and contact the service or your bank through its official number.
- The device is physically damaged, swollen, very hot, smoking or smells of burning: switch it off, unplug it and do not use it.
- The problem involves a work or school device that someone else manages: ask the help desk, because your changes can break policies.
- A fix needs risky steps that you do not understand, such as repartitioning a disk or editing system files.
- You have spent a long time and made no progress: a fresh pair of eyes often finds it in minutes.
- Risk of data loss, a security breach or physical danger?
- YesDo thisStop. Contact a professional, your help desk or the official support channel.
- NoHave I read the docs and searched the exact error?
- YesStill unsolved after a fair try?
- YesDo thisWrite a precise question and send it to a help desk, trusted community or knowledgeable friend.
- NoDo thisWrite the fix in your notes so you can find it next time.
- NoDo thisRead the official pages and search the exact message.
- YesStill unsolved after a fair try?
Read this figure as text
A decision tree for deciding between continuing alone, asking a community, and getting professional help.
Start: Is there risk of data loss, a security breach or physical danger? If yes, stop and get professional or official help now. If no: Have I read the documentation and searched the exact error? If no, do that first. If yes: Is the problem still unsolved after a fair try? If no, record the fix in the notes. If yes, ask a precise question to a help desk, a trusted community or a knowledgeable friend.
Common mistakes
✖ Instead of: Sending a message that says only that something does not work.
✔ Do this: State your goal, system, steps, the exact message and what you tried.
✖ Instead of: Sending a screenshot of a whole desktop with emails and private details visible.
✔ Do this: Crop or copy only the relevant text, and remove private details first.
✖ Instead of: Solving a problem and not writing it down.
✔ Do this: Write a short dated note named by symptom, with the fix and its source.
✖ Instead of: Carrying on with experiments on a drive that is failing or a suspected hacked account.
✔ Do this: Stop, protect what you can, and get professional or official help.
If something goes wrong
- I cannot reproduce the problem to write the steps.
- Write what you remember, say that it is intermittent, and note when it happened. Next time it appears, copy the exact message before doing anything else.
- I cannot find my old notes.
- Search the folder for a word from the symptom. Rename files by date and symptom, and keep the notes in one folder that is backed up.
- Nobody answers my question online.
- Check that it is complete, short and in the right place. Add details you left out, and try the official support channel or a local person who can see the device.
- I am not sure whether a problem is serious.
- If it involves your money, accounts, important files or physical danger, treat it as serious and use an official source or professional help. You can always ask a trusted person.
Key terms
- Minimal example
- The smallest set of steps or the shortest code that still shows a problem.
- Personal knowledge base
- Your own organised collection of notes about problems you solved and how.
- Error message
- A message from the computer or program that says something went wrong and often where and why.
- Naming convention
- An agreed pattern for naming files so they are easy to find and sort.
Practise it for real
Reading is not the same as being able to do it. Complete these on your own computer, then tick only what you have actually done. These ticks are your own honest record: nothing checks them for you.
Write a question and a note
Choose a small problem you had recently, for example a slow start-up or a document that would not print. Write a question about it using the template: goal, system, steps, expected, actual with the exact message, and what you tried. Remove private details. Then create a folder called my-fixes in your practice folder, add the note template file, and write the fix as a note named by date and symptom.
Challenge: rescue a bad question
Take this vague message: Excel not working, help. Without any other information, write a list of at least six things a helper would need to know. Then invent realistic details for a made-up case and rewrite it as a precise question. Finally, write two situations from daily life in which you would not keep trying alone but get help.
Knowledge check
6 questions. You need 80% to pass. Mistakes here are part of learning, and you can retry as often as you like.
Summary
- A good question has a goal, system, steps, expected result, exact message and what was tried.
- A minimal example removes everything that is not needed to show the problem.
- Remove private details before you share any text or screenshot.
- A personal knowledge base of dated notes saves you from solving a problem twice.
- Stop and get help when there is a risk to data, security or safety.
Checklist: can you do these?
Marking a lesson as read does not prove you can do it. Skills count as demonstrated when you pass the quiz (not yet) and complete the practical tasks (not yet).
Related lessons
References and further reading
Official sources for details that can change between versions.
- How do I ask a good question? (Stack Overflow)
- Top tips for staying secure online (UK National Cyber Security Centre)