In short, the Assure Model is:<\/p>\n
- \n
- A procedural guide for planning and delivering instruction that integrates technology and media into the teaching process.<\/li>\n
- A systematic approach to writing lesson plans.<\/li>\n
- A plan used to help teachers organize instructional procedures.<\/li>\n
- A plan used to help teachers and instructors perform an authentic assessment of student learning.<\/li>\n
- A model that can be used for most media development.<\/li>\n<\/ul>\n
ASSURE is a acronym:
\nA<\/span>nalyze<\/u> your Users\/learners
\nS<\/span>tate<\/u> your objectives
\nS<\/span>elect<\/u> methods & media
\nU<\/span>tilize<\/u> that material
\nR<\/span>equire<\/u> participation
\nE<\/span>valuate<\/u> and revise as necessary<\/p>\nSo, with the users in mind, let’s take a look at some quick and easy guidelines:<\/h3>\n
<\/div>\nDesign Principle #1: Focus on the users and their tasks, NOT the technology<\/h2>\n
The bottom line is that you need to analyze your users. (You should note this common theme among all the principles)<\/p>\n
- \n
- for whom is the product being designed?<\/li>\n
- what is the product or service for?<\/li>\n
- what problems do the intended users have now? (what do they like and dislike about the way things work now?)<\/li>\n
- what are the skills and knowledge of the intended users? what is their motivation?<\/li>\n
- how do users conceptualize and work with data now?<\/li>\n
- what are the users’ preferred ways of working?<\/li>\n<\/ul>\n
So, with the users in mind, let’s take a look at some quick and easy guidelines:<\/h3>\n
<\/div>\nDesign Principle #2: Consider function FIRST, presentation later.<\/h2>\n
Most of us get hung up in ‘cute’ design… but function over format should be a mantra you follow:<\/p>\n
- \n
- if you were given the task to design a site, what is the first thing you would do?<\/li>\n
- this does not mean that you should tack user interface on at the end.<\/li>\n
- if done correctly, functionality is built into GUI.<\/li>\n
- developers should consider the functionality of the GUI and the overall site.<\/li>\n
- function does not mean implementation – not how does it work but what does it do?<\/li>\n
- develop a conceptual model (this is really what Project #1 is all about). What is different is that we will also pre-produce a scale of the user interface also.<\/li>\n
- perform an objects\/actions analysis.<\/li>\n
- write task scenarios.<\/li>\n<\/ul>\n
So, with the users in mind, let’s take a look at some quick and easy guidelines:<\/h3>\n
Go to top<\/a><\/div>\nDesign Principle #3: Conform to the USER’S VIEW of the task.<\/h2>\n
Again.. don’t let the tail (technology) wag the dog (the usefulness):<\/p>\n
- \n
- strive for naturalness. (don’t require them to perform ‘unnatural’ acts (how many alt-tab-delete-insert-shift-buttons can you press at once?))<\/li>\n
- “bad” vs “good” menu designs (we will discuss).<\/li>\n
- utilize your user’s vocabulary, not yours (avid acronyms\/lingo).<\/li>\n
- differentiating between “newbies” and veterans (give them a choice).<\/li>\n
- advantages and disadvantages of task-specific design (Adobe Photoshop is great for seasoned artists, but what if you are a newbie?)<\/li>\n<\/ul>\n
So, with the users in mind, let’s take a look at some quick and easy guidelines:<\/h3>\n
<\/div>\nDesign Principle #4: Don’t complicate the user’s task.<\/h2>\n
Sometimes the viewing experience ruins the value being added by content being made available:<\/p>\n
- \n
- Analogy to the regular coming into his favorite restaurant and ordering the “usual”<\/li>\n
- Support customization<\/li>\n
- Provide wizards<\/li>\n
- Minimize the need for problem-solving the computer domain and its issues.<\/li>\n<\/ul>\n
So, with the users in mind, let’s take a look at some quick and easy guidelines:<\/h3>\n
<\/div>\nDesign Principle #5: Promote learning.<\/h2>\n
Learning in this sense is learning the navigation of the site.. but it also could apply to learning content<\/p>\n
- \n
- how difficult is the domain to learn?<\/li>\n
- think outside in not inside out (you are close to it, you KNOW how it works.. will the user?)<\/li>\n
- avoid ambiguity (textual and graphical (how hard are the icons to figure out?)<\/li>\n
- Think of three words: consistency, consistency, and consistency<\/li>\n
- evaluate your environment for risks<\/li>\n<\/ul>\n
So, with the users in mind, let’s take a look at some quick and easy guidelines:<\/h3>\n
<\/div>\nDesign Principle #6: Deliver information, not just data.<\/h2>\n
![\"\"](\"\/wp-content\/uploads\/2012\/05\/dothis.gif\")
<\/a><\/p>\n