12 min read · Case Study
I sat through a training program built for someone I wasn’t. So would every person who came after me, until we built something better.
The Situation
The project was growing fast. The engineering talent pool for telecommunications work is small, and competing for experienced engineers in an expanding market was neither efficient nor sustainable. The decision was made to hire directly from college, recruit people with engineering degrees, bring them in with no prior telecom experience, and build them from the ground up. It was the right strategic call. The training model waiting for them was not.
I was brought in as the Quality Control (QC) Project Manager for a specific market. That meant I needed to get up to speed fast, because I was going to be the QC bottleneck for every job leaving that market. To do that, I went through the existing program myself. Two weeks. Three days of classroom with an Outside Plant (OSP) trainer, then seven days shadowing with a Subject Matter Expert (SME) in a database the project was already retiring.
The content was real. The delivery was a structured brain dump from someone who knew everything about the work and very little about how to transfer that knowledge to someone who had never seen it before. There was also a problem nobody had fully reckoned with. The system being taught was being replaced within two months. All new jobs would move to a new mapping platform, a layered construction drawing tool that bore no resemblance to what we were being trained on. Every job currently in process would finish in the legacy system. The new engineers walking through the door would be working in something entirely different.
By day four of shadowing, I had mentally checked out. I knew I was wasting the SME’s time. I knew it wasn’t going to click in the remaining three days. I was fuming inside and scared at the same time, because I had been hand-selected for this role by peers who believed in me, and I was sitting there shaking my head. It felt like climbing Everest in the middle of winter with dental floss for a rope.
There was also a larger problem taking shape that nobody had an answer for. The SME Lead was handling QC for the experienced engineers already on the floor, a manageable load given their skill level and low error rate. But the project was about to grow significantly. A new cohort of twelve college graduates was on its way in. The QC workload was going to multiply faster than any one person could absorb, and the program had no plan for it.
· · ·
How the Job Changed
If I was struggling with this training, every cohort coming in behind me with no experience would also struggle. I took that to leadership. Then came the question that changed everything. If the training isn’t going to work as written, how would you do it differently? The thing I had just complained about was now mine to fix.
The pattern: Sometimes the responsibility arrives before the solution does. You don’t get handed the fix. You get handed the job of finding it.
I didn’t have an answer when I walked in. I didn’t have one when I walked out. But my role had just shifted. I was no longer going to run a specific market as its QC person. I was now responsible for the training program and every new person who came through it. The mission had changed, and now I could look at the problem differently.
The Diagnosis
The diagnosis came from lived experience. I had just gone through the broken version, and the gaps were real.
Three root problems were clear. First, the OSP training was all abstract. Engineers were being asked to build a mental picture of manholes, conduit, fiber, guy wires, and central office equipment from diagrams and description alone. Accurate diagrams, but nothing you could hold, measure, or walk up to in the field. Second, the job was being taught as one big block when it was actually three distinct disciplines, built one on top of the other. Site Verification (Phase 1), Feeder Plant (Phase 2), and Distribution Plant (Phase 3). Third, the training model offered no mechanism for identifying who was ready to advance and who needed more time. It was calendar-based, not competency-based. Everyone moved together regardless of where they actually were.
Twelve college hires were already on their way in. That turned the problem from something to study into something to fix now.
Where the Model Came From
The solution wasn’t handed to me. It was pulled out of a conference room conversation.
I got access to the new platform the client wanted to use, a mapping tool with an additional layer added. I sat down with the SME and asked him to help me break a single job into bite-size pieces. I also brought in the program manager for insight.
The three of us stood in front of a whiteboard. I started asking questions. I wasn’t looking for a specific number of pieces, I didn’t know if it was going to be two or ten. We started at the top and worked down, and when three chunks fell out naturally, Phase 1, Phase 2, and Phase 3, it felt like a clean stopping point. I asked the SME directly, “Could each of these be taught separately, as its own complete module?” He smiled and nodded.
That was the signal. I started scribbling on the whiteboard.
Almost immediately, something from earlier in my career surfaced. When I worked in retail management, associate managers rotated through distinct positions, operations, scheduling and people development, stockroom, and merchandising, so that when you eventually became a general manager, you understood how every part of the whole worked. Three distinct chunks. Sequential competency building. Rotation through each one before advancing to the next. The spine of a competency-based training model was starting to form organically. I also raised the concern about the abstract OSP training and whether we could get our hands on real equipment so trainees could feel and touch what they were about to build. The SME had contacts and said he would see what our options were.
The pod model came from that. I sketched it out, walked the SME through the logic, and he didn’t see any holes in it. That was all I was looking for. The program manager was in near disbelief at how quickly it came together.
The Intervention
Rebuilding the foundation. The OSP training was extended from three days to five. The first four days covered theory, but now with physical context. The SME had industry contacts and access to spare equipment. Fiber samples, conduit sections, innerduct, splicing trays, splitters, and physical hardware came into the classroom so engineers could hold and visualize what they were learning. On day five, sixteen of us, twelve trainees and four staff, went into the field together. They experienced firsthand manholes, telephone poles, guying structure, anchors, drop wires, and active infrastructure. The moment people could see and touch the real thing, the abstraction dissolved.
Day one in the fishbowl. All twelve engineers worked together in a single room we called the fishbowl. On day one, I told them the truth. I had gone through the existing program myself, I knew it didn’t work, and what we were about to do hadn’t been tried before. It might not be perfect. If they wanted out, that was their right.
Nobody left.
Fresh out of college, working on a project like this, that alone goes on a resume. Being told on day one that you’re the test case is a strange way to start.
The pod structure. The three phases of every job, Phase 1, Phase 2, and Phase 3, became three distinct training silos. The full cohort started together in Phase 1, establishing a shared foundation. I stayed in that room every day, listening, facilitating, watching. When a question surfaced in one group that the whole room needed to hear, I jumped in. Hey, everybody listen up.
The SME was stationed in the fishbowl running double duty, handling technical questions from the new engineers while simultaneously managing QC for the experienced engineers on the main floor. People would direct questions at him. I started watching what happened in that room. One engineer began answering those questions before the SME could get to them. After he answered, he would look over at the SME as if to ask, “Am I right? Did I explain that correctly?” The SME would nod and smile. Slowly, two others followed the same pattern. They’d answer, look for confirmation, and the SME would fill in any gaps. Three people were quietly taking over the room, not to show off, but because they couldn’t help themselves.
The pattern: Leadership often appears before anyone calls it leadership. People who naturally answer questions, help others understand, and look for confirmation that they are right are usually already doing the job before anyone gives them the title. The work is not assigning leadership. It’s noticing it.
Those three became the pod leads, with one stepping up as the lead for the group. The remaining nine engineers were organized into three pods of three, each anchored by one lead. One engineer drove. Two looked over their shoulders with the lead checking the work. Each pod thinking through the problem, collaborating, and sharing what they knew. After an hour or two they rotated and someone else took the driver’s seat. Nobody was alone. Nobody was thrown into the deep end. I had been pushed into a sink-or-swim situation myself and I was not comfortable there. I was not going to do the same to this group.
When I pulled the pod lead aside and told him he was going to anchor a group, he pushed his glasses up on his nose and said, “Yeah, I’ll do that.” That was all I needed to hear.
Live jobs from day one. These were live jobs, real deliverables the project was paid for. Training costs were offset from day one. After each pod completed three live jobs in their assigned silo, the rotation began. Phase 1 moved to Phase 2, Phase 2 moved to Phase 3, Phase 3 cycled back to Phase 1. By the end of the full cycle, every engineer had crossed the line, not because the calendar said so, but because the work said they were ready. Some got there after one rotation. Others needed two. Nobody moved until they were actually ready.
The pod leads also solved the QC capacity problem, not by design, but because they were closest to the work, fastest to catch errors, and already functioning as teachers for their pods. When their own pod had nothing pressing, they pulled load from other groups. The SME Lead stayed focused on the experienced engineering floor. A capacity gap that would have required three or four additional hires was absorbed by three engineers who had been in the building for six weeks.
The pattern: The strongest systems do more than solve the problem they were built for. A training model that only teaches people how to do the work is useful. One that also builds the next trainers, reviewers, and leaders handles problems before they even show up.
The Outcome
All twelve engineers in the inaugural cohort completed the program and moved to independent work. The difference wasn’t the caliber of the people. It was the structure they were given to develop inside.
The model scaled. Multiple cohorts came through the pod program over the life of the project, hired in groups of ten to twelve. As each new cohort arrived, the strongest performers from prior cohorts stepped into pod lead roles for the incoming group. The pod lead from that first cohort trained many of the groups that came after. Engineers became cross-trained across markets, which meant a surge of work in one area could be addressed by pulling from the broader pool without retraining. Pod size grew from four members to five as volume increased. Each cohort produced the leaders for the next one. The model grew the people who grew the model.
A kanban board on the wall tracked daily job targets. When an engineer finished a job, they walked to the board, dropped the count, and picked up the next one. When the necessary jobs for the day were completed, the floor stopped, clapped, and cheered the accomplishment. The team operated as a single coordinated unit.
The work was strong, the client was satisfied, and the project was humming.
This started with twelve engineers and grew to fifty or sixty coming through the program. Each new group was built on what the groups before them had done. The cohorts kept coming because the trained engineers did good work, the client trusted us with more of it, and new territories opened up. The engineers we built grew the team, and a bigger, stronger team kept the work coming.
· · ·
What This Signals
A program designed to throw people into the deep end and see who swam was replaced by one designed for everyone to make it across. Competency-based progression, moving when ready and not when the calendar said so, produced better engineers faster than a fixed timeline ever could. The pod leads were not recruited or credentialed into their roles. They were identified by watching who rose naturally in a room and putting them in a position to do what they were already doing informally. The QC system the program needed at scale grew organically from the work itself, unplanned, unforced, and exactly right.
We say we because this was never one person. The SME, the program manager, the pod leads, and every engineer in that first cohort built this alongside me. But the vision was clear from the start. Hire straight out of college, build our own talent pool, and create a training model that could scale. The work pool in the industry was too small to keep competing for experience that wasn’t there.
We started with a program I had gone through myself and knew was broken. The training model ultimately became more than a way to onboard new engineers. It became the system that identified future leaders, expanded capability, increased quality capacity, and prepared each generation to develop the one behind it. The organization stopped competing for experience. It started creating it.