War-game a partner certification before badge criteria, training paths, and deal benefits harden into how every partner gets ranked.
Certifications fail when the badge invents skill partners never demonstrated, when renewals dual-count the same LMS completion, when deals still flow to uncertified seats, and when customers cannot tell what the badge actually buys. A neat portal screenshot is not evidence.
Freeze the package
State the proposed levels, which skills and labs partners must clear, who owns grading and renewals, what success looks like after two quarters of certified deal quality, and the kill criteria if badge inflation or deal leakage past a named threshold. Attach the curriculum outline, lab rubrics, partner cohort samples, and the measured lag from pass to badge and deal eligibility. If channel, enablement, and sales disagree on whether the badge buys access or just a logo, reconcile before seating.
Name the decision you will make if the war game finds nothing new, and the hold criteria if any level still lacks a named grader or a measured renewal path.
Seats
- Partner. Fear that the badge still loses deals to an uncertified friend of the account team.
- Enablement. Curriculum math that looks clean while lab capacity cannot clear the cohort.
- Channel ops. Renewal tickets that sit without a timed owner.
- Customer. Badge claims that promise skill the last implementation never showed.
- Skeptic. The claim that looks strongest and is least sourced.
Optional counsel seat if partner marketing claims bind the form. Same pack for every seat.
Run the loop
Feed Pingpong the certification memo and exhibits. First pass steelmans the levels. Later passes attack from the seats above. Final pass turns surviving objections into clearer lab rubrics, a published renewal SLA, or a hold. Delete invented "partners already ramp fine" claims and dual-counted completions.
Force a day-after narrative: what happens if a customer screenshots a failed implementation by a badged partner, if renewals never log, or if sales still routes deals around the requirement. If those stories are stronger than your mitigation plan, fix the package before you publish. Separate a partner certification from a partner enablement kit or a channel conflict rule so each decision stays testable.
Ask every seat to mark which steps are optional in practice. Optional lab retakes become skipped within a month if nobody names the owner and the time box. Related: war-game a partner enablement kit, war-game a channel partner deal, pretend you are the enablement lead, pretend you are the partner manager, and the war-game decisions hub. Process: how to run a Pingpong.