Having just returned from the Gartner Summit, I thought a quick recap was in order. Besides I need a break from my measurement series (Part I, Part II, Part III)
Things got started with Gartner VP and Analyst Whit Andrews taking the stage carrying a shovel. My first thoughts were he we go with another speech about breaking new ground, but I should have known better. His comment was “A Gartner guy with a shovel, never a good thing.” But it turns out, it was a prop for talking about Minecraft, an online game both he and his son play on a regular basis. Here’s a YouTube of him previewing the shovel theme. It set the tone to talk about gamification, but the rest of the conference was decidedly higher level and talked about building and maintaining higher orders and evolutions of portals and content management.
Side note: While researching Whit Andrews I found this hilarious text-speech YouTube diatribe.
All of the sessions I attended were geared more towards the portal end of the spectrum. Within the realm of portals, the major focus areas were User Experience (UX) and mobile. Of course there is a ton subtlety and secondary topics. I won’t cover every session, key sessions, and perspectives here.
My first session was Gene Phifer talking about User Experience Platforms or UXP. Any reader of the Media 1 blog knows this is a huge focus for us right now. The UXP definitely has a place in the corporate landscape and is a critical piece for creating alignment between people, process, and technology. Gene’s original article on UXP is a great overview of the session. For more of Media 1’s vision for how UXP can drive performance, see Chris Willis’s blog post “Social, Mobile, Integrated…UXP and Your Future Workforce.”
“Using Generation 7 Portals to Attract and Engage Customers” with Jim Murphy was up next. While this session was geared somewhat towards customer facing portals, the same principles apply to employee or internally-focused portals. With a lot people I talk to, “portal” has become a bad word. In a lot folks’ experience, portal technology has been purchased, implemented, and subsequently fallen short of expectations. What we have to realize is that portals have evolved and continue to evolve. The biggest shift I see in portals is that they are moving away from being company, department, or role specific and they are getting personal. When you put the individual at the center of the design and you surround that person with filtered and specific options, portals get a lot more compelling—and that’s the root of why Media 1 is bullish on UXP.
Jim Murphy describes the characteristics of Generation 7 portals as featuring:
Jim and Gene teamed up on another session later that afternoon called “Employee Portals: The Revenge of the Intranet” to address the employee-specific side of the portal equation and aptly drew the connection that the employee portal is the heart of the new intranet. The changing ways that we work have driven the corporate intranet from being information portal to knowledge portal, then to process portal, and now to the latest generation of intranet portal that includes social functionality, mash-ups and combined applications, and has a mobile enabled interface. Social is the connective tissue that ties people to process and information—or people, process and technology in the Media 1 vernacular. More than social, the new portal-based intranet (SharePoint portals included) also enables information management and process management driving alignment to corporate goals. Gartner defines the must have characteristics of the next-generation intranet as:
Day 2 of the conference started out with Jane McGonigal’s compelling presentation “Reality is Broken” on the role of game play on our society and consequently how we can use those principles when addressing the needs of our organizations. Jane’s presentation was based on her book is Reality Is Broken: Why Games Make Us Better and How They Can Change the World. While I’m not always a fan of gamified approaches to development, I must admit to having some changing perspectives based on this presentation. One of the key advantages to gaming is the resiliency gained from repeated trial and error—and sometimes subsequent failure. I think that’s why a lot of people find golf compelling and certainly the incredible volume of Angry Birds play would also seem to reinforce that supposition. Seems to me that many corporate gamified approaches take a “failure is not an option” position and with the absence of failure or the possibility of failure, you miss out on the resiliency benefit and ultimately engagement that the “game” was intended to create. I’m going to do a future blog post on this topic alone. There are some very compelling distinctions between playing, competing, achievement, failure, and losing that deserve to be explored.
I spent the afternoon of Day 2 exploring sessions on UI/UX, people-centered strategy, Yammer and Mobile. Not that these sessions weren’t valuable or intriguing, but I have to assume you have something else planned for your day other than reading my blog.
I finished up the conference with a case a study from GlaxoSmithKline where they talked about their cloud-based employee portal solution, which happened to be a SharePoint 2007 site. While many of their experiences and concerns aligned with my other clients’ SharePoint installations, the fact that the SharePoint farm existed in cloud space created very few if any new concerns. Instead, it appeared to show considerable value to GlaxoSmithKline along the lines of the value proposition of other cloud services.
The final keynote of the conference was from Seth Godin. It was engaging and inspirational to say the least. While many of the examples used where on how to create compelling messaging, or “purple cows” as he calls them, it’s not much of a stretch to see how that relates to how we market performance improvement to our own organizations. It’s more than position; it’s the stories we tell.
In summary, the conference served as an excellent confirmation that I’m talking about the right things with my clients and in the right priorities. It also has taught me that I have a different perspective to bring to gamification and a new understanding of what it takes to make these games compelling. And finally, not that I needed any more convincing, we need to find ways of engaging employees on mobile platforms in meaningful ways. Our obstacles are just that, but mobility is critical to the new work environment.
I hate being late.
I am the first guy at a party because when something starts at a certain time, I just can’t reconcile in my head this concept of being fashionably late. I also suffer from anxiety when other people don’t show up on time. I have no idea where this great sense of punctuality comes from. My brother certainly doesn’t share my views on punctuality, so I’m not sure I can blame my parents.
However I got here, I’m kind of upset that I’m late to the TED party. I guess I got a little bitter and little bent from other groundswell business talk “trends” over the years, and I mistook TED for something it wasn’t (a platform for an agenda) instead of what it is (a platform for ideas).
When you get that many ideas in one place and you leave the conclusions and actions up to the viewer, it seems to me that what you have is most likely the purest source for informal learning we have ever known.
But now I’m on the outside looking in. It’s that Labor Day party your friend invites you to every year, but you never seem to have time to make. This evidently is the year you don’t automatically get an invitation. The Grand Rapids TEDx event is happening on May 10th, and since I didn’t attend years past, I’ve got to fill out an application to explain why I’m worthy of getting an invite.
When you think about it, this is incredibly smart. Even if there was no judgment placed on the merits of the application (which evidently there is), the act of applying shows a level of commitment and engagement. By denying general admission, you ensure that people really WANT to be there. That’s something worth thinking about when it comes to development activities and even the communities of practice we build for our organizations.
At any rate, I thought I would share some of my application in this blog, if for no other reason than to put a little more of myself out there.
I am constantly seeking new inspiration—and I know I inspire others—but it takes real work, real thought, and real attention.
I live my life as an open book. My business life and my personal life are one in the same and give each other real value. The things we care about personally are therefore inseparable from the things that our businesses care about.
I will contribute to the TEDx conversation through my writing—not only as a reporter of what I see, hear and feel, but also as an interpreter of how I can apply what I have learned and how others may do so too.
I will use the inspiration I gather to help formulate my own ideas, and I will share those ideas for the greater good.
I get charged up about very small details—a riff in a song, the way the grain converges in a chunk of curly maple, the rusty piece of junk in a photograph—and I want to take those little details and think of how I can reapply them, use them differently, put my own stamp on it.
I run a company. There are plenty of places to apply those details, but I am just as proud of the music I play, the guitars that I build, the last run I took in the skate park, the puck I stopped as a goalie.
The trick is to take one of those little things and grow it into something that combines some of those passions in life into something greater than the sum of its parts. The combination guitar/skateboard didn’t stay in tune so well, but I’m sure the next big idea is just around the corner.
Now what if you take those two simple questions and apply them to your job? Would you answer the same way?
How do we get there?
I, for one, am shopping for a few ideas and hope I find them at my local TEDx event. That is, if I get invited to the party.
In my last post, Pizza and SharePoint™—Branding and Design, I drew an analogy between presenting your best work to your customers without presenting your best selves to your employees in terms of the systems and sites developed for internal use. But why is it so hard to gain user acceptance and what sorts of things can we do to make it easier on ourselves? Why do we even care if your employees “accept” sites we build for them?
It’s easy enough to operate from the perspective that there is certain information that employees “need” to do their job, and there is certain information that is “nice to have.” In corporate structures, critical information or the “need to have” information is often presented in the most expedient way possible. Very often expediency in design results in the employee having to jump through hoops to get the information. “It’s the best we could do, in the time we had.”
While we may have accomplished our basic goals for a site, it doesn’t mean we did a good job. In fact, if we aren’t careful, we may actually create new issues in the process. If we didn’t gain acceptance of the platform we used for the initiative, chances are we’ve:
While it is sometimes necessary to compromise good design for expediency, we pay a heavy price for failing to gain acceptance. When we do gain acceptance, we achieve our goals faster, cheaper, and we create repeat visits that give us a viable way to expand our goals and create something sustainable over time. AND, we send a message that we care enough to think things through and value our team.
So why, when it comes to SharePoint sites, is it so hard to design for acceptance?
When building informational or community sites, SharePoint acts as a content management system, or CMS, and allows us to present the data separately and in different contexts. This means the data or information is contained in a different technical structure than the look and feel, or branding of the site. This is wonderful when it comes to keeping the content up-to-date, but requires a little extra planning when designing page layouts that support content that is meant to be changed independent of the layout. That seems to be where many implementations fall short.
I.T. departments are typically charged with implementing systems, such as SharePoint, and while your mileage may vary, they generally do a very good job of implementing the functionality or data layer… and tend to pay very little attention to the presentation layer. The typical result is a perfectly functional data infrastructure with a bone-stock, straight from the vanilla Microsoft set of page templates. Since SharePoint wasn’t designed to fulfill a specific need from a specific audience, not much care was taken with these stock templates. Frankly, I find them ugly and filled with usability issues, and I am not alone. Nonetheless, as SharePoint is rolled out, content owners are very often forced to use these templates either expressly or because they aren’t informed that they have any control over the presentation and don’t have the knowledge of how to change it.
In many organizations, a user’s first exposure to SharePoint is an ugly, usability-challenged site, a “crew pie” to reference my previous post. They may need the information that the site contains, but they are often left frustrated and unimpressed. For organizations that recognize this failing, this typically results in a subsequent project to improve either:
The truth is you need to do both. If you fix the content organization and improve the usability, it’s hard for the user to get past the ugly and truly engage with the site. If you fix the ugly but leave the usability out, you may get your users back briefly, but they will inevitably get frustrated again. User acceptance of a site means they accept both the way a site looks AND the way it works.
Usability is a topic for another article, but for organizations that have already fallen into the bad- or no-design trap, a good design can help them crawl out of the user acceptance hole. It sends a message that this site is worthwhile and important enough to warrant thoughtful design, and likewise the users of the site are important and valued enough to warrant the time and money spent on design. For those organizations that haven’t rolled out their first sites, let this serve as a tip:
Whether you call it branding, look and feel, or design, it’s a critical piece of user acceptance.
In the next entry, we’ll focus on usability some more, starting with setting realistic objectives and how to map those objectives to the functionality you design into your sites.