Various document types, including .pdf, .docx, .xlsx, .pptx, and more, can be attached!

Include documents requiring signatures, content overview files, and optional (but recommended) reference materials in your courses.

It is best used for reference materials as it will always be a non-graded Step.

Documents requiring review and signatures can be paired with Human Steps to seamlessly integrate and acquire the required signed paperwork with your curriculum.

Use attachments at the beginning of a course as a "preview" of what's to come and follow it with other step types.

Add Attachment Steps to the end of a course as supplemental review materials.

Include additional "good to know" attachments to courses as optional reading materials.

Min 4 words/answers recommended per round

System limit - 14 characters

Use single words when able

Omit spaces for multiple-word answers

All words should be lowercase

Clues should be specific and clear (avoid obscure/vague references)

Make it count - it's the only hint the learners will get!

Keep rounds themed, with each word and hint representing that theme

No written correct/incorrect feedback is provided

Visual cues are used when answers are submitted; grid will turn green or red depending on which answers are correct

Words must have at least one letter of another word for the round to intersect them in the grid (e.g., if a round consists of two words, "hello" and "just", it's impossible to create an intersecting grid as neither of them share a letter to cross with)

For context, you should use images containing the entire screen. If you only show users a portion of the screen, they might need help finding it on the actual property when they try it out.

Should be the same width throughout the Demo (e.g., ensure the browser window is sized the same for all screenshots taken)

Recommended 1024 pixels width for desktop simulations

Recommended ~340 pixels width for mobile simulations

Crop/edit out "revolving" images in screenshots (e.g., mobile battery, clock)

For any sensitive information (such as account numbers), omit/blur accordingly

Images must be in .jpg format; can also accept .png and .gif formats

Screen name - 32 characters

Image Description - 255 characters

Guiding/action text - 255 characters

Each stage must always include at least one hotspot

Don't be afraid to have more than one hot spot within a single-stage image

Hot spots should be precise - try to avoid excess buffer space when possible

Keep Guiding/action text concise; use the Learn More option to include additional information for specific hot spots

Establish your Demo's flow overview before getting screenshots for the best results

Take a screenshot of every action completed (before and after you tick a checkbox, open a drop-down menu, etc.). Approach these as though the learner can only learn through visuals with zero verbal/text explanation

Use one Demo Step to show how to complete one task (consider creating multiple steps, depending on how complicated the task is)

Always use images from the latest version of the app or website

You can use the same image in multiple demos, such as a website's homepage

Remember to include a Screen Name for each image!

Incorporate live classroom events into your virtual learning platform

Document learning events by having a mentor confirm the learner's attendance and/or including a grade issued by the mentor

Learners can see each mentor’s email address for all meeting options (as entered in LemonadeLXP)

Inform mentors of their role before the Step is published (additionally, write a note to the mentor in the Step to explain/remind them what their part is)

Note that a good mentor = potential for good training, and a lousy mentor = potential for inadequate training

If put in a Course where learners must complete steps in order, note that Steps following a Human Step cannot be completed until their mentor confirms the meeting (or the learner enters a code)

Must be existing content accessible through a URL

URL must be RFC compliant (not sure what that is? Ask your admin!)

Provide a URL that directly links to the desired content (don’t make learners search to find specific content within a website - unless that is the goal)

You will need a fully qualified domain name (e.g., if you wish to link to your intranet site, you would need an RFC-compliant URL such as "intranet.local")

Don’t provide links to pages that regularly rotate content (e.g., homepages or blogs that highlight new content each week)

Best used for reference materials as it will always be a non-graded Step

The Link Step is the least engaging Step type, so aim to provide information broken down into small paragraphs using bullet points/numbered lists where possible. As a rule of thumb, stick to one learning point per link.

Linked interactive page must be built/pre-existing outside of LemonadeLXP

You must include LemonadeLXP-specific coding in the link’s HTML

The linked page should contain HTML with all the essential parts

You must include the LemonadeLXP Link Listener file and Data Events in your code

Coding knowledge is necessary for successful integration

Great for including pre-existing external content within LemonadeLXP software

Recommended limit - 125 characters per question

Max 12-14 questions per step

Recommended limit - 90 characters per answer

System limit - 125 characters per answer

Four answer options per question are recommended (min 3, max 8)

Recommended limit - 125 characters

Expands or elaborates on the correct answer(s)

System limit - 125 characters per message

Individual incorrect feedback is provided for each wrong answer

Keep the reason why it’s wrong concise

Do not explain the correct answer

Don’t introduce new material

Avoid having only one correct answer for most of the questions (use a Streak Step instead)

Avoid “all of these” as a single answer option - instead, have learners highlight all available answers (don’t do this too often, or it will be too easy)

To avoid lengthy answer options, add more details to the question itself (if needed)

If the number of questions asked is lower than the number of questions available, enable question shuffling to ensure the inclusion of all questions in subsequent replays

If you need to create some questions with more than four answer options, try to vary all the questions so that there is no clear pattern to the questions (i.e., don’t just use six answer options when you need 5 or 6 to be correct).

Aim for 1-3 large paragraphs, or 3-7 small paragraphs

Roughly 5-15 lines of text

Recommended number of deviations (the "lies") - Min 3, Max 5

Recommended number of options, per deviation - 4 (3 wrong + 1 original text)

Deviations shouldn’t be too similar to the correct answer

Highlight only 1-3 words as part of the deviation

Match formatting in deviations (e.g., if you write a number as "1,000", do not write deviation number options using "1000" or "1000.00" formats!)

Ensure all deviations are incorrect - avoid synonyms/"technically correct" options!

Avoid impossible deviations (e.g., "Bananas can be yellow." - If the correct term is "are," realistically, the learner won't be able to identify it!)

No feedback given

Include a deviation near the end of the text; that way, the reader is guaranteed to read the whole thing

Consider setting the "How many Deviations shown in the game" number to 1 or 2 fewer than the number of deviations created - this will randomize which deviations appear each play-through (and will keep learners on their toes!)

Deviations should fit smoothly into the text and be similar in length to the correct text

Only deviate from known/already taught terms and/or words that can realistically be identified (e.g., if learners don’t yet know the difference between “debit” and “credit," don’t deviate from those terms!)

Consider using deviation points that reinforce crucial terms (e.g., the correct term is an essential term learned in a previous Step)

Don't be afraid to make deviations a bit obvious to ensure learners can find them (e.g., "Bananas are blue." "Savings accounts are a terrible way to save money.")

Make sure deviations include all words that can be seen as connected to the main focus, e.g.:

“A relationship won’t prosper with hurtful words.”

"A relationship will suffer with hurtful words.”

Min 3 questions are recommended

System limits - 256 characters; ~32 avatar text boxes

Recommended limit - Less than 175 characters

We recommend creating a Scenario that takes less than 5 minutes to complete

Recommended number of answer options - 2-4 (depends on variation of Scenario)

System limit - 256 characters

Recommended limit - Less than 125 characters (longer is acceptable with fewer presented answer options)

Keep answers short and around the same length

Can include any mix of positive/neutral/negative choices; use what makes the most sense!

No feedback given

Save often so you don’t lose work!

Create your "perfect path" first, then build out your alternate /poor paths after

Points must be added or subtracted in desired or undesired conversation paths

Point value always starts at zero and can never go below it (e.g., if a learner has zero points and chooses a path that subtracts 1 point, their point value will remain at zero)

Try reading your conversation paths out loud to check for awkwardness

Focus on the flow of conversation (appropriate responses, facial expressions, grammar, and punctuation)

Connect all dialogue options to a proper response (not doing so means that particular dialogue will not appear when played!)

The character always has the last word - their final words should not have any learner responses attached to it (if it does, those learner responses won’t appear)

Ensure that you include at least one “perfect path”

If designing two or more valuable/desired conversation paths within one Scenario, try to limit repeated material to keep the text box count under the limit

In complex Scenarios, it can be easy to miss mistakes - make sure to test each possible conversation path, as well as review answer weight and point values

Scenarios are most effective for introducing course material as an overview and reviewing/practicing material that has already been taught

LLXP can use only SCORM 1.2 files

The file should be in .zip format

Use each .zip file in a single step

If it's meant to record a grade, it must send a "finish" as well

Ungraded SCORMS can be set to record the step as complete/incomplete

We recommend including an appropriate completion time in the step summary, especially if it takes longer than 5 minutes

Questions should specify the list type being reviewed

System limit - 125 characters per list item

Max 8 list items per sequence question

List items must be added to the system in order, from top/first to bottom/last

Can summarize or expand on the correct answer

System limit - 125 characters per list item

Should strongly suggest or tell the learner what that step of the sequence should be

Incorrect feedback is "tied" to the list item's position and does not move

Incorrect feedback for the last list item isn't necessary (the system won't show it since learners will always answer the last one correctly when the second-last one is correctly answered!)

Keep category titles concise - we recommend 1-5 words

Min 2 categories

System limit - 125 characters per fact

Recommended limit - 90 characters per fact

Min 6 facts - the more facts, the better!

It can include a high number of facts as each replay will randomly pull various options from the “answer pool” every time

If you have lots of facts, we recommend a max of 10-12 questions presented per play

Recommended limit - 125 characters

Can summarize or expand on the correct answer

Should only (and always!) restate what was selected, along with which category the chosen answer is part of

Remember that facts and categories are shuffled and pulled at random, leaving no guarantee that all facts will be included within a single playthrough - if you must address all facts individually, treat your Sorting step as a supplemental round and aim to have a different step type precede it to address and "introduce" each fact

When using as a main (non-supplemental) round, we recommend including context via a brief but clear intro to the content within the description (e.g., finish your description with a call to action that names all categories the learner will be matching facts to, such as, "Do your best to identify the categories ["fruit," "vegetables"] for the following produce!")

Facts should only fit into one category (e.g., good = "These have beaks" plants / birds / planes; bad = "These have wings" plants / birds / planes)

Set questions asked per round to less than the total number of facts to reduce repetition within a single round

Sorting Steps can be tricky; playing one as a test will help you get a feel for it

Recommended limit - 125 characters per question

It can only be set to ask precisely 8, 10, or 12 questions per round

An additional/odd number of questions can be included (depending on how the step is configured, either some questions will be repeated each playthrough or learners will encounter a different set of questions each time)

The question format should be varied. Use a combination of fill-in-the-blank and question format to keep the learner engaged.

Recommended limit - 90 characters per answer

System limit - 125 characters per answer

Four answer options per question are recommended (min 3, max 8)

You can have more than one option as correct (make sure to address all right choices in correct feedback so learners know about it!)

As discussed in this Confluence article on Writing Multiple Choice Questions, you should balance the likelihood of choosing different answers to challenge learners appropriately. In the answer options, try to aim for 1 = correct, 1 = close to correct, 1 = a stretch to be correct, 1 is wrong (ideally funny). The underlying math is that the learner should have a 35-40% chance of getting the correct answer the first time through the content.

Recommended limit - 125 characters per message

Summarize or expand on the correct answer

Introduce new and relevant information

Should only state what the correct answer is

Do not explain the correct answer

No new information here

When including “all of these” as a correct answer option, ensure you also include some questions where “all of these” is the wrong answer

If you end up with an odd number of questions (e.g., 9 or 11), or the number of questions asked is set to be lower than the number of questions available, enable question shuffling to ensure subsequent replays will include all questions

A mix of formatted text (including embedded URLs) and images, created as an internal document for learners to view

Recommended limit - 2-3 pages worth of content per step

For large passages, split content into two or more Text steps

It is a great way to include additional materials to supplement learning

Perfect for having visual items for reference (e.g., consider the difference between a ripe banana and a rotten banana)

Best used for reference materials as it will always be a non-graded Step

The Text Step is one of the least engaging Step types; try to only include this for supplemental items and/or reference materials

5-8 questions are recommended

Recommended limit - 125 characters per question

True or False are the only options

Recommended limit - 125 characters

Summarize or expand on the correct answer

Introduce new and relevant information

Should state what the correct answer is

Do not explain the correct answer

No new information here

Great training game for reviewing general knowledge

Avoid number-based questions that require the learner to remember exact figures

Avoid double negatives as they add unnecessary confusion (e.g., If the statement is “Sally is not blond” and the answer is FALSE, this is like saying Sally is not not blond!)

If you set the number of questions asked to be lower than the number of questions available, enable question shuffling to ensure subsequent replays will include all questions

Supported file types: .3gp, .aac, .avi, .flv, .mp4, and .mpeg-2!

LemonadeLXP is designed to transcode the above video formats for seamless playback

Can include subtitles uploaded alongside the video in .vtt file format

It will vary, but aim for short and sweet! (It’s better to have two quick Steps in a course than have one long one)

It shouldn’t be longer than 6-7 minutes

Choose videos that have minimal “filler” content (should get straight to the point and be concise

Make sure the video is of good quality

Add a subtitle file to a new or existing video at any time

Any videos uploaded to YouTube

It will vary, but aim for short and sweet! (It’s better to have two quick Steps in a course than have one long one)

It shouldn’t be longer than 6-7 minutes

Choose videos that have minimal “filler” content (should get straight to the point and be concise)

If the YouTube link is blocked on a browser, then learners will not be able to access the video

Video must be publicly available

Make sure the video is of good quality

Always test before publishing the Step to ensure you’ve addressed the above notes