Mock-up video

Dream Squash on Youtube

Prototype of the interface

Initial video script

1. Teaser (scenes from the squash club)
2. Text on the screen: One is needed for running, two for playing squash
3. iPhone  makes a sound and there is a text on the screen: “Sorry my friend, can’t play with you tomorrow, I have a business trip. See you next time!”
4. Photo of a sad smiley on the screen.
5. Text on the screen: Squash is a high-speed racquet sport played by two players in a four-walled court with a small, hollow rubber ball.
6. Video of people playing squash.
7. Fingers on the keyboard, interface of the calendar is visible on the screen. Red booking is turned into yellow.
8. Birgit is sitting and is turning the racquet sadly.
9. Text: “I want to play squash. But no partner…”
10. Photo of a sad smiley on the screen.
11. Birgit got an idea.
12. Text or photo: Lamp will light!
13. Fingers on the keyboard, logging in. There comes a text on the screen: Welcome, Birgit! She is scrolling with the mouse. She finds that Juhan want’s to play.
14. Text on iPhone screen: “Birgit has answered to your request. Do you wan’t to play with her on 16.05, Wed at 18.00?” Accept!
15. Happy smile:)
16. Children playing squash (or two random)

User stories

Photos of paper prototypes

Paper protoypes

Summary of the participatory design session

Date and time: 23.02.2012, 14.00-16.00

Participants: 4 students, who at the same time have a full-time job. They represent scenarios

Scenario 1: Juhan’s friend cancels the usual squash playing time

• Does the system does or give something more besides only booking?
• That is real situation, because of different reasons there might be cancellations.
• How is the payment done?

Scenario 2: Birgit has free evening and wants to play squash

• Very similar persona with Juhan.
• Scenario has some timing errors compared to the Juhan’s scenario.
• Very realistic because of working and studying at the same time.
• Somehow not too much of activity, but there not many options anyhow.
• The system might give more information and still possibility to contact with the other person.
• To be sure that the partner has accepted to play there should be still a double confirmation.
• If there is less time before the booked time and the person is not online, there should fast way to confirm and notify SMS would do.
• To be sure that the both partners have gotten the booking and confirmation.

Scenario 3: Anni at work

• Not clear the role of the administrator.
• It is realistic that she is spending time in Facebook.
• Probably she should have more roles besides those activities.
• Most likely she is the technical support to the customers and explains how to use the booking system.
• If the courts have not been booked she could invite people who have not visited the club for a while.
• She can be someone who helps to find a partner if there are many people only looking for but not responding.
• She can see all the data about the bookings.
• She has the possibility to cancel the booking if something goes wrong.

Scenario 4: Roman uses mostly his iPhone

• Is he really interested of squash?
• Overall people use some kind of a smart phone not only iPhone, it should not be limited to one brand.
• Should the system show who is playing with whom?