Human-AI Collaboration

Tuesday afternoon, a product lead pastes last week’s customer complaints into a personal assistant and asks for “the board version.” The paragraph that comes back is fluent. It names a theme. It even invents a tidy percentage. By Thursday finance has a different number in a sheet, legal has a different clause in a redline, and the pack that goes upstairs contains a sentence nobody would sign if they were asked to put their name under it. The model did not fail. The role did. Someone produced a draft. Nobody owned the outcome.

That is the ordinary shape of human-AI work in most companies right now. McKinsey’s State of AI found that 88 percent of respondents say their organisations use AI in at least one business function, up from 78 percent a year earlier, while nearly two-thirds remain in experimentation or piloting and only about a third have begun to scale. Use has become ordinary. A shared job with a named closer has not.

Human-AI collaboration is not a slogan about synergy. It is a change in what the person is for. The person spends less time producing the first draft and more time judging whether the result may leave the room — and leaving a record of that judgement. What is collaborative AI is the definition of the shared job. This page is the role question: what the human still owes the organisation once the model can write.

Why a personal assistant fails this job

A personal assistant is built for one owner. That person types, pastes a file, copies a paragraph out, and sends it under their own name. If a colleague needs the same answer, they open their own window and start again. Microsoft and LinkedIn’s 2024 Work Trend Index found that 75 percent of knowledge workers use generative AI at work, and that 78 percent of those users bring their own tools. Personal use is already the default. That is useful data about desks. It does not tell you whether two departments share one job.

The failure is not that the paragraph is bad. The failure is that the paragraph has no home. Asana’s Anatomy of Work Index (2022), from a survey of more than 10,000 knowledge workers, attributed 58 percent of the day to coordination — “work about work.” Asking who has the latest draft, which file is live, and whether legal already said no is that tax. A personal assistant can summarise each inbox. It cannot give the next person one job with the same files, the same rejection, and a named closer.

Yang and colleagues, writing in Nature Human Behaviour (2022), used email, calendar, and message data from more than 60,000 information workers and found that firm-wide remote work made collaboration networks more static and siloed, with fewer bridges between groups. Handoffs that used to cross a desk now die in channels the next shift does not watch. A private copilot makes the silo cheaper to live in. Each person has a fluent answer. Nobody has the same file.

Collaborative AI and personal assistants is the side-by-side. Keep the personal tool for solo writing. Add a shared layer where two teams must stand on the same number, clause, or customer change. The org-chart problem is what happens if you buy the personal tool and stop there: the work moves into private windows, and the accountability stays on a job description that still says “produce the pack.”

How the shared room works

The shared room is not a channel with a bot in it. It is a named job with a roster, the files both teams already forward, a bounded role for the model, and a person who can refuse.

At minimum the room holds four things:

• A named job, not “the channel” and not “the thread.”
• People who can see the same files and the same history.
• Tools that read, and sometimes propose a write, with a recorded step.
• Someone who can say the change does not go out.

The AI role is narrow. It may read the attachments you put on the job. It may draft a list, a commentary, or a payload quote. It may not send customer mail. It may not change a live system until a named person signs the exact change. What is human-in-the-loop AI is that gate: a person sees the exact change, signs with their identity, and leaves a record. A thumbs-up on a chat is not that gate.

Governance as a multiplayer primitive is why roster, rejection, and inherited authority have to live in the room. A connector that can write is a loaded tool. A person without the authority to release must not inherit that tool because the prompt was confident. RBAC for enterprise AI is the access model: a guest sees a slice; a member proposes; someone else can reject.

The skill that rises is not a longer prompt. It is knowing which context the model must see, and when to stop it. “Promptcraft” as a private art — structuring queries to elicit a nicer paragraph — is still a personal-assistant skill. In a shared room the scarce skill is judgement: which extract is live, which definition is in force, which rewrite dropped a defined term, which payload must not go out. Data interpretation and ethics are the same skill under another name. The model can analyse at a scale no person can. The output is only as good as the files it was shown and the question it was asked. The final decision, the contextual understanding, and the moral responsibility stay with a named person.

Systems thinking is the organisational version. It is no longer enough to be expert in a single domain if the model’s draft will be treated as the company’s sentence. The person has to see how the draft travels: from a private window into a pack, from a pack into a target, from a target into a customer email. Decisions made in direct messages is how a draft becomes three drafts. The shared room is how you stop paying that tax.

What breaks if the org chart stays the same

Legacy structures assume the person who produces the artefact is the person who owns it. Once a model can produce the first draft, that assumption fails. The work moves toward whoever has the friendliest prompt. The accountability stays on a title that still says “analyst,” “counsel,” or “controller.” Someone still has to own the outcome the model helped produce. If the chart only names who may log in, and not who may release a number, a clause, or a customer sentence, the organisation has bought speed without a closer.

Team-level autonomy with guardrails is the useful version of “agile.” Smaller teams can take on more because the model drafts. That autonomy is not a licence to release. The guardrails are the roster and the stop: who may propose, who may refuse, what class of write is even available. Experimentation closer to the customer is valuable when the experiment is a draft. It is a liability when the experiment is a fare-like sentence or a journal that posts.

Learning cultures are not a moat if the learning lives in private threads. The valuable learning is the stored rejection: finance’s “no,” legal’s “no,” the controller’s “no.” That “no” has to survive the person who typed it. Search is not memory is why “search Teams for last Thursday’s pack” is not a file. Keep the decision on the job while it is open.

A common pilot is one person and one copilot. That can be the right first step. The next step, if the work is shared, is a room — not forty copies of the same prompt, and not a reorganisation that adds “AI” to every title while leaving the closer unnamed.

How to practise the new role on one job

Pick the next joint artefact that already has two owners: a forecast line, a discount exception, a clause that will be sent, a hold that a partner will pick against.

Ask four questions:

• Does more than one department have to stand on the result?
• Could the output change a live system or a customer-facing sentence?
• Will someone who missed last week’s chat need to pick this up?
• Would you need to show a proposal, a rejection, and a landing six months later?

If you answer no to all four, a personal assistant is enough. Sanction it. If you answer yes to any, put the brief in one place, add the people who already argue about it, attach the two files they always forward, and name who can say no. Run it once with the model drafting and the humans deciding.

The harness — the tools, stops, and checks around the model — is what keeps “just send it” from becoming an unsupervised clerk. Harness engineering is the environment guide. How to evaluate collaborative AI is the sheet to score whether any vendor keeps files, rejections, and a second department on the same job.

Do not start by renaming roles. Start by naming the closer on one class of work. What an AI workstream is is the container: brief, files, people, finish line. The organisation already thinks in tickets, packs, and matters. The missing object is often the shared ticket that finance and legal can stand on, not another bot in a channel.

NIST’s AI Risk Management Framework asks for measurable governance. On a role, measure three things: how often a joint artefact is still decided in a side chat after the job exists; whether a later reader can reconstruct who signed without asking the author; and how many runs stopped because a person refused. A month with drafts and no refusals is a month you bought fluency without a control.

How this shows up in Nimbus

In Nimbus, the shared room is a workstream: brief to signed-off deliverable, humans and agent teams on the same surface. Agent teams draft. Humans release. Governance defaults to read-only writes. Approval workflows sit on every write action. Soft, Hard, and Critical checkpoints name how serious the stop is. Decision History logs actor, tier, and timestamp. Nothing writes back until you explicitly approve the deliverable.

That is the product expression of the role change. The person is not there to type the first paragraph. The person is there to judge the payload and leave a name on it. The Lifecycle Graph keeps signed-off work as institutional memory the organisation owns. A private chat does not.

Score any vendor, including this one, with how to evaluate collaborative AI on a real joint artefact, not on a polished email demo. The use cases hub lists the function walkthroughs if your first shared job is a forecast, a clause, a hold, or a people decision.

Get started for free. If two departments already share the artefact and need one roster before anything can leave, talk to sales.

Related guides

• What is collaborative AI — the definition of the shared job.
• Collaborative AI and personal assistants — when the personal tool is enough.
• What is human-in-the-loop AI — a person sees the exact change.
• How to evaluate collaborative AI — the sheet for the job, not the copilot.
• Governance as a multiplayer primitive — roster, rejection, and inherited authority in the room.