Monthly Archives: April 2014

IndieWebify.Me and the Knowledge Gap

Last week, a friend asked me what I thought of IndieWebify.Me, a movement intended to allow people to publish on the web without relying on the tools and storage of the giant corporations that currently control the majority of the social web. I’m the kind of person who gladly supports her local independent bookstores and farmers’ markets and food purveyors, links to IndieBound.org instead of Amazon to buy books, and admires the ideals of Open Source Software. So, I’m biased towards an independent and open experience.

IndieWebCamp, the conference devoted to strengthening the Indie Web, describes the concept of the “Indie Web” thus: “We should all own the content we’re creating, rather than just posting to third-party content silos. Publish on your own domain, and syndicate out to silos. This is the basis of the ‘Indie Web’ movement.” You’d think I’d be all over a movement aimed at bringing back more of that feeling to the modern internet.

I’d love to be, but I can’t just yet. IndieWebify’s an ideal with some pretty serious barriers to implementation; key among them, the base level of knowledge necessary for the average citizen of the internet to “Indie Webify” themselves.

If you look at IndieWebify’s main page, there are three levels of “citizenship,” each with two steps to implementation. In theory, six steps don’t seem that challenging. Unfortunately, the reality is more like WordPress’ Famous Five Minute Install – it assumes familiarity with technical concepts that your mainstream Internet citizen lacks. I’m a reasonably tech-savvy person. I can write HTML and CSS and SQL and work with JavaScript and JQuery; I’ve maintained self-hosted websites for almost 15 years now. Steps 1 and 2 seem fairly straightforward – set up a domain name, then on the home page, add a few slightly enhanced links. Not too difficult. But Step 3 (the first step to publishing on the “Indie Web”) is more confusing: “Mark up your content with microformats2.”

Okay, clearly, I’ve got some reading to do, so I click through to learn about microformats2. The general idea isn’t too difficult for someone accustomed to writing HTML and CSS – microformats2 is a collection of standardized class names that should be applied to web content to help computers contextualize things like blog posts and comments. But this leads me to a lot of questions: Can I make my existing installation of WordPress automatically include the microformats2 markup when I write blog posts? (No.) Do I need to manually mark up my content every time I write a post? (Maybe, but that’s a long list of class names to memorize or be constantly referring to.) What is an h-card in this context? Why does it seem to represent multiple opposing standards? … and who do I know that knows how to use the existing “implementations” (which are actual code libraries to be imported and implemented, rather than more user-friendly plugins)?

Talk about jargon-filled! The amount of technobabble here depends on any users possessing a fairly high baseline of coding knowledge. Though I’m willing to click on the links to learn more, this process is nowhere near as quick and simple as joining an existing social site. And this is just step 3 of 6 – we haven’t even gotten to implementing the technology to have the federated (whoops, more technobabble) cross-site conversations that are the core that would allow for you to properly “own” and attribute all of your words to you in the context of your personal domain. Compare this to the existing Corporate Web options, like Facebook and Twitter and Google, where the only thing you need to know how to do is type the natural language words you want to share.

Even assuming you have the motivation to learn, this is not an easy proposition. Buzzfeed’s Charlie Warzel wrote of Twitter: “Ask a longtime user to tell you about their first experience with Twitter and they’ll probably lead with some variation of, “Somebody showed me how to use it…” The idea [is] that, unlike most social networks [today], you didn’t usually just discover and use Twitter – you are taught, or at least climb a fairly steep learning curve.” He then goes on to explain that this isn’t good enough anymore; that for Twitter to continue growing, they need to cater to the mainstream, and make it easier to understand. IndieWebify’s version of this is so far from that point of being accessible to the mainstream that even early adopters are barely on the horizon.

Noted tech evangelist Anil Dash has pointed out how this technical insularity burned the development of the Open Web in the past: “We took it as a self-evident and obvious goal that people would even want to participate in this medium, instead of doing the hard work necessary to make it a welcoming and rewarding place for the rest of the world. We favored obscure internecine battles about technical minutia over the hard, humbling work of engaging a billion people in connecting online, and setting the stage for the billions to come.” Right now, IndieWebify.Me feels like it’s a lot of technical minutia. Maybe that’s how it starts, but it needs to get beyond that for broader adoption.

So, if you’re one of the few who actually knows how to implement these new Open Web tools and want to see the Open Web succeed, what can you do to spread this? As I mentioned above, “somebody showed me how to use it” doesn’t scale, so new tools require accessible design and/or tutorials. The challenge is that IndieWebify.Me currently has a simplified set of instructions, but these still need to be translated further to the technical capabilities of the early adopters, not all of whom are programmers. In comparison, most new social apps and websites come with engaging tutorials that do not require learning a complex set of standards or platform protocols, or being tied to a dictionary of these terms. This is the opportunity for evangelists who are serious about the development of the Indie Web as a competitive and viable alternative: create tools that will let users add these capabilities to existing publishing platforms as easily as I installed Facebook and Twitter on my phone. Heck, WordPress itself is already Open Source. I’d love to be able to install a WordPress plugin that would IndieWebify this blog; there are some plugins out there for older microformats standards, but none fully supporting the microformats2 standard as far as I can tell. I don’t want to have to write my own CMS just to connect this blog to the Indie Web communications mechanisms.

Despite my idealism and my honest desire for an Open Web, I am concerned about IndieWebify’s ability to support this dream; it can’t be just a niche for techies. They need better outreach targeted to idealists like me whose desires outweigh their current coding capabilities, and they need to make the process itself much simpler. I hope the current model of IndieWebify is an intermediate step towards a simpler adoption pattern that will compete with Apple and Google from a usability perspective. In today’s computing world, usability has proven to be the ultimate judge of adoption as social tools such as Tumblr and WhatsApp have proven. By bridging the knowledge gap, the IndieWebify movement can go a long way towards building the next generation of the Open Web.

How #Gartner Got Gamification Wrong

Apparently, Gartner has decided to “Redefine Gamification.”

I’m torn. On the one hand, I’m glad that Gartner is putting a stake in the ground in an area where I’ve done projects on and off for the past decade. But on the other hand, the reasoning behind their definition is not backed up by the market or by hands-on experience.

Their definition is as follows:

“Gartner is redefining gamification as “the use of game mechanics and experience design to digitally engage and motivate people to achieve their goals”

That is not a bad definition. It’s a bit incomplete, but I could use this in a consulting engagement as a “Gartner-approved” definition without losing credibility or face.

However, I disagree with all of the element definitions, because those details would make me look amateur in my understanding of gamification. To explain why, let’s walk through this definition bit by bit.

“Game mechanics describes the use of elements such as points, badges and leaderboards that are common to many games.”

No. Game mechanics define game and play-based interactions, only some of which are defined by award-based elements such as points, badges, and leaderboards. This is a basic definition of what game mechanics are. Chess is a game. Hopscotch is a game. Gamification does not have to consist of point-based interactions to be gamification. Game mechanics also include the methods, rules, and actions used to play the game. Effective gamification requires efficient rule creation and engaging behaviors.

As a basic example, you could create a basic data quality project where everybody cleans up a contact list. For every missing field that gets filled in, somebody gets a point. And the top 5 go on a leaderboard. That’s the addition of a game element.

But to make a better gamification experience, you could add a manual aspect, such as clicking a big button that says “Next Challenge!” that brings you to the next field that needs to be filled in. Or to increase productivity, you could force employees to only move horizontally or vertically. you could change the text color when the player completes a certain number of fields within an hour. The addition of time constraints, buttons, and movement control are all game mechanics as well and they should be included in a grown-up gamification effort.

Fundamentally, “dynamics” are dynamic and represent some sort of action. The motions and efforts used to play a game are a vital part of game mechanics.

I realize that some of these options still don’t exist in existing “gamification” platforms. I would argue that this is part of why gamification still hasn’t taken off: the platforms in place aren’t ready for the level of gamification maturity that is necessary to truly optimize business processes.

“Experience design describes the journey players take with elements such as game play, play space and story line.”

Play space and game play are both important, but are very different skills and experiences. “Dungeons and Dragons” and “Hide and Seek” are both rewarding game experiences, but an open-ended scenario development design is a fundamentally different structure and space from a closed “tag, you’re it” design.

In addition, narrative is different from game mechanics. You can watch a movie or read a book and get a story line. Yet, none of us call these activities “playing a game” because they lack the interactive nature of a game. Although narrative is an interesting potential aspect of gamification, it should really be an optional add-on rather than part of the core gamification experience design.

Going back to the data quality challenge, there are ways to add game play aspects that are outside of the core game mechanics. You could change the text color every time you fill in 40 fields in an hour to move to the next level. Or add bonuses by filling in multiple fields in one row or by taking on a new empty field within 10 seconds of the last field.

“Gamification is a method to digitally engage, rather than personally engage, meaning that players interact with computers, smartphones, wearable monitors or other digital devices, rather than engaging with a person.”

Also disagree on multiple levels. Players can compete and engage directly with other players in a gamified experience, but there is a game design or interface that facilitates interaction. But computer-facilitated personal interaction is still personal interaction. The separation between interacting through a computer or in person reminds DataHive of the false dichotomy that existed between “on-line” and “off-line” friends in the pre-Facebook era. Now that almost all of us have at least one friend that we’ve spoken to “on-line,” that false comparison is disappearing and we call them all “friends.”

It is possible to have a gamification experience that is solely digital with one person against one environment, but this is more akin to an arcade game like “Pac Man” or “Donkey Kong” where only one person can play at a time, nobody else can interact or interfere, and there is a single goal to achieve. This type of gamification is ill-suited to the gamification of business processes to enable team or corporate goals. In business settings, there is typically some level of team or community aspect to gamification. As a general example, the existence of a scoreboard is a level of social ranking and interaction between players.

The advancement of wearable monitors and mobile devices means that the interactions for gamification may not even be manually entered into a digital device. Consider two field service employees or delivery people racing against each other through the city to complete their orders. Their actual behavior is only minimally related to computer-based interactions, yet through their mechanically tracked actions and a set of game mechanics, this could quickly become a very gamified work place.

For a data quality challenge, one could add a chat window for employees to trash talk or help each other. Or one could enable messages or user tags within each corrected cell to show who had corrected or filled in each cell. There are a number of ways to provide “digital engagement” that personally engages players. In fact, the goal should be to personally engage players through some sort of appeal. By taking away the personal engagement, you remove much of the ongoing benefit of a gamification environment.

“The goal of gamification is to motivate people to change behaviors or develop skills, or to drive innovation.”

No. The ultimate goal may be behavioral or skill change, but the tactical goal that gamification actually accomplishes is to drive a specific action or set of actions. Let’s not forget that we’re talking about “game-based behavior.” The initial goal is to provide a behavioral framework and incentive structure to get specific work done. This doesn’t have to result in a Pavlovian reaction or behavioral change any more than Tetris forced players to obsessively rearrange their furniture into neat rows. Once you leave the game, you may not necessarily change behavior. It can be enough to simply participate in a gamified environment willingly and learn the rules of the game.

“Gamification focuses on enabling players to achieve their goals. When organizational goals are aligned with player goals, the organization achieves its goals as a consequence of players achieving their goals.”

Actually, corporate gamification is about teaching players to achieve corporate goals. Don’t get me wrong: I believe that personal and corporate goals should be aligned in the workplace. But gamification should focus on the behaviors that make employees more effective and gamification should be used to get work done. Otherwise, what is the value? It’s odd to have to tell this to Gartner, but we don’t go to work in mid-sized or large companies just to do what we want. We go to work to achieve goals as a team that we can’t accomplish as individuals. Gamification should be built around the corporate goals first, then be customizable based on individual KPIs and achievements.

This is an area that gamification platforms are starting to understand by developing increasingly modular and individualized incentive structures that are still based on a corporate strategy and corporate decisions. Platforms that are still stuck in a top-down, one-size-fits-all model are point tools that may be well designed for specific tasks such as sales, marketing, or ideation, but are not well-suited for enterprise usage.

So, why is Gartner so far off?

It’s not because of the quality of the analyst: I have actually enjoyed the vast majority of Brian Burke’s work and consider him to be one of the top infrastructure analysts in general. But Burke is ignoring all of the real hands-on work that has occurred in gamification for decades and it looks like he is coming in as a newcomer in this space. There is nothing wrong with that, but Burke needs to come in with the understanding that many best practices in gamification are older than the best practices for hybrid IT architectures or data warehousing. This isn’t an area where Gartner can simply come in and redefine all of the existing terms and best practices.

But this description shows a lack of experience in gamification and I would hazard to guess that Gartner has few analysts who have built out gamification environments in the last five years or have expertise working with the likes of Bunchball, Badgeville, and Bigdoor or related software such as InnoCentive and Mindjet that create open scenarios for new ideas.

It’s a shame, since I expect that the net result will be that Gartner will continue to go along its own path and build a confusing definition of gamification that is poorly aligned with both the software and consulting markets. The last thing that an emerging market needs is confusion, especially since networked, social, and digitally enhanced work environments are going to continue to be hot topics over the next few years. This should be a good time for gamification efforts to succeed on top of existing social networking and enterprise mobility efforts. I only hope that we don’t lose the opportunity in the next few years because analysts try to create their own untested models for gamification.