Custom Development
Build all module assets from scratch with workplace simulation embedded. Every asset should feel like a job task, not test prep.
What you need before starting
- Planning handoff complete: planning doc, objectives, assessment map, activity map, simulation frame, source links.
- Naming prefixes and lab/SBA structure (see below).
What you need to produce
Per module: blueprint, lessons, slides, labs, KBAs/SBAs, facilitator guide. Simulation context must appear in materials; naming must follow conventions; links must work.
What to do
- Confirm planning handoff and simulation frame.
- Build slides (one objective per cluster, workplace context, reflection prompts).
- Build labs (objectives, scenario, steps, reflection) and SBAs (scenario, content parts, questions).
- Build KBAs and other assessments; map each to objectives.
- Write facilitator guide (timing, coaching tips, stand-up prompts, red flags).
- Apply naming convention to all assets; check links.
- Run self-QA (worksheet + PS ID Companion ) before submitting.
Exit criteria
Development is complete when: all required assets are built; naming is correct; links work; facilitator guidance exists; simulation context appears in materials; self-QA is done.
Common mistakes
- Slides reteach what learners could read asynchronously.
- Lab instructions are vague (missing scenario, steps, or requirements).
- Facilitator notes are too thin (don’t tell instructor what to do).
- Assessments don’t map cleanly to objectives.
- Simulation context is pasted in once but doesn’t affect the task.
Wrap every module in a workplace scenario. Labs and assessments = real job tasks (tickets, deliverables, KB-style docs). AI output should be checked for job role and scenario.
Naming convention
Example: Lesson 301.1 - Introduction to Project Management · 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.
Labs: Title, Objectives, Requirements, Scenario/Instructions, Steps, Reflection. SBAs: Same + Content Parts/Steps, Questions. Software: Google Docs/Slides, Camtasia/Captivate/Articulate, Google Sheets, Grammarly. Full list
Step 1: Slides Build
Create slide decks that bring the learning objectives to life with workplace context and simulation framing.
What to Include:
- One objective per slide cluster
- Workplace scenarios and role context
- Interactive elements and reflection prompts
- Clear visual cues and professional design
Example: Network Security (SecureCorp) — inquiry-led
Scenario first; concepts revealed through the investigation.
First day: What’s on the board?
You’re on the SecureCorp security team. Multiple employees have reported odd network behavior; the firewall is blocking connection attempts and several workstations are slow. What would you look at first to tell if this is one incident or several?
SecureCorp — New analyst
This module puts you in the role. We’ll use one scenario to decide what to investigate, then build the concepts you need to do it.
Step 2: Lab Build
Design hands-on activities that mirror real work tasks with realistic constraints and deliverables.
What to Include:
- Realistic work scenario and role context
- Clear step-by-step instructions
- Expected deliverables and scoring criteria
- Time constraints and realistic duration
Example: Revenue Cycle Discrepancy Lab (MedFirst Health)
Healthcare domain — built from scratch with workplace simulation methodology
MedFirst Health Revenue Cycle Discrepancy Lab
MedFirst Health — Revenue Cycle Discrepancy Lab
Scenario
MedFirst Health flagged 14 claims from last week that were denied or underpaid. Your manager pulled the batch and assigned three to your queue. For each claim: identify why it was denied, determine whether the issue is a coding error, a missing modifier, or a payer rule mismatch, and document what needs to happen for resubmission.
Learning Objectives
- Interpret denial codes and payer remittance advice
- Identify common claim errors (coding, modifiers, authorization)
- Document corrective actions for resubmission
Lab Tasks
- Review denial details: Open each claim's ERA (Electronic Remittance Advice) and identify the denial reason code
- Cross-reference documentation: Check the patient chart notes against the codes billed — does the documentation support the claim?
- Identify root cause: Coding error, missing modifier, timely filing, or payer policy mismatch?
- Write corrective action: For each claim, document what needs to change and who needs to act (billing, provider, auth team)
- Prepare resubmission summary: Create a one-page summary for your supervisor showing claim ID, denial reason, root cause, and recommended action
Time constraint
Complete within 60 minutes. Revenue cycle teams typically work 48-hour turnaround on denied claims — speed and accuracy both matter.
Step 3: Assessment Build
Create assessments that directly measure each objective with clear scoring and workplace relevance.
What to Include:
- Coverage of all objectives
- Clear scoring rules and feedback
- Workplace-relevant scenarios
- Retake policies and remediation
Example: Cloud Infrastructure Assessment (CloudOps Inc)
Cloud/data domain — workplace scenarios with professional context
CloudOps Inc Cloud Infrastructure Assessment
CloudOps Inc — Cloud Infrastructure KBA
Assessment Instructions
You're on the CloudOps infrastructure team. A client's web application is experiencing performance issues during peak hours. Use what you've learned about compute and storage to answer these questions in context.
Question 1
The client's EC2 instance is hitting 95% CPU during peak traffic (9-11 AM). They want a fix before tomorrow. As the CloudOps engineer on this ticket, what's your recommended approach?
Question 2
The same client stores user-uploaded images in S3. Monthly storage costs jumped 40% but traffic is flat. What should you check first?
Step 4: Case Study Build
Develop case studies that apply learning in realistic workplace scenarios with decision-making and problem-solving.
What to Include:
- Complex workplace scenario
- Multiple stakeholders and constraints
- Decision points and consequences
- Reflection and learning outcomes
Example: Multi-Client Case Study (spans domains)
Shows learners how the same case-study format works across different industries
Multi-Client Case Study
End-of-Module Case Study — Three Clients, Three Contexts
Instructions
Each scenario requires you to apply the module's concepts in a realistic client context. Pick one, complete the deliverable, and be ready to present your recommendation to the team. Your lead will evaluate both the technical accuracy and whether your documentation is clear enough for someone else to act on.
Case A: MedFirst Health — HIPAA audit prep
Role: Revenue Cycle Analyst
Situation: MedFirst is three weeks from a HIPAA audit. The compliance officer flagged 8 areas where patient data handling doesn't meet policy. Your job: review the flagged areas, determine which are documentation gaps vs. actual process failures, and produce a remediation plan with owners and deadlines.
Deliverable: Remediation plan (1-2 pages) with findings table and priority ranking.
Case B: CloudOps Inc — Cost spike investigation
Role: Junior Cloud Engineer
Situation: A client's AWS bill jumped 35% month-over-month. Traffic is flat. Your lead wants a root-cause analysis before the client meeting tomorrow. Check compute, storage, and data transfer. Identify what changed and recommend a fix.
Deliverable: One-page cost analysis with root cause, supporting data, and recommendation.
Case C: SecureCorp — Phishing incident response
Role: Cybersecurity Analyst
Situation: Three employees clicked a phishing link. Two entered credentials. IT reset passwords, but your team needs to determine scope: were any systems accessed? Is data at risk? Document your investigation steps and produce an incident report.
Deliverable: Incident report with timeline, scope assessment, and containment status.
Quality Check
Before you publish, run these final checks:
- ✅ Objectives present and unchanged from handoff package
- ✅ Simulation frame visible in every artifact (company, role, team context)
- ✅ Every objective has at least one assessment
- ✅ Every assessment has at least one supporting activity
- ✅ All internal links work and resolve correctly
Related tools/templates
- Naming convention — prefixes and lab/SBA structure (see above)
- PS ID Companion — planning, scenarios, and QA review
- Deliverables — templates and examples
- QA Worksheet
Next step
Quality Assurance — Run self-review, complete the QA worksheet, and submit for review.