A maker enablement programme that produces a hundred certified makers and ten active builders six months later has not succeeded. The objective is capability β makers who can take a real business problem and build a solution that works reliably in production.
The problem with most training approaches
Tutorial-based training produces makers who can follow steps and cannot generalise to new problems. The gap between completing a tutorial and independently solving a business problem requires exposure to real complexity: ambiguous requirements, imperfect data, error handling, testing, deployment.
A more effective structure
Phase 1 β Foundation (2-3 weeks): platform fundamentals, environment structure, solution concepts, basic connectors.
Phase 2 β Guided build (3-4 weeks): real-world scenario with coaching. Makers encounter real complexity with support.
Phase 3 β Independent project (4-6 weeks): each maker identifies a real problem and builds a solution with structured check-ins but no step-by-step guidance.
Phase 4 β Community integration: completed makers join the community and answer questions from newer makers.
Selection matters
Selective cohorts β working with people who have identified a real problem β produce better outcomes than open enrolment driven by curiosity.
The best maker I have ever worked with was a procurement analyst furious about a specific manual process. The fury was the motivation. The problem was the learning vehicle.
Measure your programme by active builders and deployed solutions six months after completion β not by enrolment numbers or certifications.