CREATING WEAVING INCENTIVES
INTO STRUCTURES
How designing a certification program around real motivations instead of mandates produced lasting organizational change.
THE CHALLENGE // 01
THE PROBLEM
A consultancy wanted more employee certifications in cloud provider skills. Periodic announcements produced limited results. I was assigned to solve this using systemic design rather than temporary pushes.
THE APPROACH // 02
UNDERSTAND, DESIGN,
FACILITATE
Discovery: Understand without assumptions
Through ethnographic interviews, I identified key friction points:
Uncertainty prevented action — employees didn't know if efforts would be recognized or how certification processes worked.
Motivation types mattered more than motivation levels; willingness alone doesn't ensure long-term follow-through.
Incentive mapping revealed disconnects between stated company values and actual rewards.
Design: Hook into real motivations
Design guidelines focused on reducing uncertainty, removing information barriers, and decreasing reliance on self-discipline. The solution — "Cloud Cohort" — included five components:
- A cohort leader for coordination
- A prioritized "bounty list" of certifications
- Weekly group study sessions
- Company-wide achievement announcements
- A memorable name, presentation, and spokesperson
Each element addressed specific friction points while building social reinforcement and peer recognition.
Facilitation: Getting the fire started
The catchy name helped people discuss it as an entity. I served as first cohort leader, using humor and accessible information to generate initial momentum until the system became self-sustaining.
OUTCOMES // 03
THE RESULTS
The program produced significantly higher certification numbers than previous attempts and lasted for years with rotating leadership. It proved successful because it aligned with genuine incentives rather than imposed requirements.
SYSTEM INSIGHT: A system that hooks into real motivations instead of mandating compliance can produce lasting change with minimal ongoing effort. The structure does the work.
METHODOLOGY // 04
THE LESSONS
The methodology applies broadly:
DISCOVERY: Research before designing. Understand the actual friction points, motivations, and disconnects in the system before proposing solutions.
DESIGN: Hook into existing motivations. Reduce uncertainty, remove information barriers, and decrease reliance on self-discipline rather than adding mandates.
FACILITATION: Make systems accessible and momentum-driven. Provide the initial energy and structure so the system can become self-sustaining.