<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Benjamin Hapka on Medium]]></title>
        <description><![CDATA[Stories by Benjamin Hapka on Medium]]></description>
        <link>https://medium.com/@benjaminhapka?source=rss-6044e7bbe6a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZLJt91_yFe4qZSsvB8qEOA.jpeg</url>
            <title>Stories by Benjamin Hapka on Medium</title>
            <link>https://medium.com/@benjaminhapka?source=rss-6044e7bbe6a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:34:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@benjaminhapka/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Scenario: Ben goes to the airport.]]></title>
            <link>https://medium.com/@benjaminhapka/scenario-ben-goes-to-the-airport-84c5f15072ae?source=rss-6044e7bbe6a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/84c5f15072ae</guid>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Benjamin Hapka]]></dc:creator>
            <pubDate>Tue, 01 Sep 2015 03:03:15 GMT</pubDate>
            <atom:updated>2015-09-20T20:20:21.723Z</atom:updated>
            <content:encoded><![CDATA[<p>Before boarding my flight to New York City I asked the Southwest service representative, “I thought my seating was Section A?”. She said, “Let me see your boarding pass; there’s no seating section for you yet sir, but for an extra 15 dollars we can get you Section A ticket.” But I ended up Section C.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HCvtX6XDcC8mi-xdk6KauQ.jpeg" /><figcaption>Taken by <a href="https://unsplash.com/francoisvanwyk">Francois Van</a></figcaption></figure><p>What happen that afternoon? Why didn’t I get my section, I was intended to get? But what helped me further understand this insight is reading Andrew Hinton book, “Understanding Context”. Andrew Hinton presents typical scenarios and user experiences that “illustrate challenges of a growing “context problem.” What does that mean?</p><blockquote>Well, Hinton said, “Still, in some ways, the context actually isn’t so mysterious, because from one moment to the next we seem to know it when we see it. Whenever we’re trying to figure out what one thing means in relation to something else, we say we’re trying to understand its context” (Hinton 2).</blockquote><p>Context is everything, but it creates the users experience, pokes the users sub-conscious, and in turn revealing the insights or the “Elephants in the Room.” First off I am not a regular flyer, and I fly maybe twice a year. So, I don’t use Southwest iPhone App to check in or utilize the extra royalties from the airlines when prompted. I learn from a young age, technology is like a box of chocolates, and you never know what to expect. Each time you add that new delicious chocolate, you added the extra context of information.</p><p>My story begins, walking towards the airport terminal holding my southwest printed email, enclosing my flight confirmation number. When I approached the Southwest Airlines check-in kiosk, I was prompted to enter my flights confirmation number and my personal information. The next screen presented two buttons, one that said “would you like Section A seating?” or “Cancel.” I didn’t want to “Cancel”; therefore I picked option one. The Kiosk printed my ticket, and I went on my way. As I glanced at my ticket, there was no seating information. But the kiosk said I was in “Section A” so I figure it was a misprint or potential problem. While trying to locate my gate, my ticket said, “Gate C16”. The airport signage around me helped tremendously; the context was easy to read and easy to fine. Therefore, I made it to my gate in no time at all. But my Gate wasn’t “Gate C16” it was “C20”. Good thing it was C20 not D20 or something else.</p><p>The overall growing “context problems” were. What is my seating section, is it “Section A” or something else? Why did my ticket say “Gate C16” if it wasn’t “Gate C16”? Therefore, brings me to the point of my story I am talking to the Southwest, service representative. After talking to her all my problem were cleared up, and I was ready to board the flight. The problem started with the Check-in Kiosk and then branched off to multiple growing “context problems”.</p><p>Hinton describes a comparable airport scenario in his book, but with a greater amount of “context problems”. My scenario consisted of just a couple contextual structures to ensure I make it to my flight on time. Hinton’s major contextual structures included Check-in kiosk, iPhone, Passbook, Airline App, Boarding Zones, SkyMiles Member, Airport WiFi and Cellular data.</p><blockquote>Hinton illustrates, “scenarios like this, we find ourselves in a tangle of digital, semantic, and physical structures. We are agents trying to take action in our environments, and we have to understand those environments well to take the appropriate actions” (Hinton 7).</blockquote><p>What creates such an interesting insight from both Hinton scenarios and mine? Each encounter was designed and built by people. From the individual who designed the check-in kiosk to the printed ticket stub.</p><blockquote>We created these environments to be “meaningful relationships between elements …. these problems caused extra work and stress activity that used to be much more straightforward” (Hinton 8).</blockquote><p>As designers we need to create experiences that go beyond the general and can be tailored to each customer. Not a manufactured product or standard experience, but an experience that comes to life as an integrated, coordinated, experience.</p><p><strong>Citation</strong></p><p>Hinton, Andrew. <em>Understanding Context: Environment, Language, and Information Architecture</em>. Sebastopol, Calif.: O’Reilly, 2015. Print.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84c5f15072ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>