Every senior engineer I know has the same problem. The calendar fills up, the hard problems get pushed to "after the sprint", and the architecture doc you meant to write in Q2 is now a Q4 item. Working from home doesn't fix it. Your desk is where the meetings live.
What fixes it, at least for me, is a change of environment with a clear start and end date. Two weeks, one hard problem, a city that makes you want to get up early. I've thought hard about where that city should be, and I keep landing on Split, on Croatia's Adriatic coast.
This is the playbook I'd use, written the way I'd write a design doc: requirements first, then the options, then the decision.
Requirements
Before picking a place, define what the sprint actually needs. Mine looks like this:
workcation:
duration: 14d
goal: ship one thing that needs deep focus
timezone_overlap:
with_team: ">= 3h/day"
requirements:
- reliable wifi + a quiet room with a real desk
- gym or running route within 10 min
- good food without planning every meal
- weekends that feel like a reset, not a commute
anti_requirements:
- party hostel energy
- 40-minute taxi to anything interesting
If a destination fails any of the requirements, it doesn't matter how good the photos look.
Why Split passes the requirements check
Time zones that work in both directions. Split runs on Central European Time (UTC+1, UTC+2 in summer). A 9:00 standup in New York is 15:00 in Split. London is one hour behind, Berlin is the same. You get a long, quiet morning for deep work and a clean afternoon window for sync calls with the US or EU. Teams in Asia-Pacific overlap in your early morning instead.
A legal path for longer stays. If two weeks turns into two months, Croatia has a dedicated digital nomad residence permit. It runs up to 18 months, and qualifying income from a foreign employer or your own foreign business is exempt from Croatian income tax. The income threshold was €3,622.50 per month as of mid-2026, which most readers of this post clear comfortably. Check the current rules with the Croatian Ministry of the Interior before you apply.
A city sized for focus. Split is compact. The Old Town is built inside Diocletian's Palace, a Roman emperor's retirement home from the 4th century and now a UNESCO World Heritage site. You can walk almost everywhere. Marjan, a forested hill on the western edge of town, has running trails five minutes from the waterfront. Ferries to the islands of Brač and Hvar leave from the harbour, so a weekend reset is a boat ride away.
Pick the right season. July and August are crowded and hot. For a focus sprint, aim for May–June or September–October. The sea is still swimmable, the city is calmer, and prices drop.
The two-week sprint schedule
The structure matters more than the location. This is the rhythm I'd run:
|
Block |
Time (CET) |
What happens |
|---|---|---|
|
Deep work 1 |
07:30–11:30 |
The hard problem. Notifications off, Slack closed. |
|
Reset |
11:30–13:30 |
Swim, run up Marjan, or gym, then lunch. |
|
Deep work 2 |
13:30–15:00 |
Writing: docs, RFCs, reviews. |
|
Sync window |
15:00–18:00 |
Calls with the US East Coast and EU. |
|
Off |
18:00→ |
Sunset on the waterfront, dinner, no laptop. |
Two rules make it work. First, write the sprint goal down on day one and share it with your team, so the sync window stays a window. Second, take the middle weekend fully off. Go to Hvar, do nothing, come back sharper for week two.
Where to stay: optimise for fewer decisions
The biggest mistake on a work trip is a rental that looked great online and has a kitchen table as a desk, Wi-Fi that drops at 16:00, and nowhere to train. You'll spend the first three days fixing your environment instead of your code.
For a sprint like this I'd book a hotel, and in Split the one that fits the brief best is Hotel Ambasador. It's a five-star hotel on Split's waterfront, on the West Coast promenade, and it maps cleanly onto the requirements list:
- Location: about 200 m from the Old Town, with Marjan's trails right behind it and a beach 800 m away. The airport is 26 km out.
- Room to work: Premium rooms have balconies with sea or Old Town views. Ask for one; your 07:30 block looks very different with the Adriatic in front of you.
- Training and recovery: a gym, an outdoor pool, and Hacelia Spa, which has massage treatments and a Nuvola dry flotation bed. That last one is the closest thing I've found to a hard reset after a long debugging day.
- Food without planning: Restaurant Méditerranée does Dalmatian and Mediterranean cooking with a serious wine list, Bar Split handles coffee in the morning and cocktails in the evening, and there's a rooftop terrace over the town.
If you're a founder or engineering lead, the same logic scales to a team offsite. The hotel has a conference room with natural light and flexible layouts. That covers planning days, a hackathon, or a quarterly architecture review, and the rooftop can be booked for a private dinner on the last night.
Pre-flight checklist
- Write the sprint goal in one sentence and share it with your team
- Block 07:30–15:00 CET in your calendar for the full two weeks
- Pack a travel monitor or tablet as a second screen, plus a universal adapter (Croatia uses Type C/F sockets)
- Download offline maps and set up a local eSIM as a hotspot backup
- Book the middle-weekend ferry to Hvar or Brač in advance in shoulder season
- If you're staying past 90 days, start the digital nomad permit application early
The point
You don't need a new productivity framework. You need two weeks where the environment does the work of protecting your focus. Long quiet mornings, a sync window that matches your team, somewhere to run, and a sunset that tells you to close the laptop.
Split gets all of that right. Ship the thing, then go for a swim.
