🔬 Design principles for an agentic Confluence We've been exploring what "agentic" actually means inside a collaborative document, especially how we represent humans and agents working together. Here’s a behind-the-scenes walkthrough from Confluence designers Nat Johnson and Eden Gorton on their application of these principles: 1) Extend what already works - leverage a common design system for both humans and agents, so users do not need to relearn anything 2) Agents appear wherever humans do - this naturally involves a ton of trade-offs between visibility and UI density, but we're aiming to find that sweet spot for comprehension 3) Make it easy to 'Pop the hood' - you should be able to drill down and see the specific moment of a particular edit Agentic Confluence is a hugely powerful and exciting phase shift for teams, and I hope hearing from the designers communicates the care (debates and all) that is going into the change.