Learning Experience Design "The Mortar and Pestle Method"

Mortar and pestle are implements used since ancient times to prepare ingredients or substances by crushing and grinding them into a fine paste or powder. Although it takes more time and effort than using an electrical food processor, the use of mortar and pestle offers the advantage that the substance is crushed with low energy so that the substance will not warm up.

It is a great cooking example that shows time is an important ingredient in every dish. When it comes to LX-design, I often use it as a metaphor. You want to "blend" your program? Let's carefully look at the ingredients and take time to understand the wishful outcomes before we throw it all in the food processor and simply push the " blend" button. Here are some tips that might help driving valuable discussions with stakeholders.

No problem? No program

As a first step in the Mortar approach, we need to understand the problem. Not just opinions on the problem, but data that shows we actually have a real problem. When we understand the problem, we can think about solutions. These discussions take time. What is the root-cause? Is it a "skill" or a "will" problem? And is the problem being acknowledged by all involved or just by a few? Focus on the learners at this stage, not easy but needed ... we are creating a dish for them only to eat.

No practice ? No program

Now that we better understand the problem, we can start browsing for options. What worked in the past, might not work in todays environment. One element that is close to my heart, is the practice element in every program. We can create awesome content as a quick fix and measuring the views is tempting... but where is the application element? Who will guide the learner once that webinar is over or once that video is stopped? Where is that sandbox that allows people to fail over and over again, until they feel comfortable enough to go to the real environment - on the job? A colleague of mine shared this great post last week with me: "The more you sweat in training, the less you suffer in combat." I think it is true, the best learning experiences show a bit of mental-sweat :-)

No data? No program

There is no golden nugget when it comes to measuring program-effectiveness. I see a lot of L&D experts trying to prove that the program contributed to the business performance, often after the program, to close the cycle. In my opinion, it is important to have a look at the available data as early as possible ... yes.. at the design stage.. remember, no problem, no program. What data is available to measure the problem? What is your baseline and what are your ambitions? Are these realistic? Use that data-set to learn and measure on a continuous base .. be curious to see how it evolves over time and use it as a feedback loop to constantly improve. Avoid bringing in new metrics at a later stage.

No passion? No program

The above might seem obvious to all of you. However, too often we forget these steps as we are keen to start working on the solutions or we might put pressure on ourselves, as we have deadlines to make and business is asking us when the program will be launched.

If you feel that pressure, I advise you to think about the mortar and compare it to the machine. If you are passionate about cooking, you know it is worth waiting and you know time is your friend, even if you are hungry. If you are passionate about learning I presume you love to have discussions to better understand the problem, I believe you can get passionate about practice-areas where people can sweat and .. I think you can truly be happy when you found that data-set that helps you measure " the real thing" .. Passion is what you need.. what else?

So, although tempting ... don't just push the automated "blend" button .. take time and go for the "mortar" approach!

Anke