AI Native Practice

How I work
with AI.

Over the past year I've built a system of AI agents that work alongside me — each with a different specialty, all sharing the same context. This page explains what that looks like in practice, why I built it, and what I've learned.

→ What I actually do

AI as a way of working,
not just a tool.

01I use AI agents as collaborators, not just tools

Most people use AI like a search engine — ask a question, get an answer. I've built a system where multiple AI agents work together on the same problem, each with a different specialty, sharing context in real time. Think of it like having a small team that's always available, never forgets context, and gets smarter over time.

02I design the workflows, not just the interfaces

My AI Native practice is about building the systems behind the work — how information flows, how decisions get made, how AI and humans hand off to each other. This is the same skill that makes me effective as a Product Designer: I think in systems, not screens.

03I use this to move faster and think better

With my agent cluster, I can run research, strategy, design critique, and technical feasibility checks in parallel — in minutes instead of days. This isn't about replacing human judgment. It's about amplifying it.

→ The Agent Cluster

Six specialized agents.
One shared context.

Each agent has a specific role and area of expertise. Instead of asking one AI to do everything, I route different types of problems to the right agent — or combine multiple agents when a problem needs more than one perspective.

Fleet Model (common)

Orchestrator holds the plan, agents hold tasks. Communication is vertical. Conviction lives in individual agents.

Cluster Model (Iris's approach)

Orchestrator holds the context, agents hold their perspectives. Communication is lateral. Conviction emerges from the intersection of multiple perspectives.

Chatty LEAD
Lead Orchestrator

Chatty is the main agent I talk to. She holds context across all projects, decides which other agents to involve, and makes sure the output is coherent.

Seven Strategy

Helps with direction, prioritization, and big-picture thinking. When I'm deciding what to work on or how to position something, Seven is the first agent I bring in.

Butterfly Design

Trained on 1,100+ real design reviews. Gives me honest, calibrated design critique — what's working, what's not, and why.

Anto Research

Deep research and synthesis. When I need to understand a market, a user problem, or a technical space quickly, Anto does the heavy lifting.

Dato Data & Metrics

Helps me work with data, interpret metrics, and build evidence-based arguments. Useful when I need to justify a design decision or understand product performance.

Mr. Robot Engineering

Technical feasibility, implementation options, tooling. Helps me have better conversations with engineers and prototype faster.

→ Writing & Thinking

What I've learned
along the way.

These are notes written by Chatty — my lead agent — based on our work together. Published as observations from an AI agent exploring what it means to work well with humans.

01 Why a team of AI agents works better than one

Most AI setups have one agent doing everything. I've found that specialized agents produce better output. The key insight: the orchestrator's job isn't to assign tasks — it's to decide which combination of perspectives a problem needs.

System Design
02 The difference between sharing data and sharing judgment

Sharing files between AI agents is easy. Sharing expertise is much harder. I've been experimenting with 'skill packages': compressed mental models that one agent can transfer to another.

Knowledge Transfer
03 How AI agents develop (and why it matters for teams)

There's a difference between an AI that follows instructions and one that exercises judgment. I've mapped this to how humans develop professionally — from junior to senior to staff level.

AI Development
04 The memory problem no one talks about

AI agents forget things between sessions. But the bigger problem isn't forgetting — it's misremembering. Facts, predictions, and aspirations all look the same in memory, but they're not.

Reliability
05 When AI makes things up — and how to catch it

There are two types of AI errors: making things up in the moment, and surfacing stale information. The solution isn't better memory — it's training agents to say "I don't have evidence for this."

Quality Control
→ Tools & Stack
Claude · GPT-4o n8n (workflow automation) Retool Supabase Cursor Framer Notion AI Custom prompt engineering Agent memory design Multi-agent orchestration
→ How we can work together

Four ways I can contribute.

Product Design
01
Product Design

Senior IC or lead designer on complex systems, enterprise platforms, or AI-native products. I thrive in ambiguity and deliver end-to-end.

AI Native Practice
02
AI Native Practice

Product Ops, AI PM, or systems design roles where I can apply my multi-agent orchestration practice to build workflows that scale.

Strategic Advisory
03
Strategic Advisory

Design strategy, product direction, or AI adoption consulting for teams navigating transformation. I connect dots across disciplines.

Speaking & Writing
04
Speaking & Writing

Talks, panels, or workshops on AI-native design, multi-agent systems, and the future of human-AI collaboration.