To keep training content timely and relevant, your content governance strategy should include both pull mechanisms (requests) and push strategies (proactive sourcing).
This hybrid approach ensures you meet immediate needs while also planning for upcoming changes.
🧾 Pull: Intake-Based Workflow
Pull strategies rely on teams to submit training requests. Ideal for:
New feature rollouts
Policy or process changes
Regulatory updates
🛠 Common Setup:
Intake form or ticket system (e.g., Google Forms, Microsoft Forms, Jira)
Review step by CoE or L&D
Assignment of SME, owner, and priority
Drafting + Review of content
Publishing by a Publisher or CoE
Feedback loop to gather learner data and suggestions
📈 Tip: Track intake-to-publish timelines to identify bottlenecks and improve responsiveness.
📣 Push: Proactive Content Sourcing
Push strategies embed training planning into upstream processes, so training is ready when change happens.
Plug into These Workflows:
Product release roadmaps
Compliance calendars
Quarterly planning cycles
Change management or onboarding checklists
🧠 Run a monthly or quarterly content sourcing review with stakeholders (L&D, Product, Ops, Compliance) to gather needs ahead of time.
🧩 Putting It All Together
A mature workflow uses both push and pull:
Pull ensures teams can get help when they need it
Push ensures you’re not always reacting—you're anticipating
Combined Workflow Example:
Phase | Pull | Push |
Source | Team submits intake form | Needs flagged in planning or release cycles |
Review | CoE reviews and qualifies | CoE surfaces need via review meetings |
Create | SME or creator drafts content | SME or creator drafts content |
Approve | CoE or Compliance approves | CoE or Compliance approves |
Publish | Publisher posts content | Publisher posts content |
✅ Use both workflows together to build a responsive AND strategic content engine.
📌 Next Step:
Ready to implement the intake side of your workflow? Head to Setting Up an Intake Process to choose your tools and get started.