Scenario Testing

Once we had the core of our final established, we decided to do a scenario test. Marking out an area identical to our example bus stop, we decided to roleplay as patrons.

Scenario Testing

Drawing from the knowledge we gained in field testing we could easily see what the worst case and best case scenario would be. The best case would be that patrons start lining up orderly even before the bus arrives, once the bus comes, seated patrons (usually those who arrive at the stop first) would be closest to the door and board first, other would file orderly along the floor marking. Worst case scenario would simply be that users disregard the installation, or intentionally cut the queue (eg. climbing over the seat or walking around the front of the bus pole).



I think the greatest advantage of this method is that it can give a similar result to field testing without the need to observe strangers. The disadvantage is that it can limit the outcomes a little. For example, in the field test, we saw a patron begin to cut in front of the bus pole, but upon seeing the queue, walked the full way around the bench to line up. Or for situation where more than 1 bus arrives at the same time, or bus stopping in the wrong area. Overall I think field testing is better, but when that is not always an option, it scenario testing is a great accompaniment or fair substitute.

Mapping patron’s BEFORE our installation (When waiting for bus vs when bus arrives):

Mapping patron’s AFTER our installation (When waiting for bus vs when bus arrives):



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s