Friday, July 16, 2010

It takes a village to build a community

We've been busy behind the scenes planning for the Tandem Learning Innovation Community (TLIC). As excited as we've been to get things started, there are just some logistics that need to get taken care of, things that need to be planned, strategies to be set. And the truth is, we have questions...questions that we need the community to answer. We could certainly move forward with the things, strategies, initiatives that we're interested in, but this community is all of ours and we need all of our input to shape it. So let me pose some questions here with the intent to collect your feedback...let's plan the path forward together...


  • What technologies are the most interesting to the TLIC? Are there technologies you'd like to learn more about? Are their particular companies or products that would be interesting to feature?

  • In the interest of continuing a research arm of the TLIC, are their companies that would be interested in participating in or contributing to research or case studies? We have been exploring partnerships with several universities, but would love to see what, if any, interest there is for companies to contribute to the research initiatives.

  • We're considering moving the community off of the LinkedIn site, although we are hoping to maintain the link to our LinkedIn profiles. If there were no restrictions, what would be useful features/functionality on a community site, or what might you find most valuable?

  • We're thinking of holding our first networking event on our Second Life island (in development) in early/mid August. We were planning for the first event to be an open discussion to address some of the above questions and pose some additional opportunities. What kind of structure have you found most beneficial in the past for Innovation Community events? What would you like to see more of?


We're looking forward to your input and perspectives and will be announcing details of our first official TLIC event soon! Stay tuned...

Friday, June 25, 2010

ThinkBalm Innovation Community becomes the Tandem Learning Innovation Community

After we broke the news that we planned to disband the ThinkBalm Innovation Community, members of the community expressed lots of interest in finding new leadership for the community moving forward. We are excited to announce that effective immediately, Tandem Learning will assume the community management responsibilities of the newly named Tandem Learning Innovation Community.

The value of this community is in the membership and the collective wisdom and experience of the group, and Tandem’s focus on new technology, user experience, learning design, and strategic business innovation allows them to touch on the areas of interest that bind our community together. We believe the leadership at Tandem is committed to maintaining the integrity of the community while finding new and exciting ways to add value to everyone who participates.

Exciting times are ahead for all of us and we’re looking forward to what happens next!

Erica Driver, co-founder and principal, ThinkBalm
Sam Driver, co-founder and principal, ThinkBalm



We’re so pleased to have the opportunity to continue the amazing work that Erica and Sam began in 2008 as we assume responsibility for the newly deemed Tandem Learning Innovation Community. While we know many of you from our work in virtual worlds and immersive technologies, we’re looking forward to interacting with all of you in the weeks ahead as we plan for the future of the community. In our new role as the community managers, we will honor the tenants of the community as established under ThinkBalm and will seek even more ways to bring value to our members. Please feel free to contact me directly with your thoughts, ideas, and feedback...this community belongs to all of us and it’s your input that will continue to make it valuable and successful.

Koreen Olbrish, CEO, Tandem Learning
Koreen.olbrish@tandem-learning.com

Thursday, June 24, 2010

LEEF wrap up: The best little conference you're missing

Just back from LEEF 2010 at Harrisburg University, and in its second year, it did not disappoint. Last year we attended the first LEEF conference, and were thrilled at the structure and the content. With a focus on serious games, simulations, and virtual worlds for learning, we were treated to in depth case studies and demos that you just didn't see at other conferences.

This year was even better. The quality of the sessions was amazing. We got to see demos of products, like IBM's Innov8, before they are released on the market. We got to play full blown games and ask all of the design and strategic questions that you don't normally get to ask at conferences. And we got to really meet and connect with brilliant practitioners in our field.

The keynotes blew me away. Mike Cuffe, Vice President, University of Farmers, Claims at Farmer's Insurance, is doing some of the most cutting edge training I've seen. It was refreshing to see a visionary in corporate training who practices what he preaches and is vigilantly staying ahead of the curve. Jerry Heneghan, Managing Director, Virtual Heroes Division at Applied Research Associates gave a really inspiring presentation on 3D immersive games that gave some insight into how they have been effective in changing behaviors. I am looking forward to seeing what his group will be doing next related to health.

Tandem presented two sessions on ARGs (alternate reality games) and both were really fun for me, in different ways. The first was our case study overview and we presented to a pretty packed house. Even more exciting for me was the line of people afterwards that wanted to talk more. I'm excited to see ARGs really seeming to have some traction for corporate learning, and I'm looking forward to our next projects in this area. The second session was a debrief of the ARG that we helped support at the LEEF conference, The Robots are Eating the Building. It was a truly valuable learning experience, and I got a lot out of the debrief.

Thanks so much to Jen Reiner, Andy Petroski and Charles Palmer for putting on such a great conference. Can't wait to see what you put together next year...and hopefully some of you who haven't already will join us!

Monday, June 21, 2010

Taking responsibility for big, bad problems

I just read this post by Patrick Strother about BP's failures in light of the gulf oil spill...or gushing, which is a bit more accurate than spill. It made me think about corporate responsibility, and personal responsibility, and knowing when to say when.

I'm not going to defend BP. But I might, just for a moment, empathize with Tony Hayward. Don't get me wrong, I think what BP has been doing is criminal and I think their attitude in dealing with a global environmental crisis is beyond reprehensible. And I think Tony Hayward is a first class douche.

But do any of us really think that this is one man's fault?

Tony Hayward is responsible for his actions and for the actions of BP in the gulf oil spill crisis. But he is also being positioned as the scapegoat in a saga that demonstrates that sometimes, you need to admit your failures and step aside. Tony Hayward's biggest problem is insisting BP can fix a problem that they created but now is too big for them to overcome.

The truth is, in any situation or crisis, what led you there is usually several people's responsibility. Very rarely does a problem start as a big problem...usually its a little problem that just keeps getting worse over time. Sometimes people ignore a problem or situation. Sometimes people are aware of a problem, but don't have the means or the skills to fix it. Sometimes even when people are aware and have the means, they just don't have the desire to fix it or don't want to exert the effort to take responsibility. All of these attitudes lead to the inevitable...if you ignore a problem long enough, something big and bad will eventually happen.

And when disaster strikes or big, bad things happen, someone has to take responsibility. Usually, the person who gets blamed for the problem is not the person, or certainly not the only person, who caused it. But in any big, bad crisis, someone is always left holding the bag.

Big problems are difficult to address. Because it was the collective negligence of many people that got you there, you'd think that if everyone just started paying attention, addressing the issue, that it would be fixed and things would be better because people would have learned their lessons. But that's not how life works and people are, in the end, who they are. What got you into the big problem will very likely be the very same reactions that prevent you from getting out of it.

Sometimes you get too far down the road, and there's no way that the people who caused the problem are going to be able to fix it. They are defensive, exposed, and confused. They grasp at half-baked solutions or go through the motions of looking like they are trying to fix things, all the while still engaging in their old behaviors that got them there. They consult with experts, they read about similar situations, and they vow to be different, to do better. But sometimes, too much has happened. Sometimes its too late. Sometimes organizations, cultures, relationships are not able to handle the big, bad problem. Sometimes they shouldn't. Sometimes, despite their best intentions, it just drags the problem out and makes it worse.

We're seeing that with BP now. They vow to fix it, they come up with solutions...but the attempts they are making keep falling flat. Why? Because BP had the ability to prevent this from happening, but instead of preventing it or preparing for it, they just hoped they wouldn't ever have to face it. They did not develop a culture of responsibility and now their laziness, their ineptness, and their fraud has been exposed.

And the scapegoat, the one who gets pinned with the problem, has to suddenly step into the spotlight and make a decision, take responsibility for the actions and decisions of everyone who got them to that point, for everyone that contributed to the big, bad problem. Yes, maybe a leader is ultimately responsible for everything that happens, but that's usually because that leader is the one who has to deal with the consequences of the actions of everyone around them, and so it behooves him or her to stay in control.

You can't control everything. Sometimes you just have to trust people. The best leaders trust those around them. And when that trust turns out to be ill-placed, its the leader who must step up and say, yes, this is a really bad problem. Yes, we caused the problem. No, we aren't prepared to deal with it and we don't want to make things worse by trying. Unfortunately, we aren't seeing a lot of that from Tony Hayward.

Organizations fail at this all of the time. Look at Enron. The banking industry crisis. And now BP. Sure, there are one or two people that are blamed...but it was the organizational culture that failed, not just the leaders at the top. It was the organization that recognized there was a problem and ignored it, covered it up, pretended like everything was ok...until it couldn't be ignored anymore. And then, its usually too late. Sometimes when an organizational fails in such a big, bad way...the right answer is to step in and dismantle the organization. Or in the case of BP, to hold them accountable but relieve them of the task of fixing the problem. Its clear they are ill-prepared and unequipped, and their attempts are making the situation worse.

Who knew that Kenny Rogers would have so succinctly taught us how to face big, bad problems? Unfortunately, it seems too many times we err on the side of holding 'em when we should walk away, or run.

Tony Hayward is responsible for what has been happening with the oil spill, and I have no doubt that he will have to deal with the consequences of his actions and decisions. But he is not the only one who is responsible. I only hope that Mr. Hayward and BP recognize sooner rather than later that their attempts to fix the mistakes that they've made are making things worse for them and us and is ultimately dragging out the time its taking to get to the inevitable stopping of the oil leak so that we can start cleaning up and healing. Sometimes the most responsible thing you can do is admit when a problem is just too big for you to fix.

Wednesday, June 16, 2010

The right people

When we first started Tandem Learning, we used to have Wednesday night "rockstar" meetings. (I hear that this is a very start-up thing to do.) We would sit around as a group, talk about our strategy, make plans about what kind of company we wanted to be. We talked about our mission, vision, and values. We brainstormed the types of problems we wanted to help organizations solve. We matched our expertise and potential solutions with those problems. We dreamed about who we would become as a company.

One of the highlights of those meetings was a list of what we wanted. Here's that list (paraphrased, because I can't find the flip chart paper we put it on):

  • Do good, meaningful work
  • Work on cool stuff
  • Only work with smart people we like
Seems pretty simple, right? But in reality, not so much. The first one has been easy...we all focus on the quality of our work. The second one? Well, sometimes what pays isn't what's cool, and sometimes what's cool violates the first bullet...and we definitely aren't sacrificing that.

The complication is really the third bullet. We've all known what its like to work with amazing people...the problem is finding them, and when you do find them, convincing them that they want to work with you. We've been really picky here at Tandem, and we've been lucky. We've worked with some exceptionally smart and likable people, and we've met a lot along the way. Now that we're in a position to grow our team, we've had some serendipitous moments of mutual interests and good timing that are helping us honor that third bullet. And we couldn't be more excited.

We're going to be making more hiring announcements in the next few months, but we are thrilled that Tim Martin is joining the Tandem Learning team. We met Tim in 2008 when he was working for the eLearning Guild and we were planning our first conference as a vendor at DevLearn. Sometimes fate or circumstance presents opportunities, and we're ecstatic that Tim is coming on board.

Tuesday, June 15, 2010

Even more change in the virtual worlds industry

I was a little surprised and saddened to hear today that Erica Driver from ThinkBalm has taken a marketing position for a software company and will no longer be serving as an analyst for the immersive technologies market. Her departure is a blow to a much needed role in the virtual worlds industry: independent data and research on the use of immersive technologies. In addition, the closing of the ThinkBalm Innovation Community leaves a gap the development of users groups and a community that can share best practices.

In any emerging market, start ups lead with ideas and as the industry matures and the market becomes established, start ups grow, fade away, or get bought up by larger companies who want to enter the market. We've been seeing these changes over the last few years in immersive technology companies, but it seems the services companies are the ones that have taken the hardest hit from the snail's pace of immersive technology adoption.

Erica is a bright star in the virtual worlds industry and I very much valued and trusted the work that she was doing on behalf of all of us to evangelize immersive technologies and virtual worlds for enterprise use. I wish her and Sam the best of luck.

And now, the onus is on us to continue the good work they were doing.

Monday, June 14, 2010

Virtual worlds industry changes and what it means for learning

A few things have happened over the last week that have been big news in the virtual worlds industry...but what does it all mean for learning?

First there were rumors, then there were the actual Linden Labs layoffs. From all accounts, it appears that the enterprise focus of Second Life is gone, at least as far as Linden Labs is concerned.

Next, Proton Media announced their partnership with IBM. Given they were already integrating with Microsoft, that definitely puts them in line to pick up where Second Life was leaving off.

And then this week (today actually!), Reaction Grid launched Jibe, which they describe as:

... unique among virtual world solutions, offering the ability to deploy under your own branding on your existing websites & blogs. It works in web browsers, desktop (Mac & PC), mobile devices like iPhone & iPad, and even game consoles.

So what does all of this conflicting information actually mean to us, enterprise proponents of virtual worlds for learning?

1. Despite the chicken littles out there, the sky is really not falling for virtual worlds. Probably not even for Second Life. Yes, maybe Second Life won't be the leading enterprise virtual world platform, but I've said from the start that Second Life isn't the best platform for learning and that's not what it was designed for anyway. The enterprise focus was a retro-fit, an attempt to capitalize on the obvious benefits of virtual worlds for collaboration and learning. But there were many more drawbacks than benefits of using Second Life for those purposes, and other virtual world technologies like Protosphere from Proton Media, Vastpark, and Teleplace have focused on overcoming the functionality deficits that Second Life had in addressing enterprise customers' needs.

2. We're moving towards the browser. In a year or so, any virtual world that isn't accessed via browser with no or minimal plug ins is probably not going to be viable.

3. Social networking will eventually move virtual worlds more mainstream, not business. Just like other social media technologies, virtual worlds will be successful when people see the social benefits and it doesn't seem like work. Right now, they are a lot of work. That will shift and will move virtual worlds as a much more viable enterprise learning tool. And since learning is social, it just makes sense, no?

4. Content and design are still the key. Virtual worlds will need well-designed and appropriate content to move forward. Reaction Grid's Jibe seems to be moving in that direction, allowing for learning affordances that haven't been seen in other platforms to date, or at least not all on one platform. It will continue to be the case that no matter how cool the tools and technologies are, that the content design and user experience will drive adoption. We're still woefully behind in the learning space in having great examples of appropriate virtual world content design. But we'll get there, or virtual worlds won't.


I'm encouraged by the recent news that change is coming for virtual worlds. I've been waiting for a shift, a big announcement or event that would throw virtual worlds into the limelight and drive adoption. What's more likely, based on the news of this past week, is that the little steps will keep accumulating, until we don't remember how we practiced things before we had avatars in virtual worlds.