Expectations Cloud

What is Expectations Cloud?

Expectations Cloud is a simple activity for the start of a workshop or training.

Participants write what they expect from the session. The answers appear as a word cloud. The facilitator then opens words in the cloud, reads the cards behind them, and helps the group discuss what people really meant.

The cloud helps the group align early.

A word like alignment may appear in large letters. That does not tell you enough. One person may mean alignment on the project goal. Another may mean alignment between teams. Another may mean alignment with their manager. Another may be saying, in a polite way, that the workshop already feels off track.

The word gives you a door into the conversation. The cards behind the word give you the meaning.

When to use it

Use Expectations Cloud when you want to understand what people expect before the main work begins.

It works well for:

• workshops,
• training sessions,
• project kickoffs,
• webinars,
• online sessions,
• in-person sessions where people can answer from their phones,
• large groups where asking everyone out loud would take too long.

It is useful when people may arrive with different ideas about the goal, the agenda, or what the session can solve.

How to run it

A simple Expectations Cloud takes a few minutes to collect answers. Plan more time for the debrief.

How to debrief the cloud

Use the word cloud to start the debrief.

The best question is simple:

Is there a word you would like to see behind?

Let participants choose the words they want to explore. Then open the selected word, show the cards behind it, and discuss what people meant.

Useful debrief questions include:

• What do you mean by this expectation?
• Is this shared by other people?
• Is this clearly in scope for today?
• Is this partly in scope?
• Is this outside the scope of today's session?
• Does this need clarification from the facilitator, sponsor, or manager?
• Which word should we open next?

Participants help choose what to discuss next. The debrief becomes more engaging because the group is helping to make sense of the cloud.

Why big words can mislead

A large word usually means that the word appeared often. It does not prove that the expectation is the most important one.

UC Berkeley School of Information has a useful critique of word clouds. Their point is simple: word clouds are easy to like, but weak at showing meaning.

Two traps matter in facilitation.

First, the same word can hide different meanings. If several people write clarity, they may be asking for different things. One may want clarity about the agenda. Another may want clarity about decision rights. Another may want clarity about what happens after the workshop.

Second, a small word can matter. A word mentioned by one or two people may reveal a risk, a concern, or a weak signal that the facilitator should not miss.

Look at the big words. Also explore small words. Ask the group what looks interesting, surprising, unclear, or important.

Good questions to ask

The question shapes the cloud.

A broad question can work:

What are your expectations?

More concrete questions often work better:

What would you like to achieve by the end of this workshop?

What would you like to be able to do at the end of this training?

What question do you want this session to answer for you?

What would make this session useful for you?

What concern should we keep in mind today?

For a training, focus on what people want to learn or do. For a project workshop, focus on what people want to clarify, decide, or align on.

Tools and setup

You need a way for participants to send short written expectations and a way to show a cloud from those answers.

Low-tech and general-purpose tools

In a very small group, you can ask people out loud or use sticky notes. This is simple, but it does not scale well.

Most word cloud tools can collect one-word answers and show repeated words. That can be useful for a quick pulse check. For Expectations Cloud, richer answers are better. A word like tutorials or alignment is often too vague by itself.

If your tool only shows isolated words, use the cloud as a light signal. Ask people to explain their own words voluntarily. Do not over-interpret the image.

Using Stormz

Stormz makes the activity easier because the cloud stays connected to the original cards.

Participants can write fuller expectations. The group sees a word cloud. The facilitator can open a word and read the contributions behind it.

That changes the debrief. You can inspect what people wrote instead of guessing what a word means.

Participants can also explore the cloud from their own devices. This creates useful options:

• individual reflection before the plenary debrief,
• pairs exploring the cloud together,
• small groups choosing one word to bring back,
• breakouts reviewing the expectations before the full group discussion.

For more complex or strategic questions, the Tag cloud view can go one step further. It can show tags or themes instead of raw words, especially when auto-tagging is active. For a simple expectations opener, the Word Cloud view is usually enough.

Facilitation tips

Common mistakes

Stopping at the pretty cloud

The weakest version is to collect expectations, show the cloud, say “interesting”, and move on.

That creates a visual moment, but little facilitation value.

Asking only for isolated words

Many word cloud tools push facilitators to ask for one-word answers. Words like alignment, tutorials, or clarity are too short to explain the real expectation.

Ask for short expectation cards instead.

Debriefing alone

If the facilitator chooses all the words and explains the cloud alone, the activity becomes less collaborative. Let participants choose what they want to open.

Treating frequency as importance

A big word may be common, but a small word may be critical. Frequency is useful, but meaning, urgency, and importance are different.

Avoiding out-of-scope expectations

If an expectation is outside the scope, say it early and respectfully.

For example:

I hear that some people expect a full tutorial on this topic. That is outside today's scope. We will focus on the decision process, and I can point you to resources for the tutorial part.

If the session is mandatory and the mismatch comes from the sponsor's goal, the sponsor may need to explain why the session exists and how other expectations will be handled later.

Variations

Learning outcomes cloud

Instead of asking for expectations, ask:

What would you like to be able to do at the end of this training?

This is useful when you want concrete learning goals.

Concerns cloud

Ask participants what concern the group should keep in mind. This can surface risks early, especially in change, strategy, or project workshops.

End-of-session reflection cloud

At the end, ask participants for their main takeaway, remaining question, or next action. Compare it with the expectations from the beginning.

Small-group exploration

After the cloud appears, ask pairs or small groups to explore it themselves. Each group chooses one word to bring back to the plenary discussion.

Useful background

UC Berkeley School of Information on word clouds is a good starting point for understanding why word clouds are engaging but weak at showing meaning.

DIES has a practical word cloud exercise for workshops. It covers online and face-to-face use, group size, setup, and basic debriefing.

LevelUp has useful guidance on setting expectations in training. It is helpful when you need to manage participant, organizer, and trainer expectations early.

FAQ