14.2 Deciding When and How to Outsource Development

Outsourcing is a make-or-buy decision

The CIT development blueprint asks when to outsource course components. Outsourcing assigns work to an external provider; it does not transfer the employer's responsibility to identify the need, validate requirements or accept the result. A provider can bring specialized capability, capacity or equipment, but still needs a clear brief and appropriate oversight.

Begin by defining the required outcome and the capability gap. The team might lack accessible media-production skills, translation expertise, specialized simulation development or sufficient delivery capacity. Distinguish that gap from a missing decision about objectives. Hiring a provider before clarifying the task can produce an expensive asset that solves the wrong problem.

Comparing internal and external options

Evaluate capability, time, total cost, quality, maintainability, confidentiality and control. An internal team may understand local work but lack a specialist skill. A provider may have production experience but little knowledge of the site's approved procedure. A hybrid approach can assign specialized production externally while keeping technical ownership and local validation internal.

Compare like scope. A quote for a video is not equivalent to a quote including practice, assessment, captions, source files and updates. Include internal coordination and review effort in the cost comparison. Low initial price can be misleading if future revisions require expensive proprietary changes or the organization cannot retrieve its own records.

Writing the development brief

Specify the audience, objectives, sources, conditions, deliverables, access needs and acceptance criteria. Supply current approved procedures and identify which questions require technical-owner resolution. Describe permitted use of learner or workplace information and avoid sending unnecessary sensitive data. Include milestones for prototype, review, pilot and final acceptance.

The brief should identify what the provider may change and what requires approval. A media producer can improve visual structure, but cannot invent a torque, medical rule or hazard-control limit. A translator must preserve technical meaning and route uncertain terminology to qualified reviewers. A contractor's polished output does not replace subject matter validation.

Evaluating provider evidence

Ask for relevant samples and evidence of the specific capability. Review accessible functionality, instructional decisions and maintainability rather than relying only on branding or references. Where appropriate, use a small prototype to test the proposed approach. Check whether representative learners can use it and whether the provider responds constructively to evidence-based feedback.

In a hypothetical project, a vendor proposes an interactive inspection module. Its prototype looks attractive but does not let learners consult the reference they use at work. The internal team requests a revised design that preserves that condition and checks the same performance objective. Accepting the original solely because it has interactive buttons would ignore the task requirements.

Coordinating and accepting work

Assign an internal owner, technical reviewers and the acceptance decision-maker. Consolidate comments so the provider does not receive contradictory directions. Record version, issue, rationale, action and disposition. A changed objective may require a formal scope decision; a correction of a factual defect may be part of meeting the original acceptance criteria. Treat these distinctly and use the agreed process.

Verify the final deliverables against the brief. Check source files, functioning media, captions or other access support, correct references, assessment keys and maintenance instructions. Pilot the actual package rather than an earlier prototype. Resolve blocking issues before release, and confirm that instructors have the current version.

Maintaining the outsourced product

Plan for updates when equipment, requirements or learner needs change. Identify who can revise the materials, how changes are validated and what licensing or hosting dependency remains. Retain the appropriate source and acceptance evidence under policy. If a provider ends service, the organization still needs a usable continuity and record-recovery arrangement.

For an exam scenario, choose outsourcing when evidence shows a capability or capacity need and an external option can meet defined criteria. Do not outsource simply to avoid resolving a technical disagreement, and do not equate purchase with successful development. The sound decision includes specification, review, acceptance and a plan to maintain the learning product.

Testing the continuity plan

Before acceptance, demonstrate that the organization can obtain the approved materials and necessary editable files in the agreed format. Confirm how future corrections will be validated and distributed. A promise of continued vendor support is different from a tested ability to maintain the product.

If hosting or licensing is essential, record the dependency and renewal responsibility. Determine what happens if the service ends or access fails. This prevents a successful initial delivery from becoming an unusable course or an inaccessible evidence record later.

Key takeaways

• Outsourcing addresses a defined capability or capacity gap with retained internal ownership.
• Provider selection considers total cost, quality, access, data and maintainability.
• Acceptance verifies the actual package, source files, evidence and continuity plan.