The food and the speed hold up. The room does not. Four problems showed up in one morning:

Tight space. The aisles are narrow, and with 10 workers and 7 customers inside at once there isn't enough room to queue, order and wait without crowding each other.

A rush that slows the line. Pickups slowed between about 8:55 and 9:20, and were slowest around 9:15.

An uneven wait. Five of the seven timed orders landed between 2:42 and 3:19. The one outlier, 5:09, was a barbecue chicken sandwich, a more involved build than the breakfast sandwiches. So the menu has no single wait time, and nothing tells a customer which kind of wait to expect.

Empty outdoor seating. Nobody was sitting outside.

The room is small for how it is used. The staff and customer count crowd a footprint with tight aisles, so the space, not the menu, sets the limit.

The register is not the bottleneck. Paying took about 3 seconds, and 3 of the 10 workers were on the register. Five were cooking and two were stationed between. The wait builds between ordering and pickup, so the front of the shop is staffed for a speed the kitchen and handoff can't match.

Demand comes in a wave. The slowdown was concentrated in a 25-minute window, which is what you'd expect from a morning rush that the layout and workflow weren't set up to absorb.

Outdoor seating: I don't have evidence for why it goes unused yet. That needs a question to customers, not a guess.

Wollastons is a good case because the basics are already right. My interviewee called the food quality and the options good, the price came out cheaper, the service felt fast, and the shop was favored over Tessies. The lighting is solid and the white and gray palette keeps it clean. A place that passes those tests has earned its customers, which means I'm not redesigning the product. I'm looking at what surrounds it.

What's left is the physical experience: tight aisles, not enough space, a slowdown in the morning rush, and outdoor seating nobody uses. That is a design problem I can actually work on, because it comes down to layout, flow and wayfinding, not menu or pricing.

The numbers made the problem specific. Paying took about 3 seconds, while the average wait for a sandwich was about 3 minutes. The transaction is fast and the wait is the experience, so the opportunity sits in the space between ordering and pickup. And since the fixes are mostly cheap, like floor marking, a staffing shift and a pickup point, an owner could test them right away. A small, measurable problem at a place people already like is where a design change can show results.

One morning, one window. I observed starting around 8:40, which is a rush window. It may not represent the rest of the day.

Small, hand-timed sample. Seven orders, timed by me, with my own judgment of when each started and ended.

I'm a maker. I come from carpentry and product design, so I lean toward physical and spatial fixes over menu, pricing or staffing ones.

I'm part of the customer group. The shop serves college students and teachers, and I'm a college student, so I may over-identify with what they want.

The Tessies comparison is secondhand. It comes from a single interviewee, not from my own side-by-side observation.

Scored 1 to 5. Desirability: do users want it. Feasibility: can the technology and operations power it. Viability: will it make money.