These are the projects I get called into.
From AI ambition to scalable AI impact
You have licenses, pilots, and rising token spend, and no business process that is meaningfully better. The work is picking the bets worth depth, then changing the workflow, ownership, feedback loops, and decisions around them until the impact is real enough to fund the next round.
How this work runsSpeed you can ship, review, and stand behind
Coding got faster and the pipeline got slower. Review queues grow, specs thin out, architecture happens by accident, and your best engineers spend the week validating code they did not write. The work is rebuilding the lifecycle so speed survives review, release, and adoption.
How this work runsOutcomes and evidence, not a feature roadmap
Product titles, ceremonies, and roadmaps are in place, but the real decisions still behave like project delivery, and too much is in flight to finish any of it well. The work is changing who decides, what evidence moves those decisions, and how much runs at once.
How this work runsThrough OKRs, funding, and leadership cadence
Strategy changes and team goals do not. OKRs report activity instead of driving trade-offs, funding and governance keep work alive past the point of confidence, and cross-functional initiatives stall between the functions that have to move together.
How this work runsAlso Part Of This Work
Pieces that usually show up in service of one of the four above, rather than as the project itself.
How I Work
I have deep expertise in deploying and scaling management operating systems: OKRs, Scrum, Agile, Flow/Kanban, Theory of Constraints. But I orient toward the opportunity or constraint and pull only the relevant patterns. My preference is to evolve what is working rather than arrive with a shiny new framework that promises to be a silver bullet.
I work with the leaders and the people doing the work, long enough that a new way of operating survives contact with real work. I aim for stickiness of new ways of working, and leverage AI capabilities to shape that stickiness. I call this the Forward Deployed Adoption Strategist: bringing together strategy and hands-on work to try, sense, and iterate the change to fit the organizational context.
Shifting activity to impact at
Bring the situation that feels stuck. The first job is to sort signal from noise and decide which constraint is worth working on first.
