Training & Enablement Services
This page defines our training and knowledge transfer offerings.
Purpose
Training is not an add-on — it's central to our model. We exist to make clients self-sufficient, and training is how we transfer capability.
Types of Training
End User Training
Description: Training for people who will use the system daily.
Intended outcomes:
- Users can perform their job functions in the system
- Users understand the workflows relevant to their role
- Users can find help resources when stuck
- Reduced reliance on support for basic tasks
Delivery formats:
- Live remote sessions
- On-site workshops (where applicable)
- Written documentation and guides
- Recorded sessions for future reference
What it covers:
- Core workflows for each role
- Navigation and interface basics
- Common tasks and procedures
- Where to find help
What it does not cover:
- Administrative functions
- Technical troubleshooting
- Customization or development
- Process redesign
Administrator Training
Description: Training for people who will administer and configure the system.
Intended outcomes:
- Administrators can manage users and permissions
- Administrators can perform routine configurations
- Administrators understand system architecture
- Administrators can troubleshoot common issues
Delivery formats:
- Live remote sessions
- On-site workshops (where applicable)
- Technical documentation
- Hands-on exercises
What it covers:
- User and permission management
- System configuration options
- Backup and recovery procedures
- Basic troubleshooting
- Monitoring and health checks
What it does not cover:
- Deep customization or development
- Infrastructure management
- Security auditing
- Performance optimization beyond basics
Developer/Technical Training
Description: Training for technical staff who will extend, customize, or integrate the system.
Intended outcomes:
- Developers understand platform internals
- Developers can make safe customizations
- Developers understand upgrade-safe patterns
- Developers can build and test integrations
Delivery formats:
- Live remote sessions
- On-site workshops (where applicable)
- Technical documentation
- Code review and mentorship
What it covers:
- Platform architecture and internals
- Extension and customization patterns
- Safe development practices
- Testing and deployment
- Common pitfalls to avoid
What it does not cover:
- General programming skills
- Infrastructure or DevOps
- Security engineering
- Performance engineering beyond basics
Training Approach
Principles
- Hands-on over lecture: Training includes exercises, not just presentations
- Role-specific: Training is tailored to what each role needs to know
- Documentation included: Written materials support live training
- Sustainable skills: We teach how to learn, not just how to do
What We Expect from Clients
- Dedicated time: Training requires focused attention, not multitasking
- Right participants: Send people who will actually use what they learn
- Follow-up practice: Skills require reinforcement after training
- Feedback: Tell us what works and what doesn't
What Training Does Not Include
| Not Included | Why |
|---|---|
| Ongoing support | Training ends; support is separate |
| Process redesign | Training teaches systems, not processes |
| Organizational change | Adoption is a client responsibility |
| Certification | We don't issue credentials |
| Vendor materials | We provide our own materials |
Training Success Factors
Training succeeds when:
- Participants are properly selected and prepared
- Time is protected from interruptions
- Managers support the learning investment
- Practice follows training promptly
- Documentation is maintained and used
Training fails when:
- Wrong people attend
- Participants multitask during sessions
- No time is allocated for practice
- Documentation is ignored or lost
- Training is treated as a checkbox
How to Discuss Training with Clients
Explaining the Purpose
"Training isn't optional in our model — it's how we ensure you can operate independently. The goal is capability transfer. After training, your team should be able to do the work without us."
Setting Expectations
"Training requires investment from your team — dedicated time, attention, and follow-up practice. We provide the knowledge transfer, but building skills takes effort on your side."
Addressing "We Don't Have Time"
"If you don't have time to train your team, you don't have time to implement this system successfully. Training is not separate from implementation — it's part of making the implementation successful."
Addressing "Just Document It"
"Documentation supports training but doesn't replace it. Reading about how to do something isn't the same as being taught and practicing. We provide documentation, but we recommend live training for critical functions."
Documentation Deliverables
Training engagements typically include:
- User guides: Role-specific instructions for common tasks
- Administrator guides: Configuration and maintenance procedures
- Technical documentation: Architecture and development guidance
- Quick reference cards: At-a-glance reminders for daily tasks
- Recorded sessions: (Optional) Video recordings for future onboarding
Documentation is delivered in editable formats so clients can maintain and extend it.