Returning to the question I started with

I began by asking how shared airport accessibility could better respond to the individual sensory needs of autistic adults travelling independently. The report brought me back to the way a traveller uses information and decides whether to accept support. A person may have prepared for the journey in advance and still need to make a new decision when something changes. I wanted the conclusion to reflect that situation and the differences in what people wanted from assistance.

The claim I could make from the evidence

The literature and questionnaire accounts gave me grounds to propose clearer journey information, coordination across airport services and a choice about when to use support. My interpretation was that support is useful when someone can find it, understand it and decide how to proceed. The work also kept the airport’s responsibility visible. A personal interface can help someone decide what to do, while the airport still supplies the information, staff and environments that make the decision possible.

Where I left the technology question

I was interested in whether physiological sensing could add something to that picture. The literature and participant accounts gave me enough to consider it as a possible additional layer. I could conclude that the idea raised questions worth testing, including what a reading means in context and how an offer should be made. I left the effectiveness of a wearable open. In an airport, walking quickly or carrying bags could affect a reading, and a traveller may prefer to open support themselves.

<aside>

The report gave me a design proposition I could take into Studio Practice. Testing the proposition would need its own evidence.

</aside>

Carrying the question into Grounded

In Studio Practice I used a gate change to give those ideas a concrete setting. I could show the new gate, offer an action and let someone continue when they chose not to open support. Doing that made the next research question more specific. I want to know what people understand, what they actually do and whether the design leaves them in control when plans change. I also want to explore whether any additional feature earns the effort someone has to spend setting it up and using it. That is a more useful place for me to take the work than ending with a list of features I could build.

Looking at the conclusion beside the prototype

I would read the conclusion alongside the report’s communication diagram and the Studio Practice gate-change walkthrough. The diagram shows the proposed relationship between journey information and optional support. The walkthrough makes one part of that relationship concrete through a change of gate. The next step is to check with travellers whether they can identify the new gate, explain what they would do and resume their journey if they decline help. Those observations would answer a different question from the one I could address through the written report.