Problem Identification & Solving
DigComp 3.0 · Area 5 · 14 min read
Problem-solving is about diagnosing technical problems, identifying the right tools for a need, using technology creatively, and recognising your own skill gaps. It's the meta-skill that lets you keep adapting as technology changes — and the assessment tests your approach, not memorised fixes.
What the assessment checks
- ✓Solving technical problems methodically
- ✓Identifying needs and matching them to the right technological response
- ✓Using digital tools creatively to achieve goals
- ✓Recognising and addressing your own digital competence gaps
Key concepts
Isolate before you fix
Good troubleshooting is detective work: narrow the problem before changing anything. Is it just this device or all of them? Just this website or the whole connection? Just this file or every file? Comparing what's different between a working and a non-working case points you to the cause far faster than randomly trying fixes.
💡 Tip: The test rewards systematic isolation over drastic, untargeted fixes (like reinstalling everything).
Search the exact error
Almost any error message you'll meet has been seen — and solved — by thousands of others. Copying the precise wording into a search is often the fastest route to a fix, far quicker than guessing. Vague descriptions get vague help; exact error text gets exact answers.
💡 Tip: Capture and search the exact error text before improvising.
Match the tool to the need
Identifying needs means defining what you actually need a tool to do before choosing one — then comparing options against those criteria. The flashiest, most popular, or most expensive option isn't automatically the right fit. This applies from picking a to-do app to a team's 'build vs buy' decision.
💡 Tip: Define requirements first, then compare — don't pick by hype or price.
Use technology creatively
Often an existing tool can do more than you think — through its settings, integrations, templates, or automation features. Competent problem-solvers explore and combine tools to remove repetitive work, rather than doing everything manually or buying something new at the first obstacle.
💡 Tip: Before adding a tool, check whether one you already have can be extended.
Own your skill gaps
DigComp explicitly includes recognising your own competence gaps as a skill. The competent response to hitting a wall isn't avoidance or faking it — it's identifying precisely what you're missing and learning it (a short tutorial, asking a colleague, a quick course). This very assessment, and these guides, are an example of doing exactly that.
💡 Tip: Recognising and closing your own gaps is itself a tested competence.
Worked example: a test-style scenario
This is the kind of situational-judgement question the assessment uses. Try to choose before reading the verdicts.
Your team repeats the same manual data-entry task every week and it's eating hours. What's the best response?
Identifies the real need and applies technology creatively to remove repetitive work — the heart of this domain.
Treats the symptom, not the cause; the inefficiency persists indefinitely.
Accepting avoidable waste is the opposite of problem-solving competence.
Common mistakes to avoid
- ✗Jumping to drastic fixes (reinstall everything) before isolating the cause.
- ✗Improvising instead of searching the exact error message.
- ✗Choosing tools by hype or price rather than defined needs.
- ✗Doing repetitive work manually when it could be automated.
- ✗Avoiding or faking a skill gap instead of naming and closing it.
Quick self-check
4 practice questions. Pick an answer to see whether you got it and why. Not scored or saved — just for your own preparation.
1. A website won't load. What's the best first step?
2. You get an unfamiliar error code. Most efficient move?
3. Your team repeats the same manual task weekly for hours. Best response?
4. You hit a skill you don't have for a task. Competent response?
Free resources to go deeper
External, authoritative, free. Opens in a new tab.