Skip to main content

🧠 Lesson 4.2: Information Literacy & Problem-Solving at Work

Two digital skills will serve you for your whole career, in any job: judging whether online information is trustworthy (information literacy) and calmly solving everyday tech problems and learning new tools on your own. The internet hands you an ocean of information — some of it excellent, some of it wrong, some of it deliberately misleading. And every worker, no matter how experienced, runs into things that freeze, error out, or simply don't behave. The good news: both are handled with skills you can learn, not with panic or luck. This lesson gives you a calm, repeatable way to think before you click, and to fix before you fret.

🎯 About this course

This course builds Northstar-aligned digital skills; the official Northstar assessment/certificate is earned separately at sponsoring sites (many libraries and programs offer it free). Software and menus vary by product and version, so we focus on transferable skills and general steps — the exact menus differ, but the habits in this lesson work everywhere. As always, practice on a real computer when you can.

📚 What You'll Learn

By the end of this lesson, you will be able to:

  • Judge whether an online source is trustworthy — who published it, whether it's current, why it exists, and how to verify it
  • Spot misinformation, fake news, and AI-generated or altered content, and lean on reputable, official sources
  • Follow a calm, step-by-step troubleshooting process for common tech problems
  • Teach yourself new software using menus, Help, searches, and short tutorial videos
  • Ask for help well — giving clear details that get problems solved fast

⏱️ Estimated Time: 50 minutes (go at your own pace — there's no clock on you)

🎯 Project: Add a "My Info-Literacy & Troubleshooting Guide" page to your "My Workplace Digital Toolkit" — your own source-check questions and troubleshooting steps.

In This Lesson

Think, Don't Just Click

The internet is the most powerful information tool ever built — and that's exactly why it needs a thoughtful user. A search returns thousands of results in an instant, but the computer doesn't sort them by truth; it sorts them by relevance, popularity, and sometimes by who paid to be there. Some of what you'll read is accurate and helpful. Some is out of date, some is trying to sell you something, and some is simply false — occasionally on purpose. The skill isn't reading faster; it's pausing to think before you trust or share.

Tech problems are the other half of this lesson, and they follow the same spirit. A program freezes, a file won't open, the internet drops, a screen shows an error you've never seen. In the moment it can feel like you did something wrong — but these things happen to everyone, every day, including experienced professionals. What separates a confident computer user from a panicked one isn't that problems never happen to them; it's that they have a calm, simple process for working through them.

Both of these are learnable skills, not personality traits or luck. You don't need to be a journalist to check a source, and you don't need to be an IT technician to fix the most common problems. This lesson gives you a repeatable method for each — and building your good judgment here also protects the professional reputation you worked on in Lesson 4.1.

🧠 Mindset

Information literacy and problem-solving are learnable — and once you have them, they make you genuinely self-reliant and valuable. An employee who can tell a reliable source from a shaky one, and who tries a few sensible fixes before raising a hand, is someone a workplace trusts. You will not always know the answer — nobody does — but you can always know how to find it and how to work a problem calmly. That confidence is worth more than any single fact. 🌱

Evaluating Online Information

When you find something online — a health claim, a "fact," a how-to, a news story — run it through a few quick questions before you believe it, act on it, or forward it to a coworker. You don't need all day; even ten seconds of checking catches most bad information.

  • Who published it? (Authority) Is there a named author, organization, or institution behind it — and do they actually know this subject? A government agency, university, established news outlet, or professional body carries more weight than an anonymous post or a random blog with no author.
  • Is it current? (Currency) Look for a date. Information about laws, benefits, prices, technology, and health changes over time; a confident-sounding article from years ago may simply be out of date.
  • Why does it exist? (Purpose) Is it trying to inform you, or to sell or persuade you? An article that exists to sell a product, push an opinion, or get outraged clicks may bend the facts to do it. Ads and "sponsored" content are persuasion, even when they look like news.
  • Can you verify it elsewhere? (Verification) This is the most powerful check of all. Do other independent, reputable sources say the same thing? If a claim appears only in one place — especially a surprising or alarming claim — treat it with real caution.

These questions build directly on the safe-browsing habits from Lesson 1.3 (checking the web address, noticing secure vs. unofficial sites, avoiding scams). There, the focus was staying safe; here, it's staying accurate. Together they make you a sharp, careful reader of the whole internet.

Spotting misinformation, fake news, and altered content

Some false information is an honest mistake; some is deliberately designed to fool or provoke you. A few reliable warning signs: shocking headlines meant to make you angry or afraid, stories with no named source or date, claims that "they don't want you to know," and posts that ask you to share immediately. A quick habit that defeats most of it: read past the headline, and search the claim to see whether trustworthy outlets are reporting it too.

A newer wrinkle is AI-generated and altered content. Today's tools can produce realistic-looking images, video, audio, and writing that never depicted anything real. Photos can be edited or invented; a voice or face can be imitated; an article can be machine-written to sound authoritative while being wrong. You don't need to become a detector expert — you need the same reflex: be skeptical of anything surprising, and confirm it against reputable, official sources before you trust or share it. If a "photo" or "quote" seems designed to shock, slow down and verify.

🚩 Red flags (be cautious)✅ Green flags (more trustworthy)
No author or organization namedClear author or reputable organization behind it
No date, or clearly out of dateRecent, dated, and updated when needed
Exists to sell, outrage, or persuadeExists to inform, and separates fact from opinion
Shocking headline; asks you to "share now!"Measured tone; invites you to check the sources
Claim appears in only one placeConfirmed by several independent reputable sources
No sources, or links that go nowhere realCites evidence you can follow and verify
Odd web address imitating a real siteOfficial site (agency, university, established outlet)

💡 Go to the source

For anything that matters — benefits, health, laws, taxes, workplace policy — go straight to the official source whenever you can: the government agency, the manufacturer, the reputable institution, your employer's own documents. Official sites (often ending in .gov for U.S. government, or an organization's real domain) beat a stranger's summary of them. When in doubt, one careful search for the original beats a dozen secondhand posts.

Troubleshooting Tech Problems

When something isn't working, the biggest mistake is to panic, click wildly, or assume you broke it forever. Instead, work the problem calmly with a simple, repeatable process. Most everyday tech problems are solved by the same handful of basic steps — the ones professionals reach for first, too.

graph TD
    A["Something's not working"] --> B["Stay calm — you didn't break it"]
    B --> C["Note exactly what happened & any error message"]
    C --> D["Try the basics: save if you can, restart the app or computer, check connection/plugs"]
    D --> E{"Fixed?"}
    E -->|"Yes"| F["Great — note what worked"]
    E -->|"No"| G["Search the exact error online"]
    G --> H{"Fixed?"}
    H -->|"Yes"| F
    H -->|"No"| I["Ask/escalate to IT with clear details"]

Walking through the steps:

  • Stay calm. A frozen program or a strange error is normal and usually harmless. Panic leads to random clicking that can make things worse; a steady head fixes faster.
  • Note exactly what happened. What were you doing? What exactly did it say? Write down or photograph the error message word-for-word (or the error number). "It's broken" is hard to fix; "It froze when I clicked Print, and it said Error 0x0000" is easy to look up and easy for IT to help with.
  • Try the basics. This is where the famous question — "Did you restart it?" — comes from, and it's famous because it genuinely works. Restarting clears temporary glitches in memory more often than any other single fix. So: save your work if you can, then close and reopen the app, or restart the whole computer. Also check the simple physical things — is it plugged in, is the cable connected, is the Wi-Fi/internet on? A shocking number of "big" problems are a loose cable or a dropped connection.
  • Search the exact error online. If the basics didn't do it, copy the exact wording of the error into a search. Millions of people have hit the same messages, and reputable sites (the software maker's own support pages are best) often have the fix. Searching the precise text works far better than describing the problem in your own words.
  • Still stuck? Ask or escalate to IT — with details. There's no shame in this; it's a workplace skill. The key is how you ask. Give the person (or the help ticket) the details you noted: what you were doing, the exact error, what you already tried. Clear details are respectful of their time and get you a fix far faster than "my computer's broken."

⚠️ Before you call anyone, try the classic "did you restart it?"

It sounds like a joke, but restarting is the single most effective first fix in all of computing — it clears the temporary state that causes most freezes and glitches. Save first if you can, then close and reopen the program; if that doesn't work, restart the whole computer. Also glance at the boring physical stuff: plugs, cables, power, and the internet connection. Do these before you escalate, and you'll solve a large share of problems yourself.

💡 Give IT clear details

When you do need help, the details you gathered turn a frustrating back-and-forth into a quick fix. Tell them: (1) what you were doing when it happened, (2) the exact error message (word-for-word or a photo of the screen), (3) what you already tried (e.g., "I restarted and it still happens"), and (4) how urgent it is. This isn't just polite — it's the mark of a capable employee, and it gets you helped faster.

Learning New Tools On Your Own

No course can teach you every program you'll ever meet — and no employer expects that. What they truly value is someone who can learn a new tool on their own, calmly and quickly. The wonderful news is that software is far more consistent than it looks: once you're comfortable exploring (the confidence you started building back in Lesson 1.1), the same handful of moves lets you pick up almost anything.

  • Explore the menus — safely. Open the program and look around the menus and toolbars. Hover over buttons to see what they do; most show a little label. Remember: you can't break it by looking, and undo (Ctrl+Z / Cmd+Z) reverses most actions. Curiosity is your best teacher.
  • Use the built-in Help. Nearly every program has a Help menu or a search box inside it (often a "?" or a "Tell me what you want to do" field). Type what you're trying to accomplish and follow the guidance — it's written by the people who made the tool.
  • Search "how to ___ in [program]." This is the single most useful phrase for self-teaching. Searching "how to add page numbers in Microsoft Word" or "how to make a chart in Google Sheets" brings up clear, step-by-step answers for your exact tool.
  • Watch a short tutorial video. Seeing someone do a task once often beats reading about it. A three- to five-minute video for your specific program can make a new feature instantly clear. Pause and follow along on your own screen.
  • Then practice. Reading and watching plant the idea; doing it yourself makes it stick. Try the new skill on a practice file (not the important one) until it feels natural.

Because so many programs share the same ideas — files and saving, menus and toolbars, copy and paste, undo — every new tool you learn makes the next one easier. You're not memorizing a thousand separate programs; you're getting better at the skill of learning software itself.

✅ "I can figure it out" is the real skill

Employers know software changes constantly, so they prize people who say, calmly, "I haven't used that yet, but I can figure it out." That's not bragging — it's exactly the habit in this section: explore the menus, check Help, search "how to ___ in [program]," watch a quick video, and practice. Master that loop and no new tool can intimidate you for long.

Confident & Self-Reliant

Put the whole lesson together and you have a simple, powerful stance toward the digital world: think before you trust, work problems before you panic, and know how to learn what you don't know. These three habits will carry you through jobs, tools, and technologies that don't even exist yet.

  • Verify before you trust or share. Run online information through the quick checks — who published it, when, why, and can you confirm it elsewhere — before you believe it, act on it, or forward it to a coworker.
  • Troubleshoot the basics before panicking. Stay calm, note exactly what happened, and try the basics (save, restart the app or computer, check the connection and plugs) — then search the exact error. Most problems fall to this alone.
  • Look it up and learn it. When you hit something new, explore the menus, use Help, search "how to ___ in [program]," watch a short video, and practice. You don't need every answer memorized — you need to know how to find it.

✅ Asking for help well is a strength, not a weakness

Self-reliant does not mean struggling alone forever. The most capable workers know exactly when to ask — and they ask well, with clear details: what they were doing, the exact error, and what they already tried. That's a professional skill, not a failing. Trying the basics first and then escalating with good information is teamwork at its best, and it's precisely what a workplace hopes to see.

Practice & Project

🏋️ Exercise 1: Which source do you trust?

Goal: Practice judging a source and verifying a claim.

You're researching a workplace question and find two results making the same surprising claim. Which do you trust more, and what do you do next?

  1. Source A: an anonymous blog post with no author and no date, making a wild, alarming claim and urging you to "share this before it's taken down."
  2. Source B: a clearly dated article from a well-known official/reputable organization, with a named author and links to its evidence.
✅ Answer

Trust Source B — it has authority (named author, reputable organization), currency (a clear date), and evidence you can follow, while Source A has none of those and shows classic red flags (anonymous, undated, alarming, "share now"). Next step: even with Source B, verify the claim elsewhere — confirm that other independent, reputable sources say the same thing before you act on it or pass it along. Trust the reputable source, and still verify.

🏋️ Exercise 2: Put the troubleshooting steps in order

Goal: Fix a common problem calmly and in a sensible order.

You're working in a program and it suddenly freezes. Put these actions in the best order:

  1. Restart the whole computer
  2. Note exactly what happened (what you were doing / any error)
  3. Ask IT for help, with clear details
  4. Try saving if you can, then close and reopen the program
  5. Search the exact error online
✅ Answer

Best order: 2 → 4 → 1 → 5 → 3. First note exactly what happened (2), then try the basics — save if you can and restart the program (4), and if needed restart the computer (1). Still stuck? Search the exact error online (5). If that doesn't solve it, ask IT with clear details (3) — what you were doing, the exact message, and what you already tried. Stay calm throughout; you didn't break it.

🎯 Your Project: My Info-Literacy & Troubleshooting Guide

Add a page to your "My Workplace Digital Toolkit" that turns this lesson into your own quick-reference guide — the two checklists you'll actually use at work.

  1. (2 min) Title a new page "My Info-Literacy & Troubleshooting Guide" and add today's date.
  2. (6 min) Write your source-check questions in your own words — the four checks: Who published it? When (is it current)? Why does it exist (inform, or sell/persuade)? Can I verify it with other reputable sources? Add one line reminding yourself to be extra skeptical of shocking or AI-generated content.
  3. (6 min) Write your troubleshooting steps in order: stay calm → note exactly what happened / the error → try the basics (save, restart the app or computer, check the connection and plugs) → search the exact error online → still stuck? ask IT with details.
  4. (5 min) On a real computer, try teaching yourself one small new thing: pick a program you use, and search "how to ___ in [that program]" for a task you don't know yet. Do it, then note what you learned.
  5. (3 min) Write one sentence about a time technology frustrated you — and how this calm process would help next time.
  6. (2 min) Date the page and keep it in your toolkit for quick reference at work.

✅ Project Completion Checklist

  • ☐ I titled and dated my "My Info-Literacy & Troubleshooting Guide" page
  • ☐ I wrote my source-check questions (who / when / why / verify)
  • ☐ I wrote my troubleshooting steps in order, including "ask IT with details"
  • ☐ I taught myself one small new thing with a "how to ___ in [program]" search
  • ☐ I reflected on handling tech frustration calmly next time

👥 Working with a tutor or group?

Try a "source showdown": bring a real headline or claim and, as a group, run it through the four checks (who, when, why, verify) — then search to see if reputable sources confirm it. For troubleshooting, take turns describing a tech problem out loud while a partner walks you through the steps (calm, note it, restart, search, escalate). Practice the "ask IT" step by having someone role-play the help desk while you report a problem with clear details. A tutor can share which official sources are reliable for your area (government, health, workforce) and help you tell them from imitators. Keep it supportive — everyone has been fooled by bad information or stumped by a frozen screen.

🎯 Quick Quiz

Question 1: What is a good way to judge whether online information is trustworthy?

Question 2: A computer program just froze. What's a sensible first troubleshooting step?

Tips & Common Mix-Ups

✅ Do's

  • Read past the headline. Then search the claim to see if reputable sources agree.
  • Ask who, when, why, and verify. Four quick questions catch most bad information.
  • Restart first. Save if you can, then restart the app or computer — it fixes most glitches.
  • Note the exact error. Word-for-word (or a photo) makes it searchable and easy for IT.
  • Search "how to ___ in [program]." The fastest way to teach yourself almost anything.
  • Ask for help with details. Trying the basics, then escalating clearly, is a real skill.

❌ Common Mix-Ups

⚠️ Watch Out

  • Believing it because it's online. The web sorts by relevance, not truth — verify before you trust.
  • Sharing before checking. "Share now!" is a red flag; confirm it first, especially if it's shocking.
  • Trusting realistic images or videos blindly. AI can fake them — confirm with reputable, official sources.
  • Panicking or clicking wildly. Stay calm; you didn't break it, and undo has your back.
  • Skipping the restart. "Did you restart it?" is famous because it genuinely works.
  • Saying "it's broken" with no details. Give the exact error and what you tried — help comes faster.

✅ Affirmation

You now have two skills that will serve you for your whole career: you can tell trustworthy information from misinformation, and you can work a tech problem calmly instead of panicking — and learn any new tool you meet. That's not luck or a "tech gene"; it's a repeatable method you can use forever. You're becoming exactly the kind of self-reliant, level-headed person a workplace depends on.

📓 Learning Journal

Keep a learning journal — a notebook, or a note on your phone or computer. After every lesson, take five minutes to write down:

  • What you learned — a skill or a new word
  • What clicked for you
  • What's still unclear, so you know what to revisit
  • Where you'll use it at work or in a job search
  • How you feel about your progress

✍️ This lesson's prompt: Think of a time you weren't sure whether something online was true, or a time a tech problem left you stuck. How might the checklists in this lesson — the source checks (who/when/why/verify) and the troubleshooting steps (calm, note it, restart, search, ask with details) — change how you'd handle it now? Which of these two skills do you most want to strengthen, and why? Write a few sentences.

📝 Lesson Summary

🎓 Key Takeaways

  • Judge online information before you trust or share it: who published it (authority), is it current, why does it exist (inform vs. sell/persuade), and can you verify it with other reputable sources.
  • Watch for misinformation, fake news, and AI-generated or altered content — be skeptical of shocking claims and confirm against reputable, official sources.
  • Troubleshoot calmly: stay calm, note exactly what happened and any error, try the basics (save, restart the app or computer, check the connection/plugs), then search the exact error — the classic "did you restart it?" solves most problems.
  • Escalate well: if you're still stuck, ask or escalate to IT with clear details — what you were doing, the exact error, and what you already tried.
  • Learn new tools yourself: explore menus safely, use Help, search "how to ___ in [program]," watch a short video, and practice — employers value people who can learn tools.

🎉 What You've Accomplished

You added two career-long skills to your toolkit: the judgment to tell reliable information from misinformation, and a calm, repeatable way to solve tech problems and teach yourself new software. You also built your own "My Info-Literacy & Troubleshooting Guide" — a quick reference you'll actually reach for at work. That's the kind of self-reliance that makes you valuable in any job. 🎉

❓ Common Questions at This Stage

How can I tell if a photo, video, or article was made or altered by AI?

You often can't be certain just by looking — and the tools keep improving — so don't rely on spotting it. Rely on the same reflex you use for everything else: be skeptical of anything surprising, and verify it against reputable, official sources. Ask where it originally came from, whether trustworthy outlets are reporting it, and whether it seems designed to shock or provoke. If a "photo" or "quote" is meant to stir strong feelings and you can't confirm it, treat it as unproven.

Is it bad to ask IT or a coworker for help? I don't want to look incapable.

Not at all — asking well is a genuine workplace skill, not a weakness. The capable move is to try the basics first (calm, note it, restart, search the error) and then escalate with clear details: what you were doing, the exact message, and what you already tried. That shows initiative and respects everyone's time — exactly what a good workplace hopes to see.

What actually is "restarting," and why does it fix so much?

Restarting means closing and reopening a program, or fully shutting the computer down and turning it back on. It works because it clears the temporary, in-progress state (in the computer's memory) where most freezes and glitches build up, giving the program or system a fresh start. It's the first fix professionals try because it's quick, safe, and solves a surprising share of problems. Just save your work first if you can.

Which sources count as "reputable" or "official"?

Generally: government agencies (often ending in .gov in the U.S.), universities and libraries, established news organizations, professional or medical bodies, and a product's own maker for questions about that product. Look for a named author or organization, a date, evidence you can follow, and a tone that informs rather than sells. When something matters, go straight to the official source rather than a stranger's summary of it — and confirm important claims in more than one reputable place.

🎯 Standards Alignment (for programs & tutors)

This lesson aligns to Northstar Digital Literacy — Information Literacy (evaluating sources, authority, currency, purpose, and verification; recognizing misinformation and AI-generated/altered content) and the problem-solving/troubleshooting and self-directed learning strands woven through Essential Computer Skills — and supports WIOA Title II digital-literacy workforce preparation, CCRS evaluation of informational/technical text and evidence, and NRS ABE/ASE functioning-level work toward Measurable Skill Gains. It advances the "My Workplace Digital Toolkit" portfolio thread and complements the Workforce Readiness and Career Exploration & Pathways courses. This course builds the skills; the official Northstar assessment/certificate is earned separately at sponsoring sites. Software menus vary by version. Confirm current specifics with NDE/CRAELO.

🔭 Looking Ahead

You've now built the full range of workplace digital skills — from the computer itself to email, the internet, office software, online job search, video meetings, communication tools, your digital footprint, and the information literacy and problem-solving of this lesson. In Lesson 4.3: Capstone — Your Workplace Digital Toolkit, you'll bring it all together: reviewing and polishing your toolkit, filling any gaps, and finishing the course with a portfolio and a confidence you can carry into any job.

✅ Before the Next Lesson

  • Finish your "My Info-Literacy & Troubleshooting Guide" page and keep it in your toolkit.
  • Practice the four source checks (who/when/why/verify) on one real thing you read online this week.
  • Next time something freezes, try the basics (save, restart, check the connection) before anything else.
  • Teach yourself one small new thing with a "how to ___ in [program]" search, and note what you learned.
  • Skim your earlier toolkit pages so you're ready to pull everything together in the capstone.

🌟 Encouragement for the Journey

Knowing how to find the truth and how to solve a problem calmly is a kind of quiet power — it makes you steady when others panic and wise when others are fooled. You don't have to know everything; you now know how to check, how to fix, and how to learn. That's exactly what a workplace — and life — asks of a confident, capable person. One lesson to go. See you in the capstone! 👋