The Gnarly-Problem Offsite
Remote by default, but collapse a stalled hard decision into a tightly-agenda'd 48-hour in-person burst.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 6
- Confidence
- 92%
Distributed teams can run normal operations asynchronously, but hard, contentious, cross-functional decisions rot in comment threads across time zones — a doc goes out, comments trickle back, and a week evaporates without a decision. Miller's counter is a deliberate, event-driven in-person burst: when a problem is genuinely gnarly, wave the flag, pull people together for two days with a pre-agreed agenda, resolve it, and return to remote life.
Origin
Nikita Miller, from a fully remote/distributed career (Shanghai, Europe, Latin America, Trello/Atlassian, The Knot Worldwide). She cites Trello and Atlassian for the enabling standards — mandatory overlapping hours and in-person onboarding.
Core principles
- 01Solving a hard problem remotely with people you've never broken bread with or disagreed with in person is much harder — trust is the missing input, not information.
- 02Time zones destroy decision velocity: one doc round-trip can consume days.
- 03The in-person burst is triggered by a problem, not by a calendar quarter.
- 04The agenda must be settled and agreed before anyone travels; the room is for resolving, not scoping.
- 05Meaningful in-person time is what sustains the subsequent remote stretch.
- 06Standing standards (overlapping hours, in-person onboarding, strong async writing) are what make the rest of the time work.
How to run it
- 1
Build the async baseline first
Documentation is a thing. Async communication is a muscle everyone has to build, on video and in writing, across every role. Plus two structural standards: a mandatory band of overlapping work hours every day inside otherwise-general flexibility, and in-person onboarding for every new joiner.
Pro tip Overlapping hours were, in Miller's view, the biggest single lever at Trello/Atlassian — flexibility everywhere else, but everyone online together for a set window most days.
Watch out Teams who have never met their coworkers, never onboarded in person, and have no offsites will find hard problems disproportionately difficult — the flexibility is real but it has a cost.
- 2
Spot the stall and wave the flag
The trigger signal: a big decision with strongly-held opinions, a doc circulating, comments trickling in over days, and no landing. Rather than iterating another round remotely, explicitly call it — 'why don't we get together for two days and hash this out'.
Pro tip Say the quiet part out loud: this is a decision-velocity problem caused by the medium, not by the people.
- 3
Agree a tight agenda before anyone travels
Someone owns writing a well-articulated agenda that the whole group signs off on in advance. Arriving to figure out what the meeting is about wastes the expensive resource you just assembled.
- 4
Book 48 hours and two nights
The working sessions are still conference-room hours during the day, so the two nights are not padding — the extended dinners and long lunches are where the camaraderie and trust that make the hard conversation possible actually get built.
Pro tip Include remote dial-in for anyone who genuinely can't travel — most people will come, and the ones who can't are yes, on a screen.
Watch out Cutting it to a single day removes the social time and you get an expensive version of the Zoom call you were trying to escape.
- 5
Level the information before debating it
Frequently the blocker is not disagreement but asymmetric information. Explicitly hand the floor to the person who holds the data and let them educate the room before anyone argues for a position.
Pro tip Miller's phrasing: 'you have the floor, educate.' Give the data person the space, uninterrupted.
- 6
Land the decision and return to remote
Close the specific decisions the offsite was called for, then go back to the distributed default. This is a burst, not a return-to-office policy.
In the wild
The Knot Worldwide had a change in strategy and needed to land a few core decisions about what to build. There were many documents, many conversations, and strongly-held opinions — but with time zones, a doc would go out, comments would come back the next day, and by end of week nothing was decided. Miller called it: waved the flag, pulled everyone together.
→ The decisions landed in person. The specific unlock was cross-functional: giving the data person the floor to educate everyone, which revealed the group had simply been reasoning from different information.
Early in her career, working internationally, Miller's employer brought the entire company together globally for a week or two, two or three times a year.
→ It made a huge difference — many of the people she worked with there are still friends and mentors more than a decade later.
Common mistakes
Grinding a hard problem through more async rounds
Each remote iteration on a contentious, high-stakes decision costs days to the time-zone tax and doesn't build the trust the disagreement requires. The cost of the flights is usually less than the cost of another week of non-decision.
Showing up without an agreed agenda
The offsite's whole value is compression. If the group spends the first day deciding what it's there to decide, you've bought expensive co-location and spent it on scoping.
Treating dinner as optional
The two nights are load-bearing. Trust built over an extended lunch or dinner is what lets people disagree productively in the room — remove it and you have moved a Zoom call into a more expensive building.
Is it for you?
Best for
Leaders of distributed or hybrid teams facing a stalled, contentious, cross-functional strategy or architecture decision.
Not ideal for
Routine execution, status, or well-scoped work — those are exactly what the async baseline should be handling, and offsiting them wastes the mechanism's scarcity.
From the transcript
“solving a hard problem remotely with folks that you haven't spent in person time with that you haven't broken bread with that you haven't like…”
“there's a really gnarly problem I like wave the flag and I say hey everyone why don't we try and get together for two days…”
“one the agenda is pretty tight before we get there”
“the space to educate all of us that was it it was like you have the floor educate”
“the biggest one I think was overlapping work hours so everyone had General flexibility but there were some set of hours where everyone needed to…”
From the episode
Driving alignment and urgency within teams, work-life balance, and the changing PM landscape
Nikita Miller (The Knot, Trello)