From Certification to Career Ready: Teaching IT Skills That Matter

by Frank Marsaglia, Dan Goodman, and Dr. Babak Shoraka, zyBooks IT authors

Your student completes a VLAN configuration lab following step-by-step instructions and gets 100%. The student can list the VLAN benefits: security, performance, management.

Then comes the job interview: “Tell me when you’d recommend VLANs for a small business.”

The Framework: A Three-Component Learning Progression

At a recent zyBooks workshop we tackled how to help students prepare for real world challenges. We introduced an approach we call the “Three-Component Framework”—a systematic progression that takes students beyond step-by-step instructions to develop genuine problem-solving skills.

For each major topic, students experience three distinct learning phases: guided hands-on practice (the “how”), real-world case studies (the “why” and “when”), and scenario-based challenges (application without training wheels). This progression mirrors how IT professionals actually learn in the field and bridges the gap between certification readiness and career readiness.

Before the framework: “Um, VLANs improve security and, uh, performance? You should definitely use them because… they’re best practice?”

After the framework: “I’d first assess their needs. If they’re experiencing network congestion or need to separate guest Wi-Fi from business systems, VLANs make sense. I analyzed a case study where a company segmented their network after a breach—attackers had moved laterally because everything was on one flat network. But for a 5-person office with basic needs? VLANs might be overkill. The management overhead isn’t worth it. I’d focus on strong access controls first.”

This isn’t a hypothetical difference. This is what happens when students move beyond memorizing procedures to understanding context, consequences, and trade-offs.

The challenge: Performance-based questions are a bigger portion of certification exams than ever before. Job postings explicitly demand “hands-on problem solvers, not just cert holders.” Yet many IT graduates can follow lab instructions perfectly but freeze when asked to diagnose novel problems or explain their reasoning.

You know traditional prescriptive labs aren’t enough. But completely rebuilding curriculum with your teaching load? Not realistic.

As zyBooks IT authors who collectively teach hundreds of students annually across networking, Linux, and security courses, we’ve field-tested an approach that transforms how students think without requiring a curriculum overhaul.

Why Traditional Labs Fall Short

IT education has traditionally relied on prescriptive labs: Click here. Type this command. Verify output matches screenshot.

Students become proficient at executing instructions but can’t transfer that knowledge. They complete the RAID configuration lab perfectly but don’t understand when RAID protects data and when it doesn’t. They can configure a firewall by following steps but can’t troubleshoot when something goes wrong.

“Students coming out of programs know how to push buttons in the right sequence, but they don’t know how to think.” — Dan Goodman, zyBooks, 25+ years IT instruction

We’ve all seen it: Graduates pass certification exams but struggle in technical interviews. They earn credentials but require extensive on-the-job training before contributing.

The Three-Component Framework: How It Works

After years of classroom trial and error (plenty of error, honestly), we’ve identified a progression that develops both certification readiness and critical thinking. Students need three distinct learning experiences for each major topic, not just one type of experience.

Here’s why this sequence works: Students need to see failure consequences before they care about prevention. They need context before independent problem-solving makes sense. The progression mirrors how professionals actually learn in the field—guided practice, mentored analysis, independent execution.

Component 1: Guided Hands-On Practice (The “How”)

Your existing step-by-step labs already do this well: teaching students to configure RAID arrays, set up VLAN segmentation, and implement PKI certificates. These guided labs build the procedural knowledge required for both certification exams and workplace tasks.

You’ve already invested in this foundation. Now let’s leverage it more powerfully.

Component 2: Real-World Case Studies (The “Why” and “When”)

This is the critical bridge most IT programs lack, and where transformation happens.

After students complete a technical lab, connect that skill to an actual security breach or network failure— not hypothetical scenarios, but real incidents with real consequences.

Example: From RAID Configuration to Ransomware Reality

After teaching RAID configuration in our security course, students analyze the Change Healthcare ransomware attack that caused approximately $9 billion in direct and indirect costs. The case study reveals how RAID arrays, which are designed for hardware resilience, actually worsened the situation by copying corrupted data to backup systems across all array levels.

The discussion question: “Based on what you just learned about RAID 0, 1, and 5, why didn’t these configurations protect against ransomware?”

Students discover that RAID addresses hardware failure, not security threats. They grasp why defense-in-depth matters. The technical concept transforms from abstract checkbox to critical decision-making tool.

“Case studies push students to move beyond memorization and engage with material in a more thoughtful way.” — Instructor survey feedback

More Case Study Connections

  • Flat Networks to VLANs: Analyze how lateral movement during a breach prompted network segmentation
  • DNS Fundamentals: Connect to the Dyn DNS DDoS attack or recent AWS outage
  • PKI Implementation: Examine the Comodo certificate authority breach

Time investment: 10-15 minutes to add one case study to an existing lab

Source materials: Free breach reports from CISA, Krebs on Security, or vendor post-mortems

Common concern: “Won’t case studies feel like I’m going off-syllabus?”

Not if you tie them directly to certification objectives. Change Healthcare teaches RAID levels (Network+ objective 3.3). Dyn DNS teaches DNS fundamentals (Network+ objective 1.6). The case study isn’t extra; it’s deeper engagement with required material.

Component 3: Scenario-Based Challenges (Application Without Training Wheels)

The final component removes guidance entirely. Students face open-ended problems with no step-by-step instructions.

In our networking courses, students encounter scenarios like this:

ABC Tech’s sales team reports PC4 contains a critical database but is unreachable. Your task: Diagnose and fix the network connectivity issue.

Students receive a network diagram and current configurations. That’s it. They must identify whether the problem is physical (disconnected cable), configuration-based (wrong IP address), routing-related (mistyped static route), or some combination.

“We want students challenged, not frustrated. There’s a fine line to walk.” — Dan Goodman, zyBooks

How to Calibrate Difficulty

Finding that line takes practice. Here’s what we’ve learned:

  • Start with one or two obvious issues plus one subtle misconfiguration
  • Provide hints after the first failed attempt
  • Include clear success criteria so students know when they’ve solved the problem
  • Gradually increase complexity. Don’t throw network troubleshooting at students who just learned IP addressing

Time investment: 30-45 minutes to convert an existing lab to scenario format or 2-3 hours to create from scratch

Don’t Have Sophisticated Lab Software?

We’ve made this work with:

  • Broken network diagrams on paper
  • Misconfigured VMs students must fix
  • Configuration files with deliberate errors

The challenge matters more than the platform.

“Students did great in the scenario lab because they finally understood the WHY behind security decisions.” — Instructor feedback

What Changes: Measurable Impact

This integrated approach leads to classroom success, but the real transformation shows up in job interviews and first-year performance.

The student who completed all three components can now:

  • Evaluate trade-offs, not just recite benefits
  • Apply concepts to novel situations
  • Reference real-world context
  • Make reasoned recommendations

That’s career readiness, not just certification readiness.

Making the Framework Sustainable

The three components work together, but you need daily practices to make them sustainable:

Keep content current: Start each class with a 5-minute current event discussion. Pull headlines from Krebs on Security, Dark Reading, or The Hacker News. Ask: “What technical concept from last week would have prevented this?” When AWS experiences an outage, connect it to DNS fundamentals and single points of failure. Built-in currency without curriculum rewrites.

Connect to their everyday tech: “Your home Wi-Fi is slow when gaming? That’s a QoS problem. Let’s fix it.” Encourage home lab experimentation: “Set up two VMs: one attacker, one victim. Play both sides.”

As Frank Marsaglia puts it: “I’ve smoked a lot of motherboards because I put the wrong pins in the wrong places. But I learned the second time not to put that pin there again.”

Evolve your role: Use daily standup-style discussion prompts: “What did you learn this week? What’s blocking you?” This fosters peer learning and provides immediate feedback about what students actually comprehend.

“IT’s a practice-based discipline… the more they do, the more they learn. And by ‘do,’ I mean grapple with messy, real-world complexity—not just follow instructions.” — Dr. Babak Shoraka, zyBooks

Your Implementation Roadmap

You don’t need to rebuild your entire curriculum mid-semester. Start with incremental changes:

This Week: Start Small

  • Add one 5-minute current event discussion to your next class
  • Pull one breach report from CISA
  • Identify which existing lab could pair with a case study

Next Month: Add Context

Add one case study (30-45 minutes total prep):

  • Find a relevant incident related to a recent lab topic
  • Create 3-5 discussion questions connecting the incident to technical concepts
  • Test with students and gather feedback

This Semester: Build Challenge

Convert one lab to scenario format (1-2 hours):

  • Take your best walkthrough lab
  • Remove step-by-step instructions
  • Add context: “Company X is experiencing Y problem. Fix it.”
  • Include success criteria but not the solution path

Next Semester: Full Integration

  • Implement the full progression (guided practice, case study, scenario) for every major topic
  • Measure effectiveness: Ask students the same troubleshooting question at the start versus end of your course

The Path Forward

The three-component framework works with any platform, any textbook, any class size. It doesn’t require expensive software or additional institutional resources.

What it requires is intentional design that moves students from “I followed the instructions” to “I can diagnose and solve problems I’ve never seen before.”

That’s the difference between a certificate holder and an IT professional. And it’s the difference between graduates who need extensive on-the-job training and those who contribute from day one.

Start with one small change this week. Track what happens when students can finally answer not just ‘how’ but ‘why’ and ‘when.’ Your students—and their future employers—will notice the difference.


Frank Marsaglia, Dan Goodman, and Dr. Babak Shoraka are zyBooks content authors with decades of combined experience teaching IT, networking, and cybersecurity courses at community colleges and universities.