Remote Work

For a long time, working meant being in the office, so the information a job needed was attached to a location. Decisions happened in hallways, the reasoning behind them passed through conversations at neighboring desks, and the written record held a single line of conclusion.

The gap showed up for whoever was not there. Someone travelling, on leave, or sitting on another floor had no way to find out why something had been decided. Pagedeck ran into that directly. Noa took two days off, came back to a restructured pricing screen, and found the reason for it in no document anywhere. Asking around to reconstruct it cost another two days.

Hiring had a wall of its own. The candidate pool was limited to people who could commute. Grace once lost a designer in another city, not over skill but because coming into an office daily was not possible. Remote work moves on both problems at once: it pulls information out of the location and into the record, and once that happens, where someone sits drops out of the requirements.

What counts shifts from being present to being written down. Five mechanisms make it run.

1. Decisions and their reasoning get written. Documentation-first is the culture of writing something up and sharing it before raising it out loud, and remotely it is foundation work rather than a preference. With the reason for the pricing change in a document, the person returning from leave catches up alone.
2. The default mode of communication becomes asynchronous. Asynchronous communication is communication that proceeds without both sides being present at once: you write, and the other person reads and replies on their own schedule. Each round trip costs half a day, though, so the first message has to carry the background and the options.
3. Overlapping hours get fixed. Core time is the block everyone has to be available in. Nail it down as 11am to 4pm and the work that requires being together happens inside it while the rest of the day flexes. Without that block, one urgent question can take a day to answer.
4. Progress gets made visible. Who is working on what, and what they are blocked on, has to be legible on a board. What an office conveys through expressions and empty chairs is invisible to everyone remotely unless somebody writes it down. A card that has not moved in four days is the remote equivalent of someone looking stuck at their desk.
5. Management works from output rather than hours. There is no way to verify whether someone is sitting at a screen, so the attempt gets abandoned and what was promised by when becomes the unit instead.

None of that discards being together in real time. Synchronous communication — exchanging in the same moment — earns its cost when disagreements tangle beyond what writing resolves, and when people meeting for the first time need to build trust.

It runs best where the output lives inside a screen. Code, design files, documents and analysis can be handed over exactly as they are. Work that handles equipment, meets people on site, or touches data that may only be opened in a particular room stays tied to a place.

The stage of the company matters too. Early on, when what gets built is still unsettled, ten verbal alignments a day make remote work heavy going. Once the direction is set and documents have accumulated, it gets easier instead, because most questions are answered by something already written.

In practice, mixed arrangements outnumber fully remote and fully in-office companies. Pagedeck keeps engineering and design remote by default, while sales moves around customer visits.

Two places where remote work is notably weak. The first is onboarding. A new joiner does not yet know what they do not know, so they cannot form the question, and remotely that state is invisible from outside. Many teams answer it by pairing someone with them for 30 minutes of live conversation every day for the first two weeks. The second is resolving conflict. Writing back and forth through a tangle makes the sentences stiffer each round, and one call usually beats twenty messages.

"Let's not hold a meeting for this — I'll circulate a document and people can comment."

Handle it without putting everyone in the same time slot.

"You asked outside core time, so I'll get you an answer this morning."

Working to an agreed rule about when replies are due.

"We've been round three times in writing and it isn't resolving. Twenty minutes on a call?"

This one is not going to come apart asynchronously, so move it.

Pagedeck's engineering team is five people across three cities. Theo opens the board in the morning, starts with whatever is blocked, and writes up the questions he needs answered in one go. An answer arriving in the afternoon does not stop him, because other work fills the gap.

Mia keeps sprint planning as a full video call and runs the rest through documents and comments. Meetings dropped from eight a week to two, while time spent writing and reading went up. The total is not far off what it was, and now people who were not in the room can read the same content later.

The most common mistake is treating remote work as the same thing as flexible hours. Picturing someone working from home tends to bring along the picture of choosing their own hours. But this term settles location only. Time rules are a separate decision, and plenty of remote teams still expect everyone available from nine to six. Left in place, a new joiner assumes any hour will do, disappears during core time, and the hours everyone spends waiting on each other start climbing.

The second is assuming that moving meetings to video makes an organization remote. The visible change is the room becoming a screen, so it reads that way. What actually needs rebuilding is where information lands. Move only the meetings and the coordination that used to happen in hallways moves into meetings too, so the count goes up while anyone who did not attend still knows nothing. Without the written record in place first, you end up doing six video calls a day and finishing more tired than the office ever made you, with no more shared context than before.