Episode Details

Here’s a question: Is SharePoint still just an old document dump with complicated permissions—or has it become the engine powering collaboration in modern workplaces? Most people haven’t seen the leap it has made inside Microsoft 365. What SharePoint can do today is very different from what it did yesterday, and it’s exactly why so many organizations now build their digital workplace on top of it. So what changed—and why does it matter for your workflows? Let’s break it down in ways you probably haven’t seen before.The Ghosts of Old SharePointMost IT pros remember SharePoint in its early years as the system that made storing documents feel like navigating a maze. You’d set up a site for a department, and before you knew it, half the team couldn’t find where their files went, while the other half couldn’t understand why they suddenly lost access. That memory lingers because for many people, the pains of old SharePoint felt like more than just technical hiccups—they felt like structural flaws in the platform itself. And once a tool gets stamped with that reputation, it tends to stick in an organization’s culture far longer than the product itself actually deserves. Think back to when the interface looked like a patchwork of early-2000s websites. You had lists layered on top of document libraries, permissions stacked on permissions, and navigation menus tucked into places no end user would naturally find. IT admins often spent hours trying to explain to employees why a document library wasn’t the same as a folder structure, but to most users it just felt like extra steps between them and their files. The bigger problem wasn’t that SharePoint lacked features—it had plenty. The issue was that every step forward for flexibility seemed to add two steps of complexity. Permissions management was easily the number one complaint. If you wanted to give one person access to a folder, you had to break inheritance. Then, if someone wanted access to part of that folder, you’d start layering exceptions, and suddenly the entire security model turned into spaghetti you couldn’t untangle. Departments often spun up sites on their own without understanding the long-term impact, and soon IT was faced with a patchwork of silos, each with its own rules. That’s when users started running into errors like, “Access denied,” or worse—finding documents that were supposed to remain private. I remember one story from a mid-sized marketing department. They needed a workspace to manage campaign assets, so they asked IT for a SharePoint site. Within a month, everyone had their own version of access levels: some as contributors, some as viewers, some as site owners. When a new employee joined, no one knew which group to place them in, so permissions were copied, pasted, and improvised. By the second quarter, files were going missing, restricted reports were viewable by interns, and no one could track which version of a campaign document was the latest. Instead of helping collaboration, the site created confusion—and that story is far from uncommon. The reputation problem wasn’t just anecdotal either. Blogs and IT forums from the 2010s are filled with admins describing SharePoint as “the product everyone is forced to use but no one enjoys.” Adoption surveys from that era consistently ranked SharePoint at the bottom of collaboration tools, and much of the feedback revolved around the same themes: confusing interface, permissions chaos, and the fact that training never seemed to stick. Even people with years of experience administering the platform admitted they often leaned on third-party tools because SharePoint out of the box felt incomplete or hard to manage. Because of that legacy, many organizations still carry strong feelings about SharePoint, even if they haven’t touched the modern version. Leaders who used it back in 2012 assume it’s still the same clunky system in 2024. That perception gap has real consequences. Teams delay projects because they believe s