Digital Literacy Is More Than Knowing Where to Click

Knowing how to open Google Docs is a useful skill. It is not, by itself, digital literacy.

Digital literacy shows up when the situation changes. The file is shared with the wrong person. A search result makes a confident claim with weak evidence. A form asks for information it does not need. A presentation works on your screen but is unreadable from the back of the room. A teammate says, “I can’t open the link.” If your only strategy is remembering which button you clicked last time, the workflow falls apart.

Model the whole digital task

A digital task usually contains more parts than the app on the screen:

PERSON
  ↓
DEVICE
  ↓
ACCOUNT
  ↓
APPLICATION
  ↓
INFORMATION
  ↓
PERMISSIONS
  ↓
AUDIENCE
  ↓
RESULT

Suppose you write a group project in Docs. The application is Docs, but the result also depends on the account that owns the file and the Drive location. It also depends on who can access the file, what information it contains, and the audience that will read it. Change one part and the result can change.

That is the mental model for this course: tools are parts of systems.

Worked case: two correct documents, one broken workflow

Ari and Sam both produce an accurate one-page report.

Both know how to type in Docs. Only one workflow makes the file easy to locate, harder to accidentally change, and easier to verify.

The lesson is not “Sam is organized and Ari is not.” The lesson is that digital choices leave observable evidence. File names, locations, permissions, links, and revision history can be inspected.

Build a Digital Task System Map

Choose one ordinary school task: submit an assignment, coordinate a club meeting, collect survey responses, or prepare a presentation.

Write the task at the top of a page. Under it, record:

1. the person or group responsible;
2. the device being used;
3. the account or identity required;
4. the application or applications involved;
5. the information that enters the system;
6. the permissions that matter;
7. the intended audience;
8. the evidence that would show the task succeeded.

Then identify one failure point. For example, a correct Calendar invite can still fail if the linked agenda is private.

The first misconception to kill

“If the file opens for me, it works.”

That only proves the file opens for your current account under your current permissions. It does not prove a partner, teacher, or intended audience can open it. This distinction will appear again in Drive, Docs, Calendar, Forms, and the final capstone.

Evidence to keep

Submit your Digital Task System Map. A strong map names the information and permissions, not just the apps. In two sentences, state:

• one thing your map proves about the workflow;
• one thing it cannot prove without another test.

You are ready to move on when you can explain why “I know Google Docs” and “I can manage a digital workflow” are different claims.