Thursday, March 26, 2015

Group Meeting Thursday 26 March 2015


Aim: Deliver the Design sprint proposal
Attendance: Everyone
Minute taker: Matt

Minutes:

Design Sprint Critiques

Presentation and all supporting materials were handed in - Awesome work. Following on, we are required to each post two critiques of the other teams. To ensure each of the other teams get a similar amount of responses, the following was assigned:


  1. E-ink
2. Scales
3. Baggage Scanning
4. Power Arm
Leila
Song
Arturo
Song
Arturo
Lilly
Stuart
Lilly
Matt
Leila
Matt
Stuart





Team catch-up

Today we had a quick discussion of the timeline and outstanding tasks. Below are our these actions.


Next week’s assessment

  • Produce one more concept card each, for the unknown activity next week


Items for Project 1 assessment

Overall

We are a bit behind the proposed schedule - initially we wanted the prototype complete before the mid-sem break. The aim for the coming week is to collate all potential concepts and have a clear decision made for the solution to assess and prototype.


Concept Cards

  • Urgent- Everyone to complete concept cards this weekend
  • Assignment of cards is to be tracked in the document, found in the concept card folder. This is only to prevent duplication. New ideas are welcome

Personas

  • The required 6 personas are almost complete
  • Each is person to complete their assigned persona using the list on the drive

Research

  • Keep any new information coming, as it will help in substantiating future concepts

Future meetings

  • Meeting at 11am on Tuesday 31 March, Group Room 2, Level 2, Duhig North (SSAH Library) (floor plan if needed)
    • Discuss through the concepts and review these against our research
  • Meeting at 12pm on Thursday 26 March, Level 2, General Purpose South (same place as last week)
    • Last chance to wrap up any actions before the break


Monday, March 23, 2015

Group Meeting Tuesday 24 March 2015

Aim: confirm assessment for Thursday is on track, assign next tasks for completion
Attendance: Leila, Arturo, Song and Lilly
Minute taker: Lilly

Minutes:

Items for Thursday assessment

Prototype - 2 screens have been completed, a third will be added (Arturo and Song)
Persona - completed, template has been set up to create other personas (Lilly)
Concept cards - various stages of completion, on track to finish before Thursday


Actions

  • Lilly (& everyone) to print persona and concept cards on Thursday morning (26/3).  If you do not have your concept card uploaded to the file on Google drive by 8am then you are responsible to print your own concept card (A5/2-up A4).
  • Arturo to print prototype


Items for Project 1 assessment

Personas

For this assessment we need to produce 6 personas (1 per group member).  Today we collated data about the personas to be completed by each team member.  The dot points for each persona can be found on Google Drive in the Personas folder.  There is also a table in the persona document for team members to assign themselves to a persona.  A persona template has already been created as part of this week’s tasks.

Actions

  • Everyone to view the persona document on Google Drive and assign themselves a persona.  
  • Everyone to complete their assigned persona by next Tuesday 31 March 11am (meeting time)

Concept cards

For this assessment we need to produce 24 concepts cards (4 per group member).  For this week we have already completed 1 card each.  As part of the ideation process, we have already generated three problem statements and 18 possible solutions.  Team members can take from these 18 as well as develop more problem statements/solutions based on earlier bug brainstorms.

Actions

  • Everyone to choose 3 concepts and create 3 concept cards by next Tuesday 31 March 11am (meeting time).
    A concept template is in the ‘Concept card’ folder on Google Drive.  There is also a document to assign concept to yourself (either from the list or new ones) to prevent double up on the same concepts.

Future meetings

  • Meeting at 12pm on Thursday 26 March, Level 2, General Purpose South (same place as last week)
  • Meeting at 11am on Tuesday 31 March, Group Room 2, Level 2, Duhig North (SSAH Library) (this is the same level that we met at today)(floor plan if needed)

Sunday, March 22, 2015

Visit to Brisbane Airport Domestic Terminal findings

Part of our team visited the Brisbane Airport Domestic Terminal on Saturday 21st March to conduct user research. We used a range of user research methodologies, including natural observation, in-situ interviews and tracking.

Wayfinding
  • People would look at the flight information screens for long periods of time.
  • There are many signs, from the airport, from the Airtrain, from the airline, etc. It's easy to become confused and not find the specific information you are looking for.
Signage outside of domestic terminal - quite confusing
Flight departure display
Announcements cannot be heard in all areas of terminal
  
Waiting
  • People sitting on the floors, huddled around power points to charge devices
  • People laying / sitting on the floor while waiting instead of sitting in seats
    Charging phones around the internet kiosk (not actually using the computer)
Sitting on the waiting to board - not enough seating this in area 
Sitting and repacking luggage on the floor near check in area




Baggage claim
  • Passenger arrivals checking each baggage carousel as they were unsure where to pick up their luggage
  • People calling friends/family to update them about their status for getting picked up, and not knowing how long it would take to collect bags
  • People standing around the carousels instead of sitting. Many ended up standing for upwards of 30min as bags were delayed caused by the storm.
  • People picking up the wrong bags and having to put them back onto the carousel
  • People pushing through the crowd to get their bags, sometimes almost missing them as they went past.
  • Crowds around the middle section of the carousel, and not many at the ends.
  • Matt and I did participated in the process - we waited for a Cairns flight to arrive and disembark, and followed passengers to baggage claim. The walk from the arrival gate to claim was fairly quick and easy to follow (about 5 mins). None of the display screens showed the Cairns flight number, so there we were confused about where the Cairns baggage was to be picked up (there are only 3 carousels, all were stationary). We stood around for about 20 minutes as the baggage claim area got more crowded with other arriving passengers from various flights. There was an announcement that bags were delayed due to the storm. We waited another 15-20 mins. One of the baggage carousels started, the carousel's screen displayed the Hobart flight number only, but passengers from the Cairns flight got their baggage off this carousel too.
Crowds around the middle of the carousel
Waiting for baggage -
people standing in the middle of thoroughfares
  
Other
  • We passed through security section very quickly and easily. Although it was fairly quiet at the airport that day and we weren't carrying much on us. 
  • Some of the announcements were hard to understand, and some sections of the airport do not broadcast flight announcements.
  • Two taxi ranks exist 1 and 2, however only one was in use
  • Kids were running around, making games in the seating and pedestrian areas
  • Baggage / Landside area had no shopping or activities to pass time

      Some general feedback from people we interviewed:
      • Woman in transit - waited 2 hours for connecting flight, delayed due to storm: 
        • Liked Brisbane airport as it wasn't crowded
        • thinks all airports are the same
        • sitting on the floor next to powerpoint to charge her phone
        • wants more charge points
      • Woman waiting to board flight:
        • "airports are the same"
        • doesn't like waiting
        • doesn't like walking on the tarmac to board flight.
      • Group of people waiting at baggage claim area:
        • wish there were more TVs so they can watch something while waiting
        • more places to buys food while waiting
        • cleaner  toilets
        • background music
        • more seats
      • Male, late 20's, semi-professional, Irish ex-pat:
        • Irish ex-pat who has worked in Australia for several years
        • Heading back to ‘home’ for a holiday
        • He was found sitting on the ground, against a wall
        • The wall had a power outlet, which was connected to his laptop
        • He suggested power supplies built into comfy seats


      • Other observations made
        • 2 elderly ladies during check in
          • Physically shaked their heads on the approach to the computer screen
          • After starting the program, the attendant came over to help
          • The ladies started talking to the attendant, quoting their flight number, while the attendant pressed the screen
          • There appeared to be confusion and the attendant directed the ladies to the bag-drop desk, without a ticket being dispensed
          • During the bag drop, one of the ladies appeared to be struggling to lift their bag onto the conveyor
            • Lifting with outstretched arms, with weight of up to 20kg, with a body of potentially weak bones is a major OHS issues


      Thursday, March 19, 2015

      Design Sprint

      We were tasked with a Design Sprint due in the next tutorial session. The deliverables being:
      • Presentation
      • 1 Prototype
      • 1 Persona
      • 6 Concept cards
      To get started on choosing our 6 concepts we continued brainstorming concepts for the 2 extra problem statements generated last week (based on "nothing to do while waiting" and "unclear signage"), fleshed these out in some more detail and took note of their limitations. 

      As we have already conducted some user research, we decided to select concepts that have grounding in this research. After this we chose 6 concepts to use for the concept cards, 2 each from the 3 problem statements, and assigned a team member to each one. 

      The 6 concepts chosen were:
        • Search touch screens (Arturo)
        • Baggage collection zones (Matt)
        • Bag tracking (Stuart)
        • Sleeping pod/modular seating (Song)
        • Physical locater devices (Lilly)
        • Flight forum - social app (Leila)
      Each team member is to give the concept a name, produce a thumbnail sketch/picture, and give a "back-of-the-box" description that is detailed enough to convey the concept and differentiate it from other concepts.

      • We chose one of these concepts to develop into a prototype: Search touch screens that give users directions and times to their desired destination. We further explored this concept by brainstorming features, functionality, processes.
      • We brainstormed and created the persona "Retiree Judy" 
      • We continued to work on the low-fi prototype in some more specific details - the exact steps different users will take, how the interface will be organised, extra features such as a "countdown bar" that visually show the time breakdown to get to your destination. 

      Notes on our Persona

      Notes on our selected "Search Touch Screen" concept

      Notes on concept prototype

      Design Sprint deliverables for team members (due next week in class):
      • Concept cards - 1 per team member as above
      • Matt - Gather together and clarify our brainstorming notes from today
      • Lilly - Persona - continue to develop and refine the "Retiree Judy" persona
      • Arturo and Song - Prototype - Continue to develop a paper (or other low-fidelity) prototype of the concept.
      • Leila - Consideration of the environment, location and signage for this product. Produce a mockup of where it is to be situated in an airport setting.
      • Stuart - Presentation - devise to to present the concept and explain it through a story/scenario in which it would be used. No more than 5 min long.


      Group Meeting Thursday 19 March 2015

      Aim: Finalise Team Charter, Project 1 planning
      Attendance: Leila, Arturo, Matt, Stuart and Lilly
      Minute taker: Lilly


      Meeting minutes:
      • Finalised our team charter for submission today
      • Assigned functional roles for Project 1 (are flexible as design process proceeds)

      Role

      Responsibilities

      Person

      Product Leader

      Responsible to ensure the product delivered is what is proposed, editing of final document

      Lilly

      Prototype Leader

      (Prototype)

      Responsible of the management of the prototype budget and creation

      Arturo

      Research Leader

      (Empathize)

      Responsible of the curation of information and resources

      Leila

      User testing Leader

      (Test)

      Responsible of managing the testing stage and feedback

      Song

      Ideation Leader

      (Ideate)

      Responsible of the curation of ideas and possible solutions

      Matt

      Conceptual Leader

      (Define)

      Responsible of the evaluation framework, scenario/storyboard

      Stuart

      • Quick 10 minute update on the group's current status, have completed:
        • identified 3 broad problem areas from our bug lists
        • narrowed each area into a problem statement
        • started research and brainstorming
        • created the team charter and 
        • started our blog
      • Getting back to Assignment 1. 
        • Research: before week 4. We decided some team members will visit Brisbane Airport this Saturday to conduct further user research such as observation and interviews (the specifics of this to be further discussed before Saturday). Other team members will keep on researching from other means and add their findings to the Research folder in Google Drive.
        • Problem definition: before week 4.
        • Creating more concept cards, concept maps/scenarios and storyboards and evaluation framework: Work on this in week 4.
        • We are hoping to meet before next week's tutorial to discuss the Design Sprint and Assignment 1.

      Wednesday, March 18, 2015

      Brainstorming activity

      Each team member compiled a list of 20 airport 'bugs'.  We compiled these into a larger list to brainstorm from.



      After compiling our larger bug list, we broke down the bugs into categories of problem.



      We then chose three of those bugs and developed problem statements by looking at user perspective, needs and insights.



      Using this information, we developed and fine-tuned a problem statement for each of these bugs.



      Choosing one of these problem statements, Problem Statement 2: Overcrowded Baggage Claim, we then brainstormed possible solutions to this problem.



      We then split up the remaining two problem statements between the group to finish during the week.

      Problem space 1


      (LW, LB, SM)

      Problem statement


      Passengers in transit with a wait time over 2 hours outside of regular business hours (9am-9pm) need somewhere nice and comfy to pass the time and something to do.

      Steps

      1.     Brainstorm possible solutions (2 ideas each)
      2.     Flesh out brainstorm ideas, detail steps in process (different 2 ideas each)
      3.     Outline any problems with ideas, especially for other user groups

      Ideas


      • Modular seating with sections that can be upright (chair), incline or flat (lying down) with built in power points to allow charging of devices
      • Airport ‘hotel’ that you can rent by the hour to sleep in
      • scavenger hunt style game for fun and to get people moving
      •  entertainment areas to watch movies, play video games, read books/magazines
      • Create a forum for people on the same flight to meet, discuss, share about travel plans about the destination - make it more social.
      • swimming pool/gym
      • quick tour of city

      Problems/Considerations


      •  Modular seating
        • moving parts = more breakable parts
        • international powerpoint problems
        • no security for bags if want to sleep
        • children might jump
        • safety issues (OH&S)
      • Airport ‘hotel’
        • cost money
        • considerations for resourcing/staff (ie who washes the sheets)
        • take up a large amount of space
        • not necessary for domestic (shorter transit times)  
      • scavenger hunt style game
        • coordination
        • maintaining points for scavenger hunt
        • increase pedestrian traffic
        • might not appeal to all age groups
        • not possible/practical for PWD
      • entertainment area
        • finding space
        • people can damage
        • would it work like a library? rent games/books?
        • movie times/wait times
        • take business away from airline lounges
      • Forum
        • data sharing -how do i know i’m taking a specific flight
        • privacy concerns
        • need smartphone/tablet/device
        • introvert people
      • Swimming pool/gym
        • spa, sauna, massages
        • cost money?
        • maintenance, facilities, staff considerations
        • space
      • city tour
        • timing really important
        • cost? free?
        • security issues?

      Problem space 3

      (MT, SR, AI)

      Problem statement


      Passengers who are first time users of the airport need to know where to go, how to get there and how long it will take.

      Steps

      1.     Brainstorm possible solutions (2 ideas each)
      2.     Flesh out brainstorm ideas, detail steps in process (different 2 ideas each)
      3.     Outline any problems with ideas, especially for other user groups

      Ideas


            replace signs with monitors (electronic signs)
            expensive to replace signs
            easily updatable
            technical support
            lose electricity/computer fails = no backup
            physical locator/guide (like art gallery or app)
            airport would have to provide device or passenger have to own smartphone
            lost/damage (device)
            collection after use
            could airport track guide - where is the person?
             
            smartphone app with map/times
            need device
            development considerations
            hassel to download/setup (is there free wifi)
             
            search screen with directions (ie like shopping centre)
            crowding issues
            have to remember directions
            really clear
             
            driverless, programmed golf cart
            cost
            safety
            traffic
            space
            mobility
            good for elderly or PWD
            travelator with routes to gates
            expensive
            multiple routes?
            what about going other places (ie bathroom, newstand)
            navigation, if you go off, how do you find your way back
            no back-up if fails
            line markings on ground (like hospitals)
            confusing
            have to know system
            easily maintainable (not super permanent)