AI workspace setup for People teams (Claude, ChatGPT, Copilot)

"We gave the whole company Copilot. Why does nothing feel different?" It is the question a CEO asks about six weeks after the rollout, and it is the right question. The honest answer is that an AI workspace setup was never done. People open a fresh chat, paste a question, get a fresh-from-the-internet answer, and conclude the tool is shallow. The tool is not shallow. The setup is. The same model that gives you a bland onboarding checklist on Monday gives you something specific to your company, your tone, your last reorg and your CPO's stated priorities on Friday, once it can see where it is standing.

Nothing about the model changed between those two days. The context did. A workspace is the structured layer that carries that context, and it is the cheapest, highest-return thing a People function can build first. It is not glamorous. Skip it and every other layer you build on top is weaker.

What an AI workspace setup actually is

Every consumer AI tool gives you the same three primitives. Learn them once and the naming stops mattering.

A standing brief the model reads at the start of every conversation: who you are, who you work with, the tone you want, the things you never want it to do. Named containers that hold files, instructions and history for one kind of work. And reference documents, the five to ten files the model should always be able to see when it works on a given thing. That is the whole unit. Everything else is variation on those three.

The tools disagree only on vocabulary. If you have picked a tool because you were told one of them "does workspaces" and the others do not, you were sold a feature that all four share.

Pick the one your company already pays for. The setup is portable, so the tool decision matters far less than the setup decision, and waiting for a tool review before you build the workspace is how a team loses a quarter. If you are genuinely choosing between models, choosing AI models for HR work is the piece for that, but it is a separate decision from this one.

Custom instructions: write a brief, not a personality

The mistake people make is treating the standing brief as a vibe. "Be friendly. Be concise. Use British English." Fine, but it barely moves the output. What moves it is telling the model what you actually do, what you actually care about, and what you have already decided.

A real standing brief for a Head of People at a 250-person scale-up reads more like this:

I am the Head of People at a Series B B2B SaaS company, 240 people, growing to 350 this year. Our principles are written, used, and matter, and I will share them. We run hybrid with a London hub. Our biggest current pressures are manager capability, performance differentiation, and absorbing 120 hires without losing the culture.

When I ask for drafts: write in plain British English, sentences short, no consultancy padding. Never use the words "leverage", "synergy", or "best practice". Never recommend a framework without telling me the trade-off.

When I ask for analysis: assume I have read the obvious, skip the 101, show me the second-order effects. If you do not know something specific to my company, ask before guessing.

That is a brief. The model behaves differently because it now knows where it is standing, what good looks like to you, and where the edges are. The last line does more work than the rest combined: an instruction to ask before guessing is what stops the confident, wrong, generic answer that makes people distrust the tool in the first place.

Projects: one per workstream, not one per task

A project is a folder with memory. The only real skill is choosing the right size of folder.

Too small, one per task, and you spend your life setting up new projects and re-uploading the same handbook. Too large, a single project called "People Ops", and the context becomes a blur and the model loses the thread. The right grain for most People functions is roughly six to ten projects, mapped to the workstreams that actually repeat.

• Performance and calibration. Cycle docs, calibration grids, manager guides, last cycle's learnings.
• Comp and levelling. Job architecture, salary bands, last benchmarking exercise, comp philosophy.
• Onboarding and first 90 days. The playbook, role-specific plans, the six-week check-in template.
• Manager development. Capability framework, training catalogue, last enablement deck.
• Engagement and culture. Survey results, action plans, the principles, the rituals.
• Talent acquisition. Workforce plan, EVP, scorecard templates, last quarter's funnel.
• Org design and change. Current org chart, planned changes, prior reorg postmortems.
• Board and exec comms. Board pack template, last three updates, voice and tone notes.

Each of these is a project. You open a conversation inside it and the model already holds the context. You do not paste the handbook for the fortieth time. The workstream is the unit because that is the thing that actually recurs. A role is not the unit. A role is forty workflows in a coat, and half of them belong in different projects.

Reference documents: the three-tier rule

Inside each project, not every document deserves equal weight. Give the model everything at full volume and it drowns. The structure that works is three tiers, and they are a genuine stack: the always-on layer is the ground the other two stand on.

Tier 1 is the one people get wrong, in both directions. They either skip it, so the model has no ground truth and every answer starts from the internet, or they bloat it, so the model reads three thousand words of preamble before it reads the actual question and every answer comes back padded. Keep each Tier 1 document to half a page. Dense, not long. The model reads them every time, so their weight is the tax you pay on every single output.

Most teams have only Tier 3. They paste, work, lose. Adding Tiers 1 and 2 is precisely what turns AI from a clever search bar into a colleague who already knows the context.

What never goes into the workspace

A workspace is defined as much by what it excludes as by what it holds. Run every document through a short filter before it goes in, because a standing project is the one place careless data becomes permanent.

Those first two rules cover most of the risk. Employment law varies, contracts have teeth, and confident-sounding generic answers about either are dangerous. This is the floor, not the ceiling. When you get to it properly, the governance work sharpens it further, and AI governance for People teams is the piece that does that. But you do not need the full policy to start. You need these four questions and the discipline to actually ask them.

The team move, and the 90-minute build

Everything above can be done by one person. The move that compounds is doing it together. A shared workspace, the same projects, the same Tier 1 documents, the same standing brief, means everyone in the function works from one source of truth. The output looks like it came from one team. The improvement one person makes flows to everyone. And the institutional memory stops walking out the door when a long-tenured colleague leaves, because the context they carried in their head now lives in a project.

This is where the champion model earns its keep. The champions own the workspace. They keep the Tier 1 documents tight, retire stale projects, and update the shared context when the reorg lands. They are the librarians of the team's context, and without a named owner the workspace rots the way any shared drive rots.

The build itself is not a project plan. It is 90 minutes.

The whole thing takes less time than most teams spend, across a quarter, complaining that AI feels generic.

What good looks like three months in

A team with a working workspace looks different in a few quiet ways, and the difference is easiest to see side by side.

Quiet, unglamorous, infrastructure work. But it is the precondition for everything above it. You cannot build reliable skills, automations and agents on top of a generic chat history, which is why moving from prompts to systems starts here and not with a tool purchase. The workspace is Layer 1 of the People Ops AI stack, and skipping it is why so many teams stall at clever demos that never become part of how the work runs.

If you are not sure where your function actually stands before you build, the Readiness Assessment scores you across the four capability layers in about ten minutes, and it tends to make the case for starting here obvious. For the wider map of how workspace, skills and agents fit together, the AI workspace for People Ops pillar holds the full arc.

Set the workspace up. Then build.