Skip to main content
Paul Welty, PhD AI, WORK, AND STAYING HUMAN

· strategy · 2 min read

I don’t want to have an experience or a partnership with vendors. I just want to get my stuff done.

Discover why sometimes a straightforward transaction is preferable to deep partnerships and experiences with vendors in today's business landscape.

Duration: 1:21 | Size: 1.5 MB

We hear frequently, ever since The Experience Economy about designing experiences. We talk about the customer experience, the employee experience, and the student experience. Everything is an experience. Or, at least, everything is supposed to be an experience. It’s certainly not supposed to be a (mere) transaction.

This reminds me of the term “partner” in business relationships. Frequently, a vendor doesn’t want to be called a “vendor” nor to be known as a vendor. They tell their clients that “we want to be your partner”. Relationships are suppose to be partnerships, not vendor-client relationships.

I think that the idea in both cases is to increase the depth of relationships. By itself, this seems like a great idea. Who doesn’t want their relationships to be deep, personal experiences?

Yet, how many relationships like this can you have?

I’m all for having some things be deep, personal, partnership experiences. But, can everything be like this? I think that would be exhausting.

What’s more, can your average service provider, or vendor, even know what I want in an experience or partnership?

So, in this sense, I’m getting the opposite of what I want from a vendor when they insist on providing experiences and partnership.

Sometimes, all I want is a simple transaction and to move on with my life.

The agent-shaped org chart

Every real org has the same topology: principal, role-holder, specialists. Staff AI maps onto it, node for node, and the cost collapse shows up in the deliverables that were always just human-handoff overhead.

AI as staff, not software

Two frames for what AI is doing to work. The tool frame makes tools smarter. The staff frame makes roles unnecessary. Those aren't the same product, the same company, or the same industry.

Knowledge work was never work

Knowledge work was always coordination between humans who couldn't share state directly. The artifacts were never the work. They were the overhead — and AI just made the overhead optional.

The work of being available now

A book on AI, judgment, and staying human at work.

The practice of work in progress

Practical essays on how work actually gets done.

How do I get my dev team to adopt AI?

A stub on helping mixed-interest development teams find their own useful ways into AI.

Want to learn about agents? Talk to someone who ran an agency.

I spent 20 years running consulting engagements at Fortune 500 companies. Turns out that's the best preparation for running a fleet of AI agents ... because the problems are identical.

Your AI agents need a water cooler

We run a twelve-session AI fleet that coordinates through an IRC breakroom. A friend asked: why are you making AI agents act like humans? The answer turned out to be more interesting than the question.

Moving up the vendor value chain. Getting to the vendor tipping point.

Elevate your agency by mastering the vendor value chain to become indispensable and flexible, securing your position in the market.

Your sales team should take a page from marketing

Boost your sales by leveraging marketing insights. Discover how collaboration can enhance lead understanding and drive more conversions.

Defensive innovation: Stop de-innovating

Explore how to combat de-innovation and unleash the constant potential for creativity in your projects to drive meaningful change and growth.