Most consultants have either theory or practice. I use both — a Doctorate in Strategic Leadership for how systems actually change, and a PMO Director seat that shows me, every week, what actually blocks it. The doctorate teaches the pattern. The PMO reveals the friction. AI is the lever that finally makes them move together.
I didn't pivot to artificial intelligence because it was trending. I built RACEprompt because I watched teams burn months on back-and-forth with models that didn't know what they wanted. I built QuietPulse because I needed it — a calm, structured pause for people who actually have jobs. I help ship F3 because my partner needed a builder who could move. Problem, tool, ship — that is the pattern.
I don't write frameworks to be read. I write them so something gets done before the meeting ends.
The RACE framework — Role, Action, Context, Expectation — is small on purpose. Most people's prompts fail because they skip one of the four. Name the role you're casting the model in, state the action, ground the context, and specify what "done" looks like. That is the whole method. The app only exists because memorizing it isn't enough; you need to write it down, and most people won't.