Feb. 11, 2026

From SME Pathways to Stakeholder Highways

From SME Pathways to Stakeholder Highways

Projects stall when one expert carries the content, decisions, and approvals. We flip that script with a clear, usable playbook for building a stakeholder highway—bringing sponsors, learners, frontline leaders, operations, tech, and compliance into the right moments so training actually lands in the real world. You’ll hear why SME-only pathways create bottlenecks and blind spots, how to map the roles that matter, and when to loop each voice in across discovery, design, development, implementation, and evaluation.

Roadblocks happen: the ghost SME, conflicting leader feedback, or last-minute compliance asks. Jackie shares practical responses, from clarifying who decides versus who advises to offering trade-off options that protect timelines without sacrificing quality. A quick scenario shows the reset in action—expanding beyond one overbooked SME to include a frontline manager, operations, tech, and a learner pilot—so the course is accurate, feasible, and ready for day one performance. Close with one task: sketch a one-page stakeholder highway for your next project, add two new partners, and watch momentum return. If this approach helps you, subscribe, share it with a colleague, and leave a review so more designers can build learning that sticks.

🔗 Episode Links:

Please check out the resources mentioned in the episode. Enjoy!

Ask a Trainer: Time Slade on Working With Difficult Stakeholders and Subject Matter Experts

Stakeholder Highway Checklist

Send Jackie a Text

Join PodMatch!
Use the link to join PodMatch, a place for hosts and guests to connect.

Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.

Support the show

💟 Designing with Love + allows you to support the show by keeping the mic on and the ideas flowing. Click on the link above to provide your support.

Buy Me a Coffee is another way you can support the show, either as a one-time gift or through a monthly subscription.

🗣️ Want to be a guest on Designing with Love? Send Jackie Pelegrin a message on PodMatch, here: Be a guest on the show

🌐 Check out the show's website here: Designing with Love

📱 Send a text to the show by clicking the Send Jackie a Text link above.

👍🏼 Please make sure to like and share this episode with others. Here's to great learning!


00:00 - From SME Lanes To Stakeholder Highways

00:51 - Why Overreliance On SMEs Backfires

01:45 - Mapping The Stakeholders Who Matter

03:11 - Timing Engagement Across The Project Arc

04:36 - Keeping Alignment Clear And Simple

05:53 - Roadblocks And Practical Fixes

07:17 - A Real-World Scenario And Reset

08:37 - One Action This Week And Resources

09:24 - Closing Inspiration And Support

WEBVTT

00:00:00.800 --> 00:00:04.240
Hello and welcome to the Designing with Love Podcast.

00:00:04.240 --> 00:00:12.320
I am your host, Jackie Pelegrin, where my goal is to bring you information, tips, and tricks as an instructional designer.

00:00:12.320 --> 00:00:17.280
Hello, instructional designers and educators.

00:00:17.280 --> 00:00:22.000
Welcome to episode 89 of the Designing with Love Podcast.

00:00:22.000 --> 00:00:35.200
In this episode, I'll walk you through a practical playbook for scaling beyond the subject matter expert, who to engage, when to loop them in, and how to keep everyone aligned from kickoff through launch.

00:00:35.200 --> 00:00:42.079
So, grab your notebook, a cup of coffee, and settle in as we explore this topic together.

00:00:42.079 --> 00:00:50.560
Think of today's episode as your roadmap from moving from narrow SME pathways to wide open stakeholder highways.

00:00:50.560 --> 00:00:56.560
Let's start with why relying on SMEs can hold our projects back.

00:00:56.560 --> 00:01:04.799
Many projects default to a single SME lane where one expert carries content, decisions, and approvals.

00:01:04.799 --> 00:01:14.879
Some of the risks that can occur are bottlenecks, narrow perspective, burnout for the SME, and misalignment with the broader organization.

00:01:14.879 --> 00:01:18.719
There's a simple mindset shift I would encourage for you.

00:01:18.719 --> 00:01:24.400
SMEs are critical, but they're not the only voices that shape successful learning.

00:01:24.400 --> 00:01:34.319
Our job as educators and instructional designers is to design a stakeholder highway where the right people can merge in at the right time.

00:01:34.319 --> 00:01:44.319
Remember, when we expand beyond SME pathways, we design learning that actually lands in the real world it's meant to serve.

00:01:44.319 --> 00:01:51.120
Once we've reframed the problem, the next step is to map out who really belongs on that highway.

00:01:51.120 --> 00:01:56.000
Here's some core stakeholder groups you should consider in your projects.

00:01:56.000 --> 00:02:02.400
Project sponsor and business owner Define success, outcomes, and constraints.

00:02:02.400 --> 00:02:06.799
SMEs, bring deep subject knowledge and context.

00:02:06.799 --> 00:02:10.719
Learners, the people actually using what you designed.

00:02:10.719 --> 00:02:18.240
You can represent them via surveys, interviews, or user proxies, frontline leaders and managers.

00:02:18.240 --> 00:02:36.879
Influence time, priorities, and reinforcement, operations and process owners, no workflows, handoffs, and real world constraints, tech or platform partners, LMS admins, IT, and systems owners.

00:02:36.879 --> 00:02:40.479
Finally, compliance, legal, and HR.

00:02:40.479 --> 00:02:44.560
Ensure risk, policy, and regulations are covered.

00:02:44.560 --> 00:02:49.280
Next, here's a quick activity you can perform next week.

00:02:49.280 --> 00:02:53.840
Pick one project you are working on right now or getting ready to start.

00:02:53.840 --> 00:02:59.360
Next, draw a simple highway and label each lane with a stakeholder group.

00:02:59.360 --> 00:03:03.120
Then ask yourself, who's on my highway right now?

00:03:03.120 --> 00:03:04.560
Who's missing?

00:03:04.560 --> 00:03:10.960
Mapping is a great start, but timing is where projects either flow or jam up.

00:03:10.960 --> 00:03:19.280
Here, I recommend using a simple project arc, using a framework such as ADI or something with similar phases.

00:03:19.280 --> 00:03:22.879
Arc one, discovery and analysis.

00:03:22.879 --> 00:03:31.439
This can be your sponsor, SMEs, learner reps, operations, and possibly compliance to clarify any constraints early.

00:03:31.439 --> 00:03:33.680
Arc two, design.

00:03:33.680 --> 00:03:43.120
This is going to be your SMEs, learner reps, frontline leaders, and tech partners to validate concepts and delivery methods.

00:03:43.120 --> 00:03:45.759
ARC 3, development.

00:03:45.759 --> 00:03:55.599
These are also going to be your SMEs for spot checking accuracy, tech and platform partners for feasibility, and possibly a learner pilot group.

00:03:55.599 --> 00:03:58.879
ARC 4, implementation and launch.

00:03:58.879 --> 00:04:07.039
This is going to consist of your sponsor and leaders for communication, operations for logistics, and tech for support.

00:04:07.039 --> 00:04:11.520
Finally, ARC 5, evaluation and iteration.

00:04:11.520 --> 00:04:20.160
This would probably consist of your sponsor, leaders, and learners to review the data and decide on the next steps.

00:04:20.160 --> 00:04:22.160
Here's the key idea.

00:04:22.160 --> 00:04:25.680
Engage early and lightly rather than late and heavy.

00:04:25.680 --> 00:04:30.319
Short, well-timed touch points beat last minute fire drills.

00:04:30.319 --> 00:04:35.920
Incorporating these elements will save you much time and energy throughout your project.

00:04:35.920 --> 00:04:43.600
Now that we've mapped who and when, let's talk about how to keep everyone driving in the same direction.

00:04:43.600 --> 00:04:47.920
Step number one, set simple alignment goals.

00:04:47.920 --> 00:04:56.560
First, develop a one-page project brief with a purpose, audience, success metrics, scope, and timeline.

00:04:56.560 --> 00:05:04.639
Next, use a decision log to track key decisions and who made them so you're not re-litigating past conversations.

00:05:04.639 --> 00:05:14.800
Finally, incorporate a communication rhythm, which includes quick, predictable touch points such as biweekly check-ins or short updates.

00:05:14.800 --> 00:05:20.240
Step number two, translate ID speak into stakeholder speak.

00:05:20.240 --> 00:05:27.360
Here you want to focus on outcomes, risks, and time instead of only talking about models and tools.

00:05:27.360 --> 00:05:35.600
Make sure to use plain language to explain things like pilots, iterations, and feedback cycles.

00:05:35.600 --> 00:05:38.319
Step three, visuals.

00:05:38.319 --> 00:05:44.800
This includes a simple timeline or journey map, which calm nerves more than a 10-page document.

00:05:44.800 --> 00:05:48.079
Remember, alignment doesn't have to be fancy.

00:05:48.079 --> 00:05:52.319
It just has to be clear, consistent, and easy to find.

00:05:52.319 --> 00:05:58.240
Of course, even on a well-planned highway, we're going to hit traffic and detours.

00:05:58.240 --> 00:06:01.920
Here's some common roadblocks to watch out for on your highway.

00:06:01.920 --> 00:06:04.000
A SME who goes quiet.

00:06:04.000 --> 00:06:06.079
I call this the ghost SME.

00:06:06.079 --> 00:06:10.800
A SME who is too busy or changes their mind late in the process.

00:06:10.800 --> 00:06:13.839
Conflicting feedback from different leaders.

00:06:13.839 --> 00:06:18.959
Or surprise requirements from compliance or IT at the last minute.

00:06:18.959 --> 00:06:25.360
Next, here's a few practical strategies you can implement to handle any roadblocks.

00:06:25.360 --> 00:06:27.519
Clarify roles up front.

00:06:27.519 --> 00:06:35.040
Even a simple who decides versus who advises conversation can prevent chaos and misunderstandings.

00:06:35.040 --> 00:06:37.920
Use the project brief as your anchor.

00:06:37.920 --> 00:06:44.399
When new requests come in, you can ask, how does this align with our agreed outcomes and timeline?

00:06:44.399 --> 00:06:47.279
Offer options, not just problems.

00:06:47.279 --> 00:06:53.519
This could mean saying something like, we can add that new module, but here's what it means for scope and timing.

00:06:53.519 --> 00:06:55.600
Which trade-off feels right?

00:06:55.600 --> 00:06:58.000
And finally, stay learner-centered.

00:06:58.000 --> 00:07:03.920
When disagreements arise, bring it back to the impact on the learners and the organizational goal.

00:07:03.920 --> 00:07:16.399
If you would like to learn about some additional strategies about working with difficult stakeholders and SMEs, I have included the link to a short video by Tim Slade through ATD in the show notes.

00:07:16.399 --> 00:07:25.199
Alright, so now that you have some strategies in hand, let me walk you through a quick example of what this can look like in real life.

00:07:25.199 --> 00:07:26.959
Here's the scenario.

00:07:26.959 --> 00:07:32.079
You're asked to design training for new processes in your department.

00:07:32.079 --> 00:07:38.800
At first, you're paired with one SME who is clearly overwhelmed and juggling multiple priorities.

00:07:38.800 --> 00:07:41.360
What are some early signs of trouble?

00:07:41.360 --> 00:07:50.319
Meetings get rescheduled, feedback comes in late, and you get conflicting information from emails versus conversations.

00:07:50.319 --> 00:07:52.399
What should you do next?

00:07:52.399 --> 00:07:57.519
You pause and ask for a quick reset with the project sponsor by sharing the risk.

00:07:57.519 --> 00:07:59.759
Right now we're depending on one SME.

00:07:59.759 --> 00:08:04.240
I'm concerned we're missing the learner perspective and operational impact.

00:08:04.240 --> 00:08:08.560
Next, you build a small stakeholder highway together.

00:08:08.560 --> 00:08:12.879
First, add a frontline manager to sanity check the scenarios.

00:08:12.879 --> 00:08:16.800
Then bring in operations to confirm the workflow.

00:08:16.800 --> 00:08:21.680
Next, loop in tech to validate system screenshots and access for learners.

00:08:21.680 --> 00:08:27.040
Finally, you can invite a couple of learners to pilot key activities and provide feedback.

00:08:27.040 --> 00:08:31.360
The solution isn't about adding more people to slow things down.

00:08:31.360 --> 00:08:36.480
It's about inviting the right people so the training actually works on day one.

00:08:36.480 --> 00:08:42.559
Before we close, I would love to give you one simple action you can take this week.

00:08:42.559 --> 00:08:49.200
Choose one project, current or upcoming, and create a one-page stakeholder highway for it.

00:08:49.200 --> 00:08:51.519
You can include the following elements.

00:08:51.519 --> 00:09:04.080
List your core stakeholders, circle one person you have been treating like just this me, and then add at least two more stakeholders who could help share the load and improve the design.

00:09:04.080 --> 00:09:09.440
To help you put this into action, I have developed a checklist you can utilize.

00:09:09.440 --> 00:09:14.399
Make sure to check out the show notes to make a copy of the Canva template.

00:09:14.399 --> 00:09:17.200
If you try this, I would love to hear how it goes.

00:09:17.200 --> 00:09:23.840
You can message me on LinkedIn or share your takeaways and tag me so we can keep learning together.

00:09:23.840 --> 00:09:32.240
I want to leave you with an inspiring quote from Henry Ford that captures the spirit of building these stakeholder highways.

00:09:32.240 --> 00:09:39.519
Coming together is the beginning, staying together is progress, and working together is success.

00:09:39.519 --> 00:09:43.759
As instructional designers, we're not just wrangling content.

00:09:43.759 --> 00:09:45.600
We're bringing people together.

00:09:45.600 --> 00:09:55.039
SMEs, sponsors, learners, and leaders, and helping them stay aligned so the learning experiences actually drives change.

00:09:55.039 --> 00:10:06.480
Remember, as you move from SME pathways to stakeholder highways, you're not just building courses, you're building connections that make learning work in the real world.

00:10:06.480 --> 00:10:10.559
Thank you for taking some time to listen to this podcast episode today.

00:10:10.559 --> 00:10:12.799
Your support means the world to me.

00:10:12.799 --> 00:10:21.600
If you'd like to help keep the podcast going, you can share it with a friend or colleague, leave a heartfelt review, or offer a monetary contribution.

00:10:21.600 --> 00:10:27.360
Every act of support, big or small, makes a difference, and I'm truly thankful for you.