"AI employee" is one of the easiest metaphors to reach for to describe agents, but unchecked, it's dangerous, and both over and underestimates what agents are capable of.
It's easy to describe AI in human terms. It takes on work we would historically have assigned to humans, and chats with us in a human form factor. But framing AI as an employee shapes the way we think about both the technology and the people we work with.
In this episode, Eric and John outline the three most common types of AI employees that people put to work (personal assistant, researcher/analyst, and advisor/coach), giving real examples of how they have implemented each one.
Then they step back and ask the hard question about the metaphor: why is thinking about AI as an employee dangerous? The answer is that it can foster wrong thinking about both AI and humans, leading you to believe that AI is more than it is, and defining human value through the lens of cost, efficiency, and ease of management.
The answer is using AI with deliberate intention, trying to harness its full power to increase human creativity and productivity, not displace it.
They end with practical advice, including multi-player human/agent workflows and using fun, fictitious names for the agents you build.
I have a great question
to start this episode out, and that is, do-- would you consider any of the agents that you run
AI employees?
I don't refer to them that way. I don't, I don't think.
Okay.
I try not to. [both laughing]
Try not to.
But, but potentially worse, we, we do have names for them. Um-