P3: Refined Prototype – Spoon Fight (Restaurant Rivals)

Spoon Fight

Team Members: Paprika, Emma, Olu, and Saharat (Game)

Playtest Dates: November 11 and November 15, 2026

Refined Prototype: Play Spoon Fight – November 15 Version

Previous Prototype: P3: Playable First Draft – Restaurant Rivals

Our Prototype and Playtesting Process

For this iteration of Spoon Fight (formerly Restaurant Rivals), we focused on making the game clearer, more strategic, and more representative of the challenges of running a restaurant.

In our game, two former business partners compete to win the Golden Spoon. Over five days, players manage their own City or Countryside restaurant by making decisions about advertising, staffing, purchasing food, and serving customers. Their goal is to outperform their rival through financial success and reputation.

Our previous prototype already included competitive shopping, advertisement cards, restaurant service, and unexpected events. However, we were still unsure whether players understood the consequences of their decisions and whether the competition involved meaningful strategy rather than simply clicking quickly.

To investigate these questions, we conducted two in-class playtesting sessions on November 11, followed by an outside-class playtest on November 15.

  • November 11, in-class playtest 1: Jessica and Xingyi tested the game and provided feedback on advertising, the market, restaurant service, and overall usability.
  • November 11, in-class playtest 2: Judy and Alex played the game and discussed restaurant management, competition, and their gameplay strategies.
  • November 15, outside-class playtest: Emma playtested with her friend Alice. This session helped us understand how someone approached the game, what strategies they discovered, and which mechanics still felt confusing or unrealistic.

We used these observations to revise several mechanics and screens in our latest prototype.

What We Learned From the Playtests

1. Players needed to understand the consequences of decisions before making them

One of the clearest problems was the order of gameplay.

During the first November 11 session, Jessica pointed out that advertisements came after players had already made staffing and food-purchasing decisions. This made it difficult to plan for the actual number of customers. She was also reluctant to purchase advertisements that would attract more customers because she could no longer adjust her restaurant’s capacity.

This feedback made us reconsider the relationship between different stages of the game. Advertising, staffing, and food purchasing should not feel like unrelated activities. They are connected decisions, and players need opportunities to plan around those connections.

Our change: We moved the advertising stage to the beginning of each day, followed by staffing and the market. Players can now consider their potential customer demand before deciding how many employees and plates they need.

We also clarified that blue advertisement cards affect the player’s own restaurant, while pink cards affect their opponent. The interface now tells players they can purchase multiple advertisement cards if they can afford them.

Figure 1. Before and after: The landing page, advertising instructions

Figure 2. Before and after: The landing page, advertising instructions

2. The market felt competitive, but not necessarily strategic

Both Jessica and Xingyi felt that the market involved too much repetitive clicking. Jessica described purchasing ingredients without fully understanding how much food she needed. She also experienced a delay of approximately 10–15 seconds compared with Xingyi when entering the market, which raised a fairness concern in a first-to-click competition.

Alice noticed a related issue during the outside-class playtest. She discovered that purchasing as much food as possible was often an effective strategy, particularly because rushing food during service could become expensive. She also suggested that the market would be more interesting if players had to think about the possibility of buying too much food, not just too little.

One question we discussed was whether the market should become an auction, where players bid for ingredients rather than racing to click them.

Our change: For now, we retained the simultaneous market but changed the purchasing options. Instead of every market item representing a single plate, players can now choose bundles with different quantities. The updated screen shows how many plates each bundle provides, their prices, and whether the food arrives tonight or tomorrow.

We also improved the information panel showing how many dishes players can prepare and how many plates are still on their way.

Our intention is to make the quantity and timing of purchases more meaningful. However, we still need to test whether this creates better strategies or whether the market remains mostly a clicking race.

Figure 3. Before and after: The market now offers bundles of different sizes and clearer information about available food and delivery.

3. Players enjoyed managing the restaurant, but the simulation did not always reflect their expectations

The service simulation generated several interesting comments.

Jessica and Xingyi expected restaurant tables to be reused as customers finished eating. They also pointed out that restaurant capacity depends on more than the number of tables. Staffing matters because employees can only serve a limited number of customers at once.

We also received feedback that the service screen contained too much information and that the simulation moved too quickly. This sometimes made it difficult for players to understand what was happening or respond to customers in time.

Alice raised an important question about realism. Before playing, she described restaurant management as difficult because owners must attract customers, hire staff, follow regulations, and handle unpredictable demand. After playing, however, she said:

“Based on this game, I think it must be super easy, I did really well.”

We found this particularly interesting because our goal is not simply to make players successful restaurant owners. We also want them to understand the trade-offs and uncertainties involved in running a restaurant.

Our change: We clarified the relationship between staff and their assigned service areas, made table reuse more explicit in the instructions, and revised the costs and consequences of food shortages.

We also changed rush-food prices to $5 in the Countryside restaurant and $6 in the City restaurant. These costs are half the corresponding meal revenue. Our intention is to make rushing food a meaningful decision: players give up part of their potential profit to serve customers and protect their reputation.

4. Reputation needed to matter throughout the game

Another issue was how players understood the relationship between money and stars.

Jessica was unsure how the final winner was determined. Other players questioned whether reputation was actually worth protecting, especially when they could earn enough money through normal restaurant operations.

During the outside-class playtest, Alice compared the cost of rushing food with the value of stars. This showed that she was thinking strategically about the game’s economy, but it also revealed that our rewards and penalties needed further balancing.

Our change: We revised the reputation system so that stars have a financial impact at the end of each day, rather than only contributing to the final score.

In the revised rules, serving every customer earns one additional star. Leaving one to three customers unhappy loses one star, while leaving four or more unhappy loses two stars. Each star also contributes $20 to the restaurant’s daily earnings.

We increased Countryside meal revenue from $8 to $10 and adjusted the cost of apology vouchers to $18.

These changes are intended to create a clearer trade-off between protecting reputation and maximizing immediate profit.

The daily recap now shows the financial contribution of stars alongside sales, staffing, food purchases, and other expenses. It also compares the two restaurants’ overall scores, helping players understand their position in the competition.

Figure 4. Before and after: The revised daily recap includes star-related earnings and clearer information about profits, expenses, and the competition.

5. We needed clearer explanations, not necessarily more instructions

Across the playtests, players sometimes struggled with terminology and the game’s story.

For example, Alice did not initially understand the statement that only one player would get “The Two Spoons” back. She also questioned what the “shady deal” actually involved.

Jessica wanted clearer explanations of Express and Regular delivery, and Alice did not initially realize that multiple advertisement cards could be selected.

Our change: We revised the landing page to explain the competition for the Golden Spoon more directly. We expanded the shady-deal scenario to explain why the offer is risky, rather than relying on the word “shady.” We also improved the How to Play instructions, advertisement guidance, and explanations of restaurant service.

These may seem like small wording changes, but they matter. A player should be thinking about whether a decision is worthwhile, not struggling to understand what the button means.

Figure 5. Before and after: The landing page, advertising instructions

Figure 6. Before and after: The shady-deal screen provides clearer context for player decisions.

An Important Balance Question: The Cost of Firing Staff

One mechanic we are still uncertain about is employee dismissal.

During the November 15 playtest, Alice realized she had hired more employees than necessary, but the cost of firing staff made it difficult to adjust her strategy later in the game.

We discussed changing dismissal costs so that they depend on employee wages, remaining staff, and the restaurant’s financial position rather than using a fixed penalty. The revised prototype introduces a variable “goodbye pay” calculation.

However, after reviewing the revised interface, we noticed that the cost can become very high when only a few employees remain. In one example, firing an employee costs $110.10, with the next dismissal shown at $220.20.

This raises an important design question: Are we making players think carefully about hiring decisions, or are we making it too expensive to change their strategy at all?

Our team discussed this concern on November 15. Rather than immediately changing the formula again, we decided to keep the current version for the next playtest and observe how players respond.

We think this is worth testing before making further adjustments. We want hiring and firing to have consequences, but players should still feel that they have meaningful options.

What Went Well, and What Still Needs Work

One encouraging observation from the November 11 sessions was that engagement increased once players understood the implications of their choices. The first round often served as a learning round, after which players began making more deliberate decisions.

Alice also said she would consider playing again if she had a different strategy to try. This suggests that replayability may depend on whether players can discover several viable approaches, rather than one strategy that consistently works.

At the same time, we still have several concerns.

The simultaneous market remains a first-to-click competition, and we have not yet established whether the new bundles make it sufficiently strategic. Players also continue to spend time waiting for their opponent during some stages. The service simulation may still be too fast and visually crowded.

We have discussed adding more variety during the last two days, such as a wedding reception or another large event that would force players to adapt their strategy. We have also considered a clearer final winning announcement and a way for players to share their results. These are ideas for future iterations rather than changes we have already validated.

Questions for Our Next Playtest

  1. Is the new employee dismissal cost reasonable? Does it create an interesting consequence for overhiring, or does it discourage players from adjusting their staffing decisions?
  2. Does the revised market encourage strategic purchasing? Do players now consider quantity, delivery time, expected customers, and food waste, or do they still try to buy as quickly as possible?
  3. Do the new star rewards improve the balance between money and reputation? Since stars now provide daily earnings and also contribute to the displayed score, are we rewarding reputation appropriately?
  4. Can players explain why they succeeded or failed? After each day, can they identify which decisions affected their profits, customer satisfaction, and overall standing?
  5. Does the game communicate the complexity of restaurant management? Do players recognize meaningful trade-offs, or does the experience still make restaurant management seem easier than we intended?

Reflection and Next Steps

The biggest lesson for me from this round of playtesting is that adding more mechanics does not automatically make a game more strategic.

We initially thought that more events, advertisement cards, and purchasing options would make the competition more interesting. However, players showed us that the relationship between those mechanics matters more than their number.

If players do not understand how advertising affects customer demand, how staffing affects service capacity, or why buying too much food might be wasteful, their decisions become guesses or repetitive actions.

We also learned that players can enjoy a game without necessarily understanding the real-world system we are trying to represent. Alice’s comment about restaurant management seeming easy was a useful reminder of that distinction.

For this iteration, we therefore focused on improving connections between decisions, making consequences more visible, and adjusting the economic balance. Our November 15 changes are now reflected in the revised prototype, but they still need to be evaluated with players.

For the next playtest, we would like to pay particular attention to whether players can make decisions independently, explain their reasoning, and try different strategies across the five days.

Ultimately, we want Spoon Fight to be fun and competitive, but also to help players experience how running a restaurant involves balancing limited resources, uncertainty, customer satisfaction, and financial survival.

About the author

Saharat "Game" Laksanasut (In Thai: สหรัฐ ลักษณะสุต) is an English language teacher, educational researcher, and learning designer from Thailand. He is currently pursuing an M.S. in Learning Design and Technology at Stanford University as a Thai government scholarship recipient. His work focuses on English language learning, educational technology, AI-supported learning, gamification, teacher professional development, and inclusive learning design.

Before coming to Stanford, Saharat taught English at Angsilapittayakom School in Chonburi, Thailand, where he worked with secondary students and led educational research and development initiatives. He has also participated in international education and youth programs, including the Fulbright Foreign Language Teaching Assistant Program at Ohio University.

Saharat is passionate about designing meaningful learning experiences that connect technology, local contexts, and learner agency, particularly for students and teachers in under-resourced educational settings.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.