The progressive dinner is the oldest trick in the neighborhood playbook and the one almost nobody in Chicago uses, which is strange, because this city was built for it. A high-rise in Edgewater is forty dinner parties stacked on top of each other with an elevator between them. A block of two-flats in Andersonville is a dozen kitchens within a two-minute walk. A progressive dinner, sometimes called a strolling dinner, takes four of those kitchens and runs one meal through all of them: drinks at the first door, a starter at the second, the main at the third, dessert at the last. Nobody cooks a whole dinner. Everybody gets to host one course.
It works because it fixes the two things that stop people from hosting at all: a kitchen too small for the whole meal, and the fear of carrying the entire night alone. Here is how to run one in December without anyone freezing, waiting, or standing in a hallway holding a casserole.
Pick the route before you pick the menu
Four stops is the number. Three feels thin and five runs past eleven. Every door should be within a five-minute walk or one elevator ride of the last, because the walk is the fun part only while it is short. One building is the easiest version: four apartments on four floors, and the elevator is the hallway. One block is the classic: four front doors, and a December walk under the streetlights that lasts ninety seconds and makes the next apartment feel twice as warm.
Put the route on the invitation in order, with the time at each door. Guests who know the plan arrive relaxed. Guests who are texting "which apartment" at 8:40 do not.
Give each host one course, and match it to the kitchen
The host with the biggest oven takes the main. The host with the best living room and the smallest kitchen takes drinks and bites, which need a counter and no stove. The host who bakes takes dessert. The fourth host takes the starter: a soup, a salad, a big plate of something cold. Each host plans one course for the whole group, which is a Tuesday-night amount of cooking, and the week-of checklist shrinks to a single page per house.
Two rules keep it honest. Every course is ready before the group arrives, because there is no cooking while twelve people stand in your kitchen. And every course must be served and cleared in forty-five minutes, which is the whole clock.
Nobody has to host a whole dinner. Everybody gets to host one course.
The clock: forty-five minutes a door
Start at seven. Drinks and bites until 7:45, starter until 8:30, main until 9:30 with an extra fifteen for the course that deserves it, dessert until the last person leaves. The host of each stop texts the next host when the group is walking, so the next door is open and the next course is on the table when the first coat comes through. The group moves together; nobody stays behind to help with dishes. That is the next host's job tomorrow morning, and it is one course worth of dishes, not four.
What each stop needs
The drinks stop. One batched cocktail in a glass cocktail pitcher* on the counter, a bowl of ice, and the wine for the night carried over in an insulated two-bottle wine tote* so it arrives at the right temperature instead of having spent an hour in the trunk. Bites go on a large serving platter set* that holds the whole first course on one surface, so the host is not plating in a kitchen the size of a closet while the room fills up.
The starter stop. Whatever it is, it should be served in one motion: a soup ladled from the pot, a salad already dressed and tossed, a board that is on the table before the door opens. This is the shortest stop and the one with the least room for a host who is still cooking.
The main stop. A braise, a baked pasta, a roast that rests well: anything that holds for an hour in a lidded casserole dish* with the lid on, so it goes into a low oven at six and comes out whenever the group walks in. If the main host has moved the dish from another kitchen, the transport rules apply. Seats matter most here, since this is the stop where people sit down for real; a set of slim folding chairs* that lives under a bed the rest of the year is the cheapest way to turn eight seats into twelve.
The dessert stop. One thing on a dessert stand*, coffee already made, and the lights down. A line of battery tea lights* up the stairwell or along the hallway tells the group they have arrived at the last door, and no building manager will have an opinion about a flame that is not one.
Every stop. Twelve people arriving at once means twelve coats arriving at once, and nothing stalls a doorway like a bed buried in parkas. A standing coat rack* by the door of each apartment takes the whole pile in thirty seconds and gives it back just as fast when the group moves on.
Run it as one event, not four
The thing that turns a good idea into a plan is a single guest list. Make one TableFolk event for the night with the route in the description, name each host and their course in the potluck list, and let people RSVP once for all four doors. Every host sees the same headcount, which is the number they are cooking for, and the dietary notes live in one place instead of four group texts. Hosts can send the invite together, and the headcount updates for all of them at once.
Then do it again in February with the doors in a different order. The progressive dinner is the rare party that gets easier every time, because the people who hosted drinks this time know exactly what the main host went through, and next time they want the big course. That is how a block becomes a supper club without anyone deciding to start one.