What front end evaluation is
Front end evaluation is research done at the very start of a project, before the concept is fixed and before anything is designed or built. Its job is to find out who the audience is, what they already know or believe about the topic, what they are curious about, and what might put them off. The results feed into the first decisions about content and format, when changing direction costs the least.
It is one of several stages of evaluation. Later stages test rough versions, check the finished exhibit against its goals, and fix problems in a running gallery. Front end work is different because there is nothing to react to yet. You are studying the audience and the topic, not your own design.
Why it is worth doing
Exhibit teams are usually experts in their subject. That is a strength, but it makes it hard to remember what a newcomer does not know. Words that feel basic to staff can be unfamiliar to visitors, and ideas that staff find fascinating may not interest many people at all.
Typical things front end work can reveal:
- Which parts of a topic visitors already understand, so you do not spend space explaining them.
- Common misconceptions, which are often more useful to address than gaps in knowledge. A visitor who holds a firm but wrong idea may read straight past a label that does not challenge it.
- The questions people actually ask, which can shape the story better than a list of facts the institution wants to present.
- Practical expectations, such as how long people expect to spend, who they visit with, and whether they like to use touch or voice.
- Words visitors use for the topic, which are often different from specialist terms.
None of this guarantees a successful exhibit. It reduces the chance of building on a wrong assumption.
Questions to settle first
Before talking to anyone, write down what the team needs to know. Vague aims such as “learn about our audience” produce vague answers. More useful questions are narrow, for example:
- What do visitors think this process involves?
- What would they most like to see explained?
- What do they expect an interactive screen on this topic to do?
- What would stop them from using it?
Keep the list short. Five clear questions will produce more usable results than twenty. If you are also working on how to write exhibit goals, doing that in parallel helps, because good evaluation goals point to the things worth asking about.
Methods that suit this stage
Front end evaluation does not need a large budget. Common approaches include:
Short conversations in the gallery or lobby. Staff or volunteers ask a few open questions of people who agree to talk. Open questions (“What comes to mind when you hear…?”) work better than yes/no ones, because they reveal how people think.
Interviews. One-to-one conversations allow more depth and let the interviewer follow up on surprising answers. They take longer, so fewer people are reached.
Group discussions. Small groups can show which ideas resonate and how people talk about a subject. Their limits are real: focus groups can be swayed by dominant voices.
Surveys. Useful for checking how common an opinion is, though a poorly worded form can mislead. Wording and sampling traps in visitor surveys are common.
Review of existing information. Past feedback comments, inquiries to front-desk staff, school program notes and teacher requests are free sources of questions the audience already asks. Check that any feedback you reuse was collected with appropriate consent and handled with respect for visitor privacy.
Sorting or word tasks. People can be asked to group cards of topics or to say which words they would use to describe something. This is a simple way to find the vocabulary your audience uses.
You can combine methods. Many small teams do a handful of conversations first, then use what they hear to draft a short survey.
Who to ask
The people you talk to determine what you learn. If you only speak to regular members, you will hear from people who already like the institution and have time to spare. Consider the audiences the exhibit is meant for, which might include family visitors, school groups, older adults, or people visiting from elsewhere, and try to include at least some of each.
Keep in mind the people who do not come at all. Local communities who rarely visit may hold views that visitors cannot supply. Reaching them can take more effort, such as partnering with a community organization, but it can change the direction of a project in useful ways.
It also helps to include people with a range of access needs from the start. Asking early what barriers exist for low vision visitors or for people who find busy screens hard to follow is far easier than retrofitting later.
Keeping the findings honest
Small samples are fine for finding ideas and problems, but they are weak evidence of how common something is. If six of ten people interviewed held a misconception, that is a signal worth acting on, not a precise percentage for all visitors. Report findings with that caution: “several people said…” rather than “60 percent of visitors believe…”.
Be aware of how your own questions shape answers. Leading questions (“Wouldn’t you like more interactive features?”) invite agreement. People also tend to say what they think the interviewer wants to hear, and may predict that they would use something that they later ignore. Stated interest is a hint, not a promise of behavior, which is one reason later stages of testing with rough versions matter.
Turning findings into decisions
Evidence that sits in a folder does nothing. At the end of this stage, write a short summary, ideally one or two pages, covering:
- Who was asked, how many, and how they were chosen.
- The main things learned, separated into knowledge, interests, misconceptions and practical needs.
- What the team will do differently because of it.
- What remains unknown and might need testing later.
Share it with everyone involved in the design process, including writers and technical staff, not only the project lead. When the exhibit brief is written, it should reflect what was learned.
Common mistakes
- Starting with a solution. Asking “Would you like a touchscreen game about this?” tests an idea the team already likes. Ask about the topic first.
- Doing it too late. If the concept is already approved and funded, front end results are likely to be ignored.
- Treating staff opinion as audience knowledge. Staff are not typical visitors.
- Asking too many people the same shallow question. A smaller number of richer conversations is often more useful.
- Skipping it entirely because of budget. Even a day of informal conversations can be better than none, and it costs far less than rebuilding an exhibit that misses its audience.
Front end evaluation does not replace later testing. It simply makes sure that the first rough version is aimed at the right target.