Discover Your Future in Tech · Beginner · ~6 hours

Digital Literacy & Workplace Technology

Build the everyday digital skills needed to work confidently in a modern technology organisation.

Status: Catalogue ready. This lesson version is available in review mode while subject-matter, accessibility and assessment checks are completed.

Working confidently with digital tools

Files, data and version control for teams

40 min

course progress0 of 3 lessons complete

By the end of this lesson

Organise files so another colleague can find the current version.
Distinguish working data from personal or confidential information.
Choose naming and review habits that reduce avoidable errors.

Build a clear mental model

Digital confidence begins with knowing what a file represents and who should be able to use it. A folder full of documents can look productive while still creating risk if names are vague, versions conflict or access is wider than necessary. Use names that describe the subject, time period and status without including unnecessary personal information. A shared document should make its owner, review point and intended audience easy to understand. “Final-final-new” is not a version strategy; a dated or numbered convention with a short change note is easier to trust. Data deserves a second question: is this information needed for the task? A customer record, an internal forecast and a practice dataset have different handling expectations. A learner should use fictional data when practising, remove identifying details when they are not needed and never copy credentials or private contact information into a course exercise. Data minimisation is a practical productivity habit because it reduces the amount that has to be checked, protected and corrected. Evidence makes learning and commercial work safer. In a busy workplace, people often move quickly from an observation to a conclusion: a team has grown, therefore its process must be failing; a person asked a question, therefore they are ready to buy; a learner used a spreadsheet, therefore they can manage a CRM. A better habit is to name the observation, the interpretation and the question that would test it. This does not slow every decision down. It directs attention to the assumptions that could create the most harm if they are wrong. It also helps a colleague continue the work without having to guess what was meant. Use a simple evidence note: context, observable detail, impact or desired change, uncertainty and next action. Context describes the setting without exposing personal or confidential information. Observable detail records what someone did, said or published, using their own words where that is appropriate. Impact describes a consequence without inventing a number. Uncertainty names what has not yet been checked. The next action should have an owner and should be easy to accept, decline or revise. This pattern works for a learning reflection, a customer conversation, a process review and a career example. Good evidence is also proportionate. A small practice task does not require a research report, and a complex business decision should not rest on a single enthusiastic comment. Label sources and dates, keep the minimum information needed, and be honest about the limits of the conclusion. When a learner cannot share a workplace example, a fictional case can demonstrate the reasoning without disclosing private information. The aim is dependable judgement, not a performance of certainty.

Apply the method in a real conversation

Create a fictional workspace with folders for working, review and approved outputs. Add a short readme stating the purpose, naming convention, owner and review date. When a document changes, record what changed and who needs to know. For spreadsheets, define the meaning and unit of each important field, protect formula areas where appropriate and check a sample manually. When collaboration software offers comments, use them for questions and decisions rather than leaving hidden edits. At handover, point to the current source of truth and archive or clearly mark superseded versions. A repeatable method turns a concept into behaviour. First, define the outcome in plain language: what should be easier, safer, clearer or more measurable after this work? Second, identify the people, systems and constraints involved. Third, choose the smallest useful action that will create new information. Fourth, review what happened and decide whether to continue, change direction or stop. This sequence avoids the common trap of producing activity without learning. It also makes it easier to explain why a particular message, spreadsheet, call, meeting or system change was chosen. When applying the method, use inclusive language and make room for different communication styles. A person may need extra processing time, a written alternative to a live role-play, captions, a transcript or a clear agenda. Accessibility is not a separate favour; it improves the quality of information available to everyone. Ask what format helps, avoid assuming confidence from speed of speech, and record only relevant support needs through approved processes. Review the work against the original outcome rather than against a vague idea of being busy. Did the note help another person act? Did the question invite a useful answer? Did the process reduce avoidable effort? Did the learner protect confidential information? If not, revise the method and try again. A respectful correction is a sign of professional maturity, not evidence that the first attempt was worthless.

Use judgement and leave a useful record

Convenience should not silently override access controls. If you are unsure whether a file contains confidential information or whether a colleague should see it, pause and ask the approved owner. Do not solve a sharing problem by publishing a broad link or emailing an attachment to a personal account. Record the decision and use the organisation's support route. A clear process makes it easier for people using screen readers, translation tools or slower connections because they can find a labelled, stable source instead of chasing several copies. Professional judgement includes deciding what not to do. A request may be outside scope, a data source may be unreliable, a buyer may not have a current need, or a learner may need more practice before taking on a complex task. Saying “not yet”, “I do not know” or “this is not the right fit” can protect trust. It is especially important in technology sales, where optimistic language can create expectations about product capability, implementation, security or career outcomes that no one has verified. Pressure-free practice means giving people a clear choice and enough context to make it. Do not use manufactured scarcity, fear, personal vulnerability or hidden follow-up. Explain what will happen next, what information is required and how a person can pause or opt out. In a learning context, feedback should describe the work and the next improvement rather than label the person. In a customer context, the same principle appears as accurate notes, transparent limits and a willingness to recommend a safer alternative. Finally, make the work reviewable. Keep a short record of the decision, the evidence used, the uncertainty that remains and the date to revisit it. Never put real personal data, credentials, private contact details or confidential employer information into a practice exercise. These habits build trust gradually and create evidence that can be improved, audited and shared with the right people.

Workplace example

At fictional Harbourlight Services, a team has three copies of a customer-onboarding checklist. A learner creates a readme, labels one approved version, moves drafts to a review folder and replaces real customer names with fictional labels in the practice copy.

Try this walkthrough

1.List the purpose, audience and owner for a fictional file set.
2.Choose a naming pattern that includes status and date without personal data.
3.Create working, review and approved locations and add a readme.
4.Check access, version notes and a sample of the content before handover.

Watch for these traps

Using vague names or multiple unmarked copies.
Including personal data because it is convenient for a demonstration.
Sharing a broad link instead of asking the file owner.
Treating an archive as deleted or assuming a draft is approved.

Practice studio

Make a decision. Test a response. Leave evidence.

Use the case from this lesson to practise judgement without creating a score or changing your course record.

Scenario decision

At fictional Harbourlight Services, a team has three copies of a customer-onboarding checklist. A learner creates a readme, labels one approved version, moves drafts to a review…

Choose a response

Branching roleplay

A colleague asks you to move this situation forward. What do you say next?

Evidence workspace

Draft a short known / assumed / next note from the fictional case. Use fictional details only.

KnownAssumedNext step

This is a session-only practice draft. It is not saved, graded or added to your learning record. Never enter real personal or confidential information.

Practical assignment

Build a fictional shared workspace for a customer-onboarding project. Include a readme, naming convention, access note, review date and one superseded version clearly marked. Explain how your structure helps a new colleague and protects unnecessary personal information.

Pass this lesson's knowledge check before recording it as complete.

Portfolio evidence

Practical portfolio project

Create a small organised project workspace with a spreadsheet, shared-document plan, meeting agenda and safe file-management checklist.

Turn the practical project into a bounded evidence record. Save a draft while you work, then submit it for human review when it is ready.