Vendor Development
Wrap and extend vendor content (CompTIA, Schneider, etc.) with workplace simulation so it feels like professional practice, not test prep. Do not edit the vendor material itself.
What you need before starting
- Planning handoff complete; simulation frame from Planning.
- Vendor assets (slides, labs, quizzes) and license/usage clarity.
- Naming prefixes (same as custom).
What you need to produce
Per module: module-level workplace wrapper (2–3 slides or script), supplemented materials (e.g. team dynamics, KPIs), naming applied, facilitator guide that explains how to run the simulation around vendor content. Links work; self-QA done.
What to do
- Identify the vendor asset and which objective/skill it supports; don’t rewrite vendor content.
- Create module-level workplace context wrapper (company, role, team, KPIs); keep it to 2–3 slides or one script.
- Add supplemental materials (e.g. team intro, ticket source, stand-up prompts) so the frame is clear.
- Apply naming convention; ensure links and references work.
- Write facilitator guide (how to introduce simulation, when to use vendor vs wrapper).
- Run self-QA before submitting.
Exit criteria
Development is complete when: wrapper and supplements are in place; naming correct; links work; facilitator guidance exists; simulation context is clear; self-QA done.
Common mistakes
- Editing or trimming vendor content instead of wrapping it.
- No module-level wrapper, so each asset feels disconnected.
- Vendor content pasted in without contextual framing (learners don’t see the job context).
- Facilitator notes don’t explain how to use the simulation with vendor material.
Simulation frame from Planning (role, team, tickets, KPIs) drives how we wrap. Vendor slides/labs stay as-is; we add context so it feels like real job tasks.
Naming convention
Same prefixes as custom. Example: Lesson 301.1 · GLAB 301.1.1 · KBA 301 · SBA 301 · MBP 301
Example first: Lesson 301.1 - Introduction to Project Management · GLAB 301.1.1 - Guided Lab Name · KBA 301 - KBA Name · SBA 301 - SBA Name · MBP 301 - Module Blueprint Name
| Prefix | Meaning | Type of content |
|---|---|---|
| ALAB | Assignment Lab | Labs that post a problem statement; learners go through on their own. Typically graded. |
| ACT | Activity | Simple, quick activities or exercises. |
| CS | Case Study | Scenario-based activities requiring research and tasks. |
| CAP | Capstone Project | Summative assessment capturing multiple skills. |
| DLINK | Download link | Materials that need to be downloaded. |
| ELINK | External link | External links as class resources. |
| GLAB | Guided Lab | Step-by-step labs. Usually not graded. |
| IPLAB | In-Person Lab | Labs delivered in-person only. |
| HO | Handout | Resources and/or reference sheets. |
| KBA | Knowledge-Based Assessment | Summative, end of module. Typically multiple choice. Always graded. |
| Lesson | Lesson | Slideshows/documents presenting new information; submodule. |
| MBP | Module blueprint | Document housing all resources and links for a module. |
| PA | Practice Assignment | Practice work. Not graded. |
| POC | Proof of completion | Proof of training from another vendor. |
| Quiz | Quiz | Short quizzes, daily or weekly. Graded. |
| PQuiz | Practice Quiz | Quizzes not for grading. |
| eBook | Electronic Book | Electronic books for learners. |
| RS | Resource file/Document | Template or reference document. |
| SBA | Skills-Based Assessment | Summative; learners use skills from module. Graded. |
| SURV | Survey | Surveys to measure progress. |
| VLINK | Video Link | Link to video platform. |
| WS | Worksheet | Worksheets with problems to solve. |
| DISC | Discussion | Discussion boards on Canvas. Graded or ungraded. |
Graded/required: R- prefix (e.g. R-ALAB). Quiz, KBA, SBA, Capstone = always graded.
Step 1: Identify the Vendor Asset
What the Team Does: Look at the vendor material being supplemented (slide deck, lab, quiz).
- Note the technical skill it covers
- Note the learning objective it supports
- Don’t rewrite or trim the vendor content
Example: CompTIA Module 1 - “What Does an IT Specialist Do?”
- Technical skill: IT specialist responsibilities and troubleshooting methodology
- Learning objective: “Describe what an IT specialist is and their responsibilities”
- Vendor content: Slides, labs, and quizzes stay exactly as provided
Step 2: Create a Module-Level Workplace Context Wrapper
What the Team Does: Create a comprehensive workplace simulation context that wraps the entire module, not individual assets. This saves time and provides consistent context throughout.
- Introduce a company/role (TechCorp, Junior IT Technician, Hospital IT Support)
- Establish the overall workplace scenario and learner’s role
- Set up team structure with working units and group dynamics
- Define team KPIs and performance metrics
- Create a module introduction that sets the stage for all vendor content
- Keep it to 2-3 slides or a comprehensive instructor script
Example Module Wrapper: View Example: Module Context Wrapper with Team Dynamics and KPIs - See how to create a comprehensive module-level workplace context wrapper with team structure and shared KPIs.
Full example: Module context wrapper with 8 slides
First shift: What’s on the board?
You’re in the TechCorp IT queue. Three tickets are open; your team lead said to grab one after stand-up. What do you need to know about your role and the team before you pick a ticket?
TechCorp IT — New hire
This module uses the same role and team for every activity. By the end you’ll have practiced how we work: how we troubleshoot, how we document, and how we hand off to the client.
Step 3: Set Up Team Structure and Group Work
What the Team Does: Encourage group work throughout the module by treating teams as working units with shared responsibilities and accountability.
- Set up teams of 3-4 learners as working units
- Establish team roles and responsibilities
- Create shared deliverables and group assessments
- Use team-based problem-solving scenarios
- Track team KPIs and performance metrics together
Key Elements to Include:
- Team formation and role assignments
- Shared accountability for team KPIs
- Collaborative problem-solving activities
- Peer review and feedback processes
- Team-based assessments and deliverables
Example: Team Dynamics and KPIs Introduction View Example: Team Dynamics and KPIs Introduction - See how to introduce group work, team structure, and shared KPIs in your module context wrapper.
Step 4: Add Reflection & Discussion Prompts
What You Do: After the vendor content, create 2–3 questions that tie the technical knowledge to real work.
Examples (different domains):
- Healthcare: “If this system went down in a clinic during patient intake, what’s the impact on operations?”
- Cloud: “Your client’s app is returning 502 errors during peak hours. What would you check first, and what would you escalate?”
- IT Support: “What would you document in the ticket before and after attempting a fix?”
Example: Healthcare IT reflection prompts
Post-Lesson Reflection Questions — Healthcare IT
After the EHR system administration lesson
MedFirst Health — use these with your team to connect the vendor content to the job:
1. Impact assessment
The EHR system at MedFirst goes down during morning check-ins. Front desk can't pull patient records, and providers are backing up. What's the business impact? Who do you notify first — your lead, the clinic manager, or both?
2. Compliance awareness
While troubleshooting the EHR issue, you notice a shared login being used at the front desk. That's a HIPAA concern. How do you handle it — do you fix it now, document it, or escalate? What's your obligation?
3. Handoff communication
Your shift ends before the EHR issue is fully resolved. Write a 3-sentence handoff note for the next technician that covers: what you found, what you tried, and what's still open.
Step 5: Design a Professional Deliverable
What You Do: Turn a vendor activity into a workplace-style output.
How it works: Take a vendor activity and add a workplace-style output.
- Vendor Lab: “Match each component to its function.” Add-On: “Complete an inventory report for your supervisor showing components, condition, and issues found.”
- Vendor Quiz: “Which component processes instructions?” Add-On: “Document your answer in a troubleshooting log entry explaining why it matters in the client context.”
Example: CloudOps resource audit template (cloud domain)
CloudOps Resource Audit Report Template
CloudOps Inc — Resource Audit Report
Executive Summary
[2-3 sentence overview: what you audited, key finding, recommendation]
Resources Audited
| Resource | Type | Utilization | Finding |
|---|---|---|---|
| prod-web-01 | EC2 (m5.xlarge) | [Avg CPU / peak] | [Right-sized / oversized / issue] |
| client-uploads | S3 Bucket | [Storage / lifecycle status] | [OK / missing lifecycle policy] |
Step 6: Add One Skills-Based Assessment (SBA) Per Module
What You Do: At the module level, design one hands-on SBA that ties everything together.
Example for Module 178: Install and configure OpenEMR locally, create two user accounts, and submit a setup log with screenshots.
Example: TechCorp Hardware Troubleshooting SBA
TechCorp Hardware Troubleshooting SBA
TechCorp Hardware Troubleshooting SBA
Scenario
Morning shift. You get an urgent ticket from Downtown Medical Center: patient registration PCs are so slow that wait times are over 10 minutes. The admin wants it fixed now. What do you need to ask before you start? What’s your first diagnostic step?
Your task
1. Diagnose
Use the methodology from the vendor content: identify the problem, form a theory, test it. Document what you find so the ticket can be handed off if needed.
2. Deliver
Complete the TechCorp Hardware Inventory Report (or equivalent): what you found, what you did, and a short status line for Sarah Chen so she knows where things stand.
Quality Check
Before you publish, run these final checks:
- ✅ All planning objectives covered by vendor content + additions
- ✅ Simulation frame visible in every artifact (company, role, team context)
- ✅ Professional deliverables replace academic assessments
- ✅ Team collaboration and workplace communication included
- ✅ All internal links work and resolve correctly
Related tools/templates
- Naming convention — same prefixes as custom (see above)
- PS ID Companion — planning, scenarios, and QA review
- Deliverables — templates and examples
- QA
Next step
Quality Assurance — Run self-review, complete the QA worksheet, and submit for review.