# Brief In, System Out: Why the Interface is Ceasing to be the Product

> B2B products shift from interface-centric to brief-driven, changing the UX paradigm.

- Author: Viktor Berthelius (BRTHLS)
- Published: 2026-06-12
- Updated: 2026-06-29
- Category: growth design
- Tags: agentic-ux, briefing, product-design, growth-design
- Language: en
- Canonical: https://www.brthls.com/magazine/brief-in-system-out-interface-product-change-en
- Source: BRTHLS Magazine — https://www.brthls.com

---

## Problem

For decades, software has competed on interfaces: better dashboards, better menus, better editors, better canvases. The user learned the tool and the tool gave control.

Agents are changing that relationship. More and more products no longer start by asking "which button do you want to press," but "what do you want to achieve." The user submits a brief, attaches references, defines constraints, and the system produces a first version: a video, a presentation, a campaign, a flow, a page, or a decision.

The interface doesn't disappear. It changes its place. It stops being the main product and becomes a surface for review, editing, and governance.

## Thesis

`Brief In, System Out` is one of the most important UX transitions of 2026.

The value is no longer just in the user being able to manipulate elements. It's in the product understanding intention, context, criteria, and constraints well enough to produce an initial usable system.

The winner is who turns the brief into an operational contract, not who hides more buttons behind a chat.

## Framework

A brief-first product needs four layers:

- **Intention:** what result the user is looking for and for whom.
- **Context:** brand, data, files, references, audience, and channel.
- **Constraints:** format, tone, duration, budget, rights, approvals, and limits.
- **Editable surface:** the output must be correctable without starting over.

Mini-case: a marketer needs a launch video. In a traditional editor, they open the timeline, search for assets, write a script, adjust scenes, and export. In Runway Agent, they describe the piece, upload references, decide on aspect/duration/audio, and the system proposes a concept, structure, and multi-shot video. Human work doesn't disappear; it moves to direction, selection, and correction.

**Measurable signal:** percentage of outputs that go from initial brief to revisable version without manual reconstruction.

**Posture:** the chat is not the new interface. The contract between intention and system is the new interface.

## Why it matters now

Runway presented Runway Agent on May 13, 2026, to produce finished videos from description, references, and conversation. Pitch launched Pitch Agent on May 27, 2026, to generate editable, on-brand decks within the presentation workspace.

The coincidence matters. Video and presentations are different categories, but the pattern is the same: the product no longer just offers tools; it tries to absorb the first stretch of production.

This changes the buying criteria. It's not enough to ask if the output is good. You have to ask if the system understands constraints, preserves brand, allows editing, documents decisions, and allows rollback.

## Anti-example

"Let's put a chat on top of the product."

That's not brief-first. It's a conversational layer over an old architecture. If the agent can't access templates, permissions, brand library, data, history, and work state, the user ends up describing what the system should know.

## Protocol (3 steps)

1. **Turn the brief into a schema.** Objective, audience, channel, constraints, and criteria must have clear fields.
2. **Separate generating from approving.** The system produces options; the human validates direction and risk.
3. **Maintain structured editing.** If every correction forces regenerating everything, the product is not operational.

| Layer | Key question | Risk if missing |
| --- | --- | --- |
| intention | what outcome is sought | pretty but useless output |
| context | what the system must know | genericity |
| constraints | what it can't do | legal or brand risk |
| editing | how it's corrected | starting over |

## Related

- [Adobe within Gemini: when pro tools become agent actions](/magazine/adobe-gemini-pro-tools-agent-actions-en)
- [Figma Design Agent: when the canvas becomes a product operating system](/magazine/figma-design-agent-canvas-product-operating-system-en)
- [Gemini Omni + Flow: post-output creative direction](/magazine/gemini-omni-google-flow-creative-direction-en)

## Sources consulted

- [Runway: Introducing Runway Agent](https://runwayml.com/news/introducing-runway-agent)
- [Pitch: Introducing Pitch Agent](https://pitch.com/whats-new/introducing-pitch-agent)
- [Pitch: The new era of AI presentations](https://pitch.com/blog/introducing-pitch-agent)

## Next step

Review an internal product or a tool you use daily. If the user still has to translate intention into twenty manual steps, there's a clear opportunity: turning the flow into an operational brief.

---

*Translated from the Spanish original with AI assistance and reviewed for accuracy. [Read the original in Spanish](/magazine/brief-in-system-out-interfaz-deja-ser-producto-es).*

---

_Cite as: Berthelius, V. (2026). "Brief In, System Out: Why the Interface is Ceasing to be the Product". BRTHLS Magazine. https://www.brthls.com/magazine/brief-in-system-out-interface-product-change-en_