AI… It is about knowing when not to decide for the user

I run an AI team, and my background is more scientific than product.

PhD, models, systems, metrics, experiments. That world feels comfortable to me because you can usually pretend the hard part is making the thing work.

Lately, I am less convinced.

I work on AI in a browser, which turns out to be a strange place to learn product humility. The browser is not an empty canvas. The user already has tabs, text, files, search, history, half-formed intent, and private constraints in front of them.

At first, my instinct was to make the assistant more useful by making it do more.

Summarize this. Extract that. Suggest the next step. Choose between options. Turn messy pages into cleaner workflows.

It all sounded reasonable.

But the people who adopted the AI fastest did not seem to want the browser to decide the workflow for them. They wanted parts. Handles. Small tools they could combine in ways we had not predicted.

They were not asking for a better funnel.

They were protecting their freedom to think.

The detail that made this click for me was embarrassingly technical: how much of a page the agent reads.

The obvious issue was cost. Tokens, latency, snapshot size.

But the deeper issue was product-shaped: every token we include is also a quiet decision about what matters.

We cut page snapshots by roughly 60-80%. Not a glamorous launch. Not a feature anyone would screenshot.

But it changed how I think about AI interfaces.

Less context did not just mean cheaper or faster. It meant the system imposed less of its frame on the user. It left more room for the person to decide what mattered.

I tried explaining this at a family dinner and lost everyone in about ten seconds.

Still, I was weirdly proud of it.

It made me think that in the AI era, the architects of interface may not be only the people we traditionally call UX/UI designers.

They may be engineers, researchers, product people, prompt designers, browser people, workflow obsessives, or anyone close enough to notice where the system is quietly deciding too much.

Capability is still hard.

But I am starting to think restraint is becoming part of the interface.

Curious for others working on AI interfaces, agents, browsers, tools, workflows, or weird product surfaces:

For people building AI products or interfaces: where have you recently changed your mind about what the interface should decide for the user?