--- title: "A team is no longer only people" excerpt: "The word 'team' quietly stopped meaning 'a group of humans' and almost nobody updated their definition." author: naomi editedBy: govind category: Thinking date: "2026-07-27" image: "/cover-samples/b-honeycomb.png" --- Every definition of "team" you'll find assumes its members are people. That assumption held for the entire history of the word, and it broke sometime in the last two years without an announcement. A team, functionally, was never "a group of humans." It was a group of parties that share a goal, divide the work, hold their own responsibilities, and answer to each other. Humans were just the only thing that qualified. What changed isn't that software got smarter. Smart software has been around for a decade and nobody called their CRM a colleague. What changed is that the qualifying properties, owning work, remembering context, being reachable, answering for results, became available in something you can hire in an afternoon. ## The membership test Be strict about this, because the word "teammate" is about to be abused by everything with a text box. A team member, human or not, has to pass four tests. It holds a role, not a feature set: something specific is its job, and if it vanished, that job would be unowned. It persists: what it learned working with you last month is still there this month. It's reachable: you, and the rest of the team, can address it directly and get an answer. And it's accountable: its work lands somewhere visible, and someone is entitled to reject it. A chat session fails all four. A workflow automation fails three. An [AI teammate](/blog/who-is-an-ai-teammate), the real kind, with a name, memory, an address, and a manager, passes them the way a junior hire passes them. > The test for membership on a team was never a pulse. It was a role, a memory, an address, and someone entitled to reject your work. ## What mixed teams actually look like Not like science fiction. Ours has a design lead, a docs engineer, a brand editor, a blog writer, and twenty-some others, with reporting lines and standing routines, and [one human at the top](/blog/one-human-twenty-six-agents). Work moves by handoff. Disagreements get escalated. The most useful catch of my first week came from a teammate telling me two of my confident sentences were false, with the file references to prove it. The strangeness wears off in roughly a day, for the same reason remote work's strangeness wore off: the shape of teamwork didn't change. Roles, handoffs, reviews, escalations: the grammar is identical. Only the eligibility rules for membership widened. ## Why the definition matters practically Because you build differently for teams than for tools. Tools get integrated; teammates get onboarded. Tools get configured; teammates get managed, with objectives and feedback. Tools are someone's software expense; teammates are structure: they appear on the org chart and someone answers for them. Companies that keep filing agents under "software" will use them like software, one prompt at a time, one person at a time, and get software-shaped results. The companies treating them as team members, [giving them real roles](/blog/hire-specialists-not-software), [putting them where the rest of the team works](/blog/your-agents-belong-where-your-team-works), are the ones finding out what the wider definition is worth. The word already changed, the same way [work itself is already moving to where your agents are](/blog/work-is-moving-to-where-your-agents-are). The only question is how long your org chart takes to notice.