WEBVTT
00:00:01.040 --> 00:00:04.107
Hello and welcome to the Designing with Love podcast.
00:00:04.107 --> 00:00:11.752
I am your host, jackie Pellegrin, where my goal is to bring you information, tips and tricks as an instructional designer.
00:00:11.752 --> 00:00:22.422
Hello, gcu students, alumni and fellow educators, welcome to episode 35 of the Designing with Love podcast.
00:00:22.422 --> 00:00:36.154
In this episode, I will provide an introduction to the SAM model, why you should choose it for rapid development, the phases of the model, tips for implementing the model, along with some common pitfalls and how to avoid them.
00:00:37.378 --> 00:00:45.353
The SAM model was developed by Dr Michael Allen, a well-known expert in instructional design and the founder of Allen Interactions.
00:00:45.353 --> 00:00:53.033
Sam was created as a more agile and iterative alternative compared to traditional linear models like ADDIE.
00:00:53.033 --> 00:01:01.274
The SAM model emerged from the need to speed up development, reduce rework and create more engaging learning experiences.
00:01:01.274 --> 00:01:12.453
Traditional models like ADDIE often require completing one phase before moving to the next, which can lead to discovering flaws in the design too late in the process.
00:01:12.453 --> 00:01:19.733
In contrast, the SAM model encourages early and frequent feedback, prototyping and iteration.
00:01:19.733 --> 00:01:26.373
One thing that is important to understand about the SAM model is there are two main versions.
00:01:26.373 --> 00:01:30.992
This can be helpful when you are deciding which path to take during your project.
00:01:30.992 --> 00:01:38.593
The first version is called SAM1, which is a basic three-phase model that is suitable for small projects.
00:01:38.593 --> 00:01:46.573
The second version is called SAM2, which is a more detailed version that is ideal for larger team-based projects.
00:01:46.573 --> 00:01:48.983
It includes more explicit steps.
00:01:48.983 --> 00:01:56.150
Like the savvy start, this is a brainstorming session where key stakeholders collaborate to define the project direction.
00:01:57.855 --> 00:02:09.609
Now that you have a solid background of the SAM model and how it compares to other traditional models, I will take a few minutes to provide six key reasons why this model is ideal for rapid development.
00:02:09.609 --> 00:02:13.181
These key reasons are inspired by ChatGPT.
00:02:13.181 --> 00:02:18.150
Reason number one iterative prototyping saves time.
00:02:18.150 --> 00:02:25.792
Sam encourages the development of quick prototypes instead of detailed, fully built courses from the start.
00:02:25.792 --> 00:02:33.662
In addition, prototypes are tested and revised early, reducing time spent fixing problems later in the process.
00:02:33.662 --> 00:02:38.656
Reason number two early and ongoing stakeholder involvement.
00:02:38.656 --> 00:02:48.463
From the savvy start session onward, sam brings together all key voices, including instructional designers, smes, developers and clients.
00:02:48.463 --> 00:02:58.491
This helps to reduce miscommunication, aligns expectations and ensures the final product meets learner and business needs in a quicker time frame.
00:02:58.491 --> 00:03:02.206
Reason number three reduces rework.
00:03:02.206 --> 00:03:11.111
Traditional models like Addy often lead to excessive revisions after the development phase, which can cost design teams valuable time.
00:03:11.111 --> 00:03:19.633
In addition, sam's continuous feedback loops are able to catch issues early, helping to minimize major last-minute changes.
00:03:19.633 --> 00:03:32.569
Reason number four built for flexibility and agility, sam is able to accommodate changes easily, making it perfect for fast-paced environments where client needs or content may shift.
00:03:32.569 --> 00:03:40.477
In addition, it mirrors agile methods used in technology, which helps teams to stay responsive and focused.
00:03:40.477 --> 00:03:49.884
Reason number five encourages creativity and innovation.
00:03:49.884 --> 00:03:55.282
By focusing on frequent brainstorming and collaboration, sam helps instructional designers experiment and refine creative solutions more rapidly.
00:03:55.282 --> 00:03:59.632
Reason number six improves final product quality.
00:03:59.632 --> 00:04:02.801
Remember, rapid doesn't mean rushed.
00:04:02.801 --> 00:04:12.056
Sam's frequent reviews and testing help ensure that, even under time constraints, the final learning experience is polished and effective.
00:04:12.056 --> 00:04:28.038
In a nutshell, sam helps instructional designers build better learning experiences faster by starting small testing early, improving often and staying flexible testing early, improving often and staying flexible.
00:04:30.399 --> 00:04:36.913
All right, so now that you have a good understanding of why you should choose the SAM model for rapid development, I will cover the phases of the SAM model, along with some practical examples of how it can be used in a project.
00:04:36.913 --> 00:04:40.569
The scenario and examples were inspired by ChatGPT.
00:04:40.569 --> 00:04:47.540
Here's the scenario, chat GPT.
00:04:47.540 --> 00:04:48.002
Here's the scenario.
00:04:48.002 --> 00:04:52.932
A national retail chain wants to train its customer service team on handling inquiries and upselling techniques for a new line of eco-friendly home goods.
00:04:52.932 --> 00:04:55.764
First is the preparation phase.
00:04:55.764 --> 00:05:01.144
This consists of gathering information and understanding the performance goals and learning needs.
00:05:01.144 --> 00:05:03.310
Here's the steps to complete.
00:05:03.310 --> 00:05:09.545
First, meet with the retail manager, customer service leads and a few frontline staff.
00:05:09.545 --> 00:05:17.206
Next, identify any performance gaps, such as lack of product knowledge and inconsistent customer experience.
00:05:17.206 --> 00:05:27.589
Then define what success looks like, such as the staff should be able to confidently answer questions and increase upsell conversions by 15%.
00:05:27.589 --> 00:05:34.863
Finally, gather content, such as product features, customer FAQs and current customer feedback.
00:05:36.485 --> 00:05:46.485
Next is the iterative design phase, which consists of developing rough prototypes, soliciting feedback early and often and making continuous improvements.
00:05:46.485 --> 00:05:54.920
In this phase of the process, there are three elements, which are the savvy start, prototyping and review and iteration.
00:05:54.920 --> 00:05:57.211
Here's the steps to complete.
00:05:57.211 --> 00:06:04.918
First, hold a savvy start session with the stakeholders, including the SMEs, trainers and a few customer service reps.
00:06:04.918 --> 00:06:13.218
Then sketch out the learning experiences, such as a short video demo, a product knowledge game and scenario-based role plays.
00:06:13.218 --> 00:06:20.939
Next, create a quick prototype of a scenario-based quiz and mock-up of the interactive product guide.
00:06:20.939 --> 00:06:24.932
Then share the prototypes with stakeholders for feedback.
00:06:24.932 --> 00:06:35.966
Finally, revise the prototypes based on feedback, such as including more real customer questions, simplifying navigation and changing the tone to be more conversational.
00:06:35.966 --> 00:06:47.500
Finally, there's the iterative development phase, which consists of developing working versions and testing and refining the final project through ongoing testing and feedback.
00:06:47.500 --> 00:06:49.911
Here's the steps to complete.
00:06:50.685 --> 00:06:58.516
First, begin by developing the e-learning module in your authoring tool, such as Articulate Rise or Adobe Captivate Let Rise or Adobe Captivate.
00:06:58.516 --> 00:07:10.187
Next, conduct internal testing after each component is built, such as one scenario or product interaction at a time.
00:07:10.187 --> 00:07:11.269
Then run a pilot test with 10 customer service reps.
00:07:11.269 --> 00:07:12.973
Next, collect feedback from the employees.
00:07:12.973 --> 00:07:22.538
Some examples of feedback can include please include more guidance on objection handling or add a badge system for completing the modules.
00:07:22.538 --> 00:07:31.314
Finally, apply final tweaks, such as adding coaching tips, include a short leaderboard and include a printable quick reference guide.
00:07:31.314 --> 00:07:42.747
The final result by integrating these phases into a project, as explained in the example, this provides a short, engaging, scenario-driven e-learning course.
00:07:42.747 --> 00:07:46.975
That is number one, easily completed in 30 minutes.
00:07:46.975 --> 00:07:50.913
Number two includes interactive product knowledge checks.
00:07:50.913 --> 00:07:55.788
Number three prepares staff to confidently and consistently support customers.
00:07:55.788 --> 00:08:00.817
And number four is delivered just in time for the new product launch.
00:08:00.817 --> 00:08:02.685
Great.
00:08:02.685 --> 00:08:15.658
So now that you have a solid framework for how each of the phases of the SAM model work in rapid development, I wanted to provide you with four tips for implementing the model, how to accomplish each one and why it matters.
00:08:16.625 --> 00:08:19.654
Tip number one prioritize the savvy start.
00:08:19.654 --> 00:08:23.776
Kick off with a focused, collaborative savvy start session.
00:08:23.776 --> 00:08:29.115
How to accomplish this Number one involve key stakeholders early.
00:08:29.115 --> 00:08:35.038
Number two use the session to brainstorm, sketch ideas and align learning goals.
00:08:35.038 --> 00:08:38.654
Number three keep it informal and idea-driven.
00:08:38.654 --> 00:08:43.399
Remember the goal is clarity and creativity, not perfection.
00:08:43.399 --> 00:08:51.418
Why it matters A strong start ensures everyone shares a common vision, reducing delays and confusion later.
00:08:52.465 --> 00:08:54.974
Tip number two start prototyping early.
00:08:54.974 --> 00:08:57.732
Don't wait to build a polished version.
00:08:57.732 --> 00:08:59.091
Create a quick scrappy prototype early on.
00:08:59.091 --> 00:08:59.936
This is something many designers refer to.
00:08:59.936 --> 00:09:00.438
Build a polished version.
00:09:00.438 --> 00:09:01.284
Create a quick scrappy prototype early on.
00:09:01.284 --> 00:09:05.176
This is something many designers refer to as a dirty design.
00:09:05.176 --> 00:09:12.658
How to accomplish this this can include a clickable mock-up, a rough storyboard or a sample activity.
00:09:12.658 --> 00:09:17.854
And number two share it with stakeholders for feedback before moving to final development.
00:09:17.854 --> 00:09:23.648
Why it matters feedback before moving to final development.
00:09:23.648 --> 00:09:26.755
Why it matters Early prototypes expose issues and opportunities fast, saving time and effort later.
00:09:26.775 --> 00:09:29.523
Tip number three embrace feedback loops.
00:09:29.523 --> 00:09:33.111
Build regular review and feedback points throughout the project.
00:09:33.111 --> 00:09:39.875
How to accomplish this Number one treat feedback as part of the process, not a final hurdle.
00:09:39.875 --> 00:09:46.410
Number two use surveys, usability testing and informal check-ins with users and SMEs.
00:09:46.410 --> 00:09:54.091
Why it matters Continuous feedback keeps the solution learner-focused and adaptable as needs shift.
00:09:54.091 --> 00:09:58.139
Tip number four stay agile and flexible.
00:09:58.139 --> 00:10:03.798
Be prepared to pivot or revise as needed, because SAM thrives on adaptability.
00:10:03.798 --> 00:10:05.769
How to accomplish this?
00:10:05.769 --> 00:10:12.359
Number one use short development cycles and focus on good enough to test iterations.
00:10:12.359 --> 00:10:17.514
Number two document any lessons learned for the next round of approximation.
00:10:17.514 --> 00:10:19.077
Why it matters?
00:10:19.077 --> 00:10:21.371
Instructional needs often evolve.
00:10:22.044 --> 00:10:25.951
Sam's strength is its ability to keep pace with real-world change.
00:10:25.951 --> 00:10:36.090
All right, so now that you have learned some key tips for implementing the SAM model in a project, I will cover three common pitfalls and how to avoid them.
00:10:36.090 --> 00:10:40.624
Pitfall number one treating SAM like a watered-down addy.
00:10:40.624 --> 00:10:41.966
What happens?
00:10:41.966 --> 00:10:48.508
Teams follow SAM in name only by still working in long linear phases with limited feedback.
00:10:48.508 --> 00:10:50.080
How to avoid it?
00:10:50.080 --> 00:10:53.182
Number one embrace true iteration.
00:10:53.182 --> 00:10:56.678
Build small, test fast and revise quickly.
00:10:56.678 --> 00:10:59.765
Number two keep cycles short and focused.
00:10:59.765 --> 00:11:03.845
Don't wait until everything is perfect before showing it to stakeholders.
00:11:03.845 --> 00:11:10.465
Number three shift your mindset from finish each phase to improve with each pass.
00:11:11.628 --> 00:11:15.639
Pitfall number two skipping the savvy start or making it too formal.
00:11:15.639 --> 00:11:17.104
What happens?
00:11:17.104 --> 00:11:22.379
The kickoff becomes a stuffy meeting or a skipped, entirely losing Sam's creative spark.
00:11:22.379 --> 00:11:24.066
How to avoid it?
00:11:24.066 --> 00:11:31.244
Number one keep the savvy start collaborative and hands-on by including whiteboards, sticky notes and rapid sketches.
00:11:31.244 --> 00:11:38.488
Number two include a mix of different perspectives, such as SMEs, learners, technology experts and leadership.
00:11:38.488 --> 00:11:45.427
Number three focus on exploring ideas, not finalizing deliverables Pitfall.
00:11:45.488 --> 00:11:48.197
Number three neglecting real user feedback.
00:11:48.197 --> 00:11:49.279
What happens?
00:11:49.279 --> 00:11:54.416
Designers rely solely on stakeholder input and skip testing with actual learners.
00:11:54.416 --> 00:11:56.080
How to avoid it?
00:11:56.080 --> 00:12:03.081
Involve end users early and often, even if it's with quick usability tests or feedback on prototypes.
00:12:03.081 --> 00:12:08.078
Number two watch how learners interact with the content, not just what they say.
00:12:08.078 --> 00:12:13.378
Number three use their feedback to drive design improvements, not just polish.
00:12:14.320 --> 00:12:18.999
And here's a pro tip Build a habit of learning fast, not launching perfectly.
00:12:18.999 --> 00:12:21.326
That's the core spirit of SAM.
00:12:21.326 --> 00:12:31.825
I hope you have found this information about using the SAM model for rapid development helpful as you continue creating engaging and effective learning experiences.
00:12:31.825 --> 00:12:35.575
Development helpful as you continue creating engaging and effective learning experiences.
00:12:35.575 --> 00:12:41.844
Please check out the SAM model guide resource in the show notes, which provides a comprehensive overview of what was covered in this episode.
00:12:41.844 --> 00:12:54.077
As a recap, we covered what the SAM model is, why you should choose it for rapid development, phases of the SAM model, tips for implementing the model in your projects, and common pitfalls and how to avoid them.
00:12:54.077 --> 00:13:03.024
In the future, I would recommend trying the phases of the SAM model on a small scale, especially if you have not used it before, with your projects.
00:13:04.187 --> 00:13:09.345
As I close out this episode, I would like to share an inspiring quote by Connie Malamed.
00:13:09.345 --> 00:13:17.000
One of the most important areas we can develop as professionals is competence in assessing and sharing knowledge.
00:13:17.000 --> 00:13:23.298
Thank you for taking some time to listen to this podcast episode today.
00:13:23.298 --> 00:13:25.626
Your support means the world to me.
00:13:25.626 --> 00:13:34.360
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:13:34.360 --> 00:13:39.860
Every act of support, big or small, makes a difference and I'm truly thankful for you.