Limits as Leverage

About

Who makes this, why there is no face on it, and how it gets made.

Where this comes from

I have spent about two decades running operations inside institutions — the kind where a system going down is somebody’s bad week, the data carries legal weight, and every tool arrives through procurement and security review rather than a credit card.

Most of that work was process, not technology: designing how things get done, documenting what only lived in people’s heads, and getting changes through approval chains that were not built for speed. I am not a technologist by training.

AI is the most recent chapter, and I came to it the way most people in my position do: with a workload that had stopped being survivable and a very short list of things I was permitted to try. The first year was mostly finding out which advice had been written for someone who does not exist in my building. It is the current subject here because the gap is widest there right now — not because it is the point.

Every useful thing I learned, I learned by starting from what I could not do.

That turned out to be the method rather than a limitation of it. When you cannot do the obvious thing, you are forced to work out what was actually essential about it — and the answer is usually much smaller and much more portable than you assumed. That holds whether the obstacle is a data policy, an approval chain or a process nobody is willing to change.

Why there is no face on this

Two reasons, and the second one matters more than the first.

The first is ordinary: I have a day job, and it is not this.

The second is structural. The moment I name an employer, a sector or a title, every pattern here becomes a story about that place. People in a different building read it and conclude it doesn’t apply to them — and half the time they’d be right, because sector-specific advice really is sector-specific.

So everything published here has to pass one test: is it equally true for a hospital administrator, an insurance compliance officer, a legal ops manager and a school district director? If it needs one particular setting to make sense, it is an anecdote in disguise and it gets cut. That test removes the war stories, and I think the material is stronger for it.

It also means I will never tell you what my colleagues did last quarter. That is a promise about the content, not a coy withholding: the version of this channel that traded on inside stories would be worse, and it would not be mine to trade.

Who this is for

People whose honest reaction to “just paste it in” is I would be fired.

More broadly: anyone whose work happens inside rules they did not write. Regulated industries, public institutions, healthcare, legal, finance, education. Mostly senior enough that the job has become connective rather than task-shaped — routing, sequencing, deciding who needs to know — which is exactly the shape that generic advice fits worst, whether it is about software, process or leadership.

Also, and not incidentally: people carrying a full load outside work as well as inside it, for whom “just spend a weekend learning it” is not a real instruction.

How it gets made

Plainly, because this channel would be poorly placed to be cagey about it:

Everything here is a personal project made on personal time. Nothing on this site or the channel represents any employer, and nothing on it is advice about what a law or regulation requires of you — for that, ask the people in your own building whose job it is.


Get in touch

If a pattern here is wrong, or right in a way I haven’t noticed, I want to hear it: hello@limitsasleverage.com. Corrections land better than compliments.

Get the free prompt