"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
Posts
0 comments:
Post a Comment