Operationalizing a Program When Inputs Are Thin

Most of my favorite work starts with a shrug: “We need… something.” Here’s how I operationalize a program when inputs are thin: set the stakes, find the gaps, pick two moves, make it real fast with a one-page decision brief and early proof, then keep momentum with a light weekly cadence and a decision log. Less theater, more outcomes. From fog to finish, tied to company goals.