Better, faster, differently: a question, not a project.

Every few years, business culture invents a new name for the same mistake: treating change as an event. The transformation program. The digital initiative. The AI strategy. A start date, a budget, a steering committee — and, fatally, an end date. As if one day the change will be finished and the company can go back to normal.

There is no normal to go back to. Not because consultants say so, but because the pace-setter has changed. The capabilities available to your business now improve on a cadence of months — set by model releases you don't control — while your planning runs on a cadence of years. Any plan that says "we will have adopted AI by Q4" has misunderstood what it's adopting. You cannot finish adapting to something that hasn't finished changing.

The question that doesn't expire

This is why I keep three words on the wall: better, faster, differently. Not as a slogan — as a question with three parts, asked of every piece of work, all the time. Can we do this better? Can we do it faster? Can we do it differently — is there now a way to get the outcome that makes our current process unnecessary?

Projects end. Questions don't. The firms that win this era institutionalise the question, not the answer.

The third part is the one that matters most, and it's the one project-thinking always misses. "Better" and "faster" optimise the process you already have. "Differently" asks whether the process should exist. When a machine can produce in minutes what your workflow produces in weeks, wrapping the machine in your old workflow captures a fraction of the value. Redesigning the work around what's now possible captures the rest — and that redesign is never finished, because what's possible keeps moving.

What the habit looks like in practice

The companies I watch winning don't have better strategies. They have better rhythms. Someone senior uses the tools personally, every week, so the firm's picture of "what's possible" stays current. Experiments are small, frequent, and allowed to fail quietly. When one works, it becomes practice within weeks, not quarters. And the question gets asked again — because last quarter's "differently" is this quarter's baseline.

None of this requires a program office. It requires a leader who accepts that the asking never stops, and a team that's been given permission to answer honestly.

So by all means, run projects — build the system, train the team, ship the pilot. Projects are how the answers get implemented. Just don't confuse them with the thing itself. The thing itself is the question, and the question is now permanent.