How Teams by Activated Human works: the loop, and what your team actually sees
Teams runs as a loop with five moves. The lead declares the team's mission, values, and goals in a guided session, and that context pack loads into a genuinely private AI companion for every member, called Teal. Each member's companion coaches their real working day against that mission, privately, with no manager surface anywhere in the product. What reaches the team has no names attached: every member and the lead see the identical Team Mirror, and nothing reaches it unless the member approved it on a card in their own conversation. Approved items are pooled with teammates' as patterns about the work; pulled items never appear anywhere. The lead commits moves in their own words, and the next Mirror opens with what moved since the last one, so the whole team watches them land.
That is the entire mechanism. The rest of this page walks each move slowly, because the details are where the trust either holds or does not.
Where does the companion get its context?
The loop starts pointing down. The lead runs a guided session and declares what the team is actually for: the mission, the values, the current goals, and how the team operates day to day. That declaration becomes the org context pack, and it loads into every member's companion as coaching context.
This is the difference between Teal and a generic assistant. A generic assistant knows nothing about why your team exists. Teal carries the declared mission into every conversation, so when a member is stuck, frustrated, or deciding where to put their energy, the companion can hold the real question: where does what you care about meet what this team is trying to do?
What does a member's companion do all day?
The companion is built to be the best mentor in the company, and it works for the member, not for the org. It coaches the member's real day against the declared mission: it names where their energy already meets it, says honestly where it does not, and helps the member either reshape the work or prepare a conversation they choose to have. It is also the private container for the things that today have nowhere safe to go. Frustration held alone corrodes the person; frustration vented sideways corrodes the team. A private place to put it, with something that can actually help metabolize it, is team infrastructure, not a perk.
The companion coaches with org context but never speaks for the org inside the member's space. The design bet is that the moment members sense the org talking through a friendly mask, answers go survey shaped and every downstream picture goes dead. Honesty is the fuel for everything below, so the companion's loyalty is structural.
This is also the two for one at the heart of the product: the buyer pays for the team picture, and every member gets a genuinely private companion free. Each half is what makes the other true.
How does anything cross to the team level?
Only by the member's own act, and what crosses has no names attached. Four mechanics hold that up, and each is a property of the system rather than a promise in a policy:
- Symmetry. Everyone sees the identical Team Mirror the lead sees. There is no manager view, no admin view, no back room. One render, whole team.
- The subject rule. What crosses is a property of the work, never a property of a person. Each item is one sentence about the work, the model that writes the Mirror never sees who said what, and every theme in the Mirror is about a work object: a practice, a ritual, a goal.
- The card. When a conversation shows something true about the work, Teal offers it to the member on a card in their own conversation. Nothing travels until the member approves it, and pulled items never appear anywhere.
- No individual egress. There are no individual dashboards, no sentiment scores on people, no flight-risk flags, and no productivity tracking anywhere in the product. Not settings turned off. Not built.
The result is that the org only ever sees the weather, never a person. For the generic version of this pattern and why it has to be architecture rather than policy, see what your team lead can see. For why the anonymity promises of survey tools fail exactly here, see are engagement surveys really anonymous.
What if a member wants to tell the lead something?
They tell their lead. Teams has no channel that carries a message upward, because venting is not feedback yet, and a feeling routed before it becomes an ask arrives as a complaint. Teal helps with the step before: the member works out what they are actually asking for and why, then takes it to the lead in their own words, in a conversation they choose to have. Venting stays private. What reaches the team, and how, is on the Team Mirror page.
How does the loop close?
The lead's own companion coaches the leading from the Mirror, the declaration, and the lead's own moves, never from anyone's private space. A move is something the lead commits to in their own words: a 1:1 opener, a goal restaffed against someone's actual passion, a ritual changed. The whole team sees the moves, the lead marks how each one is going, and the next Team Mirror opens with what moved since last time, for everyone at once.
This is the move the whole category skips. The listening research keeps finding the same gap: 92 percent of employees say it is important that their company listens to feedback, and just 7 percent say their company acts on feedback really well (Qualtrics, 2021 Employee Experience Trends). People stop giving signal to channels that eat it. Teams is built so that acting on feedback is visible to the entire team, in the same artifact, at the same moment, which is what makes giving signal rational again.
What does the org see, concretely?
The contrast, made explicit:
| What the member sees | What the lead sees |
|---|---|
| Their private conversations with Teal | Never these, in any form, ever |
| Their work profile and personal insight report | Never these |
| Their own cards, with the right to approve or pull each item | Nothing about who contributed what |
| The Team Mirror | The exact same Team Mirror, same render |
| Team patterns, no names attached | The same patterns, same render |
| The lead's moves, with the lead's own marks | The same moves, in the lead's own words |
The lead has two things members do not: they set the declaration, and they commit the moves. Every member reads both, and the lead's own companion sees no one's private space.
What does Teams not do?
The limits are part of the mechanism:
- It starts at three seats. Most teams do best at five to fifteen, because past a handful of people a lead stops being able to hold the whole picture in their head, and that is the gap the Mirror fills. Bigger than fifteen, get in touch and we will set it up.
- It does not do performance management. No reviews, no compensation cycles, no goal-cascade machinery, no HRIS integrations. Teams that need that machinery should buy it from the suites that build it well.
- It cannot force honesty. If members do not use their companions, the Mirror is thin. The design bet is that daily private value is what earns real use, but it is a bet, stated as one: the product launched in August 2026 and has no track record yet.
- It is not therapy. Teal is a work companion. When something heavier is happening, it points to real resources.
Questions people ask
Can my manager read my conversations?
No. There is no surface in the product where any individual's conversations, profile, or contributions render for anyone else, at any permission level. The way to verify this is structural: everyone sees the identical Team Mirror, so there is nothing manager-only to hide an individual view inside.
Does a theme need several people behind it to show up?
No. What decides whether an observation can cross is what it is about, not how many people said it. A property of the work can travel with one person behind it; a property of a person cannot travel at any number. One person seeing something clearly is often the most useful thing a team knows, and a contributor count would have thrown it away.
Does the lead see who approved an item?
No. Nothing reaches the Team Mirror unless a member approved it on a card in their own conversation, and the Mirror shows patterns about the work, never who approved what. Everyone on the team reads the same Mirror the lead reads. Pulled items never appear anywhere.
What does the team actually receive at the end of a cycle?
The Team Mirror: values mapped against the declared mission, a strengths picture, an energy read, friction themes with no names attached, and alignment opportunities where someone's actual passion fits an actual goal. From the second Mirror on, it opens with what changed.
Is this an employee survey?
No. Nobody fills out an instrument, there are no response rates to chase, and there is no quarterly window. The team picture is a byproduct of a companion each person uses because it helps them, which is precisely why the picture is true.
Teams runs a Team Mirror with your team: a private companion for every member, one picture for everyone, rendered identically. See how it works. Related: Is Teams legit? and Teams vs Lattice, Culture Amp, and BetterUp.
About the publisher. Activated Human makes Blue, an AI companion for your own life, and HeartWeave, a private space for the people in a relationship. Company facts are on the press page.