FrankESNstein

"Hateful day when I received life!' I exclaimed in agony. 'Accursed creator!  Why did you form a monster so hideous that even you turned from me in disgust?"  - Frankenstein's Monster

In 1818 Mary Shelley penned Frankenstein. In part the novel explored how electricity, a strange new power then might be used to create what only occurred naturally- life. 

The take away for me - don't mess with a good thing.

        Well, in the world of Enterprise Social I fear many didn't heed the warning. Our platforms often resemble the hideous Monster with it's parts fused together. Features such as streams, blogs, tags, filters, discussions, status updates, polling, places, groups, etc have value but when jumbled all together and released on the unsuspecting - they litter, complicate and ultimately frustrate and repel employees. It is often that the platforms resemble the 8' man-made man that terrifies the bewildered villagers. In some cases the people will slowly and only partially accept the platforms. In other cases they shun them and destroyed the incarnations through their inactivity versus overt aggression.

       Web 2.0 was a simple concept and simple technology but once brought inside an organization as an ESN it has been perverted and manipulated to mirror the comfortable but outdated systems and structures of the organization itself. 

The spirit of social technology is being crushed. It vaguely resembles the experimental, fun, easy world in which it was born. It is often a tool of the organization but not of the people. I've written about "simplicity" in the past and believe Simple is the New Black. That, like in Frankenstein, we have messed with the natural course. Twitter is a perfect example of "nature". A simple interface w/ simple rules and a simple goal to connect people which millions caught on to. It also had obvious affordances with its open API allowing for fantastic uses and integrations. Web 2.0 like Twitter blended seamlessly into the chaotic World Wide Web. In it's simplicity it amplified humanity, conversation, and sharing. The technology took a back seat. 

Work environments, like the web, are equally complex and growing more so with ever changing technology, system, customer need, and competition. Yet the answer for many is to release monstrous platforms that often add another layer of work to get working done. Ryan Tracy shared this, which I think nailed the issue because of how ridiculous it is. Yet if you swapped Facebook for many ESN implementations, it wouldn't be funny at all. Web2.0 vs. E2.0.

Social technology does work in some organizations but that depends on what one means by work and the organization using it. All are unique and one's definition of success, user adoption, is not the same as another's, work adaptation.   How do we avoid creating a monster enterprise social network? Yes we need advocacy and yes we need to draw on good examples and approaches promoted by the likes of Jane Hart but before that, potential community managers and leaders need to put egos aside and...

1. Ask yourself why? If your answer is to bring the workforce closer together, do they even want to be closer? Are they close now? It's a culture, people issue first.

2. Keep it simple. Start small doesn't mean just starting with a pilot, it means thinking of light design.

3. Play guide, not God. Encourage people to find A way, don't create THE way.

Learn from Dr. Frankenstein's mistake. Just because we can doesn't mean we should. Know the needs. Know the culture. Know your limits.

Learning is in a Holding Pattern

On a flight this week I noticed that safety awareness efforts by flight attendants is slowly being replaced by video demonstration on small monitors in the headrest (newer planes). Outsourcing this task to technology, like in other situations, can free people up to focus on other important tasks.  This is a chance to really improve learning because video has many affordances to increase attention and learning about safety as the demonstration have become white noise; ignored by most everyone. As I watched with great hope, I was disappointed to find the video is only a replica of the flight attendant demonstration... sigh - a common occurrence though where new technology support an old practice.

They chose to infuse humor into the demonstration which frankly only made me remember the corny gags and not the important actions to take or why to take them. That is the real miss. They leave to assumption that one knows why to do or not do something. Yes, making an emotional appeal is the right action but humor is not the right emotion to trigger. The reason we aren't supposed to smoke, we are to remain seated with seat belts on, and know how to use the oxygen masks are for safety and safety is serious.

Why not show me what can happen if my seat is unbuckled or my tray table isn't up? What happens if objects shifted during flight? No, I don't need to see a skull get crushed but this could be done creatively, without instilling fear through evocative reenactment. Video is the perfect medium. Show me the why/ why not and not just the how and where. Connect the right emotion, with the right content, in the right context and one is more apt to remember when it really matters.

Oh, and while your at it, show me why it doesn't hurt to ask the 6' tall guy behind you if it's ok to put your seat back before pinning his knees or snapping his laptop screen.

It's All Training Until It Isn't

The course is a seductive solution. I've written and spoken about this before as I believe it's due in part to years of formal learning dominating our lives, better known as learning learned helplessness. And because employees can't always wait for L&D to develop a solution they will take matters into their own hands. Sometimes this is good as they find the resource (human or material) to solve their own problem or it can be troublesome in that sometimes they create a PowerPoint presentation for others. It's enough to raise the hair on a learning professional's neck... but I say don't fight it. Appreciate their moxie and shift your focus to consultant and help people rethink the decision.

 It's about  an opportunity not ownership.

So what does Consultative L&D look like? Here are 5 short examples of actual engagement with some of our stakeholders that has not only worked to pragmatically solve a business issue, but helped enlighten those we worked with to stop thinking training only. Again, each of these began with something along the lines of "we need a course on..."

1. People Don't Argue with There Own Data 

A senior divisional leader requested training.  Donning Performance Consultant we stepped in to see if there was a skill gap and if it warranted training as a solution.  This is how the conversation went: 

Me:  "How are new employees learning the methodology and approaches today?"

Him: "Our programs that employ it learn on the job. Seasoned developers already know the general methodologies and our rendition is not that much different than industry best practices. The new individuals who are less aware will have a mentor who will sit with them to bring them up to speed.

Me: "What are the biggest gaps in execution today?"

Him: "Nothing that stands out. Each team/project does it slightly different to accommodate their project, environment, customer, etc."

Me: "Since our methodology is very much based on industry methodology how/where is it different?"

Him: "It’s different in just a few ways: it accommodates customer processes, documents, and tools."

Me: The objectives speak to having employees “Understand.” How will we know they understand? i.e. how will success be determined regardless of solution chosen? Are their project executables/deliverables that can be identified that would show knowledge/skill advancement?"

Him: "We are talking about very tightly knitted teams, they “self-organize” and are accountable for what they sign-up for. It’ll become immediately apparent if someone is not keeping up or they just don’t get it." 

As we dialoged it became apparent to him that a training course was inappropriate, too heavy and unnecessary. Today we are working on small modules loosely connected, some may be podcasts, SME video demonstrations, job aids and checklists that people can pull on as needed to supplement time with knowledgeable team members.

2. When a job aid will do, do a job aid.

After a SME crafted a highly visual step-by-step on generating financial reports in a PowerPoint presentation meant for a live session, I aimed to understand the need and overall objectives after the fact. Not one to throw the baby out with the bath water, we determined that simply following each screen could produce the desired results, no direct instruction needed. The next step was to fine tune through some actual user testing, then reproduce as performance support for use when generating the reports.

3. Need a presentation? Flip it.

Sometimes content is so new or the workforce is so new to the process that a more formal solution is warranted. It's important to strive to "do no harm" to the work flow and keep learning opportunities as pull vs. push for our employees. Recently I was approach again to help develop a live presentation. Ultimately it was determined, after a bit of dialog about attention and attendance, to release the session as prerecord and then tag it in our ESN. We'd give the audience a week to view and review as needed and then ask them to post in the ESN their additional questions for the SME to address along with peers.

4. Don't Reinvent the Wheel

In a desire to reaffirm the commitment we have to our client and ensure consistency of execution, the idea of creating a course for a segment of our workforce to complete on a client methodology and tools was promoted. In our analysis we though this would be redundant as much of the material was readily available. Our solution was to curate vs. create. Tapping into the already available formal materials we proposed an internal certification program which modeled similar certifications recognized by our folks. This two level certification not only recognizes employee completion of identified materials but will also acknowledges their successful application in using the materials in the authentic situations. Additionally, they are credited for sharing their knowledge and contributing to the growth of their more novice peers.

5. Pull not Push

Choosing a performance support solution over a course is not always the correct option. People need formal especially when they are new to the content or safety or security is on the line. However when people are more experienced they need less formal and more informal or social opportunities. This was the case with one of my first efforts. Initially a Project Manager's boot camp was proposed but this made little sense for our experience Project Managers just needing to understand the nuances of our organization's project management approach; which for the most part was very similar to what most Project Managers knew from their certification through the Project Management Institute. So instead we leveraged numerous SMEs to co-create job aids, templates and short recorded sessions to orient and reinforce our unique ways of executing project tasks. Each of these could be pulled on in the time of need.

Each of these efforts in and of themselves is small. They grew out of small conversations via email or phone call. In each one we have reinforced the approach I think L&D needs to take; small, embedded, impactful, and integrated with the workforce solutions focused not on just on learning but performing. For L&D to reinvent itself it must not only meet the business need but reframe the thinking throughout the organization one problem, one person, one conversation at a time.