Lead a Renewal Review When Adoption Is Uneven

An uneven adoption review should begin with evidence client leaders recognize. A renewal conversation loses trust when expansion ideas arrive before anyone examines who used the work, who did not, and why. Your role as client partner is to make a fair review possible. Gather the record, name gaps without blame, and help sponsors choose a next step from what they see.

Return first to the approved purpose. Find the statement of need, teams expected to participate, and work each team agreed to take on. Compare those expectations with current activity. Keep separate notes for planned participation, observed participation, and evidence source. A manager’s memory, attendance record, workflow record, and approved performance measure answer different questions. Do not merge them into one claim. Session attendance does not prove a new process entered daily work. A workflow record does not explain why someone missed a session.

Ask the sponsor what evidence they trust for this decision. Some sponsors value direct reports from team leaders. Others want operational records reviewed by the responsible function. You do not need to settle disagreement by selecting a favored source yourself. Say, “Which evidence would give you enough confidence to decide whether recovery deserves more effort?” Write down their answer and confirm who holds access to each record. This question prevents a later meeting from becoming an argument over evidence standards.

Define uneven adoption with team names and dates. “Adoption is mixed” says little. “Teams Cedar and North began using the agreed playbook during February. Teams Harbor, Glen, East, and South have no confirmed use record as of March 20” gives leaders a record for inspection. Use names allowed within your internal review, or use neutral labels in a fictional practice situation. Do not assign motives before hearing from local owners. A missed session might follow a leadership change, competing priorities, unclear instructions, or a training schedule problem.

In a fictional practice situation, sponsor Amina says, “Only two of six teams use the playbook. Why would we renew?” Client partner Diego replies, “Let us review adoption by team and identify what each leader agreed to own. Before discussing a new term, what evidence do you want in front of you?” Amina asks for session attendance, workflow use records, and comments from each team leader. Diego repeats her request, names record owners, and asks whether March 28 suits a review with her operations director. Amina agrees.

Diego’s next move is not an email urging everyone to use the playbook. He checks the implementation plan with delivery lead Noor and the client program owner. They find one team missed every session after a leadership change. Another team attended but never received a named local owner. Two more teams requested examples suited to their work, yet no response record exists. These findings do not excuse low use. They identify points where leaders need more information before deciding whether a recovery effort deserves support.

Build the review around questions with a decision purpose. For every team, ask whether a leader accepted local ownership, whether people received planned support, whether approved records show use, and what barrier the leader describes. Ask the delivery lead to state what support went out and when. Ask client leaders whether priorities changed. Avoid a broad question such as “What went wrong?” Such wording often invites defenses. “Who was expected to introduce the playbook to Harbor after the January session?” points toward an answer and an owner.

Keep renewal and recovery as separate choices. A sponsor might support work but request a short recovery period before deciding on a new term. Another sponsor might request renewal planning while asking different teams to own a new stage. Present neither route as automatic. State the choice plainly. “Today we need direction on whether to complete a recovery review by April 18, begin renewal planning now, or pause both discussions.” Amina and other client leaders choose a route suited to their priorities. Your responsibility is clear framing and dependable follow through.

Local ownership deserves direct attention. A central sponsor rarely has enough detail to repair every team’s adoption. For each team, name one client leader responsible for confirming local status. Do not name a person merely because they attended a meeting. Ask whether they accept the task and what support they need. A useful request sounds like this: “Priya, will you review your team’s use record, speak with the group, and bring one recommendation to the April 9 session?” Priya might ask for a fresh example or a different schedule. Record her response. Ownership starts only after the owner understands the next act.

Use a short design for the recovery meeting. Start with the evidence record, including gaps and source dates. Next, ask local leaders for their view. Then name work each person accepts before the next check in. Put the renewal choice near the end, after people hear one another. Starting with price or contract dates might pressure local leaders into defending use. A factual review lowers pressure. Nobody needs to present adoption as stronger than their records show.

Suppose fictional team Glen says leadership changes left earlier commitments unclear. Do not ask a new manager to accept responsibility for every earlier choice. Ask what they need before deciding whether their team will participate. They might request a fifteen minute orientation, one work specific example, or a meeting with the original program owner. Seek agreement from people who own those requests. Then set a date for Glen’s leader to report whether their team will join recovery work. A recovery plan without a check point turns into an informal hope.

Be precise with uncertainty. “We have no confirmed use record” differs from “The team never used the playbook.” The first statement identifies what remains unknown. The second makes a claim needing stronger evidence. If a record is incomplete, identify who will inspect the record and by when. If a leader gives an account you cannot verify during the meeting, write “leader report” beside their statement rather than presenting their statement as established fact. This discipline protects the sponsor and delivery team from a decision built on loose language.

Uneven use sometimes reflects a difference in local need rather than a failure of effort. Ask each leader whether the approved purpose still fits their present work. Keep this question separate from whether they completed training. A team might have missed required support. Another team might say the problem the playbook addressed no longer appears in their area. Client leaders need both pieces of information before deciding whether recovery, a change in scope, or a pause deserves further discussion.

After the review, write a short decision note. Include evidence reviewed, unknown points, local owners, work due before the next meeting, and the renewal decision date. Keep recommendation language separate from client decisions. Diego might write, “Amina requested a recovery review for Glen, Harbor, East, and South before renewal discussion resumes.” He should not write, “The client will renew after recovery,” unless client leaders made such a choice explicitly. Send the note for factual corrections, then prepare the next discussion from each owner’s response.

Practice with six fictional teams on one page. Give every team a different record. One has attendance and use. One has attendance only. One lacks a local owner. One changed leaders. One requested different examples. One reports no present need. Write four questions for your sponsor. At the fictional March 28 review, Diego asks Amina to name the recovery choice she wants first. She selects Glen’s orientation. Diego schedules a fifteen minute session with Glen’s new leader and asks Noor to bring the original implementation record.