There's a difference between a project that has ended and a process that has truly changed.

A project ends when deliverables are submitted, open items are closed, and final sign-off is given. But real change isn't in the delivery. It's in what happens three months later.

When we work with a client, the first sign that the change has worked isn't that the system works. It's that the team uses it without anyone reminding them that it should work.

The second sign is that they know how to fix it when it breaks. Not by calling us. By understanding where it failed and knowing how to recover it. That's real autonomy.

The third sign is that they extend it. That they take what we built together and add something we hadn't anticipated. When a client improves your work, they've made it their own.

We have a question we always ask six months after closing a project, if we can: "What's one thing you've noticed works differently now, that you wouldn't know how to go back to?" If there's a clear answer, the change has taken root. If there isn't, we ran a project but didn't change anything in a lasting way.

Our goal isn't for the system to work while we're there. It's for it to work when we're no longer there.

→ How we measure what has changed · When it's too early to automate