Frameworks
(How to Build)
Like blueprints are used to build a skyscraper, frameworks are used to build a learning product. They have pros and cons, and are used in different types of organizations.
Depending on your organization, you may work using Agile methodologies, waterfall methodologies, or a combination of several methodologies. Here is a comparison of the three:
ADDIE (Waterfall)
Large, slower-paced organizations, or large projects with little room for changes often use waterfall to build learning products. It's top-heavy, prioritizing planning as much as possible in the beginning, and then following through on the plan as much as possible through the rest of the build. It's linear, not iterative, and the previous step of the plan flows into the next step, like a waterfall flows in one direction.
Analysis, Design, Development, Implementation, and Evaluation (ADDIE) is one framework used in waterfall. The needs analysis is done to see what the learner should learn to help the organization. That information is used to create the objectives for the learning product (document, course, module, etc.) and to design the product to meet those objectives. The product is developed according to the design plan. The product is rolled out (implemented), and the results are evaluated to see of the product helped or not.
For example:
A professor turning their existing in-person course into a video-based course. They already know what content they want, and in what order they want it, so there is little room for editing the curriculum.
LLAMA (Hybrid)
The Lot Like Agile Method Approach (LLAMA) uses a form of ADDIE that includes iterative changes in the design and development parts of the process.
Needs analysis is done like it is in waterfall.
Design is done in short phases with rough drafts, and frequent feedback, and fast edits, like in Agile.
Development is done the same way: rough drafts, frequent feedback, and fast edits, like in Agile.
Implementation is rolled out like in waterfall.
Evaluation is done like in waterfall.
For example:
A course developed for a highly-regulated industry with some certain requirements to meet, but changes to other requirements happen frequently based on stakeholder feedback.
SAM (Agile)
Agile comes from the software development world, and is meant to make lots of changes fast, with each change getting closer to the goal of a perfect course. It's usually used in fast-paced organizations with little red tape to cut through.
SAM stands for Successive Approximation Model. It's a framework used in Agile.
Successive means one after another.
Approximation means as close as possible.
When an Instructional Designer or Developer uses SAM, they make a rough first draft of a learning product (a document or eLearning module, or anything else) that's easy to make changes to, and get feedback on it from SMEs and stakeholders. They go back to the draft and edit it according to the feedback to make it better. Then they send that draft out for feedback. They do this over and over until there are no more edits.
Project work is done in sprints with regular deadlines, usually every 2-4 weeks. Work is done in iterative cycles instead of one linear plan.
For example:
Making a bunch of different prototypes of a Rise course with lots of rounds of editing to get closer and closer to the ideal before it's rolled out.