People & Machines


Who’s working for whom?

Most of the software in your life was built for an organization. At work it sits beside you, and more of it now acts on its own. As a customer it stands between you and the organization: the CRM that remembers your last call, the service desk that routes your complaint, the agent that answers before a person does.

For most of computing’s history, that software worked for whoever paid for it, and everyone else took what it offered. That’s changing. You’re getting machines of your own, and products are starting to speak for themselves.

Once everyone in the exchange has an agent, the question that matters is who each one is working for.

The territory

The interface

How you and a computer meet, from the command line to the conversation, and whatever comes after the screen.

The work

What happens to a job when an agent takes on part of it. Who keeps the judgment, who checks the output, and how much change a team can really absorb.

The relationship

Customers, organizations and the agents now acting for both. What trust looks like when it has to run at machine speed.

The terms

Customer Commons, MyTerms, IEEE 7012. Who writes the rules of engagement, and whether a machine can read and honor them.

The thread

In 1960 J.C.R. Licklider published a short paper called Man-Computer Symbiosis. He pictured people and computers thinking together, each taking the part of the work the other did badly. Sixty-six years later, it’s still the best description of good software.

He pictured one person and one machine. You’re heading somewhere more crowded. At work, agents that draft, decide and hand off to one another. At the counter, your agent, the brand’s agent and the product’s own voice, all in the same conversation. Almost everything under this heading comes back to the same question. Who the machine works for. Who it answers to. Who gets to change its mind.

Featured

Additional posts from this pillar