Collaborative Document Editing

A candidate interviewing for an L5 role at Google gets asked, “How would you design Google Docs so 50 people can edit the same document in real time” and says, “I will use WebSockets and a database.” Another candidate, interviewing for the same level at Uber and Meta, gets the exact same question and walks through each layer from network to data model to conflict resolution to observability. One gets rejected, and one lands the offer. Same question. Same 45 minutes. Very different understanding of system design. Hence, different results in interviews. Here is how “50 people are editing the same Google Doc” really works under the hood. The 7 Layer Real Time Collaboration Stack 1: Network and Edge Where every keystroke begins. -- DNS to reach the right region -- CDNs to serve static assets quickly -- Load balancers to fan in millions of connections -- WebSockets or long polling to keep clients connected Get this wrong and your cursor lags before any logic runs. 2: Session and Identity Who is editing and what they are allowed to do. -- Auth tokens and sessions for each user -- Document permissions: view, comment, edit -- Mapping user to active sessions across devices If this layer is weak, one bug can leak a private document to the wrong person. 3: Data Model and Storage Where the document actually lives over time. -- A canonical document store (SQL or NoSQL) -- Versioned snapshots for recovery and history -- Metadata for ownership, sharing, timestamps Every save and rollback depends on how clean this model is. 4: Collaboration Engine How 50 people type at once without overwriting each other. -- Operational Transform or CRDTs to merge concurrent edits -- Ordering of operations across regions -- Conflict resolution rules for edge cases This is the difference between a toy editor and production collaboration. 5: Real Time Distribution How changes fan out to all active users. -- Pub or sub channels per document -- Partitioning and sharding active docs -- Throttling and batching to avoid flooding clients Your design here decides if cursors feel instant or jittery. 6: Observability and Reliability How you know things are working at scale. -- Latency metrics per document and per region -- Centralized logging of failed operations and merge errors -- Traces for a single keystroke from browser to backend and back -- Alerts when collaboration latency crosses a threshold When a team screams “Docs is slow”, this is where you look first. 7: Intelligent Optimizations Where you make the experience feel smooth even under load. -- Predictive preloading of recently opened docs -- Smart batching of low priority updates -- Adaptive sync intervals for slow networks -- Anomaly detection when a doc suddenly gets unusual traffic Master this layered way of thinking, and every problem is just another system you know how to reason about.

Question from a friend of mine: "I'm using Microsoft 365 and I'd like a colleague to review and suggest edits for a pricing table. What are my options?" Sounds simple enough, right? Then I realised that there are at least 13 ways I can do this. Did I miss any? 1. Send it as a file attachment via email (Outlook) Attach the file directly. They download it, edit offline, and send it back (no live co-editing). 2. Send it as a OneDrive link in an email Upload to OneDrive. Share a cloud link with “Can edit” permission for live collaboration. 3. Paste the table into the email body (Outlook) Just paste it. Quick for small tables. Feedback can be inline or as a reply. 4. Share it in a Microsoft Teams chat Upload the file into a private chat or paste the table into a message. Good for quick, private back-and-forth. 5. Share it in a Microsoft Teams channel Post a message with the table or upload it into the Files tab. Great if you want the whole team or project group to see and contribute. 6. Use a Loop component inside Teams or Outlook Create a live-updating table for real-time collaboration inside the message itself. 7. Upload it to SharePoint Upload into a team document library. Share the link — great for version control and broader team access. 8. Use Microsoft Whiteboard Paste or recreate the table into a collaborative canvas for brainstorming. 9. Create a Microsoft Form Set up structured questions if you want orderly, survey-style feedback. 10. Co-editing in Excel Online, Word Online or PPT. Set up deliberate live editing through OneDrive or SharePoint, with clear permission control. 11. Attach it to a Planner task or To Do item Add the table as a file linked to a task, for action-based review and completion. 12. Post it on Viva Engage and tag the person Share the table or attach it to a post, tag your colleague, and get feedback in comments. 13. Print it, walk over with a pen in hand, and have a chat! YES - we may not need tech at all! When you look at all these options, something else emerges from the fog: There are three different aspects at play: - Storage: Where the “source of truth” lives, and who should be able to access. - Conversation: Where the dialogue about it happens - Feedback: How we want the input to be captured and handled Sometimes it would be nice if life were simpler, but then again, I also love the different nuances the different options enable. How about you?

Here's a step-by-step to drastically reduce the deluge of emails between you and your clients/internal team. An absolute GAMECHANGER 👇 Enter: The Collaboration Doc 👏 I’ve stolen this idea from Cal Newport’s podcast Deep Questions. I immediately implemented it with my own clients and they LOVE it. Fundamentally, most people don’t need a response *right now* – they just need to be safe in the knowledge that everything is being taken care of. So all the Collaborative Doc is is a very clean, clearly outlined document that you and your clients and/or your internal teams can use asynchronously to reduce overhead tax. Overhead tax is all the unnecessary (and exhausting) meetings and emails flying back and forth that surround a project. Here’s how to drastically reduce your overhead tax immediately: Step 1: Create a shared document This could be in Notion, Google Docs, Word or whatever works best for you and your client. Make sure your privacy settings are all correct. Step 2: Make it incredibly easy to navigate I have mine split into: 📆 Key Details 📝 Meeting Notes 🧠 Brain Dump Within Brain Dump I’ve further split that into all the key stakeholders so they know exactly where to put their notes. Break this down however you want. They key is that it's all clear and formatted, it looks nice, but it's not overworked. This should be as bare bones as possible. Step 3: Agree a cadence The point here is to reassure your client that you will absolutely refer to their notes. If you have a weekly Wednesday meeting for example, say that you will check all notes first thing on a Tuesday. They can be confident that nothing will go un-reviewed and anything that needs to be actioned before the meeting will be. Meanwhile, you get to be clearer on when you work on each client/project, as everyone has a set cadence. Step 4: Be religious about your collaborative documents This only works if your client has absolute trust that you will keep the document updated and reviewed. Do not let anything slip! WHY THIS WORKS Instead of emailing back and forth, clients put any questions, ideas, notes etc into this one, living document. It helps you to whittle communication down to the essential, increasing the value of your work, your time and the experience your client has (remember it's reducing overhead tax for them, too!) I've done the above example for working with a client, but it works just as well for internal teams, too. It gives everyone more time as people know that things are documented and will be picked up, so there's no need to just fire little things off on slack unless they're actually needed there and then. For both groups, streamlining like this means that you can save time and energy for when a response really is needed right away. Simple, I know, but honestly SUCH a winner. Do you do this already? What problems do you foresee and how would you tweak it?

Streamlining Document Revisions: Tips for Tracking Changes and Simplifying Negotiations When collaborating on a #document that requires multiple rounds of revisions, it’s easy for things to get chaotic. To keep the process smooth and efficient, follow these strategies: 1. Centralize the Document Use a shared platform (e.g., Google Docs, Microsoft Word Online, or a dedicated collaboration tool) that allows real-time editing and tracking of changes. This ensures everyone is working on the latest version. If not make good use of nomenclature to name the document effectively. 2. Enable Change Tracking Turn on features like "Track Changes" to clearly show what has been added, deleted, or modified. Use comments for additional context or to flag areas for discussion. 3. Version Control Keep a version history or log of changes. Name versions logically, such as Date_Draft_v2_with_ClientFeedback, to reduce confusion about which version is current. 4. Summarize Changes At the beginning of each revision round, include a brief summary of what has been updated. This helps reviewers focus on the new or modified content without combing through the entire document. If multiple sections are revised its good to address them as comments. 5. Clear Communication Establish clear channels for feedback, whether it’s email, a project management tool, or in-document comments. Set deadlines for each round of review to keep the process on track. 6. Simplify Negotiation Create a decision log where key changes and agreements are documented. Use this to address recurring questions or avoid revisiting settled discussions. 7. Define Final Approval Criteria Agree on what constitutes a "final" version to avoid endless back-and-forth. Make sure all stakeholders know when and how to give their final sign-off. With a clear process and the right tools, you can transform a cumbersome revision cycle into an organized and collaborative workflow! #law #legal #agreement #contract #drafting #negotiation #review #process #work #hiring #success #advice #document #us #remote #lawyer

💡Collaborative Authoring - Simplifying Teamwork in Veeva Vault (with a few caveats!) We’ve all been there - juggling multiple document versions, endless review comments, and confusion over which file is truly “final.” 😅 That’s where Veeva Vault Collaborative Authoring steps in - bringing structure and real-time teamwork to document creation. ✨ Key Benefits: ✅ Co-author documents directly in Microsoft Word Online ; no downloads or re-uploads. ✅ Multiple users can edit simultaneously with real-time visibility. ✅ Vault handles version control automatically and integrates with workflows for review & approval. ⚠️ Limitations to keep in mind: ❌ Requires Microsoft 365 integration - users without it can’t co-author. ❌ Only supports Microsoft Word (not Excel or PowerPoint). ❌ External users can’t be tagged or added unless they’re part of the organization’s directory. ❌ Detailed audit trails remain in Vault, not within the Word file. ❌ Certain advanced formatting or macros might behave differently in Word Online. Even with these caveats, Collaborative Authoring is a game-changer ; improving teamwork, reducing document chaos, and streamlining compliance. Because when collaboration is structured, productivity naturally follows. ✅ #VeevaVault #CollaborativeAuthoring #LifeSciences #ClinicalResearch #Regulatory #DocumentManagement #QualityManagement #Veeva #DigitalTransformation