DOMINOS DESIGN SPRINT

Interactive Design

Popular Pizza

Browsing through the internet on pizza,  came across the "top 10" pizza companies. As I read through the article, Dominos wasn't listed on there. Personally, when I think about wanting to eat pizza, Papa Johns, Dominos, and Little Caesars are what come into mind. Big cities like New York City, Los Angelas, Los Vegas, etc. have many pizza restaurants. In Colorado, we don't have a plethora of famous pizza restaurants and even if we did, I wouldn't go out to eat at a restaurant for pizza. I took a poll on instagram to see what percentage of my friends go eat out during a week. 72% of the people I know, eat out sometimes and the rest say they eat out just too often. Knowing majority of my friends are college students, the poll turned out completely different compared to "Americans' Dining-Out Frequency Little Changed from 2008" by Lydia Saad. Many of the statistics on young adults eat out more often than any other age group, however that was not the case amongst my friends. Asking my friends on Instagram, they replied with 38% go with Dominos for Pizza as their first choice. Even though my friends do not go out to eat often, they don't prefer Dominos Pizza over other companies. Which made me wonder, where Dominos was place in the "Top 50". Surprisingly, Dominos was placed high than the other Pizza companies and yet amongst my poll it said otherwise.

Group Evaluations: 

Evie Weeden: 4 

She has made the bass of the prototypes we are working on.

Kate Fox: 5

Leads the group well and tries to find time to work on the project as a group.

Joah Campbell: 4

Has always been to the meetings to help improvise and was able to suggest the 8-6-4 idea which we are going off of.

Hannah Lee:

4 Contributed to making iterations on the design layout and suggested many ideas before the final selection.

8/19/19

A design sprint is a five phrase framework that helps answering questions from the business through prototyping and user testing. The five phases of the design sprint are understand, diverge, decide, prototype, and validate. The sprints help the team to identify the goals and deliverables. This process encourages user-centered thinking, shared vision amongst the team, and to launch the product launch faster. During the first day of our class, we were informed on the Dominos design Sprint. We were to create an app where family and friends can easily decide what to eat. As we briefed over the end goal, we took a look at the requirements. At the end of the project we needed an app for Domino’s Pizza where the audience would buy the pizza and pay for. After forming our groups, Kate was unanimously chosen as our group leader amongst the members; Joah Campbell, Evie Weeden, Hannah Lee, and Kate Fox. We were handed out post it notes towards the remaining time of the class and we used the “How Might We’s”; How: Assumes opportunities exist, Might: says we don’t have to find something, We: is all about doing this together to brainstorm ideas, to create more ideas for the Domino’s design sprint. We had a time limit of 30 minutes to write as many ideas as we could. It was difficult at first because Dominos already had or started certain ideas, such as the hotspot to find your locations. As we kept thinking of ideas, we noticed we were very limited to a mobile app due to the requirements as we thought of food truck like ideas. Slowly but steadily we were able to come up with a few ideas. One of our few ideas was to bring in different pizza flavors from all around the countries. For an example; Korea has many different types of pizza flavors. They come up with pizza special to their own culture. The thought was to bring in a flavor from different countries to the Dominos in the U.S.A from time to time. Another idea we had was to put in a “Create your own pizza” flavor contest. Which would increase a certain extent of business and have customers enjoy their flavors being shared out to the world. Our group at first had a hard time trying to figure out what we wanted to incorporate into the app. When we were thinking about what exactly to put in, we initially chose the pizza flavor contest. We later then realized it did not meet the requirements needed for the project. On Day 3, we were able to change our idea realizing that we skipped one of the requirements. As a group we did not look carefully into the requirements and had to change it up later. As homework for the next class we needed to make up sketches for the app and look for ideas from other industries. Personally, I did not understand to a certain extent as to why we needed to have sketches. Majority of the sketches were bound to look the same is what I had initially thought. Since it was for homework, I sketched my ideas onto my iPad.

9/2/19

We had day 2 and day 3 on the same day and so there was not a lot to say for "Day 2" due to having the session 2 and 3 on the same day. I had my sketches on my iPad, however because we needed it on paper I had a difficult time trying to send it to the computer to print it out. We were given time to print sketch out the sketches for those who did not get their sketches drawn. While I was trying to send it to the printer, the class went out in their groups to vote on which sketches had good ideas. While the printer was having a hard time to print, my group was slowly getting ready to find a spot to do our voting as well. As my sketch finally printed, my group went up to the whiteboard and taped our sketches up to vote. The instructions were to vote on which aspects of the team members sketches were decent. As we talked about how we wanted to make our website work, the professor came up and told us we needed to have descriptions underneath our sketches explaining what each section of the sketch meant without having whoever explain the details. As soon as we wrote all of the descriptions underneath the sketches, the class went back inside of the classroom to start the second part of the class. The second part of the class, the group leader Kate was to sketch out the “final” sketch. As she sketched out the ideas onto paper, the rest of the team talked about which app we wanted to use and why. We tried to get started on the mobile prototype but was confronted with a few problems. Marvel was our first choice only because of how easy it was to use but we weren’t able to work on it all as a group. Only one person had access to edit the app. Invision and Sketchapp required money and extra downloads to work on the apps. We decided to use Marvel even if only one person could edit it. While we took a couple minutes to figure that out, we tried to work on the prototypes only to be stopped by the professor. The professors wanted the teams to present their ideas to the class. One by one the group team leaders would go up and present while our group only grew more anxious. We realized our idea was far off from the needed requirements. Flushed with anxiety, Kate thought if any last minute adjustments for what she could say to the class. 5 minutes before class ended, a group finished their presentation and the professors stopped the presentations. We were the only group that did not present our ideas however, it was a small advantage for us to revise our ideas. After the class had ended, we had a small discussion on what we could change. Since our classes are more night time classes, it was very late and a lot of the trains had stopped running. A team member needed to leave as soon as possible and so we decided to meet up earlier for the next class and get some ideas out.

9/15/19

Starting our prototype was difficult due to the project being a group project. The app we wanted to use was called Marvel. You can work on one prototype through Marvel by paying a certain amount for each person. We were not willing to pay for being able to work on the same prototype. We decided to try out the other apps but they required to download other parts to work on the prototype or they required money. In the end, we used Marvel to build our prototype off of. Building the prototype was a little difficult since it was a little difficult for our team to meet up and work on it all together. We sent texts about how we should create the prototype and Evie, who was in charge of building the prototype had a difficult time trying to incorporate all of the ideas. Evie did a wonderful job building the base colors and the base of the app layout. Kate and I wanted to see if we could tweak a bit of it, but it did not turn out as nicely as we wanted it to. I wanted to change the way the Domino's Pizza app could be laid out however it was difficult to make the app still feel like a pizza app. When I changed out the layout of the prototype, it did not feel like a pizza app and so we kept the basic layout the same. While we finished up the prototype, I was not content with the “finished” product. I thought it looked very similar to the original layout of Domino’s app. We changed up the simplicity but I don’t think we really did much for the app. When I went through the app, I felt confused to what the app was trying to tell me what to do. I noticed we forgot to inform the user how to use this app and what this apps intentions were. Even though I was part of the design sprint for Domino’s, I was confused as a user. I felt as though we needed to work on much more but our team left it as it was because we were rushed into another project. This project felt halfway done and did not feel like anything was completely finished. We revisit continuously and try to fix more of it as we speak. The more we fix the prototype, the better the prototype becomes however, we still have a lot to fix but we are content to an extent as of right now. Link to the prototype: https://marvelapp.com/453c5g6

9/16/19

The outcome of your prototype in my opinion was unsatisfactory. I had personally wanted the prototype to look a little more than the Domino's original look of the app. We originally had the ingredients laid out on the app all in one page, however as we asked individuals on what they thought, they thought it was too clustered and it looked too complicated. When we took a look at it afterwards, we saw why it looked so clustered. We fixed it to look similarly like Papa John's Pizza mobile app. It was much simpler than what Dominos has right now. Even though our outcome isn't the best, our prototype is much better than it was at first. As we revised it over and over, the prototype tended to look more simpler and concise. Personally, I am not content with the way the ingredients are laid out as it is. The cheese ingredients when shown are listed in the middle exactly how the meat section is showed in the picture above. The three sections of ingredients are all shown in the middle section which makes it a little difficult to understand what is going on. The users who participated in the testing was slightly confused. The user I tested on was very confused. She wasn't exactly sure what was going on until I had to explain in detail what she had to do. As a designer, it was a little upsetting to know that the user did not know what to do and needed to be guided on how to order the pizza. In the end, we had to conclude our prototype to an extent to the limit of time. For the amount of time we had to prototype was enough time to get the basics for the app down. If I had some more time I would definitely try to fix the way the ingredients are shown and can be selected by the user. I would add a page where it explains what the game is by showing some of the steps before the user goes diving into the "game".

​

Challenges: 

The most challenging part of this project was trying to work on the prototype together as a group. It was difficult for us to meet up in general other than the set class time. We all had part time jobs and we were working close to midnight. The other part was the confusion on whether certain parts of the projects were individuals or as a group work. We had a lot of confusion as to what the project wanted us to do in some grey areas. There wasn't a day 2 since it was combined with day 3. They was no day 5 since it was combined with day 4. There were a lot of parts where there weren't set days for. 

​

Learned:

This project confirmed, group work is difficult to do especially when there are not a lot of options for you to work with. Personally, this group project was difficult due to the difficulty of understanding how the professors wanted it to be laid out in general. For future reference, I would have loved to know that we were supposed to have posted on our blogs for each day rather than having to write them all out in the end and having to recall everything we did that day to right out our blog post. The reason why the blog post has meaning when it is written the day of rather than at the end. 

​