Every 1% increase in the context your agents receive produces a 0.38% improvement in output quality. LangChain's State of AI Agents 2026 report makes that measurable — and it makes interface design the highest-leverage investment most product teams aren't treating it as. At Atlassian Team '26 in Anaheim last week, Chief Design Officer Charlie made the case: the interface is what determines how context gets captured, which means every design decision your team makes is now directly setting a ceiling on how well your agents perform. Eighty-eight percent of enterprise agent pilots fail to reach production, with context fragmentation as the top blocker. That is a design problem.
For 25 years, adaptive interfaces were the holy grail — software that reads who you are and adjusts to how you work. Charlie's announcement at Team '26: the technology limitation is gone. What remains is a design question about where to set the balance point between a system that adapts and a system a team can actually share. And at the same time, designing for agents and designing for humans has converged into nearly the same problem — Atlassian's design system is consumed by agents and human users from the same object, with 10% variation. Every shortcut taken on design quality now shows up twice.
Charlie Sutton is Chief Design Officer at Atlassian, where he leads design across Jira, Confluence, Rovo, and the newly announced Dia browser. He sat down with us at Team '26 in Anaheim.
In this episode:
Why 783 tab interactions a day means even tiny friction changes produce outsized aggregate gains — and where to look first
The 25-year holy grail of adaptive interfaces is technically solved — what remains is the design question of how much is right for teams
Why structured objects (goals, strategy, people) beat expensive inference — and why most vendors are paying more for worse results
How Atlassian's design system serves agents and humans from the same object with 10% variation — and what the 10% tells you
Why vibe coding raised the floor so everyone can build, which is exactly why the ceiling on what design must deliver also rose
Why video captures intent that text never can — and how Atlassian is encoding it into the Teamwork Graph
"The floor goes up — everyone can make things awesome. But the ceiling has also gone up. Expectations increase, what is possible has increased. Design is still focusing on that ceiling."
Charlie Sutton is Chief Design Officer at Atlassian, where he leads design philosophy and execution across the company's full product suite — including Jira, Confluence, Rovo, and the newly announced Dia browser. He was involved in building the demos showcased at Atlassian Team '26 and works at the intersection of enterprise product design and AI-native interface development. (Verify Charlie's full name before publishing.)
Guest resources:
Atlassian: https://www.atlassian.com
Dia browser: https://www.atlassian.com/software/dia
Charlie on LinkedIn: https://au.linkedin.com/in/charliesutton
We built productimpactpod.com to be your AI product insights and strategic playbook hub. Check it out.
Thank you for listening to the Product Impact Podcast — if you have feedback, guest recommendations, or want to chat — contact us.
Hosted by:
Arpy Dragffy Guerrero — https://www.linkedin.com/in/adragffy/
Brittany Hobbs — https://www.linkedin.com/in/brittanyhobbs/
Go to Substack to get AI strategy frameworks, news, and jobs: https://productimpactpod.substack.com
This episode was brought to you by:
PH1 (https://ph1.ca) — a strategy & research consultancy specialized in delivering evidence about the highest value use cases and customer profiles.
AI Value Acceleration (https://aivalueacceleration.com) — The consultancy specialising in enterprise value creation. Make sure that your spending doesn't go to waste. Find out exactly where the value creation of adopting AI products stalls.
Netherlands