Rocky Mountain STC: Best practices when creating interactive video tutorials

R ock y M ounta in STC S ess ion

B er nard Aschwanden

w w w.publ ish ingsmar ter.com

ber nard@publ ish ingsmar ter.com

Best Practices when Creating Interactive Video Tutorials

11:55

1

@publishsmarter

About this session

11:55 @publishsmarter

A picture is worth 1000 words, how many is video worth?

In this session we address how to: Develop a storyboard

Review a support topic

Create a related video

Help users visualize how to perform the task

Doing this helps your audience SEE how to resolve issues before they become problems

2

Housekeeping and note taking


Not all slides or topics are equally weighted

Use some, discard others

Slides speed varies (reference)

Questions? Ask any time!

em

3

About your speaker


Publishing Smarter: President

Content strategist, publishing technologies expert, author, and geek-enough

Certified Technical Trainer DITA

Content management

Topic-based writing

Society for Technical Communications Vice President

Associate Fellow

4

Standard disclaimer


In the interest of brevity I will make some blanket statements to keep it simple

Purists may complain

And they are wrong!

(except when they are right)

5

what goes into a s tor yboard

11:55

6

Storyboarding

@publishsmarter

Purpose of a storyboard

11:55

Explains each screen in a course

Details each screen, what the reader will see/do

Helps the reader ID course content, media, interactions before development Could be SME

Could be the client

Could be a stakeholder in the training

Guides all members on a team

Provides a source that all people can refer to during dev

Helps define the audience (crucial)

7

@publishsmarter

When to create a storyboard

11:55

After a plan has been developed and approved

Before any video is built

May not be needed in all contexts

Consider the complexity of what is being created

8

@publishsmarter

Reasons you need to put the time in

11:55

Saves time/cost in the long run

ID roles and responsibilities Graphic designer creates look/feel

Illustrator builds images

Narrator provides audio overlay

Programmer builds interactions

SME/Client approve content

Sets initial expectations, define how course looks/acts

QA tool: Compare the final course with the storyboard

9

@publishsmarter

Elements of a good storyboard

11:55

Project and slide info

Visual/video elements (graphics, callouts, citations)

Text elements (on screen text)

Audio elements (heard as the screen displays)

Interactions/navigation for users (what to click, where)

Branching (where next, options, flowchart)

Overall learning objectives

10

@publishsmarter

Minimum requirements likely include

11:55

Screen number/label/identifier

i.e. DITA-FM-01-23

Course name

Module name

Lesson name

Slide title

i.e. Basics of a DITAmap

Visual components

On screen text

Audio info

Both narrator and effects

Interactions info

Branching info

11

@publishsmarter

Audio tips

11:55

Include slide by slide script

Could have sound effect or music info (be careful)

Sound out tough words or initialism and acronym info

DITA is did-uh, and not as dee-ta

SME is pronounce smee, not spelled out Es, Em, Ee.

WYSIWYG is wizzy wig

12

@publishsmarter

Graphics tips

11:55

Used to provide ideas to a media team

Provide a description of the screen

May include simple sketches, or text notes

If video is needed, include notes and a link if possible

13

@publishsmarter

Text tips

11:55

Provide exact screen content

With audio: Include supporting text for the narrator (notes about tone for example)

No audio: consider if more text is required

14

@publishsmarter

Navigation and interactivity

11:55

Include info for every screen

Answer developer questions about course building

These may include:

Options a learner can take

Requirements that must be followed

Logical progression (what is next)

15

@publishsmarter

Common storyboard formats/design

11:55

Good for SMEs who like the details outlined

Common format: Tables (Word or Excel)

16

ID and topic

Learning objective

Narrator On screen content

Notes

10-11 DITAmap

Basic familiarity with the look and function of a DITAmap, able to

The DITA map is a document that can be compared to a table of contents, or a document plan. ..

Sample DITAmap with basic content, plus sample as code.

Talk to SME to get sample as visual map and as code.

10-12 reltable

Basics of a reltable with concept, task, reference content.

The reltable, or relationship table is used to define related topics in columns

Sample reltable with basic content, plus sample as code.

Talk to SME to get sample as visual table and as code.

@publishsmarter

Common storyboard formats/design

11:55

Good for SMEs who are visually driven

Common format: PowerPoint

Visual format with slideshows or outlines

Provides similar information, but may be visual rich

Ensure you also use the slide notes if working with a tool like PowerPoint

Samples on next screens

17

@publishsmarter

10-11: Basics of a DITAmap

11:55

Learning objective:

Basic familiarity with the look and function of a DITAmap, able to ID components of a map

Narrator/Audio

The DITA map is an XML document that can be compared to a TOC or...

Notes

Talk to SME to get sample as visual map and as code.

<?xml version="1.0"?> <!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd"> <map id="map_5D33A666A75E4B239F468C70A409CFAF" title="Working with Files"> <topicref format="dita" href="c_PrintingFiles.xml" navtitle="What is printing" type="concept"/> <topicref format="dita" href="c_SharingFiles.xml" navtitle="What is file sharing" type="concept"/> <topicref format="dita" href="c_SavingFiles.xml" navtitle="Why save files" type="concept"/> </map>

18

Screen notes

◦ Ensure the user clicks the

@publishsmarter

Tips and tricks for storyboarding

11:55

Know your audience and their needs

Know the delivery platform (web, CBT, print, mix)

Chunk the info to manageable parts

Include detailed audio and visual info

Ensure storyboard agreement before work begins

Include info about full motion recording, if needed Avoid it if you can, adds overhead (size, control, edit restrictions)

Minimal amounts, planned, might be acceptable

19

@publishsmarter

Sample: Storyboard to change a password


Consider what goes into changing a password

This is a sample only

A very brief example of things that may be in a storyboard

20

11:55 @publishsmarter 21






G ett ing a tool to make the job of implement ing a stor yboard easy

11:55

27

The right software

@publishsmarter

11:55

Everything eLearning. One complete tool.

Easily author virtually any kind of responsive interactive eLearning content. Create HD product demos, application simulations, soft-skills and compliance training materials, live and self-paced online courses, self-service videos, employee on-boarding modules, and more. Meet varied eLearning needs of users with the tool that has long been trusted by more than 80% of Fortune 500 companies to create compelling eLearning content.

28

@publishsmarter

My definition

11:55

There are many tools that build interactive content

The reason I pick Adobe Captivate is that it exceeds my expectation on what needs to be done In the context of technical communication

A tool to create video based training

An environment to create tests in

A system to create content for clients

To do this well though is a lot of work

Adobe has delivered this for years

29

@publishsmarter

Get the tools

11:55

http://www.adobe.com/products/captivate

Follow the links to the download

Create an Adobe ID (if needed)

Download, install, launch, test, purchase

more inclusive FrameMaker, RoboHelp, Illustrator, Acrobat

And, of course, Captivate

30

@publishsmarter

http://www.adobe.com/products/captivate

c re ate a v i d e o to ex p l a i n h ow t h i n g s a re d o n e

w r i t e a b u n c h o f s t u f f

@publishsmarter 11:55

31

Review a task to document

Use software you are familiar with

Find a simple task to perform Use paragraph tags in Adobe FrameMaker

Capture/crop an image with Adobe Photoshop

Compile a help project in Adobe RoboHelp

Create a table in Word

Restart a game of cards on your computer

Navigate your company site

Storyboard how the task will unfold

11:55

32

Considerations

@publishsmarter

Video goal


Teach users how to create a basic file New, based on a template

Using the Equity Letter

Create a document, then close w/o saving

Goal is to show how templates impact new documents

Under 1 minute or so of video

33

May be based on existing task documents


Create a document based on a template New files can be created based on predefined standards.

1. Click the Office Button, then select New

2. Under Template, select Installed Templates

3. Select Equity Letter

4. Click Create

34

Considerat ions for bui ld ing eLear ning content

11:55

35

Create your first tutorial

@publishsmarter

Before recording

11:55

Take notes or outline (storyboard if you can)

Plan your steps

Work through the process

Configure screen resolution

Hide unneeded parts (e.g.: the Windows Taskbar)

36

@publishsmarter

While recording

11:55

Add extra slides as you go (easy to delete)

Mistakes happen

Add to your notes as you record

This can ALL be adjusted post recording (if you have good software,

37

@publishsmarter

Post-recording


Add transition slides if needed With repeated process: cut back on slides

Use to combine major ideas if applicable

Add markup to materials Text Caption, Rollover, Click Box, and Zoom Area

Add temporary slide number if location is unclear

38

Other considerations


If you type, steady speed

Review all background elements

Get a quality microphone

Mix audio/text for those

Save often, and save backups if needed

39

Avoid


Add audio independent of the actions (do the task first)

Keep it short, 2 to 3 minutes of video, not 10 to 15

cuz

Only add background music if truly needed Client requests

Cover other audio issues

Keep effects simple

40

More to avoid


Avoid uncontrolled environments (especially for audio)

Close messenger, email, etc.

Take time on the recording

If publishing to YouTube upload once, so get it right

Keep the interface tidy

Remember to save often

41

D emo of the ideas d iscussed


42

Putting it into practice

Assumptions

11:55

Our Adobe Captivate version may differ

If your version is different, the process may change

Recording of use of Microsoft Word Simple application demo

Can show many ideas

Video is for internal use (so no specific setup for YouTube, screen configurations, etc.)

43

@publishsmarter

Create a storyboard


The goal here is to showcase Adobe Captivate

Of course, YOU can consider what the storyboard may look like though

If you REALLY want to test yourself, develop a storyboard

44

Perform a trial run first, test the interface

11:55

Launch Word, and size as needed

Perform actions Office Button > New

(or, in older versions, File > New)

Under Template, select Installed Templates

Select Equity Letter, then Create

Office Button > Close (or, in older versions, File > Close)

Do not save

45

@publishsmarter

Repeat actions, find changed behaviour

11:55

Office Button > New (or, in older versions, File > New)




Do not save

This process gives you the chance to see what happens on screen as you perform standard actions.

46

@publishsmarter

Record your first video


1. Launch Captivate (firewall?)

2. Under New > Software Simulation, Create

3. Under Size, select Screen Area (Full Screen of Monitor 1)

4. Under Recording Type, select Automatic, and Demo, Assessment, and Training if required (only using Demo, but cool to do all three)

5. Adjust Settings, if needed.

6. Do not pan, no narration needed

7. Click Record, then wait 3 seconds

47

Perform your actions

11:55

Office Button > New (or, in older versions, File > New)




Do not save

Press End (on kbd) when done recording

48

@publishsmarter

Edit your materials

11:55

When done Captivate is ready

File > Save As in case of a crash

Review the slides, and watch performances

Press F10 to view from current to next 5

Review a few times to make sure the right ideas have been captured

49

@publishsmarter

When done

11:55

Record your audio

Add effects if required

Add interactions (such as instruction and click boxes)

The order of those may switch

50

@publishsmarter

Share the finished product


Select File > Publish

Set output options

Create and share

Publish to help repository

Import and include in FrameMaker/PDF content

Add to RoboHelp

Without interactions put it on YouTube

51

Ideas and samples of f in ished content for onl ine and PDF/pr int

11:55

52

Deliver the content

@publishsmarter

Case study example

11:55

Adobe creates and delivers the TCS software suite

Content (text) in the guide is written in FrameMaker

Video is created in Captivate

Content is converted to PDF from within FrameMaker

Content is converted to online formats using RoboHelp

All content delivered to all channels in all formats

53

@publishsmarter

Summing up the d iscuss ion, and opt ions to cont inue i t .


54

Conclusion and contact

About this session


A picture is worth 1000 words, how many is video worth?

In this session we address how to: Develop a storyboard

Review a support topic

Create a related video

Help users visualize how to perform the task

Doing this can help your audience SEE how to resolve issues before they become problems

55

Services


56

Follow up contact information


57

905 833 8448 (Eastern Time)

[email protected]

www.linkedin.com/in/bernardaschwanden

@publishsmarter or @aschwanden4stc

www.publishingsmarter.com

Business

Rocky Mountain STC: Best practices when creating interactive video tutorials