You’ve decided to bring in an instructional design agency. Maybe you’ve already shortlisted vendors, had a few discovery calls, and received proposals. Now you’re asking the question that nobody answers in the pitch meeting: what does the actual engagement look like, day to day, once we sign?
Most agencies describe their process in broad strokes — discover, design, develop, deliver. But the difference between a smooth engagement and a painful one isn’t the methodology on the slide. It’s what happens between the milestones: how decisions get made, how feedback works, what’s expected of your team, and how problems are handled when they inevitably arise.
This article walks through what a well-run instructional design engagement looks like from the client’s side — so you know what to expect, what to demand, and what to watch for.
The discovery phase: weeks one and two
A good engagement doesn’t start with storyboards. It starts with questions. The agency’s first job is to understand your business problem deeply enough to design a solution that actually addresses it — not just build what you asked for in the RFP.
Expect stakeholder interviews where the agency talks to the people who requested the training, the managers who see the performance gap daily, and — ideally — a sample of the learners themselves. Expect questions that push beyond the surface: not just “what do you want the training to cover” but “what’s happening now that shouldn’t be, and how will you know when it’s fixed?”
Your role during discovery is to provide access — to stakeholders, to subject matter experts, to existing content and performance data. The faster you can get the agency in front of the right people, the faster discovery produces a clear problem statement that everyone agrees on.
The output of discovery should be a document you can hold: a problem statement with defined success metrics, an audience analysis, and a recommended approach. If the agency skips this and jumps straight to “here’s the storyboard,” that’s a red flag. They’re building before they’ve diagnosed.
The design phase: weeks two through four
Once discovery is complete and everyone has agreed on the problem and the approach, design begins. This is where the agency architects the learning experience — learning objectives mapped to business outcomes, content structure and sequencing, the modality mix, and the assessment strategy.
You’ll see storyboards — detailed blueprints of every screen, interaction, and assessment in the module. A good storyboard reads like a screenplay: you can see exactly what the learner will experience, what choices they’ll face, what feedback they’ll receive, and how the module flows from beginning to end.
Your role during design is reviewer, not author. The agency should be doing the creative and instructional heavy lifting. Your job is to confirm that the content is accurate, the scenarios reflect real situations your learners face, and the tone matches your organization’s culture. If you’re rewriting the storyboard yourself, either the discovery was insufficient or the agency isn’t listening.
Expect one to two review cycles on the storyboard before it’s approved. Give consolidated feedback — one document with all stakeholder comments merged — rather than sending conflicting feedback from five different reviewers. This single habit saves more time and budget than any other client-side action.
The development phase: weeks four through eight
With an approved storyboard, development begins. The agency’s team — instructional designers, eLearning developers, visual designers, and QA specialists — builds the actual module. This is the phase that takes the most calendar time, but it should require the least effort from your team.
You should see the module in progress at least once before the final delivery. Most agencies build a prototype or alpha version — a representative section of the module that’s fully functional — so you can experience the interactivity, visual design, and navigation before the entire module is built. This is your chance to catch misalignments early. A change to the visual approach in week five costs a fraction of the same change in week eight.
Your role during development is checkpoint reviewer, not daily manager. If the agency is asking you for direction on every design decision, they’re not leading the project — they’re outsourcing the thinking. A good agency brings you solutions to approve, not problems to solve.
Expect a beta review of the near-complete module where you test every interaction, verify content accuracy, and flag anything that doesn’t work. Two rounds of revision are standard. If you’re heading into round five, something went wrong in discovery or design — not in development.
The launch phase: week eight or nine
A surprising number of agencies treat delivery as the finish line. They hand over a SCORM file and wish you luck. That’s not launch management — that’s a file transfer.
A well-run launch includes several things your agency should either handle or support. LMS upload and testing to make sure the module works correctly in your specific platform — not just in the agency’s testing environment. A pilot with a small group of real learners to catch issues that only appear in the real context — browser compatibility, mobile rendering, confusing navigation paths. And a communication plan so learners know the training exists, why it matters, and where to find it.
Your role during launch is to own the internal communication and provide LMS access. The agency should be available for technical troubleshooting and rapid fixes during the first week of deployment. If they’ve moved your team to a different project before your training is fully live, that’s a problem.
The optimization phase: weeks ten through fourteen
The best agencies don’t disappear after launch. They circle back to check whether the training is working.
Expect a post-launch review at 30 or 60 days. The agency should analyze completion data, assessment performance, and learner feedback — and present findings alongside the success metrics defined during discovery. If the original goal was 85% completion with 80% assessment pass rates, this is where you learn whether the program hit those targets.
If something isn’t working — a section with high drop-off, an assessment question everyone fails, a scenario that confuses instead of teaches — a good agency proposes specific revisions based on the data. This isn’t a change request that costs extra. It’s the final phase of the engagement, and it should be scoped into the original agreement.
Your role during optimization is to share the data the agency needs — LMS reports, manager observations, any changes in the business metrics the training was designed to improve. The more data you provide, the more targeted the improvements will be.
What your team should expect to contribute
One of the most common surprises for first-time agency clients is how much the engagement still requires from their side. An agency handles the design, development, and project management — but it cannot replace your organizational knowledge.
Subject matter experts will spend 8 to 15 hours per module on content review, scenario validation, and accuracy checks. This is non-negotiable. The agency can build a beautiful, engaging module — but only your SMEs can confirm it’s accurate. Block their time before the project starts, not after the first review is due.
A project sponsor — usually the L&D leader or the person who owns the training initiative — will spend 3 to 5 hours per module on storyboard review, prototype review, and beta testing. This person is the single point of contact for decisions. If five people have approval authority and none of them agree, the project stalls.
LMS administrators will need availability during launch for upload, testing, and enrollment configuration. If the agency is also handling LMS setup, this reduces to a coordination role rather than a technical one.
The timeline you should expect
A single module from kickoff to deployment typically takes 6 to 10 weeks. This includes two weeks for discovery and design, four to six weeks for development with review cycles, and one to two weeks for launch and initial monitoring.
Multi-module programs take longer in total but often overlap phases — module two enters design while module one is in development. A five-module program might take 12 to 16 weeks rather than five times the single-module timeline.
The most common cause of timeline slippage isn’t development speed. It’s review delays on the client side. When a storyboard sits in someone’s inbox for two weeks instead of two days, the entire project shifts. Build review time into your team’s calendars before the project starts.
Signs the engagement is going well
You shouldn’t have to wonder whether things are on track. A healthy engagement has consistent communication — weekly status updates that are brief, clear, and proactive about risks. The agency surfaces potential problems before they become actual problems. Feedback from your last review is visibly incorporated in the next deliverable. And the module you’re seeing matches the strategy that was agreed during discovery.
The single best indicator: your team feels like the agency understands your business — not just your training content, but the actual performance problem the training is supposed to solve.
Signs something is wrong
Watch for these early. The agency hasn’t asked to talk to your learners or their managers. Storyboards are vague or read like a content outline rather than a detailed blueprint. You’re in review round four and the same feedback keeps not being addressed. The team that sold you the project isn’t the team doing the work. Communication is reactive — you only hear from them when you reach out. And the deliverable feels generic — like it could have been built for any organization, not specifically for yours.
These aren’t minor style preferences. They’re structural problems that predict a final product that misses the mark. Address them early and directly. If they persist after you’ve raised them, the engagement is unlikely to produce the outcome you need.
What a great agency partnership actually feels like
The best client-agency relationships share a quality that’s hard to describe but easy to recognize: it feels collaborative rather than transactional. The agency pushes back when your initial idea won’t work and proposes something better. Your team trusts their expertise enough to be persuaded. Decisions happen quickly because roles are clear. And at the end, the training program doesn’t just check a box — it measurably changes how people perform.
That outcome doesn’t happen by accident. It happens when both sides understand their role, commit their best people, and treat the engagement as a partnership rather than a procurement.
