It's definitely easier to write up when you have one server and a standard three course meal, but I think it's fun to take on a challenge once in a while.
I've done a few Michelin 3-star restaurants for Coyle and while it can get overwhelming with the amount of people coming over to the table, you actually don't need that much information from the interactions. The receipt usually lists the items ordered and just about every restaurant I know has their menus posted online.
For high-end restaurants, it's also a bit easier because everyone is good at their job, for the most part. If one person does not smile and make eye contact, it's obvious and memorable. Writing a narrative with a pissed off and underpaid server from a diner is much more work.
I've also never heard of a restaurant evaluation being challenged based on runner or busser descriptions being inaccurate, so I usually just give it my best guess. I have some narratives with up to 5 servers that all have identical descriptions and it's never been an issue.
One restaurant in particular that I know of has the server come to the table and announce the dishes while two separate runners reach over you from behind and set the plates down. The first time I went there I spent the first half of the meal watching other tables to get descriptions of the food runners, and I realized that they are trying not to be seen. The server draws your attention and the plates magically appear! Since this is what the client obviously intended, I explained it that way and everyone was happy with it. If a runner dropped a plate of fiddlehead ferns in your lap, it would probably require a further description and be more memorable.
The thing that I like most about the narrative is that special circumstances can be explained. You are not forced to put an experience like a tapas restaurant into a box meant for 3-course meals (although there are still questions about appetizer and entree timings).
I've done a few Michelin 3-star restaurants for Coyle and while it can get overwhelming with the amount of people coming over to the table, you actually don't need that much information from the interactions. The receipt usually lists the items ordered and just about every restaurant I know has their menus posted online.
For high-end restaurants, it's also a bit easier because everyone is good at their job, for the most part. If one person does not smile and make eye contact, it's obvious and memorable. Writing a narrative with a pissed off and underpaid server from a diner is much more work.
I've also never heard of a restaurant evaluation being challenged based on runner or busser descriptions being inaccurate, so I usually just give it my best guess. I have some narratives with up to 5 servers that all have identical descriptions and it's never been an issue.
One restaurant in particular that I know of has the server come to the table and announce the dishes while two separate runners reach over you from behind and set the plates down. The first time I went there I spent the first half of the meal watching other tables to get descriptions of the food runners, and I realized that they are trying not to be seen. The server draws your attention and the plates magically appear! Since this is what the client obviously intended, I explained it that way and everyone was happy with it. If a runner dropped a plate of fiddlehead ferns in your lap, it would probably require a further description and be more memorable.
The thing that I like most about the narrative is that special circumstances can be explained. You are not forced to put an experience like a tapas restaurant into a box meant for 3-course meals (although there are still questions about appetizer and entree timings).