My blog

AI agents don’t need new frameworks. They need us to actually use the one we have.

Oct 13, 2026

The double diamond was built for human problems. It turns out AI agents have the same ones.

When we design AI agents, the temptation is to start with the capability. The model can do X — so we design for X. That’s the equivalent of skipping the first diamond entirely.

But the first diamond asks a harder question: what is the human actually trying to accomplish? Not what can the agent do — what does the person need to remain in control, stay oriented, and trust what’s happening?

An agent that surfaces the right answer at the wrong moment, in the wrong form, with no explanation of its reasoning — that’s a capability problem dressed up as a design problem. We built the solution before we understood the experience.

The double diamond reframes AI agent design around the human, not the model:

Discover — where does the human lose the thread in an AI-assisted workflow?
Define — what does trust actually look like at that moment?
Develop — how does the agent communicate its reasoning without overwhelming?
Deliver — how does the human stay in control when the agent is wrong?

The framework didn’t change. The stakes just got higher.

Designing for AI agents isn’t about making the agent smarter. It’s about making the human more capable alongside it.

Daily thoughts; Context is the kingdom

Oct 12, 2026

Sharing a design principle I keep coming back to — The customer is king. Context is the kingdom. Knowing your user isn't enough. You have to know where they are, what they're carrying, and what they need right now — not in general, but in this specific moment. AI unlocks context at a scale we've never had before. That's not just a technical capability. It's a design responsibility. The question isn't what the user needs. It's what this user needs, right now, in this moment, with these stakes.
That's where the design work lives.

Vasu's Laws of Vibe Coding

Oct 07, 2026

I've been building with AI tools for a while now, and here's what I've learned the hard way.


I. The Comprehension Trap
If the AI writes it faster than you can read it, you now own code you don't understand.


II. The Drift Law
Every prompt builds on the last. By prompt seven, you're solving a different problem.


III. The Debug Paradox
The more you ask the AI to fix its own bug, the more bugs you'll need to fix.


IV. The Translation Gap
What you said, what you meant, and what it built are three different things.


V. The Confidence Illusion
It will sound certain. It will be wrong. These two facts are unrelated.


VI. The Ship Trap
"It looks right" is not a test. It is a prayer.


VII. The Scope Creep Corollary
The feature you didn't ask for will break the one you did.
Enjoy. 🙂