S

SharePoint

Document libraries dressed as a CMS, with metadata columns instead of folders.

SharePoint isn't really a file folder; it's a document library that pretends to be one. Files live in lists with custom metadata columns, content types, and views you can filter and group by attribute rather than path. That column-driven model is genuinely powerful for structured records and genuinely baffling for anyone expecting a simple tree. The interface braids site pages, web parts, and libraries together, so navigation depends on how an admin built the site, and two SharePoint sites can feel like different products. Check-in/check-out, approval flows, and deep versioning are first-class. The cost is a steep conceptual load and inconsistent surfaces, plus permission inheritance that's easy to misconfigure. Governed well it's an information system; governed poorly it becomes the place files go to get lost.

Flows

Flows for SharePoint are being captured

We haven't taken SharePoint apart screen by screen yet. Explore the UX patterns it's known for, or request an audit of your own product.

Request a UX audit

Teardowns

Teardowns of SharePoint are coming

We haven't published a written teardown of SharePoint yet. Explore related topics, or request an audit.

Request a UX audit