Organization Horsepower

Thinking Like a Motorcycle Racing Team

Tag: Social Learning

Five Attributes Your Mobile Sales App Must Demonstrate

It’s been a little while since I’ve written about mobile, but I committed this week to do a talk at the eLearning Guild mLearnCon, June 19-21 in San Jose; so it’s top-of-mind. My talk is going to be about the design process we used in an actual development scenario for a client of ours. That particular application never saw the light of day, but it got me thinking about the components of that application and why we were so passionate about including them.

Specific to the sales audience, we believe the following five attributes are critical to the successful adoption of a sales-focused mobile app. Your sales app must be:

  1. Relevant everyday – On the surface, this means the content must be kept up-to-date. While that is critical, when you dig a little deeper, it also means the content must also be applicable every day. It has to be more than learning about the future, tomorrow’s product, or the sale they might someday have. It has to help them do their job today.
  2. Improve some aspect of the sales process – Sales has always been and always will be about more and faster. If your mobile sales app doesn’t help them increase or accelerate the sale by letting them access more information faster from different places, or work with other people in your company more efficiently, sales people just plain won’t use it. In fact they will find some other mobile app that will help them, or they will spend that time doing some other activity even if that’s Angry Birds.
  3. Integrated across sites and systems – In most companies, there is no lack of systems or internal sites designed to support the sales team. If mobile devices can even access behind your firewall, chances are those systems and sites aren’t very useable on a mobile device, and you can’t expect your team to ferret out and adapt while they are on the go. Your mobile app needs to be a combined interface to the sites and systems that are most critical to the sale.
  4. Socially connected – Mobile technology at its core is about real-time communication. If your app doesn’t take advantage of this, you are missing something really important. Imagine situations where your app can help sales people get answers in seconds, when it used to take hours.
  5. Intuitive – The reason Apple’s products are so pervasive is because they always put the user experience first, even if that means it doesn’t do everything that you imagined. This isn’t a ringing endorsement of Apple by any stretch, especially for the enterprise, but the point is that it has to be better than easy. It has to be intuitive to the point where it feels automatic to the end user. Mobile apps do not have, nor should they need, training programs. They just work. You are better off not including a piece of functionality rather than including one that needs to be explained.

This isn’t intended to be a comprehensive design guide; just five things you need to consider. Of course, there are big differences between organizations and the processes that they use. Device strategy, even if it’s “Bring Your Own Device” or BYOD, also factors into design. However, if your app does these five things successfully, it will make a difference in the performance of your sales team.

Pizza and SharePoint™—Branding and Design

Once upon a time, in a galaxy far, far away… I used to work for one of the giant pizza chains. As a learning professional, I took it upon myself to understand what it was like to work in a pizza store. You don’t have to be in a store for too long before a mistake happens. Wrong toppings, giant bubbles, or just plain ugly pizzas. Most operators had enough sense not to send these pizzas to the customer and would make a new pizza, but instead of wasting $3 in food cost and throwing out the mistake, these pizzas would become “crew pies” and would often sit boxed on top of the oven until someone had time for a break and would grab a slice or two.

Well, on one store trip, I noticed a sign on the wall that said “no crew pies.” My first reaction was that the store operator was sending a message about mistakes, and not making them, but the company had all sorts of slogans and signs about making quality product and “no crew pies” was not one of them, so I had to ask.

Turns out the operator had much different reasons, and it wasn’t a slogan; it was a rule. He explained to me that he was in a war for good employees with the other restaurants in town. It was hard to find and keep people, and he felt that it sent the wrong message to serve the people that worked for him the worst product his store turned out. Besides, if his team thought that bad pizza was good enough for them, how far of a stretch is it for them to expect his customers to live with bad pizza?

Fast forward to today. I am in the privileged position of consulting with some of the world’s largest companies. Companies that are selling customers some of the most advanced systems, services, and technology available. However, all too often the internal sites these companies use to support their own employees are the internet equivalent of “crew pies.” Barely branded and poorly organized. This is especially true when it comes to SharePoint™ sites.

It’s not enough to just have the information out there. The person has to first want to use the site (acceptance) and then be able to use the site (usability). Newsflash: The default SharePoint™ page templates are not attractive and are not intuitively usable. Even if you are lucky enough to have an IT department that branded the default templates, it most likely is still not good enough. Chances are if you already have an existing SharePoint™ implementation, you’ve seen these default templates in action, as have your users. They have already formed a negative impression of what SharePoint™ is and have little or no vision of what its potential is.

I’m not suggesting that all of your internal sites become graphical Flash sites with splash pages, but I am saying that at a cursory glance, your internal sites need to:

  1. Not look like SharePoint™ default templates
  2. Reflect the importance of the people, business line, product or service it is intended to support

In SharePoint™ development circles, efforts towards user acceptance are often referred to as branding, but it’s more than that; it’s part of the overall design. The goal of design should be a positive or at least transparent user experience. There are two components of user experience, acceptance and usability. Acceptance is typically the result of good positioning and good visual design whereas usability stems from information design.

If we go back to our “crew pie” example, mistake pizzas may in fact taste good, but the user experience is disrupted because admittedly user acceptance is compromised: the pizza is ugly or its usability is challenged—it has the wrong stuff. That’s not to say the crew won’t eat it, but they may not like it.

The intangible message here is that our internal sites and systems set the tone for what our employees deliver to our customers or users, and it’s imperative that our customer’s user experience be flawless. Besides, in a war for talent, our valued employees deserve better than a “crew pie.”

In my next blog post, we’ll dive more into the user acceptance side of the equation and explore some strategies for designing and validating user acceptance as part of a branding, positioning, or graphic design effort.

Overheard at Strategies 2011: Employee Engagement

Media 1 is pushing hard into the Human Capital Improvement space with SharePoint-based offerings for cohort learning (leadership and sales) and Onboarding. To learn more about the concerns and needs of people involved in talent management and development, we decided to attend MediaTec’s Strategies 2011 conference in Half Moon Bay, CA.

What a fantastic location and a great conference filled with key learning around diversity, inclusion, and techniques for managing and developing the workforce. However, the concept that I want to focus in on is that of employee engagement. Engagement isn’t a term that I have used a lot before now, but it’s one ingrained in the talent management lexicon.

It’s a great term because it encompasses and describes a level of involvement and commitment regardless of the development level or stage that an employee is in. While consulting on Onboarding systems, one of our primary goals is to increase time-to-productivity, but if we want higher levels of productivity, we have to get engagement first. A new hire can be modestly productive without engagement, but that hire won’t reach an optimum level of performance unless that person is truly engaged with their position and your company.

Beyond the Onboarding development phase, engagement is just as important. As we move through our careers, our level of engagement is variable; it waxes and wanes over time. Again we may have employees that are productive, but not engaged. Development opportunities in the form of corporate learning are one tool that talent managers have to re-establish, increase, or maintain engagement throughout the talent life cycle.

Looking back at the conference, it occurs to me that I saw a lot of curriculums designed to address engagement, but the really impressive ones paid as much attention to how the curriculum was delivered as they did to the curriculums themselves. In all cases, engagement programs were not single learning events or courses, but included a series of different kinds of learning opportunities delivered over a period of time. None stated it as such, but the net effect of the approach is the creation of a robust “learning experience.”

The more advanced engagement models also took into account where the employee was in their development within the organization. New employees have very different development needs than top executives, and their motivation and engagement levels will also vary widely. While that is the common-sense practical application of different engagement models for different types of learners and content, it also aligns with commonly accepted theories of employee development stages and talent management cycles.

I’m thinking deeply on how SharePoint-based curriculum frameworks can be targeted and mapped to specific phases in career development and how that can translate into better engagement and better performance. Stay tuned.

More Thoughts on Mobile Learning

Here at Media 1, we’ve been looking at mobile for quite a few years now, and my personal experience experimenting with mobile goes back to the Palm® Pilot days. The trick with mobile has always been overcoming the hurdles associated with varying platforms, sufficient bandwidth, LMS connectivity, and being able to produce compelling content. While all of those challenges to mobile are still present, the general sense is that mobile is truly becoming more accessible.

Several viable authoring systems are now available that allow you to develop once and deliver to the vast majority of platforms, while the mobile devices themselves have larger screens and better connectivity. Many LMS now have mobile-specific connectivity, leading us to the remaining challenge of creating compelling content. Having Adobe® Flash available on almost every platform (with the exception of the iPhone) certainly helps, but much of the content I’ve seen still lacks an engagement factor. The mobile content that appears to be most successful is different in two ways:

  1. It is framed as performance support, not training.
  2. It is focused on messaging, not use of media.

When it comes to performance support, one of the best applications I’ve seen was a product-related reference guide from Sephora and JC Penney. Delivered via iPad, the content provided both product fact and application techniques for beauty products in a manner that was both educational for the consultant and shareable with the customer. While it wasn’t executed on a phone-based mobile device, I think it’s indicative of the types of mobile content that can be deployed successfully.

Absent the larger format of the iPad or Flash-based content, other successful mobile performance applications display an awareness of good writing and storytelling. People read books all the time. Books don’t have animations and rarely have pictures, yet publishing remains a multibillion dollar industry. Text is easily displayed across almost all devices. It’s logical that we re-frame our concept of what engaging mobile content is to include writing that is compelling and not just a collection of fragmented bullet points from a slide deck. Think back to the text-based discovery games of the early 90’s and how maybe some of those principles could be applied to writing for mobile.

There is also huge upside to performance support delivered via e-reader devices. Both Kindle and Nook now have educational text branches of their business focused on the education market. But for corporate practitioners, what’s not to like? Big Screens, non-fatiguing text, wireless connectivity, and falling prices for hardware make this segment one to watch.

While good writing for text-based content is critical, the untapped potential for all mobile devices is in how they can be leveraged for around-the-clock access to Social Learning communities behind the corporate firewall. Take a look at how much activity on Facebook and Twitter is now originating from mobile devices. Now imagine how much more use your corporate community could get if it was accessible from phone-based mobile devices.

I believe that eventually we will see compelling content on phone-based devices, but I also believe that tablets and e-readers represent a significant opportunity. They serve as an excellent stepping stone that can help us define and produce good mobile content without some of the constraints of the smartphone. As mobile moves forward, we also have to figure out realistic ways to allow mobile devices access to content behind the corporate firewall.

For more perspectives on mobile, check out Chris Willis’ prior post “Mobile Learning – Are You Ready?” 

Learning 2010 and DevLearn 2010: Social Learning and Communities

It’s been a busy last couple of weeks as I travelled to both Orlando for the Learning 2010 conference and to San Francisco for a portion of DevLearn. Attending sessions on Social Learning and Communities at both conferences, it wasn’t so much about learning new things as it was a confirmation of our beliefs and writings on Social Learning to date. It’s always nice to get some validation, but more importantly it’s an indicator of overall corporate readiness to adopt Social Learning principles into learning strategies.

It was also nice to see that there were quite a few companies who have chosen Microsoft SharePoint as the underlying technology for their efforts. However it was disappointing to see many of the sites shown showed little attention to aesthetics, user experience, or true collaboration. SharePoint is capable of so much more. Not only can it look great, but you can also mash-up work flows, forms, discussion, and blog elements to form a cohesive community with true collaborative functionality.

Beyond SharePoint, there were a number of key take-a-ways for those developing communities based on any technology platform. Probably the most pervasive sentiment was that communities are so much more than a collection of functionality. You can build the sexiest community site with chat integration, message boards, blogs, tagging and all the rest, but still see low usage rates if you don’t plan for more than just the functional community framework.

At some point at Learning 2010, I read an interesting tweet from a well known and respected colleague at Intel, Allison Anderson. She wondered “Why is it when we do create and open environment, we get low participation?”

Successful corporate communities have ownership, a pre-planned group of super-contributors, and are centered on functions or tasks that people want — and need — to have conversations about. Not every group within your organization needs a community, but when you plan carefully and pick the right focus areas you may hit on a community that has the potential to become self-sustaining.

Another question heard quite often at both conferences was in effect: “How do I control what people put up on the community?” The knee-jerk answer to this question is that you have to monitor it closely, but the truth is that you shouldn’t have to. People have to be allowed to have opinions, and if those opinions cross the line to misinformation or slander, then most companies already have a way with dealing with that. The point is in order for communication to open and active, there has to be trust. It can be a balance, but you have to temper trust and control.

I also overheard another comment in the crowd about how popular their community was at first, but how a year later it had virtually died out. While this person was looking for suggestions on re-energizing their community, it got me thinking about whether or not this was a bad thing. Sometimes, groups have a logical lifespan. It’s not always a bad thing when a conversation has run its course; it can mean that the topic has reached a new baseline of competence, and that has to be a good thing.

My final thought in retrospect on these two great conferences in respect to Social Learning Communities, is that we have to find a way to make our communities accessible and relevant on mobile devices. I find myself increasingly relying on my mobile device for my own social networking activities and would dare say it surpasses my desktop use by a good margin. I can’t help feeling that our busy, travelling, and multi-tasking team members feel the same way. While many social networking platforms include some mobile page support, SharePoint included, gaining secure access from a mobile device remains elusive in environments that require hardware/software security and encryption.

Looking to the future of corporate communities and social learning the potential is clearly evident. However, that potential can only be fully realized with care full attention to:

  • Design and planning for the function AND use of the community
  • Appropriate topics and focus areas
  • Trust
  • Accessibility and usability from both desk-based and mobile devices

Media 1 can help you plan and build SharePoint communities that work. For more perspective on corporate communities, check out my prior blog “Communities of Practice: Batteries Not Included”.