top of page

5 Beginner IT Home Lab Projects to Build Your Confidence

5 hours ago
5 min read

You do not have to wait for a job title to start building IT skills. You can begin with the computer, internet connection, and curiosity you already have.


These five beginner IT home lab projects give you a practical place to start. You will practice noticing details, documenting your work, and explaining what you found—the habits behind good technical support. If you are a woman exploring a career change into technology, this is your invitation to take the first step.


What you need before you begin


For all five projects, use a personal Windows 11 computer, a browser, internet access, and a personal Google account. A notebook or document is enough for your reports. You can complete the network map, file permissions exercise, and help desk ticket on another computer, but the Windows projects below use Windows 11.


You do not need a server rack, a paid Microsoft 365 or Google Workspace admin subscription, or a coding background for these starter exercises. Google Drive practice here uses My Drive; it is not an enterprise Shared Drives or administrator lab.


Practice on devices and accounts you own or have permission to use. Use made-up data. Keep passwords, recovery codes, serial numbers, home addresses, and private network details out of anything you publish.


1. Create a PC inventory and support report


Your goal: learn what is inside a computer and describe its current condition clearly.


  1. Open Windows Settings, select System, then About. Record your processor, installed RAM, and Windows edition and version.

  2. Open System, then Storage. Note the space used and available. Do not delete files for this exercise.

  3. Ask yourself: What does this computer need to do? Write a short use case, such as everyday browsing, video meetings, and document editing.

  4. Create a one-page report with the device specifications, storage observations, and one question you would investigate next.


Save this result: PC-Inventory-Report.pdf. A useful observation might be, “Storage is nearly full; I would review what is using space before recommending cleanup.” Distinguish an observation from a diagnosis. A low storage reading alone does not prove why a computer is slow.


Skill you are practicing: gathering evidence before suggesting a fix.



2. Draw a simple home network map


Your goal: understand how everyday devices connect to the internet.


  1. List the devices you use: for example, a laptop, phone, printer, and smart TV.

  2. Draw your internet connection, your router or combined modem/router, and the devices connected to it. Mark wired and Wi-Fi connections. If you do not know how something connects, label it “not yet confirmed.”

  3. Write one troubleshooting scenario: “My laptop cannot open websites, but my phone can use the same Wi-Fi.”

  4. List your next checks: confirm the laptop is on the intended Wi-Fi, try a second website, and compare another browser. Record what each check would help you learn.


Save this result: Home-Network-Map.pdf, plus a short troubleshooting note. Use labels such as “Laptop A” rather than your actual Wi-Fi name or address details.


Skill you are practicing: separating a single-device problem from a wider connection problem. Keep this project observational; you do not need to change router settings or run network scans.


3. Practice cloud file access with Google Drive


Your goal: understand the difference between owning, viewing, and editing a file.


  1. In your personal Google Drive, create a new, private practice folder and a document containing only fictional information.

  2. Open the document’s Share dialog. Inspect General access and keep it Restricted. Review the Viewer, Commenter, and Editor roles.

  3. If you have a second personal Google account, grant that account Viewer access to the practice document. Sign in as that account in a separate browser profile and check what it can do. Otherwise, document the expected role behavior without sending an invitation.

  4. Change the test account to Editor and compare its capabilities. Remove its access when finished, and confirm the document remains Restricted.


Save this result: File-Access-Practice.pdf. Include a small comparison of the roles, what you actually tested, and what you only reviewed. Use a new private folder so inherited access from an existing shared folder does not complicate the exercise.


Skill you are practicing: giving the right person the access they need. A Viewer can view; an Editor can make changes. This is a small introduction to permissions, not a Google Workspace administration credential.



4. Document a basic Windows security check


Your goal: review protection status and explain the results without guessing.


  1. Open Windows Security and review Virus & threat protection. Record which security provider is active.

  2. If Microsoft Defender Antivirus is active and Quick scan is available, run it. If another antivirus provider is active, use its documented scan process instead.

  3. Record the date, scan type, result, and any recommended next action. Leave protections enabled and follow the security app’s guidance if it identifies a threat.

  4. Write two sentences explaining what the result tells you and what it does not tell you.


Save this result: Security-Check-Notes.pdf. For example: “The quick scan reported no threats. This records one scan result; it does not establish that the device or every account is completely secure.”


Skill you are practicing: communicating security findings accurately. You do not need to download sample malware, disable protection, or add exclusions.



5. Write and resolve a practice help desk ticket


Your goal: turn a vague complaint into an organized support record.


  1. Choose a harmless scenario, such as “I cannot find my practice document.” Keep the exercise limited to files you created.

  2. Write a ticket with a short summary, user impact, when the issue started, and the expected result.

  3. Record the checks you performed: the signed-in account, the folder location, and the search terms used. Note the result of each check.

  4. Write the resolution and how you confirmed it. If you did not resolve the issue, document the next step rather than inventing a successful outcome.


Save this result: Practice-Help-Desk-Ticket.pdf. A good closing note says what changed and how you verified it: “Located the document in the practice folder and confirmed it opens in the intended account.”


Skill you are practicing: clear documentation, calm troubleshooting, and useful follow-through.


Turn your practice into a beginner IT portfolio


Create a private folder called iTGirl-Portfolio and save your five reports there. For each project, include the goal, tools used, steps taken, result, and one thing you would do differently next time. Remove private information before sharing screenshots or reports.


Describe these honestly as personal practice projects. They can demonstrate your learning and how you explain technical work; they do not replace professional experience or guarantee a job. Your strongest evidence is a result you can explain in your own words.


Beginner home lab questions


Do I need to know how to code?


No coding is required for these five projects. You are practicing device support, networking concepts, permissions, security observations, and documentation.


Do I need to buy expensive equipment?


These starter projects use a personal computer and accounts you already have. Start there before buying equipment. A larger lab can come later as your goals become clearer.


Can I add these projects to my resume?


You can include relevant completed work under a Projects section. State that it was a personal lab, describe what you actually did, and be ready to explain the result. Do not label practice as paid IT employment.


Ready for a structured next step?


You have started putting your curiosity to work. Now give it a pathway.


iTGirl Tech 101 — Cloud IT Foundations is a 12-week online program for women, offered by Atlanta-based iTGirl Technologies. Build on these foundations through Windows and PC support, networking, Microsoft 365, Google Workspace, and security fundamentals, with hands-on labs, portfolio development, and twice-monthly live Q&A.


Open enrollment: the Winter 2027 Founding Session begins January 10, 2027. Explore the program, tuition options, and seat reservation details on the Tech 101 page.



Still exploring? Join our free email community for class announcements, new resources, and iTGirl updates.



Building Women. Powering Business. Advancing Technology.

 
 
 

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page