When the canvas starts acting, who's really in control?UX Collective
DesignEthics
As design canvases gain agentic AI capabilities, the old rules of user control and authorship stop applying.
- The shift: Design canvases (Figma-style tools) are gaining agentic features that act on the user's behalf, blurring who's actually authoring the work.
- Core question: When an AI agent edits a canvas autonomously, who owns the outcome — the user, the tool, or the model?
- Design challenge: UX patterns need new signals for reversibility, attribution, and consent when a canvas 'acts' instead of waiting for input.
- Why it matters: Trust in canvas-based tools depends on perceived control — agentic behavior without clear boundaries risks eroding it.
For design
Before adopting agentic canvas features, insist on explicit undo/audit trails — users need to see exactly what an agent changed and why, not just accept a fait accompli.
AI took away engineering's right to say noUX Collective
DesignProduct
AI coding tools are quietly eroding engineering's ability to push back on unrealistic scope or timelines.
- The dynamic: When AI can generate code or features almost instantly, 'that would take too long' stops being a credible pushback from engineering.
- Cross-functional fallout: This removes a natural check that used to force honest product/design conversations about tradeoffs and priorities.
- Design implication: Designers may face pressure to ship more variants faster, with less built-in friction to catch bad ideas before they ship.
- Why it matters: Losing 'no' isn't just an engineering problem — it changes negotiation dynamics across the whole product team.
For product
Explicitly rebuild scope-guardrails into your team's rituals — like dedicated tradeoff reviews — since AI removed the natural friction that used to force prioritization conversations.
Designing product simplicity for the agentic AI eraShared design components alone can't guarantee consistency as agentic AI reshapes how products behave.
- The problem: Component libraries and design systems were built for static UI, not for dynamic, agent-driven interactions.
- New approach: Achieving simplicity in agentic products may require standardizing behavior and outcomes, not just visual components.
- Why it matters: Design systems teams need a new playbook as agentic features multiply across products.
- Bottom line: Consistency in the agentic era is becoming a behavioral design problem, not just a component-library problem.
For design
Start auditing your design system for behavioral consistency rules — how agents should respond, fail, and hand off control — not just visual component guidelines, before agentic features proliferate across your product surface.