A quick question about a link shouldn't cost eight hours

The cheapest question is the most expensive one

At 09:14 someone in Lisbon needs the staging URL. The person who knows it wakes up in Denver seven hours later, answers in nine seconds, and that is a day gone from a task that needed one link. Multiply it by the four other quick questions that week and by everyone who is too polite to ask a fifth time, so they guess instead.

In an office this problem does not exist, and not because offices are better organized. It is because you overhear things. You see someone's screen. You ask across a desk and the cost is four seconds. Remote teams do not lose more links than co-located ones - they lose the ambient mechanism that used to make links findable without anyone maintaining a list.

Remote teams do not lose links, they lose the overhearing that used to make links findable.

The new tab is the shared wall

The Linksley extension can make your boards the new-tab page. It renders instantly from a local cache and it is searchable, so the surface everyone opens forty times a day carries the team's links instead of a search box and six sites you already have open. That is the closest a distributed team gets to a wall everyone walks past.

It works because it requires no discipline. Nobody has to remember to check a wiki. The links are on the page that opens when you press Cmd-T, whether or not you were looking for them.

Push the essentials, group the rest

An admin can mark a board required, so it shows up for everyone in the group and cannot be removed. That is the layer for things nobody should have to be told: the handbook, the status page, the request forms, the on-call rota, the meeting-notes doc. A new hire in a timezone with no overlap gets exactly what everyone else has, on day one, without a synchronous walkthrough.

Groups handle the rest. Engineering, support and finance each get the boards that belong to them, shared once, with view-only where a board should not be edited by everyone who can see it. If you are setting this up for the first time, share links with your team walks through the structure.

Search first, ask second

The behavior change is small and it is the entire point: before typing quick question in Slack, you type two words in a new tab. Because the boards are cached locally, that search is instant even on a bad hotel connection, which is more of a remote-team consideration than it sounds.

Sessions cover the other half of distributed work - the machines. Save a set of open tabs and windows as a session and a saved window reopens as one browser window, so a working context moves between your desktop and your travel laptop. Opt-in browser snapshots handle crash restore and new-machine restore, window positions included.

The honest limit

A link board answers where, not why. It will not replace your handbook, your decision docs, or the async writing culture that makes remote teams work - if the real problem is that nobody writes anything down, boards will not fix it, they will just make the undocumented links findable. There are no Slack, Zapier or SSO integrations, no Safari extension, and no mobile app, so a teammate working from a phone in transit is using the web app on a small screen. And if your team is four people in two timezones who genuinely all read the same channel, a pinned message is free. It fails later, at the size where the pin is buried and half the team joined after it was written.