How should AI design connect individual work to team knowledge?

Atlassian's design guidelines for its Rovo AI product state that AI interaction design should extend past the individual user to the team around them. The guidelines say AI should "connect individual work to the broader team's knowledge, context, and workflows," surfacing "relevant expertise, resources, and shared information so people can build on each other's work while maintaining privacy and permissions," such that "AI amplifies both personal productivity and team impact." A companion guideline asks AI to "support multiplayer collaborations by letting work move fluidly from individual effort to shared human-AI teamwork," so that work "feel[s] continuous and connected across people, teams, and intelligent agents."

The guidelines frame this team-level connection as resting on several individual-level principles stated earlier in the same set: AI should read "the context of the person, team, and company knowledge" to make "smart assumptions about when to be proactive"; it should "preserve a user's flow" with controls "embedded directly in the working surface" and state that "carr[ies] over seamlessly" across interfaces and devices; and it should give people "clear insight into system state and how outcomes are produced," with logs, documentation, or advanced controls "adjusted to user role and preference." A further guideline ties Atlassian's brand identity into the interaction itself — "a subtle blue thread" of tone, color, and micro-animation meant to "anchor the interaction in a cohesive Atlassian identity" even as outputs vary by context. The set closes by asking that delegated AI output stay "high quality and efficient, not rushed or careless," with risks and "opportunities to course-correct along the way" communicated as work proceeds.

This reframes Can AI boost how teams work together? as an interaction-design checklist rather than a research argument: where Microsoft's report argues for the shift in the abstract, Atlassian's guidelines operationalize it as specific UI commitments (embedded controls, cross-surface state, role-adjusted transparency, multiplayer handoff). The guidelines sit in the same genre as How should AI systems be designed across different interaction phases? — a company- or lab-authored list of principles for human-AI interaction — but organize by theme (context, flow, modality, transparency, team, brand, quality) rather than by interaction phase, and add team/multiplayer collaboration and brand consistency as categories Amershi's list does not name. The transparency guideline — giving users "clear insight into system state," adjustable by role — echoes the demand in How can users verify what an AI agent actually plans to do? that agents make their plans and actions inspectable, though Atlassian's version is framed as a design commitment rather than a common-ground requirement.

The excerpt is a design team's own published guideline page, undated in the source and carrying no study, user test, or validation data — unlike Amershi's guidelines, which were checked against existing products and vetted with practitioners. It states what Atlassian's Rovo design practice aspires to build, not evidence that these principles produce better outcomes, and the "multiplayer" and team knowledge guidelines are stated as short directives without detail on how privacy and permissions are reconciled with surfacing a teammate's work to an AI agent.