Collaboration Mode

When twenty people sat in one room during the same hours, none of this needed a name. If you had a question you turned your chair around and asked. If something was urgent you grabbed a room and settled it in ten minutes. Whatever got decided lived in the heads of the people who were there, and that was enough, because everyone being in the same place at the same time was an assumption nobody ever had to say out loud.

The assumption broke, and everything it had been holding up came loose at once. Headcount passed forty. One person worked from home, another came in after lunch, a third was on vacation that day. A decision made in ten minutes in a meeting room was, to the six people not in that room, an event that never happened.

Pagedeck ran into exactly this. Four people met on a Tuesday afternoon and agreed to reword the pricing screen. Noa was working from home that day and wasn't there. Two weeks later she brought a design with the old wording still in it, and the conversation went "we decided this in the meeting" against "I wasn't in that meeting." Neither sentence was wrong, which is why blaming either side guarantees the same thing happens again next month. What was missing wasn't diligence. It was a rule. Goodwill doesn't close that gap, because both people behaved reasonably given what they knew; only a written agreement about where decisions land can.

So teams started writing down, ahead of time, when they gather and talk and when they read and write on their own, where a decision goes once it's made, and which hours of the day people can expect to reach each other. That bundle of agreements is what collaboration mode refers to. It isn't a question of which chat app got installed — it's a question of what gets sent through it, when, and in what shape.

The terms under collaboration mode fall into three groups: what information travels on (communication), where bodies are and when (work arrangement), and what the shared hours get spent on (meetings). The three don't work as a menu to pick from. Each one narrows the options available to the next.

Communication covers the shape information takes in transit. The first fork is whether sender and receiver have to be present at the same moment.

1. Synchronous communication — exchanges that happen in the same moment. Video calls, phone calls, a chat thread where replies land immediately. A misunderstanding can be caught and fixed on the spot, which makes it fast, but the cost is locking several calendars together. A thirty-minute meeting with five attendees spends two and a half hours of company time. That's worth paying when the topic is genuinely contested and wasteful when it's a status update four people could have read.
2. Asynchronous communication — exchanges that move forward without both sides being present. Write it down and the other person reads and answers in their own hours. For a team whose working hours barely overlap, this is effectively the only option left. The price is that a single round trip can take half a day, so a thin first message turns into two days of follow-up questions.
3. Documentation first — the habit of writing something up before bringing it to a conversation. The background and the options go into a document that circulates before the meeting, and attendees arrive having read it. Async work needs something to read, which makes this the floor the other two stand on. The real payoff isn't shorter meetings — it's that someone who wasn't in the room can read the same thing six months later.

Work arrangement covers where people physically are. Communication rules can be written perfectly and still play out differently depending on whether the team shares a building.

1. Remote work — working without gathering in an office. Hiring widens from one city to a whole country, and in exchange the information that used to drift by in a hallway disappears. Build nothing to replace what people used to overhear, and two people carry two different pictures of the same project for two weeks. Teams that make remote work well usually over-invest in writing: notes from every meeting, decisions logged where anyone can find them, and a habit of answering in a shared channel rather than a private message.
2. Hybrid work — mixing office days with remote days. Teams usually set a rule like two days a week, but unless the days are coordinated per team, people come in and find the person they needed is home. And when a meeting has three people in a room and four on a screen, the screen half usually loses its opening to speak.
3. Core time — the hours everyone is expected to overlap. Fix it at 11am to 4pm and people can arrange the rest of the day themselves, with anything that needs two heads handled inside the window. It's the minimum overlap a team with flexible hours keeps so that live conversation doesn't vanish entirely. Teams spread across time zones end up with a narrow window, sometimes two hours, and guard it carefully because it's the only slot where a hard question can be settled in one sitting.

Meetings cover what the gathered time is used for. If the first two groups decide when people can be together, this one decides what happens once they are.

1. Meeting hygiene — rules that keep meetings from being waste by fixing their purpose and their guest list. The invitation states whether this is a decision, an update, or a discussion, and pure updates get sent as a document instead. A recurring meeting with no agenda is cancelled, and what was decided and who does what next gets written down before anyone leaves. None of these rules are clever; they're just the ones that stop being followed first when nobody owns them.
2. Kickoff — the session that starts a project by aligning its goal and its roles. What is being built and why, who owns which piece, what lands by when. Save thirty minutes here and the same questions come back one person at a time over the following weeks, at several times the cost.
3. Demo — showing the actual thing. Progress reported in words produces sentences like "it's about 80 percent done," while putting the screen up and clicking through it makes what works and what doesn't visible immediately. It replaces claims about progress with something the room can check.

Settle all three and one question is still open: after everyone has talked, who decides? That belongs to decision making. If collaboration mode lays the channels that words travel through, decision making determines whose words become the conclusion at the far end. Lay good channels and leave the end unspecified and a document collects forty comments over two weeks without resolving.

"Let's take this one async. I'll write up the background and three options, and you can comment by tomorrow morning."

This isn't urgent enough to gather for, so read and respond on your own time instead of booking a meeting.

"Please keep meetings inside core time. Anything after four and half the team can't join."

There's an agreed window where everyone overlaps, and a meeting outside it can't expect full attendance.

"Is the purpose of this meeting a decision or an update? If it's an update, a document would work."

Checking whether there's a reason to spend an hour of eight people's time, and proposing to cancel if there isn't.

Pagedeck runs two office days a week with core time from 11am to 4pm. When Theo gets stuck mid-task inside that window, he pings Mia directly. At five in the afternoon he writes the question into the document instead and picks up the answer the next morning. A rule like this falls apart if everyone draws the line between urgent and not-urgent somewhere different, so the team wrote the line down in a few sentences: a blocked deploy or a customer-facing outage gets a call at any hour, and nothing else does. Writing it down also removes the judgment call from whoever is stuck, which is the person least able to make it well at that moment.

The same rule governs how Sofia hands customer conversations to the product side. When a call ends she writes five lines about what was asked for and why, drops it in the document, and books no meeting. Mia reads the accumulated notes once a day and pulls only the ones that need a decision into an agenda. Handling the same volume through a standing meeting would have consumed an hour every week; instead Sofia spends ten minutes writing. The moment one person skips those ten minutes and passes the request along verbally, that request leaves no trace, and three months later nobody can say why the feature was built.

The most common mistake is treating collaboration mode as a tooling decision — install a chat app, add a document tool, and collaboration improves. Tools are visible and can be adopted in a day, while rules have to be negotiated and take weeks, so reaching for the tangible option first is a natural move. In practice two teams on identical tools work in completely different ways. In one, decisions end up in documents; in the other, the same decisions scroll away in a chat channel. The difference isn't the software, it's whether a single sentence exists: decisions get written down. Add tools without rules and all that grows is the number of places information could be. That's how a team ends up with thirty channels and two document tools and still can't find anything. The fix is never another tool; it's picking one place per kind of thing and saying so out loud.

The second mistake is believing async is always the better choice. It cuts meetings, leaves a record, and protects focus time, so the upside is easy to see, especially for anyone who already dislikes meetings. But async is priced per round trip. A question where opinions diverge and five exchanges are needed takes three days in writing and twenty minutes in a room — the classic case being two people arguing from different unstated assumptions about where a feature should go. Force that kind of question into async and the comment thread grows until everyone stops reading, and eventually someone gives up and books the meeting anyway, two weeks later than they could have. The rules that actually work in practice don't pick one mode over the other. They name a default and spell out when to switch to the other one. A common version is written by default, with a call allowed the moment a thread hits its third round without converging, and whoever calls it writes the outcome back into the same document afterward.