← All speakers

Bio, Work & Ideas

Maximillian Piras

Conference affiliation: Founding Designer · Yutori · 2026

Maximillian Piras is the founding designer at Yutori, where he shapes interfaces for software agents that navigate websites and complete tasks. His work addresses a central problem of AI product design: how to make increasingly capable systems understandable without locking them into interaction patterns that quickly become obsolete.

Piras’s portfolio credits design projects for the music platform 8tracks, and his writing describes onboarding work at Headliner. His creative portfolio spans product interfaces, animation, illustration, commissions for Giphy, and a music-video project involving Ryuichi Sakamoto. His Headliner onboarding work captured individual users’ preferences; he reports no meaningful activation dropoff as onboarding steps were added, alongside improved retention from personalization.

In a 2023 essay on machine-learning interfaces, Piras argued that strategic interface friction can improve personalization, reduce mistakes, and generate clearer behavioral signals. Extra onboarding questions proved valuable when they produced more useful recommendations without the abandonment his team had anticipated. His 2024 writing on alternatives to conversational AI extended that thinking to language models: visual manipulation, navigation, and comparison can outperform chat when matched to the task.

  • The Bitter Layout: Piras’s analysis of convergent AI interfaces explains why text input, sequential conversation, and model selectors keep reappearing. While model capabilities remain a competitive differentiator, a generic interface can absorb improvements faster than specialized workflows built around yesterday’s limitations.
  • The flexibility-usability tradeoff: Interfaces optimized for well-understood tasks can be clearer and more efficient, while general-purpose systems accommodate unexpected tasks and rapidly changing models. For Piras, the right balance depends on a product’s users, technical constraints, and stage of development.
  • Model pickers as interface modes: Switching models can silently change available features, tools, and output quality. When users must match a model to a compatible feature, they inherit the product’s internal complexity instead of concentrating on their goal.
  • Designing with goals and constraints: As AI systems become less predictable, Piras sees designers specifying boundaries and desired outcomes instead of scripting every possible interaction. Potential approaches include using design systems to constrain generated interfaces and translating user stories into higher-level instructions.

Piras tests AI interfaces beyond chat through CC-1, an LLM-powered word-arithmetic calculator.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

A prompt box and a crowded model picker can be frustrating to use, yet remarkably good at absorbing new capabilities. That trade-off changes what AI interface design must optimize for.

  • Different tools, the same layout
    0:23 ↗
  • Usability critiques meet adoption
    1:51 ↗
  • The model picker adds another mode
    3:31 ↗
  • An interface has a useful lifetime
    5:46 ↗
  • Where to integrate, where to stay modular
    6:50 ↗
  • The interface must accommodate the next model
    8:31 ↗
  • Design above the level of individual procedures
    11:13 ↗
  • From design systems to gardening
    12:44 ↗

Key ideas

Scroll to read ↓

Maximillian Piras explains why token counts fail to show whether agents create value, why faster generation moves the bottleneck to verification, and how task uncertainty can help identify work worth delegating.

  • Token volume measures system activity, not customer value. Trace spend to accepted outcomes such as bugs closed or support requests resolved, then connect those outcomes to an objective.
    10:12 ↗
  • Faster generation moves the bottleneck to verification. Agent output creates value only after its quality can be judged and the work can be accepted or deployed.
    11:42 ↗
  • Mousepower is not a literal cursor-speed metric. It is the requirement to give customers an understandable rubric for deciding whether agent work was worth its cost.
    14:19 ↗
  • Use deterministic scripts when task steps are predictable, and avoid delegation when checking requires doing the work again. The best agent candidates combine moderate execution uncertainty with relatively clear acceptance criteria.
    18:19 ↗
  • When verification follows a repeatable pattern, an agent can help check another agent—but the checking rubric must still reflect the customer’s definition of good work.
    13:49 ↗

References