Remote work and async comms means that latency tends to be high. Latency issues can be overcome by not stopping to wait at each decision point.

For example, low latency this is ok: “do you want to go to dinner or a movie?” Movie. ”Do you want to see Barbie or Oppenheimer?” Oppenheimer. “Do you want to go at 6:00, 7:00, or 8:00?” 8:00.

Instead for high latency, this will cut down on a lot of dead time in back and forth: “Do you want to dinner or see a movie? If you want dinner do you prefer to go to Il Capricio (Italian) or Sushi Go 55? I can make reservations at 6, 6:30, or 7. If you’d rather see a movie, do you want to see Barbie or Oppenheimer? Barbie is at 6:15, 7:20, and 8:15. Oppenheimer is at 6:00, 7:00, and 8:00.” Let’s do Oppenheimer at 8

It’s more work up front and any unchosen paths are “wasted effort”, but for work there’s usually value in fully exploring the alternate paths anyway.