How do you give a project-driven engineering company one place to see every customer project — status, team, milestones, BI and documents — without leaving the tools they already live in, and within the platform's native components?
A German intralogistics / warehouse-automation company runs large, complex customer installation projects in parallel. Status, team, milestones, reports and documents lived in different places — so there was no single, governed view of a project.
This had to live inside Microsoft 365 using native SharePoint components and Teams — not a free design canvas. The real challenge was designing a clear, scannable experience within an existing component system that engineering could actually build and maintain.
Unify news, milestones, org chart, embedded BI and documents so people stop hunting for information across tools.
No free canvas: design within native components, keeping consistency and real build-feasibility for the client's team.
Sensitive project data needed a separate, governed layer — not everything visible to everyone.
Project info was scattered across tools and folders.
A single project view unifying news, milestones, org chart, embedded BI and documents.
It kills the hunt for information — the project is legible at a glance.
People think by project and by client, not by document library.
IA structured project → client, filterable by real identifiers (project / offer number, project lead).
Navigation matches how the company actually works, so nothing needs translating.
The platform was constrained to SharePoint / M365 components.
Design within native components instead of a custom canvas.
A maintainable system the client's team can own and extend — not a one-off mockup.
Some project data is sensitive and shouldn't be visible to all.
A separate confidential layer in Teams ('sensitive data') with its own permissions.
Governance of who sees what, without bolting on a second system.
The org chart needed to be actionable, not decorative.
Interactive org chart with a context menu + a person modal.
Role, team membership and contact are one click away, without leaving the page.
People think by project and by client — so the IA does too, with a parallel Teams layer for collaboration and governance.
The hub is organized the way the company runs projects: overview → single project → its facets, with a parallel Teams layer for collaboration and governance.
One governed entry point: every customer project as a card, found by the identifiers the company actually uses.
The heart of the hub: everything about a project assembled in one governed place, built from native SharePoint components.
One project, one screen — news, milestone plan, org chart, embedded BI and documents, so nobody has to leave to assemble the picture.
The org chart is actionable, not decorative — it answers 'who owns this?' in the flow of the project.
Context menu: quick actions on a person without leaving the chart.
Person modal: role, team membership and contact in place.
The hub never asks people to leave the tools they already live in. SharePoint, Teams and PowerBI converge on a single project.
Project overview, single project view, reports, documents — built from native components.
Per-project channels, posts, milestone plan, and a confidential 'sensitive data' library.
SAP-sourced reporting embedded directly into the project view.
Three Microsoft 365 surfaces, unified per project — the user never leaves the tools they already live in.
Project conversation lives where the team already is — channels per project.
The same milestone plan, surfaced inside Teams — one truth, two surfaces.
A separate confidential library governs who sees sensitive project data.
Reports surfaced inside the project, not in a separate reporting tool.
Progress tracked against the milestone plan — status you can trust.
Documents governed by SharePoint, attached to the project they belong to.
Aggregated dashboards for the portfolio-level view across projects.
The result is a single place for every customer project across SharePoint and Teams — status, team, milestones, BI and documents unified — built entirely within Microsoft 365's native components so the client's team can own and extend it.
I'd instrument whether PMs actually land here first, and track time-to-find for key project info.
The context menu + modal pattern works, but I'd refine discoverability and keyboard access.
I'd templatize the project view so a new project spins up with zero design effort.
Anonymized case — real work, no client or end-customer names. Screens are shown blurred for confidentiality (logos, project numbers and sensitive-data markings are not legible).