Sunday, November 28, 2010
Friday, November 26, 2010
Tuesday, November 23, 2010
Usability Analysis I
Key Issues Raised in First Usability Test
1. Orientation of “Parent Menu”
a. Reach – some users may not be able to reach the menu in the middle of the table.
b. Viewing – if the menu can’t move, users will be staring at the menu upside down or, if the menu is too far away, the users may not be able to see the contents.
i. There will no longer be a Parent Menu, however, there will be one menu for the “Mood” options, so the problem is still relevant.
ii. Users will be able to drag the menu.
2. How do we know if a menu can be dragged?
a. Tabs are not a good enough indicator.
i. It should be an intuitive design.
ii. When it appears it could move or glide slightly, to encourage users to touch the menu and explore.
3. How to indicate scrolling on the menus?
a. Without any indication, the quantity arrows next to the menu items appear to be for scrolling.
i. A bar on the right-hand side of the menu would allow users to see that the menu has scrolling capabilities
ii. The bar will also show users how far they can scroll down/where they are on the menu
4. Arrows next to menu items are confusing.
a. They are meant to increase and decrease the quantity of the menu items, but appear to indicate scrolling.
i. A “+” sign on the upward arrow and a “-“ sign on the downward arrow will indicate that the arrows are for increasing and decreasing the quantity of the menu items.
5. Nutrition facts, ingredients, and photos of the dish need to be presented differently.
a. This additional information that is presented in a way that creates too many unnecessary pages. Also, the navigation bar for these options is presented too many times.
i. The information could be more easily organized in pop up windows. The navigation buttons are located only below each menu item and do not reappear in the pop up windows.
6. When selecting menu items, where do they appear?
a. They currently appear in both the Parent Menu and the Individual Menu, but the Parent Menu concept has been scrapped.
i. The items will appear in the individual menus under two tabs: (1) My Order and (2) Entire Order.
7. Payment issues. Where to pay? How to pay?
a. What if you’re paying cash?
i. Option to call a “Table Attendant” to take the cash and bring you your change.
b. Where do you slide your credit card?
i. On the side of the table. Each user has a slot to insert their credit card on the edge of the table where they are sitting.
8. What is the table shape? How many people does it seat?
a. These are important decisions that determine many decisions relating to the layout and functionality of the
i. The table will be rectangular – more practical for restaurants for flow of traffic.
ii. The table will seat a maximum of six people.
9. “Mood Menu” orientation
a. Will everyone be able to control the menus? Individual “Mood Menus” for each user?
i. There will only be one Mood Menu that everyone at the table can bring up in order to change the ambiance of the table. Multiple menus may cause confusion.
Tuesday, November 16, 2010
Contextual Interviews
SUMMARY OF CONTEXTUAL INTERVIEW (1) WITH POTENTIAL USER (NI)
The first potential user, referred to as NI, was interviewed on October 24, 2010 at the Hampton Chutney & Company (the case-study restaurant). The interview was conducted over lunch and lasted about an hour. I (AQ) conducted the interview, while a friend of mine; Natasha Butt assisted me, taking detailed notes (the full interview is made available below).
NI is in his early 20s, and is a student of medicine. He has owned an operating system since the age of twelve, and has been highly exposed to technology, but posses an average understanding of it. NI lives and schools in Manhattan, and has an active social life. He has visited the case-study restaurant several times and is very familiar with their menu. He is also well traveled and welcomes new experiences.
During the interview, I lead NI toward the idea of being able to place an order from the table directly to the kitchen, without having to use waiter/waitress mediation. It was then that he revealed that he has used a digital menu before, which allowed him to do so. Asking him to describe the device and the experience of using it, he associated it with a kindle. A device placed on a turntable in the center from which each customer at that table could place their order. He admitted that it was a very self-explanatory process, but lacked information about the items. Nevertheless, he was excited about the concept, saying that it just needed to be further developed.
We discussed the digital menu that NI and used, and brainstormed other physical formats that the device may take. He prefers that the menu be stationed at the tables, as it would defeat part of its purpose if it needed to be brought to and taken away from the guests. He was most intrigued by the idea of embedding the device into the table, but was certain that there should only be one menu per table, explaining that placement according to the seating may become problematic if extra chairs are added to the table.
When discussing other functions that the device could perform, such as gaming activities, entertaining, ambiance, he seemed to be uncertain. He said it was a possibility, but he would prefer that the menu simple be just that, mocking it by saying, “it’s a menu, not Dave and Buster’s!” The idea of customizing the ambiance through music and lighting was plausible only if the party had a private area or room in which to do it, and which otherwise disturb the other guests.
After brainstorming further, NI suggested that the menu could perhaps allow the guests to leave reviews about the restaurant and their items. When asked if that would mean that a keyboard is also provided, he began rethinking the idea since he thought it was beginning to complicate the device. NI suggested that perhaps instead of writing out a review, the guest could simply give ratings.
I asked NI of his thoughts about the menus being able to remember the customer’s order for his/her next visit. He welcomed the idea, but pointed out that that too will require a keyboard, shunning the idea. After rethinking it, NI stated that the keyboard will only be needed to input the customer’s identification, and proposed an alternate way of doing so by fingerprint reading!
In general, NI was keen about the idea, and preferred that the device serve only the purpose of a menu.
CONTEXTUAL INTERVIEW WITH POTENTIAL USER (KM)
AQ: What do you think about their menu?
NI: It’s appropriate for this type of restaurant.
AQ: I agree, but do you think it provides customers with information that makes placing their order easier?
NI: Well since I’ve been here many times, I know a lot about their food, but I can see first-timers wanting more information from the menu. It leaves out a lot of information. But I also think it is positioned well and the big writing means that you can read and decide what you want to order while you wait in line.
AQ: What if you did not have to wait in line to place your order, and could simply do it from your table?
NI: Like regular restaurants?
AQ: Yes.
NI: In that case the menus would have to be at the tables too.
AQ: Do you think by doing that, the restaurant would need to also provide the services of waiters and waitresses?
NI: Yea.
AQ: Do you enjoy being waited on?
NI: Well, isn’t that the point of going out to eat, so you can be served… someone bring food to you.
AQ: Does that imply that you do not particularly need them when actually placing the order?
NI: Sometimes I do need to ask them questions about the different items… sometimes I want to discuss my choices with them, and ask them questions.
AQ: Can you think of an instance when you wish you were not being waited on?
NI: Yea! When I get the real bitchy ones! Sometimes they have an attitude, sometimes they aren’t attentive enough, and sometimes they rush you. The ones with attitude reflect negativity on the entire restaurant, and then you don’t enjoy being there. Sometimes I feel like giving them a piece of my mind… I could have done that myself!
AQ: You said, “I could have done that myself,” do you mean placing the order?
NI: Yea.
AQ: What if you could place the order yourself, without having to deal with a waiter/waitress?
NI: Do you mean like this place, ordering at the counter yourself?
AQ: Not really, I mean placing your order from your table, which would directly go to the kitchen?
NI: I’ve actually done that! This place in Virginia, I think it was call High Up… they had digital menus!
AQ: Really! What did you think about that concept?
NI: It was really cool, but I got stuck.
AQ: Stuck? How so?
NI: Well, we didn’t know what to expect when choosing… especially because we didn’t like what we ordered.
AQ: Why was that, did the menu not have a description of the items?
NI: Yea, they did, but we still weren’t exactly expecting what we got.
AQ: Do you not think that you might have experienced that even if you had a waiter describing the item to you?
NI: Yea, true. That does happen sometimes when you even have a waiter helping you.
AQ: Do you think it might have been helpful if the digital menu had pictures of each item?
NI: Yea, it would have… that would have definitely solved it.
AQ: Can you describe the digital menu you used?
NI: It was like a kindle; touch screen, about the same size, and I went through the pages.
AQ: Was there a digital menu for each customer?
NI: No, there was one per table. It was placed at an angle on this central turntable, so people would place their own order. When everyone was done, the menu would verify the entire order and send it straight to the kitchen.
AQ: Did you know how to use it, or did you have to be given a demonstration?
NI: No, the hostess just introduced the digital menu to us as she walked us to our table. Then, the rest was pretty self-explanatory.
AQ: Did you enjoy the experience of ordering through such a menu?
NI: Yea, it was pretty cool. Plus, I didn’t have to leave a tip!
AQ: Would you like to see more digital menus in restaurants, if they were better developed?
NI: Yea, anything can work well once its developed.
AQ: Do you think that there should have been more menus at each table, one per person?
NI: No, because that would take up too much space. And even if it weren’t built onto the table, it would mean that a waiter would have to come give you the menus and then take them away from you once you’ve ordered. I like the way that restaurant had it.
AQ: The menu you used was built onto the table, right? What if it was embedded into the table?
NI: Yea, but then the screen would get dirty with the food on top of it. But that would be hot!
AQ: The actual device would be under a protective, transparent surface, so even if the table did get dirty it would simply have to be wiped clean without affecting the menu.
NI: I don’t know that much about technology… I’m not a digital kind of guy, so I wouldn’t understand its technological side of it.
AQ: Do you think other people like yourself, who are not technology savvy, would be able to use the digital menu too?
NI: Yea, why not. I said I don’t like digital stuff, or gadgets, but I still own an iPhone because it is designed so well. They have made it so easy for people. It probably is a very complicated technology, with it’s programming, but it’s the easiest thing to you. So, I guess it depends on how it’s designed.
AQ: Since the technology would already be present, do you think it should be utilized to perform functions other than being a menu?
NI: Hmm… it could talk to you, but I don’t think it should be used to do anything else.
AQ: What if the menu screen could be used for other activities, playing games for example.
NI: Then it would become a Dave & Buster’s! I want to enjoy my meal and not have any distractions… unless, that was the theme of the restaurant – eat while you play games. But it would have to be a place you go to eat on your own.
AQ: What if you could use the device to create a customized ambiance for your party?
NI: Music?
AQ: Sure.
NI: It would be disturbing, since the people besides me would also be playing their own music and it would disturb me. Their music would clash with mine. This would only work if each table had their own party room, in which they could play their own music without bothering the other people at the restaurant.
AQ: Can you think of any other uses for the technology?
NI: It could read my mind! Haha! I would like something sweet and warm… haha! I think the menu should just be a menu.
Maybe it could give you the time in which your food would be prepared, and if there were a delay, it would update you.
What if I could go onto Zagat.com and rate the restaurant?
Maybe it could give you the time in which your food would be prepared, and if there were a delay, it would update you.
What if I could go onto Zagat.com and rate the restaurant?
AQ: Would that require the menu to have Internet access?
NI: Yea, but it would be very limited. It only goes to that page, so you don’t get distracted and start checking your email.
AQ: To write a review you would need a keyboard, right?
NI: No; that will be too much. Maybe you could just rate it using stars.
AQ: Are you required to sign in to review your experience?
NI: Hmm… maybe. But you don’t want to give a restaurant your email address. That’s giving out too much information unnecessarily.
AQ: Perhaps you could simple create a user name without having to enter your email address.
NI: That could work.
AQ: However, you would still need a keyboard, right?
NI: Hmm… no keyboard, its too much. Plus that would mean you would be spending too much time thinking of a username and trying different ones out. Also, people could be making offensive usernames and the restaurant would not be able to control it. They could probably use fingerprint reading instead! The screen is already there.
AQ: That is a possible solution. Also, now that the system is able to recognize you, could it remember all that you ordered for when you returned?
NI: That would be hot! But now I’m double thinking the fingerprint reading idea… maybe, its too much information to be giving out unnecessarily. Maybe we should keep it simple.
AQ: Do you have any final thoughts about the concept of digital menus?
NI: I love it! When I used it the first time, I kind of like it… maybe 80%, but once it has been developed and all the features we spoke about are incorporated, it will be perfect! I can see it everywhere! Soon it will be in every restaurant in either a small way or it will be there entirely. I love it; it’s exciting and new.
SUMMARY OF CONTEXTUAL INTERVIEW (2) WITH POTENTIAL USER (MK)
The second potential user, referred to as KM, was interviewed on October 26, 2010 at the Hampton Chutney & Company (the case-study restaurant). The interview was conducted over lunch and lasted about forty-five minutes. I (AQ) conducted the interview, while a friend of mine; Natasha Butt assisted me, taking detailed notes (the full interview is made available below).
KM is a banker in his early 40s, with average exposure to and knowledge of technology. He has owned and used operating systems since the age of fifteen, and is most fond of Apple’s interface usability. He has owned an iPhone for the last two years and appreciates its use of touch screen interfaces. MK lives and works in Queens and often dines in Manhattan. This was his first visit to the case-study restaurant.
KM foresaw the potential of a digital menu very early in the interview, before I even had the chance of introducing the idea to him. His initial vision of this concept was a virtual screen that pops open in mid-air, referencing the movie “Minority Reports”. He said that it was an approach that he could envision being realized within the next twenty years. When asked to visualize the digital menu using available technology today, he leaned towards the idea of touch screens.
He acknowledged that this method would benefit customers, giving them full control in the decision-making process, although he was highly concerned about the loss of employment opportunities for waiters/waitresses. However, he understood that this was a direction many services were already embarking, quoting the self-checkout counters at supermarkets.
When asked to describe the digital menus and its features and capabilities, he stressed that it should not be hand held since it would be inconvenient. The dialog revealed that it should be embedded within the table. He envisioned a ‘parent’ menu in the center of the table from which each customer could drag a copy for themselves, or to share, in front of them. He described the menu to have pages with a description of each item, its ingredients, nutritional facts and pictures. He also mentioned having a preview of how it was made. With this information, the customer will be able to make their best choice and place the order directly to the kitchen.
When discussing other functions that the device could perform, such as gaming activities, entertaining, ambiance, he seemed to be uncertain. He said it was a possibility, but he would prefer that the menu simply be just that, and perhaps only perform activities that related to the actual experience of dining. These included paying the bill by swiping/scanning a credit card, watching their meal being prepared, tracking the process of preparation. The idea of customizing the ambiance through music and lighting was plausible only if the party had a private area such as a booth in which to do it, and which otherwise would be a futile feature.
KM also approved the idea of customers leaving reviews, and allowing the menu to remember what was ordered once that customer signed in. He said that once a favorite item was marked, the customer would be given other similar suggestions the next time he/she returned.
Overall, MK was excited about the concept, saying that it was possible to execute and that it would make for an enhanced dining experience for anyone at any restaurant. He also took into consideration the older generation, saying that if the menu is designed correctly it should not be an obstacle for them, referring to his mother using Apple’s iPad with great ease.
CONTEXTUAL INTERVIEW WITH POTENTIAL USER (KM)
AQ: What do you think about their menu?
KM: It’s all right, nothing to write home about… It could be a bit difficult to read.
AQ: How do you feel about not having a waiter or waitress?
KM: Well, I think I’d prefer the help of one at this restaurant since they are serving specialty foods, and I want to ask consult my choices with someone.
AQ: Would you prefer ordering from your table, using the typical menus?
KM: Hmm… Well, it would be pointless having menus at every table if there aren’t any waiters to take down my order. I would need to place my order from my table and it magically gets delivered directly to the kitchen. It would just pop up in front of me, like a digital menu!
AQ: A digital menu, what do you mean?
KM: It would be the coolest thing! A screen would pop up in front of me, like a in that movie… I would just pick things from this virtual screen and the information would be delivered directly to the chef! We’re in the 21st century! We wouldn’t need waiters… but it would get a lot of people fired.
AQ: Do you think our technological skills are far from virtual screen?
KM: Not at all! Give it another 20 years.
AQ: Perhaps we could resort to existing technology until we get there, such as touch screens?
KM: Yea, that’s doable - touch screen menus! But maybe we are too used to being served by waiters? I don’t know if it’ll be such a great idea after all.
AQ: There are a lot of services today that eliminate the human factor, such as ticketing consoles, digitized desk-clerks at hotels, even electronic backing.
KM: Yea, even the self-checkouts at supermarkets. They are more efficient and faster… except when a problem occurs, then there is an annoying delay… its not that people are always incompetent, some times the systems aren’t very user friendly. Maybe they should let Apple design everything!
AQ: Do you think the menu should be more like an iPad?
KM: Yea, its easy, simple… even my mom can use it! But I don’t think the menu should be hand held. They should have it on the table.
AQ: On the table, or in the table?
KM: On or in, as long as I don’t have to hold onto it… I wouldn’t want to have to deal with it. It should be discreet.
AQ: Could you describe what the digital menu would look like, or do?
KM: Well, it would have pages assorted into two sections, lunch and dinner. The relevant section would appear depending on what time you’d come. Then suppose I choose grilled chicken, it would give a description of it, its ingredients and its picture. Maybe it could even give me a preview of how the chef prepares it!
AQ: What other features could you incorporate?
KM: Hmm… what if its voice activated? But that might complicate things... I might need to keep screaming into it, trying different accents, hoping that the correct order is registered.
AQ: How many menus do you imagine per table? One for the entire table to share, or would you prefer that each guest have their own?
KM: I think one per guest.
AQ: What if an additional chair had to be added to the table, then what?
KM: That could be a problem… Well, there could be a parent menu in the center of the table, which is permanent, and each guest would drag a copy out from it and place it in front of them. That way you can drag out as many menus as you want, and you could even choose to share a menu.
AQ: Since the technology is created for each table, could it be utilized for other activities besides a menu?
KM: It could produce your bill at the end of your meal! All you’d have to do is swipe, or scan your card.
AQ: Could the screen and its interactivity used for entertainment purposes?
KM: Sure! Listen to music or watch movies… maybe the restaurant could even charge for the movies… But who watches movies at a restaurant? No, it’s a bad idea.
AQ: What about games? Would you be able to play games with your party, or even by yourself?
KM: Yea, like chess or something? Sure. But I think that’s still a bit much. You’re out for dinner... let’s keep things simple. It’s a menu after all; you don’t want to complicate it. But maybe you could offer it? I think it’s a matter of preference. I don’t know… I have mixed feelings.
AQ: What about mood? Are you able to customize an ambience for yourself and your party?
KM: Like music?
AQ: Both music and lighting – perhaps the table emits certain colors to create a mood of your choice.
KM: But that would mean that you’d want your own space too, like a booth or something. Otherwise, I don’t think it’ll work.
AQ: Would you personally prefer that the devise be used for activities, entertainment or ambiance?
KM: I like it simple. Keep it just a menu. I think any added features should be associated to your actual restaurant experience, such as viewing and paying for the bill. Maybe it could even give the cook-time, or the preparation stage your meal is in, like Dominos! When you order online from Dominos, it tracks the progress of your pizza, telling you that Paul is creating your pizza, your pizza is in the oven, your pizza is on its way to your house, etc. Maybe even show the chef in the kitchen preparing your food – it would be like digital hibachi!
AQ: What do you think about leaving a review?
KM: Yea, that would be a good idea!
AQ: Does that mean you would need to create a username and sign in?
KM: You could, or you could just write an anonymous one.
AQ: Either way, you would require a keyboard, right?
KM: Right. But that shouldn’t be a problem.
AQ: From all that you have described, can you outline how the digital menu is more effective over the traditional print menu?
KM: In comparison, the traditional menus are extremely dull and boring, digitizing it adds a lot of excitement into the simple experience of ordering food. The customer has full control over their order and decision-making. Also, this means that they will not have to deal with waiters with attitudes, and nor with tipping! The digital menu provides a more thorough description with ingredients and pictures. And the fact that the menu remains there is great! So if you do want to add something, you can do so immediately, without having to call on someone and waiting. Plus, you won’t have waiters running around the place… it would be more calm, nor would you have them constantly pestering you if you’re done with your meal or not! I love it! Digitize those menus!
Personas
POTENTIAL USER PERSONA 1: NI
- Name: NI
- Age: 23
- Education: Student of medicine, New York University, Manhattan.
- Job: Student. NI volunteers at a hospital to gain experience in his field and is also a freelance model. Previously, he has worked with his father in a family car dealership business.
- Major Responsibilities: NI’s major responsibility is being a student and focusing on the career he is pursuing. Living on his own in the city, he is also responsible for his bills and daily expenses.
- Family Status: NI is from an upper class family, who own many businesses and properties around New York.
- Exposure to Technology: NI has owned an operating system since the age of twelve, and been exposed to and welcomes technology. He however does not have a great understanding of the programming behind the technologies
- Goals in Relation to Interface: NI currently uses traditional print menus at restaurants in order to place his order, whether it’s through a waiter/waitress or directly at the counter. He often also places orders over the Internet. NI has used a form of a digital menu before, where he was able to place his order directly to the kitchen, while seated at his table.
- Tasks in Relation to Interface: NI needs to essentially place his order using the interface I am designing. The menu alone should provide him with all the information he needs to make the best choices. He should be able to view the description, ingredients, and nutritional facts of each item and place his order directly to the kitchen.
- Environment: NI lives and studies in lower Manhattan. He is surrounded by eateries, which he takes advantage of daily as he lives alone. He loves to experience new foods and trends. The case-study restaurant, Hampton Chutney & Company, is located close to NI, and he has dined there several times.
- Persona Priorities: “I love to eat out and try new foods! I love the experience of enjoying a good meal with good company and no distractions”.
POTENTIAL USER PERSONA 2: KM
- Name: KM
- Age: Early 40s
- Education: KM attained his college degree from Baruch University in Manhattan, where he later pursued an MBA.
- Job: Bank Manager at a CHASE Bank in a Manhattan branch. KM has been with two banks prior to CHASE, beginning his career as a clerk and working his way up. He resides in Queens with his family and commutes to work everyday.
- Major Responsibilities: KM is responsible for his wife and children. Both him and his wife earn a comfortable income.
- Family Status: KM is from an upper-middle class family. He is a hard working, self-made man.
- Exposure to Technology: NI has owned an operating system since the age of fifteen, and has been exposed to and welcomes technology. He has an average understanding of the programming behind the technologies. He acknowledges the exponential advancement of technology, and predicts that in another twenty years, virtual reality will be an integral part of out lives.
- Goals in Relation to Interface: KM currently uses traditional print menus at restaurants in order to place his order, whether it’s through a waiter/waitress or directly at the counter. He rarely places orders over the Internet. He welcomes new technology, and eager anticipates the future.
- Tasks in Relation to Interface: KM needs to essentially place his order using the interface I am designing. The menu alone should provide him with all the information he needs to make the best choices. He should be able to view the description, ingredients, and nutritional facts of each item and place his order directly to the kitchen.
- Environment: KM lives in Queens with his family and commutes daily to mid-town Manhattan for work. For lunch, he usually goes to local delis or nearby cafes, where he places his order over the counter. Most Saturdays, KM will take his family out for a sit-down dinner at a restaurant in Queens. He had however never been to the case-study restaurant, Hampton Chutney & Company.
- Persona Priorities: “I look forward to the Saturday dinner with the family, its an opportunity for all us to share the experience, relax and simply enjoy each other and the”.
Case Study Restaurant
The Hampton Chutney & Company is the ideal case study restaurant, located in SoHo, Manhattan. The area and restaurant attract a hip and modern audience, who are keen and willing to explore new, unique trends.
This quaint and chic restaurant serves South Indian cuisine over an open kitchen counter. The nature of the cuisine, coupled with the restaurant’s serene and inviting ambiance, encourages guests to eat in. Such an environment only increases the usefulness of digital menus.
Pictures of the restaurant and their menu can be viewed below.
Proposal
Project Title:
The Digital Menu
Team Members:
Aisha Qureshi
Required Skills:
Working alone, I am required to solely tackle all relevant responsibilities regarding this project. It is therefore vital that I thoroughly plan, prepare and manage the tasks, enabling me to play multiple roles. The roles include being an innovative problem solver, who designs an indispensable user interface. I must also exercise acute observational skills to scrutinize the design for sustainability, which translates into effortless user experience. I will need to be analytical, constantly producing, testing and revising prototypes in order to create the most efficient interface. Once the prototype and usability is perfected, I will need to then treat it with appealing and appropriate graphics.
Motivation:
The concept behind digital menus is to facilitate a thorough and efficient ordering process for restaurant customers. The digital menu will enable customers to browse through the menu easily, while giving them the option to view photographs of the meal, and it’s ingredients and nutrition facts.
The interface will also allow customers to order their meal directly from the menu, without having to deal with a waiter/waitress. The interface will however, provide the option for calling open a human waiter/waitress. This concept will also benefit the restaurant itself, as it will gain from the significant employment cuts. Another aspect of this concept that caters to the restaurant itself is the ability to update the menu without having to tape over or cross out items that are no longer served.
I understand that human interaction is a part of the restaurant experience, but some restaurants, where there is an open kitchen concept or where order are taken over the counter, already exclude the human factor. In such cases, the digital menu will only refine their service philosophy. Additionally, I expect restaurants in the near future to eliminate human mediation entirely, similar to many services today (ticketing counters, hotel desk clerks). Another concern may be the cost of implementing such technology on every table at the restaurant. This does not necessarily stand true, since technology only gets better and cheaper, and in the mean time, restaurants could resort to creating revenue by hosting advertisements when the devise in not in use.
Approach:
I will need to first allocate a specific restaurant, which I can base my study upon. The Hampton Chutney & Company is the ideal case study restaurant, located in SoHo, Manhattan. The area and restaurant attract a hip and modern audience, who are keen and willing to explore new, unique trends.
This quaint and chic restaurant serves South Indian cuisine over an open kitchen counter. The nature of the cuisine, coupled with the restaurant’s serene and inviting ambiance, encourages guests to eat in. Such an environment only increases the usefulness of digital menus.
I will need to study the current menu, examining its format and location within the restaurants, how guests interact with it, what information do guests look for, and whether further inquiry is needed. I would also need to survey how much, if any, help is needed from the staff during the ordering process, as well as, monitor the wait time in the ordering line. Additionally, I would also need to consider the restaurant’s needs and requirements from the menu.
Once I thoroughly research the restaurant and their menus, the guests and their experiences, can I evaluate the information to incorporate it into an effective interface, and design the interactive prototype.
Scope:
At the end of the term, I shall deliver a prototype of a digital menu that is not only customized for the case study restaurant, but will also fulfill the general needs for many other restaurants. The prototype will consist of the menu pages, and the sequence of pages that are required to access the other options the interface offers.
Resources:
I need conducted behavior studies of guests and evaluated the requirements of the restaurants, in order to translate them into a significant and effective interface. Once I have gained a better understanding of the interface, shall I be able to develop a prototype and present a plan for required equipment and materials.
Subscribe to:
Posts (Atom)































