So, one of the things that’s happening is that my ideas on learning science are driving the development of elevator9‘s platform. And, that’s a good thing, I think, because my postulate is that too many platforms have nobody in the C-suite who understands learning. I’ve talked before about learning from this endeavor, but I want to take a step back and talk more in principle about getting real in practice.
Of course, right now it’s easy for anyone to make a platform, and many are. Which doesn’t mean the design is based on learning science, to be sure. I recall meeting a new platform provider’s team, and their answer to the guiding principle was what the customer wanted. Which, to be clear, isn’t what the customer needs. (This was all pre-GenerativeArtificialIntelligence, of course). And I get it, but it’s not a long-term strategy.
What, instead, is that the goal here is to take the principles of spacing, and see how that works for learning. One of the things to realize is that, for pragmatic reasons of access and c0st, many studies are done a) with college students in psych, b) in quite small windows of time, and c) with only one learning goal. I get it, but…that’s not how the real world works. So, we’re facing some challenges.
What the intent is is to augment face-to-face events with the reactivation over time and bridging the gap from event to ultimate performance. However, most events have more than one learning goal. So, which to space? Also, if done right, there may be more than one event (certainly for leadership, one of the areas that prompted CEO David Grad to start this whole initiative). The events may also have new and different learning goals. So, for instance, evaluating self and others’ emotions at one event, and moving on to coaching at the next meeting). Which means that we’re starting some goals new, and there are likely still some previous goals that need addressing.
It gets more complicated, too. What if the audience is busy and/or unmotivated? How do we make it easy to accomplish? Short interventions, to be sure, but how abour rescheduling on an individual basis? These issues begin to bring in interface design issues on the part of the learning designer and the learner! What’s happening, of course, is iteration: trialing, evaluating, revising, etc. Learning, in short.
What is a positive, of course, is the learning that accompanies this effort. elevator9’s going from an initial vision to a combination of what folks know they need, and what we know they need! We’re also going from a app-building environment to a true developed system. We’re going from a couple of folks and a drawing board to a full team. Along the way, lots of issues emerge. I’m don’t have much experience outside of learning design and cognition, so I’m listening and learning. I of course can’t keep my big yap shut all the time, and weigh in on some things (even, occasionally, usefully!).
In retrospect, that’s also true of what I’m doing with LDA, of course. We’re trialing different curricula, testing out things about the offerings, and trying to not just survive, but succeed in our goals to lift the game of the industry. In both cases there’s established competition, so it’s not an easy step. Still, it’s the right one (and I’m stubborn ;).
The reality, not really new but always a revelation, is that it’s great to know theory. It’s great to solve real problems. Mixing them together, trying to apply theory to real problems, is even better. It improves the solution, and informs the theory. It’s all about getting real, and that’s a blessing. That’s my take, what’s yours?
