The Importance of Using a Process for Mobile Learning Design

1,423 views
1,347 views

Published on

A presentation on the benefits and basic steps that should be in a design phase for a mobile learning project.

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,423
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

The Importance of Using a Process for Mobile Learning Design

  1. 1. Process How do we go about this, anyway?
  2. 2. Describe your process • Strategy • Design • Develop • Deliver
  3. 3. Float uses our S3D process • Strategy • Design • Develop • Deliver
  4. 4. What does the process do? • It’s replicable • It’s predictable • It’s measurable • It’s cost effective
  5. 5. Process Overview • Not ADDIE (though, I have nothing against ADDIE in particular) • It’s agile • It’s flexible • It’s cost effective
  6. 6. Is your current prreplicableocess is • Too many steps • Too many deliverables • Too many stakeholders • Too many sightseers • Too lengthy
  7. 7. • Clear high-level goals and direction • Refined process • Solid learning objectives with stakeholder buy- in • Organized content  • Storyboards and templates • Current development tools/software • Talented well trained team of designers and developers Rapid development strategies
  8. 8. • Demographics • Goals • Tasks • Device Specifics • Connectivity • Tech Familiarity • More? Use cases/user stories
  9. 9. Use them! A scene from a Yahoo! Session
  10. 10. Craft Use Cases http://www.alistapart.com/articles/tamingscope/
  11. 11. • Start Analog! • Understand the scope • Ask some tough questions • Not artistic, specific! Sketches
  12. 12. Storyboards
  13. 13. Wireframes
  14. 14. • The “feel” of the app • The brand distilled into colors, shapes, textures • Not a design, but rather design elements • Quick to put together Moodboards
  15. 15. • Be careful not to incur design debt • Know your HIG! • Go as close to native as possible • 2-3 revisions, max Mockups
  16. 16. • Moving from mock to life! • So rewarding • Get buy in ASAP • Circulate and socialize Prototypes
  17. 17. • Best Practices • Create for each step in the process: Storyboards, Wireframes, etc. • Style Guides  • Core graphics Templates
  18. 18. • Approach with caution • Now is the time for a requirements analysis • Have a frank discussion with your vendor - what’s up with their mobile strategy? • Maybe time to get off the upgrade train? Rapid Tools
  19. 19. Q&A?

×