In the sample journey, BA256 moves from B12 to A04. I imagined the airport or airline confirming the change, the departure board showing it to everyone, and the phone repeating the same flight and gate before offering directions. A traveller could use the board, signs and staff to find their way. The phone could add step-by-step directions and optional support, with personal choices kept on the traveller’s own device.

What happens if the information disagrees?

The live flight lookup in Grounded shows that the app can retrieve current flight information. The coordinated board and phone are part of the fictional walkthrough. For an airport to use the idea, it would need to agree who confirms a gate change, how quickly it reaches each display and what to do if a source is late or unavailable. In my proposal, when the app cannot verify an update, it points the traveller to official airport information or staff. The airport or airline would resolve the conflict.

I would want someone who looks up from their phone to see the same confirmed gate on the departure board and know where to check if the two disagree.

Making the status of a request clear

I explored three states for staff assistance: requested, sent and accepted. Each would give the traveller different information about what is happening. Showing ‘accepted’ would depend on a response from the service responsible for providing help. For an airport to take this forward, it would need to decide who receives the request, how staff acknowledge it and what the traveller sees while waiting.

Looking after the information over time

An airport would need to keep the terminal maps, flight data and service links up to date. If a route is described as quieter, someone would need reliable information about current sound and crowding. My alternative-route study leaves those conditions marked unknown. I would also want to check how often staff and service information changes and who updates it, since an old instruction could give someone more work at the moment they need help.

Keeping personal choices on the phone

In the coordinated version, the board does the public job of stating the confirmed destination. The phone can carry choices someone may prefer to make privately, including whether to open a support activity or send an update to family. This division also keeps the board useful to someone with a flat battery or without Grounded on their phone.

I would want to work through the fallback with airport staff before asking travellers to rely on it. A message that tells someone to check elsewhere still leaves them with work to do. Where possible, the wording would need to say what they can check and where they can find it. The design question is how to make that next step clear when the information that brought them there is uncertain.

What I would show an airport team first

I would put the departure board and phone side by side and walk through the same gate change, followed by a missing or conflicting update. I would ask the team where the information comes from, who can correct it and what the traveller should do while they wait. That would give me a concrete way to discuss whether the proposal could fit the airport’s existing signs, systems and staff processes.

Studio Practice Draft 4, pp. 41, 45, 53–54 and 63 · GDE751: Week 18: Gate-Change Communication Approaches.