mentoring_program_design v1.0.0

name: "mentoring_program_design" description: "Design and run a mentoring program end to end: define purpose and format, screen and train participants, match pairs with a scored rubric and a preference check, set goals pairs can stick to, run structured sessions, check health at the midpoint, and close or rematch without harm. Use when asked to start, fix, or evaluate a workplace, school, or community mentoring program, build matching criteria, write session guides, or create tracking templates."

Mentoring Program Design

Purpose

Build a mentoring program that survives past the kickoff meeting. Most programs fail in ordinary ways. Pairs meet once, lose the thread, and stop without telling anyone. This skill prevents that with a clear purpose, a stated matching method, training before the first session, a written agreement and goals for each pair, scheduled support from the program owner, and a planned ending.

The design follows the six areas in MENTOR, Elements of Effective Practice for Mentoring, 4th edition: recruitment, screening, training, matching and initiation, monitoring and support, and closure. It also uses Kathy Kram's four phases of a mentoring relationship: initiation, cultivation, separation, and redefinition. Use the phases to time support. Early sessions build trust, the middle does the real work, and the end needs planning rather than drift.

Workflow

1. Write the program brief first. Record the purpose in one sentence, who the program serves, who is excluded and why, the format, the duration, and the outcome the sponsor wants to change. Formats to choose from:

• One to one: one mentor with one mentee. Best for career growth, leadership, and role transitions.
• Peer: people at a similar level mentor each other. Best for practice, accountability, and shared problems.
• Group: one mentor with a small group. Best when mentor supply is short or the topic is common.
• Reverse: a junior person mentors a senior person on a defined topic, such as a tool or a community they know well.
• Flash or office hours: short, single topic meetings with no ongoing pair. Best as an entry point, not as a substitute for a sustained pair. Pick one primary format per cohort. Mixing formats without saying so confuses expectations.

1. Set eligibility, capacity, and screening. State who can apply as a mentor and as a mentee, the time commitment in plain terms, and the minimum attendance the program expects. Screen for time, commitment, and suitability, per the Elements of Effective Practice. A willing mentor with no time is a failed match waiting to happen. Cap each mentor at a number of mentees they can actually serve, and write that cap down. Keep a waitlist rather than overloading mentors.

1. Recruit honestly. Describe the aims and the expected outcomes realistically in the call for participants. Say how matching works, how long the program runs, what training is required, and what happens if a pair is not working. Overselling the program fills the cohort with people who wanted something else.

1. Collect matching inputs. Use references/matching-rubric.md. Each participant completes a short profile covering:

• Goals: the one to three things the mentee wants to work on, in their own words.
• Strengths offered: topics the mentor can genuinely help with, based on work they have done.
• Preferences: meeting mode, meeting rhythm, communication style, and any preference for a mentor with a similar or a different background. Ask, do not assume. ATD guidance notes both preferences are common and both are valid.
• Constraints: reporting lines, conflicts of interest, time zones, access needs, and topics that are out of scope.
• Deal breakers: anything that should block a match outright.

1. Match with the rubric, then confirm with people. Score candidate pairs with scripts/match_score.py or by hand using the rubric in references/matching-rubric.md. Hard blocks come first: direct reporting line unless the program explicitly allows it and both sides agree, a stated conflict, a schedule that cannot overlap, or a deal breaker from either profile. Then score goal fit, strength fit, availability, and preference fit. Send each person their proposed match with a short reason for the pairing and a no fault veto window. A veto needs no explanation and triggers a rematch attempt, not a debate. Where the pool allows it, let mentees rank two or three mentor profiles. Self selection, or a choice among stated options, is a supported practice when a fully assigned match would feel imposed.

1. Train before the first session. Run one training for mentors and one for mentees, or one joint session with separate breakouts. Cover the mentor role and the mentee role, active listening, giving feedback that names a behavior and its effect, confidentiality and its limits, boundaries, what to do when stuck, and how to end a session with clear next steps. ATD guidance ties participant training in communication, active listening, and constructive feedback to better results against learning goals. Do not skip training to save a week. Untrained pairs spend their first month guessing at the rules.

1. Hold a structured first meeting and sign a pair agreement. Use the first session guide in references/session-guides.md. The pair leaves with a one page agreement covering purpose, goals, meeting rhythm and mode, how they will reschedule, what stays confidential, and how either person can raise a problem or ask the program owner for a change. Keep the agreement short enough that both people will actually read it.

1. Set goals pairs can stick to. Limit each pair to two or three goals for the cycle. Write each goal with an owner, a visible sign of progress, and a review date. Prefer a goal the mentee can act on between sessions, such as leading one meeting, shipping one piece of work, or holding three conversations with a new group. Reject goals that depend entirely on someone else, such as getting promoted by a fixed date. The mentor advises and opens doors. The mentee does the work and reports back.

1. Run sessions on a repeatable structure. Use the standard session guide in references/session-guides.md: check in on commitments from last time, review progress on goals, work one main topic, agree one to three actions, and confirm the next meeting before ending. The mentee brings the agenda. The mentor asks questions before giving answers, and shares experience when it helps the mentee decide. End every session with the next date booked. A pair that leaves without a next date is already drifting.

1. Monitor and support, do not just launch and leave. The program owner checks pair activity on a fixed rhythm and runs a formal midpoint check with every pair using references/tracking-templates.md. Watch for missed meetings, repeated rescheduling, one sided cancellations, goals that never move, and either person going quiet. Intervene early with a short, direct conversation. Offer help in this order: clarify expectations, adjust the rhythm or mode, add a resource or a joint session, reassign goals, and only then consider a rematch. Research on youth mentoring found that matches that ended early showed no benefit, and rematches after an early ending did worse in that study. That finding comes from school based youth programs, so treat it as a caution for any program rather than a workplace guarantee: protect continuity first, and treat a rematch as a serious step, not a quick reset.

1. Close on purpose, then allow redefinition. Give ample warning of the end date, which the agreement already states. In the final sessions, review the goals, name what changed, name what did not, and agree what contact, if any, continues after the program. Per Kram's phases, a pair may end cleanly at separation or move into redefinition as peers or occasional contacts. Both are good outcomes. A pair that fades out with no final session is a program failure, even if the meetings were good. If a pair must end early, state the reason clearly and directly, give as much notice as the situation allows, and hold a closing conversation. Do not let a pair end by silence.

1. Evaluate the program, not just the pairs. Pilot with one small cohort before a full rollout, per ATD guidance. Measure at four levels, following the approach ATD describes with the Kirkpatrick model: how participants reacted to the program, what they learned, whether behavior changed at work, and whether the outcome named in the program brief moved. Use the health measures in references/tracking-templates.md. Report results against the purpose from step 1, including the pairs that ended early and why. A report that only quotes happy pairs teaches the next cohort nothing.

Output Contract

Deliver a program packet containing, at minimum:

• A one page program brief: purpose, audience, format, duration, eligibility, capacity, sponsor, and the outcome to be measured.
• Participant profiles and the matching rubric with hard blocks, scoring, and the veto and rematch rules.
• The match list with a one line reason for each pairing and a record of vetoes and rematches.
• Training agendas for mentors and mentees.
• The pair agreement template and the goal sheet template, completed for each pair.
• Session guides for the first session, standard sessions, the midpoint check, and the closing session.
• A tracking sheet for pair health and a program health summary with the measures from references/tracking-templates.md.
• A closing and evaluation report that covers all pairs, including early endings, and states what the next cohort will change.

Operating Rules

• Goal fit beats surface similarity. Match a mentor's proven strengths to a mentee's stated goals. Shared background can help trust, and a different background can widen a network. Neither replaces goal fit.
• No silent endings. Every pair ends with a conversation, a reason, and a record. Silence is the one ending the program never accepts.
• Confidentiality has stated limits. What a pair discusses stays with the pair, except for safety concerns, unlawful conduct, or anything the program brief names in advance as reportable. Write the limits into training and into the agreement.
• The line manager stays out of the pair's content. Managers may support time for mentoring. They do not receive session notes or goal details unless the mentee chooses to share them.
• Mentees drive, mentors guide. The mentee owns the agenda, the goals, and the follow through. A mentor who does all the work creates dependence, not growth.
• Numbers need a source or a label. Program targets, such as attendance or completion, are management choices and must be labeled as targets. Do not present a target, or a vendor claim, as a research finding. If a number cannot be traced to a study or to the program's own data, cut it.
• Fix the system before blaming the pair. Repeated missed meetings across many pairs usually mean the rhythm, the workload, or the training is wrong. Check the program design before judging individuals.