Meraki 400-Site Rollout Stalls at Activation
A national retail chain is nine months into a 400-store Meraki rollout. 150 stores are live, but only 58 have logged into the dashboard in the last 45 days; 22% of store managers have completed the assigned onboarding path. The implementation partner configured devices and left; no store-level training was delivered beyond a PDF. The customer's project manager reports 3x the expected severity-3 tickets, mostly Wi-Fi authentication and POS connectivity. Two pilot regions show better adoption because their regional IT lead runs a weekly 15-minute store huddle. The steering committee meets weekly and focuses on site count, not usage. Go-live for the remaining 250 stores is scheduled in six months. The customer considers the project 'on track' because install dates are met.
1. Distinguish the onboarding and adoption gaps in this account. What evidence tells you the project is not on track despite install dates?
Read the worked answer
Onboarding is the set of actions that make the solution operable: configuration, integration, training, support readiness, and handover. Adoption is the repeated behavior that produces value: store managers using the dashboard, staff connecting devices correctly, and regional IT resolving issues without escalation. This account has completed deployment but not onboarding.
The evidence is specific. Only 58 of 150 live stores have logged into the dashboard in 45 days, so the tool is not part of the operating rhythm. Only 22% of store managers completed the onboarding path, and the only training artifact is a PDF, which is not a handover. Tickets at 3x the expected severity-3 rate indicate that authentication and POS workflows were not validated at store level. The pilot regions prove the gap is not inherent to the solution: where a regional IT lead runs a weekly huddle, adoption is better. The project is on track for installs, not for operational readiness. If the next 250 stores go live under the same model, the ticket backlog and adoption debt will scale with them.
2. Design a 30-60-90 day adoption plan with leading indicators. Who owns each action?
Read the worked answer
Days 0-30: stabilize and activate. The CSM owns a store-manager quick-start session and a one-page dashboard routine. The partner owns a Wi-Fi and POS authentication runbook and a ticket triage review. The customer project manager owns a stop-ship rule: no new store goes live without a named store manager who has completed training. Regional IT leads run the 15-minute huddle in all live regions, using the pilot model.
Days 31-60: scale the behavior. The CSM and regional IT leads identify peer champions in each region and publish a weekly adoption dashboard. The partner fixes recurring authentication defects and reports root causes. The customer PM adds adoption readiness to the steering committee agenda, not just site count.
Days 61-90: prove readiness and gate the next wave. The CSM runs a store-manager certification check and a support handover review. The customer PM and regional IT lead sign off on gate criteria.
Leading indicators: dashboard activation percentage, training completion, huddle attendance, tickets per live store, first-contact resolution, and time to resolve authentication issues. Lagging indicators such as site count should not be the primary success measure.
3. What gate criteria would you recommend before the next 250 stores go live, and how would you handle the customer's 'on track' belief?
Read the worked answer
I would recommend five gates: at least 85% of store managers in live stores have logged into the dashboard in the last 30 days; at least 90% have completed the onboarding path; severity-3 tickets per store are at or below the pilot-region baseline; every region has a named IT lead running the weekly huddle; and the partner has closed the top three authentication root causes.
Handle the 'on track' belief with data, not contradiction. I would say: 'You are on track for installation. The risk is operational readiness. The pilot regions show what good looks like, and the live-store data shows most stores are not there yet. If we release 250 more stores without the readiness gate, we will multiply the ticket pattern.' Then I would ask the steering committee to adopt the gate as a joint risk control, not as a CSM scorecard. I would bring one pilot-region example and one at-risk region example. The goal is to change the definition of done from 'device installed' to 'store operating normally.'