Review Usage by Team Before Calling Adoption Uneven

An overall usage percentage is a starting point, not a verdict. Totals blend differing start dates, manager routines, workloads, and events. One group might have begun last week. Another might have lost a manager. A third might have a steady coaching meeting. One percentage invites an early conclusion before anyone asks what happened inside each group. Your role is to slow the conclusion and bring the conversation back to observable context.

Prepare a segmented view before the meeting. Choose one grouping connected to how work is managed, such as manager, region, role, tenure, or start month. Do not split a small account into every available category. A report full of tiny groups creates noise and leaves nobody responsible for a follow up. Choose groups whose manager or sponsor will join a later conversation. Place activity beside group size, start date, recent operating events, and any existing review rhythm. The page should help someone decide whom to speak with next.

Use a fictional quarterly review. Sales operations leader Celia sees 40 percent activity during August and says, “Only 40 percent of sellers practiced, so our rollout is weak.” Customer success manager Malik replies, “Let’s look by manager and region before we choose a response.” They see South has 18 new hires with regular activity. North has low activity after a manager changed roles in July. East has low activity during a product launch shifting team schedules for two weeks. The same total now contains several situations rather than one diagnosis.

Malik does not assign causes from the report. Numbers show activity inside a chosen period. They do not explain a manager’s calendar, a launch schedule, or a change in ownership. He asks Celia, “Which group result surprises you most?” Celia chooses North because experienced sellers had regular practice during spring. Malik asks who led the earlier routine and who owns one now. Celia says the former manager left in July, and no current manager has taken responsibility for a meeting. A reminder message would not solve an ownership gap.

Give North a specific next conversation. Malik asks Celia to invite Omar, North’s current leader, for a short meeting. Before the meeting, Malik writes the evidence already known: low August activity, manager transition in July, experienced seller group, no identified review routine. He also writes the unknowns: which existing meeting has room for practice, what sales situation deserves attention first, and who will review progress. This preparation stops the call from becoming a debate about a percentage.

During the fictional meeting, Malik asks Omar, “Where would a ten minute practice review fit inside work your team already does?” Omar says Tuesday pipeline review runs long, yet Thursday deal preparation has room for a short roleplay. Malik asks which situation needs practice first. Omar chooses a first meeting opening for a new account segment. They agree four sellers will bring one practice example to Thursday’s meeting. Omar will decide after two Thursdays whether the time still fits the team’s workload. The decision is small, observable, and owned by a named leader.

South needs different questions because South already has activity. A positive number still deserves context. Malik asks Celia what new hires prepare before Friday and what manager Marisol does with those examples. Celia says new hires rehearse a discovery opening. Marisol listens to one recorded practice example during her Friday coaching session, then asks a follow up question tied to an upcoming customer conversation. Malik records the routine, the owner, and the next review date. South offers a useful comparison point, yet no group should copy South without checking local workload and meeting structure.

East needs separate treatment as well. The product launch moved seller attention toward release work and local leaders postponed the usual manager reviews. Malik asks Celia for event dates, affected group size, and the planned restart point. Celia says eight sellers worked on the new product motion and leader Rina scheduled a September 12 review. Rina plans to choose one practice activity for customer conversations during the session. Malik records September 12 as a check in. He does not call East disengaged because the known context points to a time limited schedule change.

Create one discussion record for each segment. Name the group. Add observed activity for the selected period. Record context, owner, next action, and a date for another look. In this fictional account, North reads: low August activity, manager transition in July, Omar owns meeting placement, review due September 9. East reads: low activity during product launch, Rina scheduled a September 12 manager review, Celia will review notes on September 19. These notes turn a chart into concrete work people recognize.

Use an order of questions which leaves room for evidence. Begin with what the group faced during the reporting period. Ask what managers asked people to prepare and how often manager reviews occurred. Ask what changed from the prior month. Then ask who will decide whether the next routine fits the team’s workload. This order helps a sponsor describe facts before reaching for a solution. Avoid presenting a percentage as proof of a cause. Conversations, meeting notes, and dates supply missing context around the report.

An executive meeting often creates pressure for one explanation. Malik gives Celia language rooted in the available record. He says, “South has an active Friday review led by Marisol. North needs a named routine after the July manager change. East has a September 12 restart meeting after launch work.” Each statement names context and avoids a promise about future activity. Celia has a clear distinction for her meeting without claiming every question has an answer.

Follow through after the first manager discussion. On September 9, Malik asks Omar whether Thursday roleplay occurred and whether four sellers had examples ready. If the meeting happened, Malik asks what made preparation easier or harder. If the meeting did not happen, he asks what took the time and whether another existing meeting fits better. Neither response requires blame. The next choice should come from Omar’s answer and the team calendar, not a generic request for stronger adoption.

After East’s September 12 meeting, Malik joins Celia and Rina for a short check in. Malik asks, “What did Rina select for the first practice, and when will Rina hear examples?” Celia says Rina chose a product opening and scheduled an example review for September 19. Malik adds those facts to East’s record. He does not claim an outcome. The group now has a clear reference point for the next report and a person who owns the next review.

Practice before your next customer session with a fictional report for 48 sellers. Divide the sellers into three manager groups of 16. Give A a July manager transition, B an August new hire start, and C a weekly coaching routine. Write one question for each group whose answer changes the next action. Ask a colleague playing the sponsor to demand one reason for a 50 percent total. Respond with the three contexts, then schedule manager conversations for A and B. Finish by entering Omar’s next Thursday roleplay, Marisol’s Friday session, and Rina’s September 19 example review into the fictional calendar before you close the practice meeting.