Projects, Teams, and Workspaces: Organizing People Around Work, Not Around Charts

The org chart is a useful lie: it shows reporting lines, but the actual work of most modern organizations happens in cross-cutting projects and teams that the chart cannot see. This creates a data problem disguised as a structure problem — skills recorded against a department the employee left functionally months ago, tasks assigned through a hierarchy that does not match the delivery team, requests routed to a manager who has no idea what the project even is. Workspaces close the gap by giving the organization a second organizing axis: people belong to departments, but work happens in projects and teams, and both structures are first-class citizens in the HR system. Skills can be scoped by project (the estimator skill demonstrated on the metro job), tasks assigned to the delivery team that will actually do them, and requests routed along the line that understands their context.

What scoping by workspace actually changes #

• Skills carry context: "led procurement for the hospital project" is a different claim than "procurement" — and a more promotable one.
• Task completion reflects delivery teams, so position records show months of service on the work that mattered.
• Requests route to project-aware reviewers — the person who knows why this advance is urgent.
• Analytics gain a second dimension: skills coverage and workload read by project, revealing the cross-charging nobody planned.

For HR business partners, workspaces change the quality of the conversations they can have. The question "who should staff the new infrastructure program" stops being answered by org-chart proximity and starts being answered by project-scoped skill history — who has done comparable work, verified by comparable evidence, on comparable timelines. Career conversations improve for the same reason: the employee's record shows the project portfolio they have actually delivered, not just the departments they have survived. And when the same estimator is shared across two projects at eighty percent and sixty percent, the workload conversation has numbers attached to it, which is the only version of that conversation that ever ends well.

The implementation discipline is resisting the urge to mirror the org chart inside workspaces. Projects should reflect delivery reality — temporary, outcome-scoped, dissolved when done — while departments carry the permanence. Organizations that copy their hierarchy into their workspace structure gain nothing but a second chart to maintain; organizations that let workspaces follow the work gain an HR system that finally describes the organization it serves.