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.
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.
Why customer tools are organized wrong
This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.
Infrastructure shapes thought
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
Server-side dashboard architecture: Why moving data fetching off the browser changes everything
How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.
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.
The second project problem
Your system works. Then you try it somewhere else and it falls apart. The gap between 'works here' and 'works anywhere' is where most automation dies — and most organizations never look.
The smartest code you'll ever delete
The most dangerous kind of waste isn't the thing that doesn't work. It's the thing that works beautifully and shouldn't exist.
The first real user breaks everything
Your product works until someone actually uses it. The gap between 'works in dev' and 'works for a person' is where most systems fail — and most organizations avoid looking.
Bookmark: AI will evolve into an organizational strategy for all
Discover how AI is reshaping organizational strategies, driving collaboration, and enabling "AI-native" startups to thrive by 2025.
Jasper is a useful tool for developing employee training.
Transform employee training with Jasper by aligning programs to business goals, engaging diverse learning styles, and using innovative methods for success.
Artificial intelligence could hit three in five workers — Possibly replacing their jobs. The warning comes in a new international monetary fund report on the future of work. It warned of lower sala…
AI could replace three in five workers, warns an IMF report, signaling potential job loss and lower salaries. Discover the implications for the future of work.