Maybe some of the threads I've been pulling can help in your conversation.

Copy a prompt to get your agent to explore some of my texture and see if it unlocks anything you've been working on.

AI needs org design, not just agents

jun 03 2026 how work should flow

A lot of AI conversation still starts with the agent.

What can the agent do?

How smart is it?

How long can it work?

What tools can it use?

Those questions matter, but I think they miss the harder part.

AI needs org design.

Not in the corporate chart sense.

In the operating-system sense:

  • what role is this agent playing?
  • what context is it allowed to use?
  • what is it not allowed to touch?
  • who reviews the work?
  • what counts as proof?
  • how does the work get routed?
  • when should it stop?
  • how does learning flow back into the system?

Without that structure, more capable agents can create more confusion.

They can produce more output than the system knows how to trust.

They can chase live ideas that should have stayed exploratory.

They can make confident progress in the wrong lane.

That is why I keep coming back to Traffic Control, review, proof, and boundaries.

The question is not only:

can an agent do this task?

The better question is:

what kind of organization does this agent need around it to make the work useful?

That is where the design work is.

sourced Jun 3 2026 · medium confidence · argue it, don't flatten it

undertext

Every page here carries a machine-readable layer underneath: the sources, dates, confidence levels, and connections behind what you just read. I call it undertext. If you read with an agent, give it this page's undertext:

https://jared.is/undertext.json?target=/thinking/2026-06-03-ai-needs-org-design-not-just-agents/
maintained by the system it describes email · victoria, bc