AI workflow · March 18, 2026

The most useful system I built wasn't the most impressive one

On building AI tools for your own workflow, and why being the most frustrated user first is a better design brief than any requirements document.

← Back to writing

The most useful system I built in the last nine months wasn't the most impressive one.

It was the one where I was the most frustrated user before I built it.

When you're the person who relies on something daily, you feel every failure immediately. Not the obvious failures. The subtle ones. The output that states a guess as a fact. The instruction that gets ignored once the context gets long. The workflow that worked for a week and then started drifting.

Frustration is a gift when you're building. You know exactly what good looks like because you're the one who suffers when it isn't.

This is why so many enterprise AI pilots underperform. They're built by people who aren't the users, for workflows they don't personally run. The gap between "this looked great in the demo" and "this still works reliably six months later" is enormous.

The practitioners getting the most out of AI aren't the ones who hired someone to build for them. They're the ones who got just technical enough to build for themselves.

EigenStrategy builds these workflows for institutional credit teams.

See how it works →