Free // Orientation
Find a direction before collecting more certifications.
The Roadmap to Break Into IT helps you choose a practical route and identify the kind of proof that route needs.
Open the free roadmap →Stage 01 // Enter Technology
Practice the work before someone hands you the title.
Studying can teach you what a tool is. Enter Technology is about learning what to do when the ticket, alert, user, handoff, or bad assumption shows up. Practice believable work, explain your decisions, and leave with evidence of what you can do.
First Role Lab // Help Desk
Selected · not yet live
L1
Scenario 014 // IdentityA new employee cannot sign in.
The visible symptom is only the beginning. The operator has to find the boundary, protect the account, document the work, and know when to escalate.
Evidence left behind
Troubleshooting path · ticket note · handoffREVIEWABLE
Help Desk is first · scenarios, guidance, evidence, and delivery are still being built
01 // LearnUnderstand the system
Build the vocabulary and mental model without memorizing your way past the work.
02 // PracticeWork the scenario
Make decisions inside a bounded environment where failure becomes useful feedback.
03 // ShowLeave the evidence
Explain what you saw, what you changed, what you refused, and what should happen next.
// Available now
Start with the rung that fits today.
The full role environments are still being bounded. These public routes already help you choose a direction, build your first useful practice environment, study with context, or get unstuck with a focused plan.
Free // First build
Turn the laptop you own into a practice environment.
The Homelab Starter walks through a useful first build without requiring a server rack or an expensive shopping list.
Build the first homelab →Library // Study and career
Connect the exam, the lab, and the first desk.
The Guides desk brings A+ study support, practical projects, career preparation, and first-90-day thinking into one route.
Browse the Guides desk →Focused // One conversation
Stop guessing what to study next.
The current strategy session is specifically bounded to CompTIA A+ and turns your exam, timeline, and sticking point into a focused fourteen-day plan.
See the A+ strategy session →// In development
A practice space shaped like the job.
Help Desk will be the first Role Lab. It is not live yet: the scenarios, guidance, evidence model, and delivery format still have to be built and tested. SOC, NOC, and identity/cloud remain later candidate labs.
First build // Help Desk Role Lab
Handle the human problem and the technical one.
Practice the first line of support as an operating role, not a list of trivia questions.
- Ticket intake and clarification
- Identity and device triage
- User communication
- Escalation and handoff
Planned evidenceTicket notes · troubleshooting path · escalation record
Later candidate // Security Operations
Investigate without outrunning your authority.
Work bounded alerts where scope, evidence, refusal, and escalation matter as much as the finding.
- Alert review and context
- Scope and authorization
- Investigation notes
- Defensive escalation
Possible evidenceFinding record · evidence trail · safe next action
Later candidate // Network Operations
Read the signal before touching the system.
Practice monitoring, incident orientation, communication, and recovery-minded handoff.
- Health and availability signals
- Impact and dependency checks
- Incident chronology
- Change-aware escalation
Possible evidenceIncident timeline · impact note · operator handoff
Later candidate // Identity and Cloud
Make access useful, reviewable, and reversible.
Practice the decisions behind onboarding, access, role changes, and clean departure.
- Microsoft 365 and Entra context
- Joiner, mover, leaver flows
- Access review and least privilege
- Change documentation
Possible evidenceAccess decision · change record · review checklist
// The evidence model
Not just completion. A record of judgment.
A finished scenario should make your thinking inspectable. The useful proof is not a decorative score. It is the trail showing how you oriented yourself, handled uncertainty, respected the boundary, and communicated the next step.
Deliberate boundary
Enter uses simulated, bounded environments. It does not provide production access, impersonate real employers, guarantee certification or employment, or convert private Labs projects into one merged training product.
01 // ORIENT
What did you notice?
Identify the people, system, symptom, scope, and missing context before acting.
02 // DECIDE
Why this next step?
Connect the observation to a bounded action and explain the alternative you rejected.
03 // DOCUMENT
What survives the exercise?
Leave a ticket note, timeline, checklist, handoff, finding, or other work-shaped artifact.
04 // EXPLAIN
Can another person follow it?
Translate the technical path into a clear account of impact, uncertainty, and next action.
// Find your doorway
What kind of technical work are you trying to enter?
Use one of the live starting points above, or tell the Front Desk the role, certification, project, or part of the path that keeps feeling vague. You do not need the perfect plan before the first useful step.