Make the buy decision honestly
Outsourcing is a strong choice when the content needs to exist, your organisation lacks the specific skills, and the work is not strategically confidential enough to justify building a permanent internal team. It is a weak choice when the content is so sensitive that external handling creates unacceptable risk, or when the subject matter expertise is the point and the production support is trivial.
Be careful about the middle case, which is the most common. Many organisations have a small internal learning team that can design and maintain content but not produce it at volume. A hybrid model, where an external producer handles production and scripting while internal designers own the learning architecture, is often the most durable arrangement, because it keeps design control in-house.
Note that outsourcing the production of content does not outsource the responsibility for it. Compliance, accuracy, and the consequences of a bad learning experience still land on the business, whatever the contract says about who made the artefact.
Decide what you keep in-house
Before selecting a supplier, decide which capabilities stay inside your organisation. For most enterprises this means learning strategy, the audience and performance analysis, subject matter ownership, governance and approval rights, and the data that describes your workforce. These are the parts that determine whether content is relevant to your business.
Everything else is a candidate for external production: scripting support, media production, build and packaging, translation coordination, and quality assurance testing. Where you keep design in-house but outsource production, you need a handoff format the supplier can work from, and your internal team needs the time and the mandate to do it.
The failure mode is the opposite arrangement, where the supplier owns the design entirely and your internal team is left reviewing finished assets without the context needed to judge them. Your reviewers will feel this, and the review cycle will slow to a crawl.
Set up the engagement for two-way work
The most common cause of outsourced projects stalling is not poor supplier performance. It is that the client side is implicitly part of the critical path while being treated as if it were not. Subject matter expert availability, legal review, brand approval, and procurement sign-off are all tasks that someone must own and schedule.
Name a single accountable owner on the client side, agree a review calendar at the outset, and set a response time expectation that is realistic. Where a review is late, define what happens in advance, for example a rule that the project continues and the content ships on a documented assumption that is reviewed later. Without such a rule, every late review becomes a crisis negotiation.
Structure the work in short cycles with a demonstrable output each time. A pilot module that proves the design approach, the tone, and the production method is worth more than a long phase of documentation, because it forces disagreements to surface while they are still cheap to resolve.
Contract for the behaviours you need
Beyond price, the terms that matter are about behaviour under pressure. Set out service levels for response times and escalation, the number of included review rounds and how additional rounds are charged, and the process for changes to scope mid-flight.
Be explicit about intellectual property and asset handover, and about what happens to source files, project files, and documentation at the end. Also set out a knowledge transfer requirement, for example that the supplier must document the build so your own team can make a small change without them. A partner who resists this is telling you what will happen later.
For the specific questions to put to a potential supplier, see our guide on questions to ask a courseware development vendor, and for the proposal stage see our guide on comparing enterprise content production proposals.
Plan the transfer out as well as the transfer in
Decide at the start what the end state looks like. Does your organisation intend to keep this supplier indefinitely, or build capability so that future content can be produced in-house? The two goals need different contracts, different deliverables, and different review criteria, and conflating them creates frustration on both sides.
If you want to build internal capability, require the supplier to work with your people, document their process, and deliberately involve your team in production. Track whether your team's throughput and quality actually improve over the engagement. If it does not, the transfer is not happening regardless of what the documentation says.
Whatever the plan, review the relationship periodically against the original business need rather than against activity. A supplier that has produced a lot of content but has not moved the measure you started with is not delivering on the engagement, and the appropriate response is to renegotiate scope, not simply to renew.
Commonly overlooked pitfalls
- Outsourcing the whole engagement including the learning strategy, which surrenders the ability to judge what you receive.
- Leaving the client side of the critical path unowned, so reviews and approvals quietly stall the project.
- Negotiating only on price and fee, and leaving service levels, review caps, and change control undefined.
- Failing to require asset handover and documentation, which converts a service relationship into a permanent dependency.
- Renewing a supplier on activity volume rather than on whether the original business measure has moved.
Next steps
- Document which capabilities stay in-house and which are outsourced, and put it in a one-page operating model.
- Name a single client-side owner and agree a review calendar with response time expectations.
- Run one pilot module to validate design approach, tone, and production method before scaling.
- Include service levels, review-round caps, IP and handover terms, and a knowledge transfer requirement in the contract.
- Define the measures of success at kickoff and review them at each phase gate against the original need.
Related guides
Put this into practice
The vendor evaluation checklist and the RFP template turn a guide into a process you can run this week.