Why Most Mentorship Programs Fail Before They Start
I spent seven years managing mentorship pipelines at two mid-tier production companies. The pattern was always the same: enthusiastic onboarding, solid curriculum, then a slow bleed of participants dropping out by month three. The problem wasn't the mentors or the mentees. It was the structure itself. People treat mentorship like a software installation where you plug someone in and expect an upgrade. It doesn't work that way. Real mentorship is messy, unstructured, and depends almost entirely on mutual investment that can't be mandated. That's why the old guard from places like the Lukecombs Brothers operation still matters. They didn't have programs or LMS platforms. They had people watching other people work until something clicked. The model was transfer of craft through proximity, not through a syllabus. I've seen people leave those setups actually competent within six months, and I've seen people spend eighteen months in corporate mentorship frameworks and come out knowing exactly what they knew before they started.
The Enduring Legacy Of Lukecombs Brother Pioneers In Media Mentors In Mentorship
The Lukecombs Brothers operated in broadcast media before the internet collapsed the distance between mentor and mentee. Their approach was simple: put someone in the room, let them fail quietly, correct them when it mattered, and don't waste energy on encouragement that wasn't earned. That's not inspiring language. It's just how it worked. The people who thrived in that environment shared a trait. They asked specific questions instead of vague ones. "Why did you cut there" instead of "How do I get better at editing." The difference between those two questions is the difference between a real answer and a motivational poster. Here's something nobody in modern mentorship programs talks about. The best mentors aren't the most experienced people in the room. They're the people who remember what it felt like to not know something. I learned this the hard way. Early on I was paired with a senior producer who had thirty years of credits but couldn't explain anything without using jargon as a wall. We lasted four months. He'd say things like "you need to feel the rhythm" and I'd nod and have no idea what that meant practically. Meanwhile, a junior producer two desks away could break down the same concept in three sentences because she was still close enough to the learning process to remember the gaps. When you're actually building a mentorship framework today, start with the matching process and spend more time there than anyone does. A bad match ruins everything. I've seen people paired by department alone, which sounds logical until you realize that two people in the same department can communicate at completely different wavelengths. One might prefer direct text feedback. Another needs a phone call to process anything. I started adding a ten-minute async exchange before any formal pairing, just a shared document where both parties answered three questions: how do you prefer to receive feedback, what's your current bottleneck, what's one thing you wish people understood about your role. It cut mismatch rate by roughly sixty percent in my experience. Ten minutes of that saves six weeks of friction.
There's a practical detail most people skip. Mentorship needs scheduled failure. I know that sounds counterintuitive. You hire mentors to prevent mistakes, right? Wrong. If a mentee never fails in a low-stakes environment during mentorship, they'll fail in a high-stakes environment and you'll have nobody to blame but your own risk aversion. I used to run what I called controlled burn exercises. A mentee would be given a real assignment with a deadline and zero guidance beyond the brief. Then they'd present what they made, and the mentor would go through it line by line. Sometimes the result was terrible. Usually it was. That's the point. The pain of seeing your work picked apart in a safe room is more valuable than any amount of preventative advice. Another thing that drives me crazy in modern mentorship discussions is the obsession with metrics. People want to measure mentorship with NPS scores and completion rates like it's a subscription service. You can't measure relationship quality with a survey sent three months after the fact. I once saw a company declare a mentorship program a failure because satisfaction scores dropped from 4.2 to 3.8 between quarters. The drop happened because the program got harder, not worse. The mentees were being pushed further. The scores reflected discomfort, not dissatisfaction. Without context, that metric is useless and actively misleading. If you're actually trying to replicate something like what the Lukecombs setup was doing, here's what you need to understand about the mechanics. First, the mentor needs skin in the game. Not a bonus structure. Actual stakes. When a mentor's reputation gets tied to a mentee's output, everything changes. I watched this work in a small newsroom where the anchor would publicly credit the producer who trained them. That created accountability on both sides. The mentor couldn't coast. The mentee couldn't hide. Second, keep the cohort small. Six people maximum per mentor. Beyond that, the mentor becomes a lecturer instead of a coach, and lectures don't build skills. Third, give mentors an exit ramp. Forcing someone to stay in a mentorship they've outgrown helps nobody. I set a ninety-day review point where either party could reset the terms or step away without paperwork or shame. Half the pairs renegotiated their arrangement. The other half moved on cleanly. Both outcomes were better than staying stuck.
Get the Full Details
There are limitations to this model that deserve honest acknowledgment. It doesn't scale well past fifty people without serious infrastructure. It requires mentors who actually enjoy teaching, which is a smaller subset than you'd expect from a pool of senior staff. And it creates dependency if you're not careful. I've seen mentees stay passive for months, waiting for guidance instead of taking independent action. The fix is straightforward but uncomfortable: mentees should present problems with their proposed solutions already attached. "Here's what I think the answer is, here's where I'm stuck." That shifts the dynamic from dependency to collaboration immediately. If someone can't do that after three weeks, the mentorship isn't the problem. The mentee's readiness is. The original Lukecombs operation worked because the medium demanded it. Broadcast media has hard deadlines, tangible output, and immediate consequences. Your results are either right or wrong, and the audience knows before you do. Modern remote-first environments stripped away most of those constraints. That's not a criticism of remote work. It's just a fact. The mentorship models that survived did so by rebuilding the accountability structures that proximity used to provide naturally. Video call check-ins replaced hallway conversations. Screen sharing replaced over-the-shoulder observation. Asynchronous voice notes replaced the quick desk visit. The tools changed. The principle stayed the same. Someone needs to watch you work and tell you what they see before you walk into a room where it matters. I've recommended the older models to teams more than once now. Not because they're nostalgic. Because they produce results that standardized programs consistently fail to match. The cost is higher upfront investment from senior staff and a willingness to tolerate early failure as a training tool. You won't see impressive quarterly dashboards from this approach. You'll see people who can actually do the work when it counts. Those are different metrics, and they show up slower. But they stick around longer.
