The Challenge
Course development at Colibri was slow, manual, and error-prone. Teams spent excessive hours on repetitive tasks — template setup, content assembly, formatting checks, and publishing workflows. Each course followed a similar structure, yet every build started nearly from scratch. The bottleneck wasn't talent or effort; it was the process itself.
The Approach
I started by mapping the architecture of the entire production pipeline — timing each phase, documenting system dependencies, and identifying where human judgment was essential versus where tasks were purely mechanical. The pattern was clear: roughly 60% of development time went to work that could be systematized. I chose JavaScript and Python for the stack — JavaScript for its DOM manipulation strengths (critical for content assembly) and Python for data processing and QA automation. I designed the platform architecture iteratively, shipping each module to the team for feedback before moving to the next.
The Solution
TAGFORCE is a custom-architected internal platform that handles template generation, content assembly, formatting standardization, QA pre-checks, and publishing workflows. It doesn't replace the instructional design process — it eliminates the mechanical overhead around it. Designers now focus on learning experience decisions while TAGFORCE handles the build pipeline. The system architecture integrates directly into our existing ecosystem, requiring minimal behavior change from the team.
Workflow Transformation
Before TAGFORCE
After TAGFORCE
The Results
60%
Faster Development
$200K+
Annual Cost Savings
Multi-Team
Adoption Across Org
TAGFORCE cut average course development time by 60% and saves over $200K annually in production costs. It was adopted across multiple teams and became a core part of Colibri's development infrastructure. Beyond the numbers, it shifted the team's focus from production mechanics to learning design quality.
Reflection
Building tools for your own team teaches you what no vendor product can. When you sit in the same workflows you're automating, you catch edge cases that outside developers miss. The biggest lesson: automation isn't about replacing people — it's about freeing them to do the work that actually requires human judgment.