Designing Positive Workspaces

Back when I was a data analyst, I used to “collaborate” by sharing screenshots, exporting Excel files, and sending copies of local ipynb files with teammates. My workflows consisted of hundreds of ad hoc queries in SQL Server scripts or Jupyter Notebook files that were organized by code comments that only made sense to me… And even worse, they were saved as v1, v2, vFinal, etc. in various locations across a disorganized file system that we only cleaned up for archiving purposes only after the project was over 😵💫 I left that job thinking it was normal for a data team to be this unorganized and that data collaboration was overrated—we just need to code and build dashboards better and faster! As I transitioned to companies where data played a much more central role in the company rather than one that was merely an auxiliary function, I learned that collaboration is not just a single thing that data teams have or do not have. There are LEVELS to this: 1️⃣ Synchronous collaboration - At remote-first companies, I needed to be able to work through problems in the same file at the same time alongside my manager when I was stuck ↳ Data tools with real-time code collaboration features that also allow for granular role-based access controls allowed me to prototype rapidly with my virtual teammates 2️⃣ Asynchronous collaboration - I have almost always worked with people across different timezones ↳ Features like commenting and versioning allowed me to pick up work on a project where a colleague left off, and vice versa 3️⃣ Organizational collaboration - All the hard work I did on an analysis was worth nothing if I couldn’t surface the insights to other data teams and business stakeholders and demonstrate the business value ↳ Team workspaces helped us build out dedicated hubs for teams to collaborate efficiently and organize data reports used to share insights interactively A data platform that boasts all of these features and is built with the collaborative data team in mind is JetBrains Datalore. If your data team knows the pain of any of these collaboration struggles, check out Datalore at 👉 https://lnkd.in/gcZSNBeU #ad

The computer interface you're using right now was created back in 1984. And yet, here we are in 2024, still using it… for now, at least. My team and I founded thinair to change the way we get work done. Bringing everything you need into one seamless flow. But, see, thinair wasn’t always what it is today. It started out as a project called "BlackBox," which even earned us a YC interview about 3-4 years ago. Back then, we were already exploring code gen before it became trendy. But the real breakthrough for us came while trying to solve our own issues. While founding a hardware startup, Daniel Lannan stumbled upon something unexpected: He noticed that while using Adobe Illustrator, having everything—code, design, documentation—in one space drastically improved productivity. No more alt-tabbing, no more window overload. That's when it clicked: We needed to build a workspace that aligns with how people actually think. Think about your current setup: - Managing 20 clients = juggling 100+ tabs - Constantly signing in and out of various accounts - Switching between countless windows - Closing tabs only to reopen them minutes later Let me give you a real-world example: Just last week, we had to coordinate a merch order for an upcoming hackathon. It involved multiple suppliers, mockups, and team coordination. Traditionally, this would take 2-4 days of bouncing between tabs, sending screenshots, and repeatedly asking: "Wait, where was that mockup again?" But with thinair, our entire team collaborated in a single shared space, all in real time. A task that usually takes days was completed in just 35 minutes. Sometimes, the best solutions are born out of solving your own problems. That’s how thinair came to be: By creating a workspace that finally works the way your mind does.

xAI's Grok Studio Just Changed the Game for AI Collaboration Have you seen what xAI just unveiled? Grok Studio has arrived, and it's redefining what AI collaboration looks like. This isn't just another AI update—it's a creative workspace transformation. Imagine: full document generation, functioning code creation, comprehensive reports, and yes, even browser-based games—all through collaborative AI interaction. What stands out to me: * Seamless Google Drive integration for working with your existing files * Multi-format support for images and various file types * Live coding environments for Python, C++, Bash, and more * Split-screen previewing that shows results in real-time * HTML testing capabilities right in the workspace For professionals looking to accelerate their workflow, this convergence of coding, content creation, and AI assistance in a single platform represents a significant shift in how we might approach creative and technical projects. While Grok 3 was already making waves in the AI space, Grok Studio appears to be positioning xAI for the collaborative enterprise environment—a space currently dominated by other players. As business leaders and creators, we should be asking: How might this tool reshape our workflows? Could this type of AI collaboration become the new standard for teams? What are your thoughts? Would you incorporate Grok Studio into your professional toolkit? What specific use cases do you see for your industry? X Grok #AI #GrokStudio #xAI #AICollaboration #FutureOfWork #TechInnovation

The debate over working from home versus returning to the office seems to be calming down, with the consensus being that it largely depends on the industry, sector, or customer needs. Organizations are now indeed embracing a triangulation of digital workplaces, physical workplaces, and workspaces, showcasing a blend of remote, in-office, and hybrid models. This integration is aimed at optimizing productivity, collaboration, and employee satisfaction. Here's how each component is expected to evolve: 1. Digital Workplace: This area includes the tools, platforms, and technologies that enable work to be done from anywhere. The digital workplace is poised to become more advanced, integrating AI and machine learning to automate routine tasks, enhance communication, and offer a personalized employee experience. Technologies like virtual and augmented reality could further enhance remote collaboration by creating immersive environments. 2. Physical Workplace: The significance of physical office spaces is being reconsidered but remains essential for nurturing company culture, facilitating collaboration, and accommodating work that benefits from face-to-face interaction. The design of these spaces is evolving towards more flexibility, incorporating hot-desking, open collaborative areas, and social interaction spaces. Factors like health, well-being, and sustainability are increasingly influencing physical workplace design. 3. Workspace: Workspaces are environments that stimulate energy, enthusiasm, and creativity through their ambiance. This concept expands the notion of potential work locations beyond the home or office to include coworking spaces, cafes, libraries, or even parks—essentially, any place that supports productive work. There's a growing appreciation for the importance of work-life balance and the role diverse workspaces can play in achieving it. Advancements in technology will facilitate seamless work from these varied locations, ensuring easy access to necessary resources and connectivity. The future is likely to see organizations adopting a more adaptable approach to work, granting employees the autonomy to select the most suitable work environment for their tasks. Employers will strive to create a cohesive experience across digital, physical, and various workspaces, ensuring that employees have the environments and tools they need to be productive, engaged, and content. This strategy will necessitate careful integration of technology, space design, and policies that encourage flexibility while fostering a robust sense of community and organizational identity.

Is the number of employees Working From Office (WFO) featuring as a discussion topic in your leadership meetings? I have observed that the discussion often misses a critical truth: Employees don't want to commute for a cubicle; they want to commute for a community. Yesterday, we held an Employee Meet focussed on Office Space Evolution for Backbase India, and the engagement confirmed my primary outlook as a Site Leader: Workspace is no longer a real estate asset—it is a cultural catalyst. When asked how we encourage WFO, my answer is built on three practices we are currently deploying in India through #ProjectApex: 1. The Pull over Push Strategy: We aren't just thinking of increasing capacity; we are designing Collaboration Zones that offer something the home office cannot— face-to-face problem solving. If the office doesn't offer a superior experience to the home table, you've already lost. 2. The Council Model (Listening): To understand why certain space solutions work or they don’t, we've created an employee-led Council. It’s a feedback loop. By listening to their friction points—from commute logistics to desk ergonomics— we're co-creating solutions. 3. Zones for Cognitive Diversity: The biggest mistake in modern office design is a "one layout fits all" plan. We are designing our future space around activity-based work. This means Vibrant Zones for the networkers, Deep Work Corners for heads-down engineering focus, and White Board Areas for teams that solve P0s together. When thinking of modern workspaces, think of creating an environment where people want to be, even when they don’t have to be. Don't just move buildings or desks; aim to evolve how people work. #FutureOfWork #WorkplaceStrategy #Backbase #LifeatBackbase Ajay Soni, CISSP, CISM, CISA, CRISC Venkat Akkapeddi Mohil Kapoor Swapna Natesh

📌 How to build a context-first cloud collaboration model When I first started managing cloud projects, every workspace felt disconnected. Docs lived in Confluence. Diagrams in Lucidchart. IaC in GitHub. And every team built from a different version of “truth.” But I learned quickly: without shared context, automation stalls, standards drift, and AI has nothing to reason from. Context isn’t metadata, it’s the foundation of collaboration. The fundamentals don’t change. Context gives intent. Structure gives discoverability. And discoverability gives intelligence. But here’s the reality. Every team organizes context differently. Architecture diagrams go stale. Naming conventions diverge. Tags get inconsistent across Terraform, Bicep, and ARM. And when you bring AI into that mix, it amplifies the noise instead of reducing it. The challenge is fragmentation. Workspaces aren’t linked to documentation. Policies don’t reference design docs. Agents can’t differentiate between a baseline and a one-off exception. Greenfield and brownfield projects coexist but don’t inform each other. The opportunity is convergence. A context-first model uses shared primitives across people, workspaces, and agents: ✅ Unified workspaces: one environment to design, review, and maintain infrastructure together, across Azure, AWS, or GCP. ✅ Contextual tagging: every doc, diagram, or decision tagged and searchable, forming a living knowledge graph. ✅ AI grounding: agents trained on your internal standards and past configurations, not just prompts. ✅ Cross-project memory: greenfield designs informed by brownfield reality; lessons encoded, not forgotten. ✅ Collaborative governance: teams co-own architecture, standards, and enforcement, all in context. A context-first cloud model isn’t just collaboration. It’s governance through shared understanding. Because the biggest blocker in AI-driven infrastructure isn’t missing automation ... it’s missing context. Ps: lmk if you would like to check the GitHub repo that we created Would ❤️ your feedback!

Hybrid work brought people back. The challenge was bringing the energy back with them. Many companies returned to the office after the pandemic, ready to rebuild momentum, only to realize something important: Presence and participation are not the same thing. Desks were occupied, but collaboration needed support. People showed up for meetings, but the spark that drives creativity was harder to sustain. The workplace needed more than a physical return; it needed belonging. A returning client saw this challenge clearly. Their hybrid team was engaged remotely, but in-person energy needed rebuilding. They wanted a workspace that people looked forward to coming to, not out of obligation, but because it felt meaningful. Instead of adding more desks, we worked together to redesign the environment around connection and teamwork. At WorkSocial | Shared Office Space | Enterprise Coworking (TM), we created: • Collaborative zones that encouraged real-time interaction • Informal spaces that supported organic conversations • Layout choices that increased movement, visibility, and energy • Creative corners to help teams think together and solve problems faster The impact became visible quickly: ➤  In-person collaboration doubled within 30 days, giving teams more shared problem-solving time and reducing back-and-forth delays. ➤ Attendance increased by 45%, driven purely by choice, not policy. ➤ Meeting quality improved, with clearer decisions and faster alignment.' ➤ Team rhythm stabilized, helping everyone work with more energy and less friction. That shift matters. A workspace can hold people, or it can activate people. One keeps operations running. The other builds momentum. If your workspace could rebuild energy inside your team, what would you redesign first: the layout, or the experience?

SharePoint, Teams & OneDrive in the Real World – Day 3 Teams: The Collaboration Hub We've explored OneDrive as your personal workspace, today, let's talk about Teams. Let's start with one of the biggest misconceptions I encounter: Teams is NOT a file storage platform. And that statement surprises a lot of people.   What Teams Was Built For Teams was designed to bring people together. At its core, Teams is a collaboration hub that combines: ✔ Chat ✔ Meetings ✔ Collaboration ✔ Shared workspaces ✔ Communication ✔ Productivity tools Teams allows you to communicate, share ideas, work on things together, hold meetings, and keep projects moving forward.   The Hidden Relationship Between Teams & SharePoint Here's something many Microsoft 365 users don't realize: Every Teams Group is a SharePoint site. When you create a Team, Microsoft automatically creates a SharePoint site to support it. That means: 📁 The files you see in Teams are actually stored in SharePoint. 📁 The permissions are managed through SharePoint. 📁 The version history lives in SharePoint. 📁 The retention and compliance controls come from SharePoint. Teams is simply providing a user-friendly way to access and collaborate on that content. Think of it this way: Teams = The Collaboration Experience SharePoint = The Content Foundation They work together, but they are not the same thing.   Why This Matters Understanding this relationship changes how you think about governance. When you know where your content actually lives, you can: ✔ Better manage permissions ✔ Improve information security ✔ Apply retention policies correctly ✔ Reduce content sprawl ✔ Improve search and findability ✔ Build a stronger foundation for AI Many governance challenges don't start in Teams. They start in the SharePoint sites supporting those Teams.   Teams and AI As organizations begin adopting Microsoft Copilot and other AI tools, this connection becomes even more important. Copilot isn't looking at "Teams files." It's looking at content stored within Microsoft 365. That includes the SharePoint sites behind your Teams. If those sites are well organized, governed, and properly secured, AI becomes far more valuable. If they're cluttered, overshared, or unmanaged, AI will surface those issues just as quickly.   The Takeaway Teams is where people talk about the things. (Collaboration Space) SharePoint is where the things we talk about live. (Knowledge Space) The more you understand that relationship, the better equipped you'll be to build a Microsoft 365 environment that is easier to manage, easier to secure, and ready for the future. Because successful Microsoft 365 environments aren't built by accident. They're built intentionally. #Microsoft365 #MicrosoftTeams #SharePoint #OneDrive #DataGovernance #InformationManagement #AIReadiness #MicrosoftCopilot #DigitalWorkplace #M365 #Collaboration #SharePointInTheRealWorld #TeamsInTheRealWorld #OneDriveInTheRealWorld #KnowGovernManageProtect

I feel like nobody’s talking about this: Slack, Notion, and Figma aren’t just new tools, they are part of a movement. A tectonic shift in how teams operate. The change is something I call “default-open” vs. “default-closed.” Here’s how to operationalize these tools in a way that’s a game-changer: 1️⃣ Slack: Workstream Visibility is now Default-Open 🔻 Old way: In most companies, visibility into teams/projects is default-closed. If you’re not invited to the meeting, or added to the email chain, you may have no idea a project even exists. ✅ New way: Slack channels are default-open. Anyone can browse all the public channels that exist. What I’m seeing is that the smartest companies lean-into this. Each workstream gets its own channel. Anyone who wants to visibility can drop-in, see pinned documents, timelines, etc. And for those of us who are already in way too many meetings, this allows us to be informed async - almost like being in two places at once. 2️⃣ Notion: “Pull vs. Push” Onboarding and Context-Sharing 🔻 Old way: When onboarding a new hire, I used to have a ritual where I’d scramble through my inbox, forwarding dozens of files. I had to manually add new hires to every tools—Google Docs & Sheets for Team A, Jira & Confluence for Team B. If I forgot something, the new hire might lack context for weeks. I had to push all the context to them because everything was “default-closed.” ✅ New way: Last year I joined a startup that had built a culture around async collaboration with Notion. Each team had a self-organized workspace with meeting notes, project boards, and a team directory. They invited me to Notion on a Friday. By the time we had our kick-off meeting on Monday, I’d already self-onboarded: I knew the growth team, the strategy, and what projects were active. I could start adding value on day one. 3️⃣ Figma: Uniting the Creative Process Across Creation, Collaboration, and Remixing 🔻 Old way: Design felt like a relay race—designers worked in Photoshop, then uploaded to InVision for feedback. Final assets were emailed as un-editable PDFs. And minor updates meant filing a ticket and going back through a designer who’d rather be doing something more impactful. ✅ New way: With Figma, Designers, PMs, marketers, and developers can all collaborate on the same platform. Feedback happens directly in Figma, and developers grab assets without the back-and-forth. Here’s where it gets exciting: non-designers can jump-in and make updates themselves. This allows marketers to move faster, and it allows designers to stay focused on the high leverage work that only they can do. 🔸 Why It Matters 🔸 If you think of these as just tools, that’s all they’ll be. But if you adopt them streamline collaboration—they drive a fundamental shift in how teams operate. By making workflows faster and smarter, they empower teams to work independently, often reducing the need for extra layers of management.

In 2006, Google Workspace pioneered real-time collaborative editing across Docs, Sheets, and Slides. Microsoft adopted it in 2013. Both solved the same problem: getting humans working together in the same documents, in real time. But the workforce has changed. Teams don't just include people anymore — they include AI agents. And the tools haven't caught up. Agents still live in separate interfaces, disconnected from the documents where decisions actually get made. From day one, Athena and the Olympus platform have been collaboration-first for both users and agents. In this walkthrough, Tithi Agrawal does research and adds it directly into a shared document. She comments and tags Aldrin Jenson and Christopher Robertson — they jump in, contribute their work, and tag Athena Intelligence. The AI agent picks up the thread, reads the context, and executes her part of the workflow. All in one place. No tool-switching, no context loss, no separate AI interface. The first wave of collaborative editing connected people. The next wave connects people and agents in the same workspace. Watch the full walkthrough below in our Microsoft-Word compatible editor.