The Visitor Question Log: Turning a Lab Tour Into a Diagnostic Instrument

Most lab tours are designed to demonstrate competence. A visitor walks past a fume hood, a microscope, a shelf of labeled samples, and a student guide narrates the work with practiced fluency. The tour ends with nods and thanks. Everyone leaves convinced that the lab is busy, serious, and hard to understand in a productive way.

That is a poor use of an audience. A tour can do more than perform expertise. It can function as a diagnostic instrument, exposing the places where our public-facing language assumes too much. The protocol described here is deliberately modest: students give short, jargon-free walkthroughs; a second student logs visitor questions instead of answering them immediately; and the lab debriefs the log within a week. The point is not to produce a polished visitor experience. The point is to find out what our materials fail to explain.

Why the Usual Tour Fails as Evidence

When a guide answers every question in real time, the tour feels smooth. That smoothness is the problem. An immediate answer often repairs a gap before anyone notices it exists. The visitor gets the information, the guide gets the satisfaction of being helpful, and the lab learns nothing about why the question was necessary in the first place.

Consider a common exchange. A visitor points at a benchtop instrument and asks, “What is that machine for?” The guide says, “That is our plate reader; we use it to measure fluorescence.” The answer is accurate and the visitor appears satisfied. But the question may have been doing more work than the guide realized. The visitor may not know what fluorescence is, why a lab would measure it, or how a plate reader differs from a microscope. The guide’s answer closed the conversation before it could reveal the scale of the assumption.

A diagnostic tour treats questions as data. It does not treat them as interruptions to be resolved as quickly as possible.

The Protocol in Brief

The tour is scheduled for roughly thirty minutes and includes no more than eight visitors. Two students run it. One serves as the guide; the other serves as the recorder. The guide speaks for about sixty seconds at each of four or five stations. The rule is simple: no acronyms, no unexplained instrument names, no phrases such as “as you probably know.” The guide describes what the lab is trying to find out, why it matters, and what a visitor is actually looking at.

The recorder does not answer questions. When a visitor asks something, the recorder writes it down as close to verbatim as possible. If the guide is tempted to answer, the recorder can say, “That is a good question; we are collecting these and will follow up.” Visitors are told at the start that the lab is testing its own communication materials and that questions are the main purpose of the visit. This framing is honest and prevents the deferral from feeling evasive.

After the tour, the two students spend thirty minutes transferring the questions into a shared document and sorting them into rough categories: vocabulary, scale, causality, relevance, and process. The categories are not sacred. They simply give the lab a way to see patterns.

What the Questions Reveal

Vocabulary questions are the most visible. A visitor asks what “assay” means, or whether “in vitro” is a kind of machine. These questions usually point to gaps in signage, web pages, or the guide’s own script. They are easy to fix, but only if someone writes them down.

Scale questions are more interesting. A visitor asks, “How many cells are in that little tube?” or “Is that a lot of samples?” These questions reveal that the lab has never explained its unit of work. A project description may say that the team studies “cellular responses to stress” without indicating whether the experiments involve ten cells or ten million. The visitor is not confused about the science; the visitor is confused about the size of the science.

Causality questions are often the most revealing. A visitor asks, “But how do you know that the drug caused the change?” That question may expose a project description that states a finding more confidently than the evidence allows. It may also expose a guide who has absorbed the lab’s internal shorthand without learning how to explain the logic of the experiment. In either case, the question is worth keeping.

Relevance questions sound naive and are not. “Why does anyone care about this?” is a fair challenge to any project page that begins with a technical problem and never connects it to a consequence. Process questions—who does which step, how long an experiment takes, what happens when something fails—often reveal that the lab’s public materials describe results but not the work.

The Debrief Is the Experiment

The tour itself is only the data collection. The debrief is where the lab decides what to change. A useful debrief produces three lists: questions that can be answered by revising written materials, questions that require a better guide script, and questions that point to a genuine gap in the lab’s own thinking.

The third list is the most valuable and the most uncomfortable. If visitors repeatedly ask how a particular measurement supports a particular claim, the lab may need to examine whether the claim is stated too broadly. If visitors ask why a project matters and the guide keeps reaching for the same vague phrase, the lab may need to write a better project description—not for visitors, but for itself.

Boundaries and Cautions

The protocol is not suitable for every tour. Prospective students, funders, and collaborators may need different kinds of information. The diagnostic tour is best used with general visitors, community groups, and undergraduate classes. It should not be used to collect questions about unpublished data or sensitive personnel matters. The recorder should log questions, not names, and the lab should tell visitors how the log will be used.

Nor should the protocol become a performance of humility. The goal is not to make students feel unprepared. The goal is to make the lab’s assumptions visible. A question log is a working document, not a verdict.

A Small Habit With a Long Tail

A lab that runs this protocol once will learn something about its signage. A lab that runs it twice a year will build a record of the questions its public-facing materials consistently fail to answer. That record is more useful than a polished tour script, because it is generated by people who are not yet fluent in the lab’s shorthand. The visitor question log does not replace the tour. It makes the tour do a second job: showing the lab where its explanations end and its assumptions begin.