Museum Exhibition Interactive Kiosk with Conflicting Curatorial and Technical Constraints
A history museum is commissioning an interactive kiosk for a temporary exhibition on local immigration. The curator wants a narrative-driven experience with long text panels, oral history audio, and a map of origin countries. The IT department requires the kiosk to run offline, on hardware that is three years old, with a touchscreen that has known ghost-touch issues. The education team wants content usable by school groups of 30 students rotating in 10-minute intervals. The exhibition runs for four months, and the museum has no dedicated maintenance staff. Visitor dwell time data from a previous exhibition showed an average of 90 seconds per kiosk.
1. How should the design team resolve the tension between the curator's narrative ambition and the observed 90-second dwell time?
Read the worked answer
Design for the observed behavior rather than the desired behavior. The entry screen should present a single clear choice (e.g., 'Find your family's country of origin' or 'Hear one story'), with the map as the primary navigation and oral histories as short 30–60 second clips. Long text panels should be moved to a layered 'read more' path for the minority who stay longer, not placed on the first screen. This preserves the curator's narrative content while matching the first 90 seconds to a complete, satisfying interaction. Justify with the dwell-time data and with the school-group constraint, since 30 students in 10 minutes allows roughly 20 seconds per student, making a single-screen, single-decision interaction essential. The reasoning is that content depth should be layered by engagement level, not front-loaded.
2. What should the team do about the ghost-touch touchscreen and the offline requirement?
Read the worked answer
Treat hardware limitations as design constraints to be tested, not ignored. Ghost-touch means spurious inputs, so the interface should avoid tightly packed small targets, use large buttons with generous spacing, require confirmation for destructive actions (like clearing a selection), and avoid drag gestures that ghost-touch disrupts. The offline requirement means all audio and map assets must be stored locally, so the team should compress audio and pre-render map tiles and test load times on the three-year-old hardware. A prototype should be tested on the actual kiosk before content is finalized. Additionally, because there is no maintenance staff, the team should include a simple restart procedure and remote or scheduled content checks. The reasoning is that interaction design must be validated against the real device, and reliability planning is part of the design deliverable when maintenance capacity is absent.
3. How should the education team's 30-student rotation requirement influence the interface?
Read the worked answer
It should drive a group-friendly mode. With 30 students in 10 minutes, individual deep interaction is impossible, so the kiosk should support a short guided sequence that a teacher or student leader can run for a small cluster, with large shared-screen text and audio that can be heard or optionally read. The interface should reset quickly between groups and avoid states that require cleanup. The team should propose a printed or projected companion for the full group and reserve the kiosk for 2–4 students at a time. This meets the education team's need without pretending one kiosk can serve 30 students individually, and it aligns with the dwell-time data. The reasoning is to match the interaction model to the actual social context of use.