Creating a Mentorship Program for Young Coaches
Coaching

Creating a Mentorship Program for Young Coaches

A practical coaching breakdown for your next practice.

By Coach Lee DeForest · Published June 29, 2026 · 13 min read
Creating a Mentorship Program for Young Coaches

Creating a Mentorship Program for Young Coaches

Young coaches improve fastest when they have an experienced guide, not just a job title. A structured mentorship program gives your staff a repeatable development path — and makes your entire program stronger season after season.

Why Mentorship Matters in Coaching

Every experienced coach you respect today had someone who let them stay late after practice, ask questions, and make mistakes in a safe environment. That transfer of knowledge is rarely accidental — it happens when programs are intentional about building it.

John Moore's "Timothy Principle," referenced in the Basketball Vault's program-building material, captures the idea directly: every coaching staff benefits from a three-tier relationship — a teacher (the experienced coach), a contemporary (a peer), and a student (the young coach being developed). When all three roles are filled and functioning, knowledge doesn't just exist in one person's head — it moves through the staff, compounds, and outlasts any single coach's tenure.

Without a formal mentorship structure, young coaches develop by accident. They learn whatever the head coach happens to say in practice, pick up habits from whoever sits next to them on the bench, and figure out the "why" behind decisions years later than they should. A program that intentionally designs mentorship gets better coaches faster — and retains them longer, because people stay where they are growing.

The other reason mentorship programs matter is accountability. A young coach with a mentor is less likely to coast. They know someone is watching their work, asking about their progress, and expecting them to bring questions to each meeting. That structure — someone invested in your growth who also holds you to a standard — mirrors the same environment we try to build for players. It should exist for the coaches too.

Matching Mentors to Mentees

The match is the program. Get it wrong and neither party benefits much. Get it right and the relationship runs itself.

The first filter is philosophy. A mentor and mentee don't need to coach identically, but they need to share a core belief about what basketball is for. A coach who sees the game primarily as player development will clash with a mentor who is purely results-focused. Ask both parties what they think the job is before you put them together — the answer tells you whether the pairing will produce friction or growth.

Obradovic's four-source recruiting model offers a useful parallel for the matching process. Just as he gathers intel from game film, past coaches, network sources, and the player directly before signing anyone, a mentorship coordinator should gather information from multiple angles before making a pairing: observe the young coach in practice, talk to the head coach about their development areas, ask the young coach directly where they want to grow, and look at the experienced mentor's actual track record of developing other coaches — not just their playing success.

The second filter is communication style. Some young coaches need a mentor who pushes hard and gives blunt feedback daily. Others need someone who asks questions and lets them work things out. Neither style is wrong, but a mismatch stalls the relationship. A quick conversation about how each person prefers to give and receive feedback — before the mentorship begins — saves months of awkward misalignment.

Avoid pairing a young coach exclusively with their direct supervisor. The power differential makes honest feedback difficult in both directions. The mentor relationship works better when it sits slightly outside the chain of command — close enough to be relevant, far enough for candor.

Finally, match on hunger. Anson Dorrance's filter for players — self-discipline, competitive fire, self-belief — applies equally to young coaches you're developing. A mentor's time is finite. Spend it on coaches who are genuinely hungry to improve, not on coaches who treat the mentorship as a checkbox. "You cannot drag the unmotivated to excellence," as Dorrance frames it. The mentor relationship accelerates growth it doesn't create growth from scratch.

Setting the Structure and Expectations

A mentorship program without a defined structure is just an informal relationship. Informal relationships are valuable, but they're inconsistent — they happen when both people have energy and disappear when the season gets hard. The goal is a program that runs regardless of whether it's December or March.

Start with frequency and format. Weekly one-on-one meetings of 30–45 minutes are the minimum baseline during the season. These should have a loose agenda: what did the mentee observe in practice this week, what decision did they make that they want to review, and what do they want to work on before the next meeting. The agenda doesn't have to be rigid, but it should prevent the meeting from becoming purely social.

Set a learning focus for each month. Mike Dunlap's practice-culture framework is built around the idea that skills are named, practiced, and evaluated — not absorbed by osmosis. The same logic applies to coaching development. A young coach working on their ability to run a post-practice film session needs that to be named explicitly as the month's focus, with specific opportunities built into the schedule to practice it and feedback built in afterward.

Parcells' 4th-quarter role test translates directly here: at the end of each month, the mentor asks the mentee to describe their specific assignment in a critical situation without prompting. If they can't, the mentor hasn't finished the teaching yet. That reframe — from "the mentee didn't get it" to "the mentor hasn't prepared them" — is the right accountability structure for a development program.

Write the expectations down. Not a formal HR document, but a one-page agreement: meeting frequency, how feedback will be delivered, what the young coach is expected to bring to each meeting, and what the mentor commits to providing. When expectations are written, both parties can refer back to them if the relationship drifts. Morgan Wootten's program at DeMatha ran on this principle — culture is a discipline, built into daily routines and written commitments, not speeches.

Every program must have non-negotiables — attitude and effort, held the same every day. How you do anything is how you do everything. You can always hear a good team.

— Kelvin Sampson, Basketball Vault

Teaching the Craft, Not Just the Plays

The most common failure in coaching mentorship is staying at the surface — teaching X's and O's, discussing what plays to run, reviewing film for tactical decisions. None of that is wrong, but it misses the deeper layer: teaching young coaches how to think, how to build relationships with players, and how to manage themselves under pressure.

Messina's concept-coach model is the right framework here. The goal is not to produce a coach who knows your system — it's to produce a coach who can read what's happening and know what to do. "If this happens, what do we do?" is the question that separates concept coaches from action coaches. A mentorship program should be building concept coaches. That means the mentor asks the young coach to explain their reasoning, not just their decision. Why did you call timeout there? What did you see in the defense that made you switch to zone? What were you trying to accomplish with that substitution?

Todd Lickliter's five-step teaching model — explain, demonstrate, imitate, correct, repeat — applies directly to coaching development. A mentor doesn't just tell a young coach how to run a pre-game talk. They explain the goal, demonstrate what it looks like (invite the young coach to observe their own pre-game talk), let the young coach try it, correct what didn't work, and build the rep count until it becomes automatic. Teaching is on the mentor, not the mentee. As Sampson puts it: "Nothing's learned until it's taught. If they're not learning, it's your fault."

The relational side of coaching is equally important to teach and equally neglected. Hubie Brown's rule — say something to every player every day, look them in the eye — is a craft skill. So is Tom Crean's framework: players expect coaches to demonstrate competence, sincerity, reliability, and trustworthiness. Young coaches need to understand what those words mean in practice, not just in theory. A mentor who models those qualities and then explicitly names what they did and why is teaching the craft at a level that no clinic can replicate.

Build in opportunities for the young coach to lead. They should run a drill, conduct a film session, lead a team meeting, or handle a difficult player conversation — with the mentor present to observe and debrief afterward. Growth happens in the doing, not in the watching. The mentor's job is to create the opportunity, observe without interfering, and deliver clear feedback immediately after. Dunlap's praise-prompt-walk-away loop is the right model: acknowledge what went well, prompt on what to adjust, then step back and let the young coach apply it.

The best mentorship programs teach young coaches how to think about the game and how to build trust with players — not just which plays to run. If a young coach can only execute your system, you've trained a technician. If they can read a situation and respond with sound judgment, you've developed a coach.

Building Accountability and Tracking Growth

Development without measurement drifts. A young coach who meets weekly with a mentor but never evaluates their own progress will improve slowly, because they have no clear picture of where they started or how far they've come. The mentorship program needs a lightweight tracking system.

John Tauer's INCHES framework — Improvement, No Excuses, Communication, Health, Energy/Enthusiasm, Selflessness — was designed for players, but each of those traits maps directly onto coaching development. At the start of a mentorship cycle, mentor and mentee can rate the young coach across each dimension, set a specific growth goal for the season, and revisit the rating at the midpoint and end. The conversation that generates the rating is often more useful than the number itself — it forces both parties to be specific about what growth looks like.

Bethel's Me First, For Us question filter is worth installing in any mentorship program. The three forbidden question types — Why is this happening to me? When will they fix it? Who dropped the ball? — show up regularly in young coaches who are struggling. A mentor who can name the pattern ("You're asking a Who question — let's reframe that as What can I do here?") helps the young coach build a more accountable internal vocabulary. The goal is coaches who instinctively ask "What can I do to make this better?" rather than coaches who look for someone to blame when things go wrong.

Monthly written self-assessments are one of the most underused tools in coaching development. Rick Majerus used one-minute daily assessments with players — "What did you do well and why? What can we do better?" — and the same discipline works for coaches. A brief monthly written reflection from the young coach, shared with the mentor before their meeting, gives both parties something concrete to work from. It also creates a record of growth over time that becomes visible and motivating as the season progresses.

Hold the mentors accountable too. A program where only the young coach is being evaluated will stall. Mentors should do a brief self-evaluation at the midpoint: Am I showing up prepared? Am I giving clear, specific feedback? Am I creating enough opportunities for the young coach to practice? The program works when both parties feel genuine accountability to the relationship — not just when one party is being graded.

Coach's Note

Start your mentorship program with a single pair before trying to scale it to your whole staff. Get the structure right with one mentor and one young coach over a full season — document what worked, what fell apart, and what each person wished had been clearer from the start. Then use those lessons to build the full program. Launching too many mentorship relationships at once without a proven model produces shallow connections that fizzle by January.

Making the Program Last Beyond One Season

The test of any mentorship program is whether it survives staff turnover, a difficult season, and the natural tendency to deprioritize development when the schedule gets crowded. Programs that endure are built into the structure of the operation — not dependent on any one person's enthusiasm.

Make mentorship part of every new coach's onboarding, not an optional perk for those who ask. Obradovic's preseason system defines staff roles before day one and onboards each person personally before expecting them to perform professionally. The same logic applies here: a young coach who joins your staff should enter a mentorship relationship in their first week, with a named mentor, a written expectations document, and a first meeting scheduled before they've coached a single practice.

Build a culture of open learning throughout the staff, not just in the mentor-mentee pair. Bob Hurley's practices were open to other coaches as a deliberate cultural signal — learning is welcome here, and we have nothing to hide. John Moore's Timothy Principle works best when the whole staff sees the mentor-mentee relationship as normal, not exceptional. When experienced coaches share what they're still learning and where they're still struggling, they give young coaches permission to do the same.

Use the program to build your succession pipeline. The young coaches in your mentorship program today are your future assistants and eventually your future head coaches. If you think of the program that way from the beginning, you'll invest differently in it. Every hour a mentor puts into a young coach's development is an investment in the long-term health of your program — and of the game. Crean's "legacy of leadership" framing is the right lens: "A player is a leader when they are in your program. The legacy of leadership is the feel he leaves when he's gone." The same is true for coaches. What habits, standards, and philosophies does your mentorship program leave behind in every young coach who goes through it?

Review the program formally at the end of each season. Bring together all the mentors and all the young coaches for a 90-minute debrief. What did each pair accomplish? Where did the structure break down? What do the young coaches wish they had been taught earlier? What do the mentors wish they had done differently? Use those answers to update the program — the expectations document, the matching criteria, the monthly focus areas — before the next season begins. A program that reflects and adjusts compounds. A program that repeats exactly what it did last year slowly loses relevance.

The final word on longevity is senior ownership. Dean Smith's program made seniors responsible for the culture daily, because it was their team. Apply the same principle to your mentorship program: the coaches who went through it become the ones who run it. They know what it gave them, they feel ownership of it, and they're motivated to make it better for the coaches who come after them. That cycle — mentee becomes mentor, standards improve with each generation — is what turns a good program into a great one.

  • Before making a mentor-mentee pairing, gather information from at least three sources: observe the young coach in practice, speak with the head coach about their development gaps, and ask the young coach directly where they want to grow this season.
  • Set a named learning focus for each month of the mentorship — not a vague goal like "get better at practice management," but a specific skill like "run a 20-minute film session independently by the end of November."
  • Use Lickliter's five-step teaching model for every skill you want the young coach to develop: explain the goal, demonstrate it, let them imitate it, correct what didn't land, and repeat until it's automatic.
  • Install the Me First, For Us question filter at the start of the program — teach young coaches to replace "Who dropped the ball?" with "What can I do to make this better?" and make it part of your debrief language all season.
  • At the end of each month, run a modified Parcells role test: ask the young coach to explain their reasoning behind one key decision they made that week. If they can't articulate the why clearly, the mentor hasn't finished the teaching.
  • Review the full mentorship program formally at the end of the season with all pairs present — update the structure based on what broke down before the next cohort begins.

Want more basketball coaching strategies, drills, and tools?

Join the Online Basketball Playbook newsletter →

Coach Development Program Building Staff Culture Mentorship Basketball Young Coaches