In my recent client engagements, I keep noticing the same thing: teams come in with unclear expectations of what a consultant should provide, usually because a past L&D vendor left them with a bad experience. Maybe the communication never matched what they were promised. Maybe the finished product didn’t hold up, not because the vendor lacked technical skill, but because the right questions never got asked, and no one surfaced how the work connected to the bigger picture until the problems were expensive to fix.

In my attempt to clarify what you can expect from a solid consulting relationship, I came up with these 15 discovery questions, organized into five categories, for you to start your engagement off strong and get the most out of your vendor relationship.

Good consulting doesn’t start with a course, it starts with questions. The difference between a vendor who simply builds what you ask for and a consultant who builds what you actually need shows up in the first conversation, long before anything goes into development.

Here’s what to expect, and what to look for, when you bring outside help into your L&D work.

Communication & Process Clarity

A good consultant meets your team where you work – your channels, your cadence, your tools – rather than forcing you into theirs. It’s important to remember that flexibility should be within reason. It’s about fitting into your workflow, not being on call at all hours.

  1. How will you communicate? Set clear expectations early, then make sure they’re followed. That includes agreeing on the cadence for project status meetings and emails, how deadlines and tasks will be communicated, and where shared project management documents, drafts, and approvals will live.

Phasing, development, and feedback get scoped at the start of an engagement, not patched in later. Before any questions about your audience, a good consultant walks you through how the work itself will run, and checks that it fits how your team operates:

  1. How will development be phased? Expect the work broken into stages, for example: analysis, then a storyboard or outline, then a first build, then revisions — so you see progress and can course-correct early rather than reacting for the first time to a finished product. Staged delivery also gives your stakeholders (SMEs, ops groups, legal, HR, marketing, C-suite, etc. – who needs to be involved should also be discussed) natural checkpoints to weigh in without derailing the timeline. Because you’re not seeing a final product, this might require a bit more imagination to see it as your audience would see it. Ask your consultant for completed examples to ensure their vision fits with yours.
  2. How will feedback cycles work? Clear rules on how many review rounds you get, who will be reviewing, how comments are collected, how much time is allowed for review, what type of feedback is needed at each stage, and what each turnaround takes. This protects the schedule on both sides and prevents the endless-revision spiral that quietly inflates cost.
  3. Does that rhythm fit your team? A process only works if your reviewers and stakeholders can keep pace with it. If sign-off is slow, approvals are layered, critical content changes occur after sign off/development, or extra review cycles are needed, that gets surfaced and adjusted for as early as possible, not discovered when a deadline slips. A good consulting team designs the cadence around your reality and works with you to meet your needs in the best way the budget, time frame, and resources allow. Taken a step further, they’ll discuss up front during discovery, what options are if there are unexpected delays.

Deliverables & Audience

With that foundation set, a strong consultant then opens with questions like:

  1. How will you use and access the deliverables? A SCORM package, an editable source file, a hosted link, or raw video each carry different implications for file transfer, future edits, and hosting. If your team needs to update content in-house later, say so now. A locked output you can’t edit becomes a recurring cost every time a policy or product changes. A good vendor confirms the handoff format, and whether you receive source files, before scoping the build.
  2. How will your audience access the courses? Desktop LMS, mobile, a shared tablet on a warehouse floor, or a printed job aid each impose different constraints (like screen size, bandwidth, offline access, and interactivity). Nailing this down early prevents building something learners literally can’t open where they work. It also surfaces accessibility and device-support requirements before they turn into rework.
  3. How are learners meant to use the material in the flow of work? A reference job aid people pull up mid-task is a fundamentally different artifact from a course completed once in a sitting. Intended use shapes length, structure, searchability, and tone. A consultant who asks this is designing for how the work actually happens, not just packaging content and handing it over.
  4. When do they need the information to do their jobs? Just-in-time support, onboarding, and annual refreshers each call for different formats, depth, and timing. Information delivered too early is forgotten; too late, it’s useless. Mapping the moment of need lets you match the right solution, and sometimes reveals that a two-minute resource beats a full course.

Business Goals & Measurement

  1. How will the training meet business goals? This might be last in the list, but it should be the first question asked in your discovery (and again in analysis. You’d be surprised how you get a different answer depending on who you ask). Every deliverable should trace back to an outcome the business actually cares about: fewer errors, faster ramp-up, compliance, retention. If a request can’t be tied to a goal, that’s worth surfacing before budget is spent. Building a large library of resources no one ever uses just to have a high document count isn’t a flex. A strong consultant will ask how each planned resource is used and what value it brings, which protects your team from building training that checks a box but moves nothing.
  2. How will we measure success? Define the metric before building, not after – completion rates, assessment scores, on-the-job behavior change, or a business KPI. Agreeing on what “working” looks like early gives your team a defensible way to show impact and a baseline to compare against. Without it, evaluation becomes an afterthought no one can answer for.

People & Constraints

  1. Who are the SMEs and stakeholders, and how available are they? Content accuracy and sign-off depend on subject-matter experts and approvers, and their availability is the single most common cause of slipped timelines. Naming them up front, and confirming they actually have bandwidth to review, protects the schedule. A consultant who asks this is planning realistically rather than optimistically.
  2. What are the real constraints? Budget, technology, accessibility standards, brand requirements, and hard deadlines all shape what’s possible. Getting them on the table early prevents designing something the constraints won’t allow. Honest constraint-setting is a sign of a consultant who wants the project to succeed, not just to sell more scope.

Rollout & Sustainment

  1. How will we communicate the training and make space for it? Even excellent training fails if no one knows it exists or has time to take it. This question forces a plan for rollout, manager buy-in, and protected time on people’s calendars. A good consultant helps you think through the change-management side alongside the content, because adoption is a shared responsibility between your L&D team and theirs.
  2. What is the plan for rollout? Whatever the reason for training – a software change, AI enablement effort, process or regulatory change, etc. – the program will not succeed just because the training exists. People need to know why it matters, what is changing, when it affects them, and where to go for help. A good consultant will push for an internal communication and change-management plan alongside the learning plan, including how the training will be marketed internally, how managers will reinforce it, who will be facilitating the change, and how adoption will be sustained once the first announcement goes out, i.e. developing a long-term engagement schedule.
  3. What happens after launch? Content ages, products change, policies update, screenshots go stale. Deciding now who owns maintenance, how updates get made, and on what cadence keeps a polished course from quietly becoming wrong. Treating the post-launch life of the material as part of the work, rather than an afterthought, is a mark of good consulting.

Good L&D consulting is consultative. At Evolve Solutions Group, we see our role as working through the problem with your team before recommending a solution, so what gets built is useful, adopted, and tied to the business need. You are not just handing over a spec; you are bringing in a partner who should ask the right questions early and help turn learning into something that actually works in practice.

In the meantime, use the Vendor Engagement Checklist (here) to help you evaluate and strengthen any current vendor or consultant engagements. If you have questions about training strategy, software change, AI enablement, digital transformation, or upskilling support, reach out through our contact form or email us at info@evolve-sg.com.