Showing posts with label mobile. Show all posts
Showing posts with label mobile. Show all posts

Tuesday, 1 November 2011

#devlearn - How to create a successful mobile learning strategy - Clark Quinn (notes taken pm)

"what partner's do we need?"

  • Fundamental (the people you need, IT, stakeholders) (security)
  • Strategic (the people that are there to help because they make sense, vendors, politics)

 For me:

  • Those that create buyin within an organization
  • Security personal
  • IT
  • Senior team
  • Policy makers
  • Hr - for equity
  • Legal team
  • Diversity and inclusivity
  • Vendors 
  • End users (participatory designers)   
  • Support teams (anticipating problems that you can't)
  • Corporate communication

"issues you need policies to address"

  • Devices you will and wont support
  • Platforms you support
  • Viruses
  • Support provided 
  • Time when it can can't be supported
  • Service costs, data access
  • Purchasing of devices hardware, Reimbursement policies   
  • Ettiquette
  • Global issues, language, services, images   
  • Info access
  • Intillectual
  • Personal info
  • Compliance
  • Info security, authication
  • Digital rights management
  • Accessibility
  • Branding, consistency 
  • Discovery when using interal and personal devices 

W3C - has a working group for accessibility and mobile learning. Both are similar in how they work for the user. 

 

RESOURCES

  • money
  • Time
  • People, designers, developers, 
  • Content, words, audio, images, 
  • Software, compression software, tracking, LMS
  • Production 
  • Devices
  • Tracking services, software, reimbursement, time 
  • Translators
  • Testers evaluation, testing, tweaking,
  • Trainers
  • Support, users, creators, they all need tools 
  • Project management (timelines might be different, Devices change, development times)
  • Mobile enabled management 
  • Continual skilling of the team
  •  

 

 

SUPORTS NEEDED

- the performers

- the devices (how do i get it, it broke, software not working,) make it look like stuff they already know.

- the team.   

 

GOVERANCE

  • templates
  • Standardized - quicker to migrate from area to area 
  • Product life cycle - off the market as well as archiving requirements
  • Training cycles earlier than later 
  • Metrics, evaluation standards 
  • Yearly updating
  • Regional updating 
  • Unionized vs non
  • Corp and biz sign off
  • Solution governance 
  • Blends
  • Schedule alignment
  • Go/no go 

WHAT DO WE MEASURE

  • Bandwidth limits
  • Time saving (learning, developing, designing)
  • Accessing the tool
  • Measure the experience, do they go back once because it's good, or bad
  • Is there a difference between one device and other 
  • Mobile environment itself, is it meeting the needs. Are people accessing because it is easy or are they jumping to the paper version
  • Is the user getting the info they want.  How much do they need?
  • Measuring the deployment of the device
  • Unique users
  • Are they using it vs changing performance
  • If they are creating their own job aids (something's not working well)
  • Impact of training should go up
  • Completion rates - yes and ... some mobile is only for on the fly training  

 Anything you do develop,....

Ou should have a measure to say YES LET'S KEEP IT, NOT QUITE WORKING TWEAK IT, KILL THE PROJECT. 

 

The percentage where you go or stay with projects should changes as you go along as well to the point you either keep or kill. 

 

BARRIERS

From Elearning Guild report. (biggest to least)

  • Integrating with enterprise tools
  • Security
  • Lack of standard
  • Content for other devices does not translate
  • Cost
  • Bandwidth
  • Management resists
  • Screens to small

Culture eats strategy for breakfast. You need a culture that is experimental, innovative,and want to try and grow. 

 

HBR article. March 2008 by Garvin, Edmunsin, & Gino

 

Custom content delivered to be specific to where you are and what you are doing. This will be where we will and should be going. Example Yelp restaurant discovery app. (augmenting reality + learning).   

   

Mobile in the workplace should not only be about training. It should be about:

 

Some mobile solutions might be more about connecting you to the people you need to speak to to work in complex problems and solutions. Formal solutions. Performance support. 

 

  


Sent from my iPad

#DevLearn - How to create a mobile learning strategy - Clark Quinn (notes from am session)

Continual innovations is the way that organizations are going to be able to change and move forward. 

Mobile is only one part of moving forward. 

There aren't lots of strategies out there to do this, but it is being discovered and there are elements that need to be encompassed. 

Internet time alliance. - great resource for social learning. 

Look to "mobile learning: landscape and trends" - Elearning Guild

 

MOBILE BACKGROUND

 Palm pilot was one of the first real successful device - pseudo recognized hand writing 

  • 4 core apps , memo, calendars, tasks, address book
  • It synced 
  • Designinglearning.com - zen of palm 
  • Accessed many times a day but on for short periods of time
  • Laptop may not be mobile because it doesn't quite fit in a pocket or purse, needs long life battery use, you don't use it for long periods of time. 
  • Laptop doesn't do something unique to the location you are using it in. 

Differentabf mobile tools have different affordances. The devices needed sometimes dependsbb mL

 on the co text in which it is being used. 

We use devices. For getting content, computing, capturing, communicating. 

Companies maybe be blocking social networks, but staff are finding work abounds with their own devices. 

Methods of disseminating info:

           Learning            performance support          context       

SMS

Voice

Audio

Video

Doc

Interactive 

 

Content specific -  we might know where and when you are, so we can push out the need info to you for the situation you are in racers

Knowledge dump and test does not get people learning. 

Putting them in the situation where they have to practice what uou want the  to learn is a better format. 

Mlearning

Biggest improvement from use (most to least) 

  • Increase learner access and availability
  • Accomodate learner needs
  • Increased speed of content delivery
  • Improver learner performance
  • Reduce costs 

 72% of the workforce is a mobile worker. (those that don't sit at a desk or on a line "all day"). These are the people that can benefit from mobile learning. 

Innovation comes from people working together and work comes from conversations g

 We want our performers to have the tools they need when and where they are.  

 

STRATEGY

 "What is a strategy?"

Who are we going to involve 

Define steps

Milestones

Means to get to targets

Who is involved

Resources including proper skills needed

Measurement

Vision of what you want to accomplish

You may need to be ready to be to change it at anytime

Feedback loop for reassessment

Plans for action and reaction

Methods, tools, content to move forward on steps 

Objectives  

Tactics

Messaging needs to be in place to get buyin

 


 

"what is different for mobile strategy"

What is users comfort level

More flexible, it's a new world

Company's culture and adoption to mobile learning

 

Mobile should be something that improves performance learning or skill set. 

 

  • GOALS augumenting org strategy unit goals
  • TACTICS Augmenting formal performance support  context sensitive
  • RESOURCES Devices, tools, infrastructure, designers, developers
  • SKILLING Tools, designers. Developers, managers
  • MESSAGING Advantages, issues
  • PARTNERS IT, Hr, vendors, ?

METRICS Access, unique contribution  

Make IT your friends they work hard to keep they network safe, but they do need to move with the times

 

WHAT'S THE PROCESS

Where do they desire to go?

Staff and mgmt

Analysis

Surveys

Plans

Marketing - describing advantages 

Measuring

 

  • Needs, problem analysis 
  • Surveying and data collection (what do people already have, tools. What are their experiences and preferences with using them). Is anyone doing any currenty with them. What tasks are they already doing on them?  What effiecienciens do we want to improve.  Are there costs we can cut back on going with this.  
  • Business case 
  • Metrics
  • Sr sponsorship
  • User involvement (plan, pilot, evaluating) 
  • Goals
  • Plan
  • Train trainers
  • Pilot 
  • Evaluate
  • Train
  • Execute
  • Evaluate
  • Remember to be fluid to make changes if needed

"what info do you need to gather"

  • Infrastucture support for one building many countries
  • Knowledge level of users, competencies
  • Who has what already
  • Motivation level
  • Is corporate culture equal enough to push through the entire plan
  • How many languages do you need to broadcast in (4, 10, 25)
  • Pictures appropriate for everyone every country
  • Tools that they have comfortable with
  • What platform will be used
  • Metric requirements
  • People profile (skill, education level) 
  • Organizational strategy
  • Special tech requirements 
  • What's going on else where
  • Legacy training (impact)
  • Cost, business case - but for later
  • Legal concerns
  • Gap between where you are and want to be

 

"What components should the strategy specify?"

 

  • Policies to guide people
  • Other existing plans
  • Timeline, schedule
  • Stakeholders, partners
  • Evaluations
  • We want a plan that is adaptable for anything. But then is flexible too  
  • Governance - scrutiny, have everyone on board, self oversight, continually overseeing what you are doing and make sure you are hitting your overall goal, 
  • Resources include do we even know how to doe what we want to do.   

Sent from my iPad