While catching up on some reading this morning two seemingly dissimilar topics are calling for similar actions. On a Jay Cross nanocast at Learning Light, Mark Oehlert talked about the lack of discussion around the design of learning in the face of (nearly) daily emerging technologies. He thinks we need to think about destroying how we think about design now – from many perspectives and create design. Kick status quo in the ass is what I’m hearing.
The other item was Steve Barth’s Emergence in Times of Emergency. It’s about the need for governments (‘the system’) to design for emergence in times of emergency vs. reorganizing post-emergency to create yet another massive bureaucracy (the status quo). He writes about ‘learned helplessness’ that leads us to believe ‘the system’ will take care of us. [is this like the organization who feels the training department will take care of a problem that may not be a problem training can even address?]. His contrast between system failure and ‘bystander success’ (successful reactions in terms of creating teams to address the emergency) made me think of status-quo ‘training.’ When faced with an emergency in our organizations do we respond with the status quo response and then fix it later for the next emergency? How can we design for emergence? I guess what I’m learning from reading both of these posts is that we are at a point in time where we need to take charge of emergent design.
I can relate this to a past ‘training’ situation where I failed miserably. Six weeks before a ‘training’ event I had no hand in developing or even knowledge of, I was asked by a senior manager to ”set up’ the event. This meant getting a room booked and making sure there was food and equipment available. Oh, yeah and collect all the PowerPoint presentations and get the attendees names in the LMS. Maybe help with travel arrangements. Coordinator of Suckfest right? It wasn’t training at all but an info-session on what is expected in the event of deployment due to a weather catastrophe (these were property claims adjusters). I didn’t want any part of it.
As I watched endless presentations about forms and expense accounts (all while making sure the coffee was properly refreshed) I wanted to cry. Here was a perfect opportunity to have designed a process for a potential catastrophe ‘teaching how to use tools to make the response happen so that the company would excel and so that adjusters could communicate with each other when emotionally spent. So my session would’ve been about access to and how to use the tools you can use to self-organize and react to the unknowns you’ll likely face. “The system” tiptoed up behind me and kicked my ass. How will you design so you can handle an organizational emergency? Is the money better spent on change management? Will you be part of the status quo or will you be Johnny- (or Jane)-on-the-spot? Coordinator of Kick-ass Design. Now that’s a title.



Bersin & Associates
Pingback: Design Shouldn’t Always Mean Instructional Design | Tom Werner