Guide to Designing and Developing an e-Learning Project

Dave GoodmanSoftAssist, Inc.

Information to be CoveredInformation to be Covered

This presentation was designed to inform you about:

Pre-Course DocumentsThe official documents representing the preliminary stages of a project

and the contract.

Getting StartedA review of our course development process.

Developing Your ContentA guide to defining your message, your audience and the goals for your course. Additionally, how to best prepare your content to ensure

success.

Expectations and TimelinesSharing expectations ensures the development of a successful course. This section reviews what you can expect from course development at

various phases including the division of responsibilities, both client-side and vendor-side.

Pre-Course DocumentsPre-Course Documents

In this section we’ll discuss the following preliminary documents used to prepare our team and your team to begin a new e-learning course:

Request for Proposal (RFP)

Statement of Work (SOW)

Contract Approval Process

Request for Proposal (RFP)Request for Proposal (RFP)An RFP informs vendors, like SoftAssist, of your e-Learning needs.

The RFP should include:Learning objectives of the potential course

A proposed project delivery date

Technical requirements, e.g. bandwidth, security, use of media, etc.

Measurement and success factors

Assessment expectations

Internal review and focus group process

In the preliminary phase of negotiations SoftAssist will respond to an RFP with our Statement of Work (SOW).

Statement of Work (SOW)Statement of Work (SOW)The Statement of Work will provide you with our views, our instructional approach and some recommendations on the project.

Based on the information provided in the RFP, SoftAssist will map out our approach to the solution for your consideration.

This detailed description can also include:References available to the client

Answers to any specific questions from the RFP

Similar project or experiences in our portfolio

Samples of work

Instructional approaches to the project

Completed ContractCompleted ContractDetermine if a Confidentiality Agreement and W9 are required.

After negotiations have been completed on both sides, a contract reflecting all parties decisions must be drafted and signed.

The agreed-upon terms are likely to include:Invoicing schedule

Timetable for deliverables

Review cycle stipulations

Scope review

After this step is complete, the kick-off meetings can begin.

Getting StartedGetting StartedIn this section we’ll review the following topics needed to understand your e-Learning project:

Course level breakdown, e.g., low, medium or high level of interactions, use of media, performance testing, etc.

Our Course Development Process

Instructional Design Approaches

Client Requirements

Review and Success Criteria

Project OverviewProject OverviewThese are the steps in SoftAssist’s design process:

Developing your contentDeveloping your content

In this section we’ll discuss how content may be developed including:

Defining your message.

Defining your audience.

Defining your goals and metrics for success.

Readiness of Existing Content

Reusing content or creating new content

Shared Lessons Learned

What is your message?What is your message?Before starting the development of the course, the content needs to be finalized as much as possible. Below are some pointers on how content is written for maximum effectiveness.

It is important to have a good grasp of the concepts and information that is most important for the learner.

Know why the training is being conducted. What behaviors or changes should be anticipated as a result of the training content?

In some cases, SoftAssist is asked to convert instructor-led courses to web-based-training (WBT). By collaborating with Subject Matter Experts (SMEs) we can ensure the context of the content is maintained.

Always be sure to communicate any expectations or ideas about the course to your instructional design team. This way, issues can be addressed and discussed according to scope and timeline in the beginning.

Who is your audience?Who is your audience?

In conjunction with preparing your course content efficiently, it is important to understand the possible audiences who will participate in the training.

Every audience has different needs and expectations.

Knowing about the audience composition will significantly affect the instructional designer’s job.

Knowing about the audience will also assist in designing the proper assessments and related measurements.

The client will determine if the course is “open” (go through the course in any manner) or prescriptive (the learner starts at Chapter 1 and proceeds). Each audience will approach learning differently.

Defining your GoalsDefining your GoalsConsider the following questions:

What are your goals for this course?

What are your goals for your learners?

What are the learners’ goals?

What makes your course a success?

What will success look like six months later?

What are the corporate and stakeholders goals?

What might hinder reaching the goals?

Defining your Goals Defining your Goals Sometimes, a new learning project is needed to correct a business issue, a process gone wrong or a behavior requiring correction.

Is your learning project providing information or is the intent to make a change or improve performance?

Is this a local, national or global learning program?

What position does diversity, inclusion, language, generation and education level play?

Defining your MetricsDefining your MetricsConsider the following questions:

What are you measuring?

What are you seeking to improve, reduce or eliminate?

When will you know that the training was successful?

Do you have the data to support your efforts?

Communicate your success and do not be afraid if your successwas less than expected.

Immediately plan and execute your next phase.

Expectations and timelinesExpectations and timelines

In this section we’ll discuss the following:

Expectation Guide & Division of Responsibilities

Where are we in the timeline?

What does SoftAssist need from you at this time? What do you expect from SoftAssist?

How do we both prevent or manage possible project issues?

Where do we go from here?

Internal Kick-OffInternal Kick-OffThe internal kick-off meeting occurs after our client kick-off meeting.

This meeting allows our team to inform each other about the project specifications and to begin the collaboration process in preparation of the design phase.

What we need from you at this point:Course Content (unless we are writing)Technical RequirementsSpecific media requestsGeneral expectations for the course based on past conversations

Estimated time to complete: 1 day

Graphic User Interface (GUI)Graphic User Interface (GUI)The design of your course’s Graphic User Interface (GUI) occurs at the fore-front of course development.

The GUI sets the tone of the course design and is often used to showcase company colors and branding information.

Based on preferences provided by you and your team and the level of your course, our graphic designer will create at least two alternative designs.

GUIs include the course navigation and the bordering information of the course display, the content layout area, assessment screens, etc.

The process of designing a GUI ends with a sign-off form which allows us to move forward to the storyboarding phase of course development.

Estimated time to complete: 1 week

GUI Design

This is a GUIThis is a GUI

StoryboardStoryboard

Storyboarding is Soft Assist's way of designing your content into a course. This process includes direct communication between your company’s Subject Matter Expert (SME) and the lead instructional designer assigned to your project.

Through the placement of content, interactive elements, graphics, video, audio and testing features, the instructional designer will manipulate the content until it is ready to be developed into a course.

Before sending you the storyboards for review, SoftAssist will complete a quality assurance/proofreading session to ensure that errors are at a minimum.

This step ends with a review and sign-off of the course storyboards.

This step will be completed with a weekly “rolling-review”.

Estimated time to complete: 3 weeks

GUI Design

One Version of a StoryboardOne Version of a Storyboard

Prototype DevelopmentPrototype DevelopmentBelow are some common Q&A’s associated with Prototype Development:

What can I expect in the prototype?

The prototype is meant to give you a taste of the course. It should set an accurate tone for the remainder of the course so that, when we continue with development, we are aware of how to direct the course accordingly.

Can I expect this version to be final?

The prototype is the initial deliverable. Revisions are expected and are built into the project plan.

Your focus should be on the style, level of instructional design, correct message and “navigation” – is the course easy to use.

GUI Design

Prototype Development (cont’d)Prototype Development (cont’d)What does the timeline look like from here?

The prototype takes about 1 – 2 weeks to complete. After receiving feedback and sign-off , we incorporate the changes and move into the development phase. A “BETA” will be the next deliverable.

Any “out of scope” issues or significant changes from the Statement of Work will be discussed.

How do we communicate with each other?

Client changes are captured in a document and tracked online. The client has access to this process. Telephone calls, weekly online sessions or onsite visits promote our communications.

Estimated time to complete Prototype: 3 weeks (including 1 week for client review)

BETA DevelopmentBETA DevelopmentBelow are some common Q&A’s associated with BETA Development:

What can I expect in the BETA?

The BETA consists of the prototype development with your revisions and

the remainder of the course (revisions and communications along the way).

The BETA should accurately reflect your vision for the course according to previous communications between you and your instructional design team.

Can I expect this version to be final?

A more thorough round of Quality Assurance checks have been completed at this point in time. If any errors are found, they will be corrected. The final course will be error free. The client has a 90 day warranty period.

GUI Design

BETA Development (cont’d)BETA Development (cont’d)What does the timeline look like from here?

After receiving feedback and sign-off we will implement the changes while comparing the requests to the initial scope of the project.

As we implement the changes and edits to the BETA we’ll also be finalizing the course.

How do I deliver feedback to SoftAssist?

The feedback from your BETA review should mirror that of the prototype review, e.g., written document, weekly review, online tracking, etc.

Feedback along the way should come from a single, client source.

Feedback should always be specified according to module number, page number and issue. We will provide you with a template to make the reporting easier.

Estimated time to complete BETA: 5 - 7 weeks (Including 1 week for review)

Final Course DeliveryFinal Course Delivery

Below are some common Q&A’s associated with Final Course Delivery:

How does the final delivery take place?

The final delivery of the course will occur after all quality assurance checks have been completed and after all revisions have been incorporated from the BETA review.

SCORM and learning management system (LMS) testing and course loading will be provided. The course can be loaded onto your organization’s LMS (if applicable) or delivered according to the agreed upon methods.

GUI Design

Final Course DeliveryFinal Course Delivery

Below are some common Q&A’s associated with Final Course Delivery:

Can I still contact SoftAssist with any questions after my course has been turned over and completed?

Yes, of course! SoftAssist is here to help you with any questions or issues you might have throughout the development of your course. We also understand that additional questions might pop-up after the course has been turned over.

Contact our lead Instructional Designer or Developer with your questions. We do not exit a project until you are satisfied and have authorized the project as complete.

GUI Design

Lessons LearnedLessons LearnedThrough our experiences we’ve learned that projects are less successful as a result of the following factors:

Goals/Objectives weren’t clearly defined at the onset of the project

Client time commitments and expectations may not be accurate

Poor planning, travel schedules, multiple reviewers create delays

Access to subject matter experts is limited

Lack of open communication

Lack of cooperation from other facets of a client’s organization

Design creep – permitting continual changes to occur

Extending the project beyond the schedule decreases engagement

Misunderstandings about “out of scope”

Making a change to the project lead during the project

Managing a project by a committee

ContactContact

Dave Goodman

SoftAssist, Inc.

1150 First Avenue

Suite 960

King of Prussia, Pa. 19406

610.265.8484 Ext. 14 dgood@softassist.com