Process

Steve opens this one by conceding the point: process is not sexy. It is also the reason some organizations turn a good idea into a result in six weeks and others take two years to decide who owns it.

The core of the session is iteration speed. A process that provides structure with quick iteration cycles empowers an organization to drive change and achieve results — and the mechanism is not that people work harder, it is that the distance between noticing something and being allowed to act on it gets shorter. Every additional approval in that chain has a cost that is invisible on an org chart and obvious in a roadmap.

From there it becomes practical: how to build frameworks that help teams and individuals prioritize, rather than frameworks that mostly generate meetings. And it ends by connecting professional goals to personal ones, on the argument that a process someone only follows at work is a process they do not believe in.