Now the Chief Design Officer at Atlassian, Charlie Sutton has previously led design at Apple, Meta, and Nokia. His career tracks the shift in interaction design from early mobile hardware to spatial computing and AI agents. Whether designing for a multimodal future or leading distributed teams, his approach is grounded in a single principle: "calm is smooth, smooth is fast."

Visual summary of operating lessons from Charlie Sutton.

Part 1: The Philosophy of Calm and Speed

  1. On operational pace: "Calm is smooth. Smooth is fast." — Source: [All Things Design]
  2. On reactive work: "Rushing rarely increases velocity; it usually just increases the error rate." — Source: [All Things Design]
  3. On steady leadership: "A steady, thoughtful pace ultimately leads to higher velocity across a massive design organization." — Source: [All Things Design]
  4. On organizational noise: "You have to deliberately design the quiet into your team's day to get the high-fidelity output you want." — Source: [Atlassian Design]
  5. On decision-making under pressure: "When everything feels urgent, the most radical act a design leader can take is to pause." — Source: [All Things Design]
  6. On sustainable velocity: "Speed is a byproduct of clarity, not frantic effort." — Source: [All Things Design]
  7. On managing large teams: "At scale, panic is contagious, but so is calm." — Source: [Atlassian Design]
  8. On friction: "Sometimes the friction is there to prevent a mistake. You don't want to remove all friction, just the unnecessary kind." — Source: [Atlassian Design]
  9. On execution: "Smooth execution comes from removing ambiguity at the start, not fixing it at the end." — Source: [All Things Design]
  10. On long-term focus: "We are running a marathon, but people treat every sprint like a 100-meter dash. You have to reset the rhythm." — Source: [All Things Design]

Part 2: Defining and Solving People Problems

  1. On the root cause: "Business problems are often just symptoms; the human problem is the root cause." — Source: [Mind the Product]
  2. On defining the issue: "What is the human problem we are solving? Define it in terms of human needs, not business KPIs." — Source: [Mind the Product]
  3. On evidence: "How do we know it’s a real problem? You need qualitative or quantitative evidence to prove it actually exists." — Source: [Mind the Product]
  4. On success metrics: "How will we know if we’ve solved it? Look for the specific human behavior change we will see." — Source: [Mind the Product]
  5. On optimization traps: "We often optimize for our PMs or our Directors just to get things out the door, optimizing for conversion or retention rather than the user." — Source: [Mind the Product]
  6. On losing connection: "The minute we start to lose the connection to the human problem, we have to recalibrate." — Source: [Mind the Product]
  7. On empathy in product: "Empathy isn't just a buzzword; it's a diagnostic tool for finding the actual friction in a workflow." — Source: [Mind the Product]
  8. On implicit needs: "Users don't always know how to ask for what they need. Product people must observe implicit behaviors." — Source: [Mind the Product]
  9. On framing: "If you frame the problem solely around moving a metric, the design team will build a mechanical solution." — Source: [Atlassian Design]
  10. On true value: "Value is created when a human being accomplishes something they couldn't do before, or does it with less suffering." — Source: [Mind the Product]

Part 3: Leading Distributed Design and Team Anywhere

  1. On distributed leadership: "The Team Anywhere policy allows you to live where you work best, relying on a distributed-first approach that prioritizes asynchronous communication." — Source: [WFA Team]
  2. On intentional togetherness: "While daily work is remote, you rely on intentional togetherness—bringing teams together in person a few times a year for high-fidelity collaboration." — Source: [All Things Design]
  3. On remote culture: "Culture isn't the office. Culture is how we treat each other and how we make decisions when no one is in the same room." — Source: [All Things Design]
  4. On synchronous time: "You have to be incredibly protective of synchronous time. Use it for debate, not status updates." — Source: [Atlassian Design]
  5. On time zones: "Time zones are a harder problem to solve than geography. You have to design the work to hand over cleanly." — Source: [WFA Team]
  6. On in-person events: "When we gather in person, we shouldn't be sitting at laptops. We should be whiteboarding, arguing, and building trust." — Source: [All Things Design]
  7. On trusting the team: "If you measure output by hours logged at a desk, remote work will fail. You have to measure impact." — Source: [WFA Team]
  8. On documentation: "In a distributed team, if it isn't written down, it didn't happen. The document is the new open-plan office." — Source: [Atlassian Design]
  9. On behavioral science: "We run a Team Anywhere Lab to research and optimize distributed work practices, building those lessons directly into our products." — Source: [WFA Team]

Part 4: Craft, Rituals, and Design Systems

  1. On design rituals: "Rituals are the mechanism through which a team maintains its culture and standards, especially at a massive scale." — Source: [All Things Design]
  2. On healthy teams: "A core principle from the Nokia days remains true: build an environment with 'no dickheads' to foster happy, healthy, and creative teams." — Source: [Rethink HQ]
  3. On design systems: "A design system isn't just a sticker sheet; it's the codified decisions of your best designers, distributed to the whole company." — Source: [Atlassian Design]
  4. On critique: "Critique should be about the work, not the person. It is a ritual of calibration, not a ritual of punishment." — Source: [All Things Design]
  5. On quality: "Quality is a continuous habit. It’s what happens in the small decisions made when the leadership isn't looking." — Source: [Atlassian Design]
  6. On tooling: "The tools we use shape the thoughts we have. If our design tools are rigid, our products will be rigid." — Source: [Atlassian Design]
  7. On craft in leadership: "As you move into leadership, your craft shifts from pushing pixels to designing the organization itself." — Source: [All Things Design]
  8. On the value of prototyping: "A prototype is a decision-making engine. It resolves arguments faster than any slide deck." — Source: [Atlassian Design]
  9. On design technologists: "We need design technologists who bridge the gap by building interactive prototypes and working directly in code." — Source: [Atlassian Design]

Part 5: The Immersive Canvas and Spatial Design

  1. On moving beyond screens: "We are shifting away from glass rectangles toward immersive, distributed, and autonomous environments." — Source: [Mind the Product]
  2. On cinematic understanding: "In VR, you have to build environments and moods that transport users, borrowing more from cinema than from web design." — Source: [Mind the Product]
  3. On interaction mechanics: "Spatial design requires learnable and discoverable game-like mechanics, not just ported 2D menus." — Source: [Mind the Product]
  4. On mobility in VR: "You have to leverage the utility of mobile interfaces to make virtual reality a complete, feasible daily experience." — Source: [Mind the Product]
  5. On user presence: "In an immersive space, the user's sense of presence and agency is the metric that matters most." — Source: [Mind the Product]
  6. On hardware transitions: "The lessons learned moving from physical buttons at Nokia to glass screens at Apple apply to the transition into spatial computing." — Source: [All Things Design]
  7. On physics in UI: "When you build for spatial environments, you have to respect physics, or you break the user's trust in the environment." — Source: [Mind the Product]
  8. On the evolution of interaction: "We are moving from direct manipulation of objects on a screen to orchestrating environments around us." — Source: [Atlassian Design]
  9. On media-evoked reality: "The goal of spatial design is media-evoked reality, where the sense of control and orientation is paramount." — Source: [Mind the Product]

Part 6: Designing for the Age of Agents

  1. On shared context: "Humans and agents largely need the same thing, and will be crippled or helped by the same things." — Source: [Mind the Product]
  2. On articulating goals: "If you are poor at articulating your goals as a leader, you have also disadvantaged a whole fleet of agents." — Source: [Mind the Product]
  3. On open companies: "If your company is very open and willing to share, then that context becomes magnified in its power for your agents." — Source: [Mind the Product]
  4. On improving workflows: "Whatever you are planning to do to make your humans happier will also make your agents happier." — Source: [Mind the Product]
  5. On the Teamwork Graph: "Agents cannot function without the same context a human teammate needs; this requires a Teamwork Graph connecting people, goals, and data." — Source: [Mind the Product]
  6. On permissions and trust: "Technical constraints like permissions aren't just hurdles; they are the foundation of trust between humans and agents." — Source: [Mind the Product]
  7. On transparency: "Popping the bonnet and showing how the AI made a decision is essential for user trust." — Source: [theCUBE]
  8. On design systems for AI: "We are optimizing design systems for agent consumption to lower token costs and improve how AI understands interfaces." — Source: [theCUBE]
  9. On human rituals: "Humans are ritualistic; we must observe implicit behaviors to build the right agent experiences." — Source: [Mind the Product]
  10. On the agent transition: "The shift from tools to agents changes the designer's job from crafting interfaces to designing relationships." — Source: [theCUBE]

Part 7: The Human Tax and Multimodal Delegation

  1. On the human tax: "The human tax is the cognitive load and fractured attention required by modern software—constant switching and searching." — Source: [Mind the Product]
  2. On paying the tax: "AI agents are the first technology actually capable of paying this human tax for us." — Source: [Mind the Product]
  3. On multimodal delegation: "We are moving away from simple text-based prompting toward multimodal delegation, where AI processes across text, visuals, and data." — Source: [theCUBE]
  4. On the end of prompting: "Prompting is giving repetitive instructions; delegation is providing high-level goals and shared context to a teammate." — Source: [theCUBE]
  5. On cross-modal transformation: "The AI isn't just answering a question; tools like Confluence Remix perform a complex transformation from text to visual presentation." — Source: [theCUBE]
  6. On freeing up humans: "Agents free up humans to focus on their 40%—the actual specialized work—by handling the 60% of knowledge work overhead." — Source: [Mind the Product]
  7. On lowering the floor: "AI lowers the floor, meaning anyone can now generate a decent first draft or a basic design." — Source: [theCUBE]
  8. On raising the ceiling: "As the floor rises, the ceiling for professional designers also rises; experts must reach levels of craft previously impossible." — Source: [theCUBE]
  9. On treating AI as a partner: "Multimodal delegation is about treating AI as a collaborative partner that understands the rhythms of work." — Source: [theCUBE]

Part 8: The Evolving Role of the Designer

  1. On amplifying agency: "The role of a designer in an AI-driven world is to ensure technology empowers the user rather than just automating tasks away." — Source: [Mind the Product]
  2. On legibility for machines: "Making design systems legible to AI agents is now just as important as making them legible to human developers." — Source: [theCUBE]
  3. On letting go of pixels: "Designers must move up the stack, focusing on logic, flow, and context, rather than obsessing over the rendering of a single button." — Source: [Atlassian Design]
  4. On building trust: "Trust is the new UX metric. If the user doesn't understand why the agent took an action, the design has failed." — Source: [theCUBE]
  5. On managing complexity: "The designer's job is to absorb the complexity of the system so the user doesn't have to." — Source: [Atlassian Design]
  6. On the nature of work: "We are redesigning work itself, moving from a culture of outputs to a culture of outcomes facilitated by AI." — Source: [All Things Design]
  7. On continuous learning: "The tools change every six months now. The only sustainable skill for a designer is the ability to unlearn and adapt." — Source: [All Things Design]
  8. On human connection: "No matter how good the AI gets, it cannot replicate the human alignment required to decide what is worth building." — Source: [All Things Design]
  9. On the future canvas: "The future of design is screen zero. We are designing for environments where the interface recedes completely into the background." — Source: [Mind the Product]