Course Content

 

We begin by outlining some basic design principles. Most of what we do in education with regards to media and technology can be based on the basic premises laid down in the ASSURE Model

In short, the Assure Model is:

• A procedural guide for planning and delivering instruction that integrates technology and media into the teaching process.
• A systematic approach to writing lesson plans.
• A plan used to help teachers organize instructional procedures.
• A plan used to help teachers and instructors perform an authentic assessment of student learning.
• A model that can be used for most media development.

ASSURE is a acronym:
Analyze your Users/learners
State your objectives
Select methods & media
Utilize that material
Require participation
Evaluate and revise as necessary

So, with the users in mind, let’s take a look at some quick and easy guidelines:

Design Principle #1: Focus on the users and their tasks, NOT the technology

The bottom line is that you need to analyze your users. (You should note this common theme among all the principles)

• for whom is the product being designed?
• what is the product or service for?
• what problems do the intended users have now? (what do they like and dislike about the way things work now?)
• what are the skills and knowledge of the intended users? what is their motivation?
• how do users conceptualize and work with data now?
• what are the users’ preferred ways of working?

So, with the users in mind, let’s take a look at some quick and easy guidelines:

Design Principle #2: Consider function FIRST, presentation later.

Most of us get hung up in ‘cute’ design… but function over format should be a mantra you follow:

• if you were given the task to design a site, what is the first thing you would do?
• this does not mean that you should tack user interface on at the end.
• if done correctly, functionality is built into GUI.
• developers should consider the functionality of the GUI and the overall site.
• function does not mean implementation – not how does it work but what does it do?
• 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.
• perform an objects/actions analysis.
• write task scenarios.

So, with the users in mind, let’s take a look at some quick and easy guidelines:

Design Principle #3: Conform to the USER’S VIEW of the task.

Again.. don’t let the tail (technology) wag the dog (the usefulness):

• strive for naturalness. (don’t require them to perform ‘unnatural’ acts (how many alt-tab-delete-insert-shift-buttons can you press at once?))
• “bad” vs “good” menu designs (we will discuss).
• utilize your user’s vocabulary, not yours (avid acronyms/lingo).
• differentiating between “newbies” and veterans (give them a choice).
• advantages and disadvantages of task-specific design (Adobe Photoshop is great for seasoned artists, but what if you are a newbie?)

So, with the users in mind, let’s take a look at some quick and easy guidelines:

Design Principle #4: Don’t complicate the user’s task.

Sometimes the viewing experience ruins the value being added by content being made available:

• Analogy to the regular coming into his favorite restaurant and ordering the “usual”
• Support customization
• Provide wizards
• Minimize the need for problem-solving the computer domain and its issues.

So, with the users in mind, let’s take a look at some quick and easy guidelines:

Design Principle #5: Promote learning.

Learning in this sense is learning the navigation of the site.. but it also could apply to learning content

• how difficult is the domain to learn?
• think outside in not inside out (you are close to it, you KNOW how it works.. will the user?)
• avoid ambiguity (textual and graphical (how hard are the icons to figure out?)
• Think of three words: consistency, consistency, and consistency
• evaluate your environment for risks

So, with the users in mind, let’s take a look at some quick and easy guidelines:

Design Principle #6: Deliver information, not just data.

Take a look at Shedroff’s concept of Experience Design to dig deeper on this… he differentiates among data, information, and knowledge. Dig as deep as you care to, this site will keep you thinking deeper and deeper into the concepts of design thinking…

• Successful presentations don’t simply present, they direct users towards
  important information.
• The screen belongs to the user . (i.e., it ain’t your site.. it’s theirs!)
• Preserve display inertia.

So, with the users in mind, let’s take a look at some quick and easy guidelines:

Design Principle #7: Design for Responsiveness

• Actual speed and perceived speed may not be the same thing (you only have 10 seconds to make a first impression… average time on site before users make decisions about the design/usefulness of your site).
• The easiest way to do this is to scale your images to the size you wish to display them.  In general, images should not be larger than 1200 pixels wide.
• If you are using a theme, look for a theme that works with phones, tablets, and desktops.  Designers have to think of users working on all of these devices

So, with the users in mind, let’s take a look at some quick and easy guidelines:

In Lessons-6207. Both comments and pings are currently closed.