This started with people close to me.
I would sit down with a friend or family member who was curious or skeptical about AI. In thirty minutes, they would go from "I don't get it" to seeing something they could use tomorrow. Not hype. Not theory. A real thing that saved them time or made something easier.
That pattern stayed with me. The real challenge was usually not explaining the tool. It was helping people get past the hesitation, feel included quickly, and discover something useful before the energy disappeared.
I can explain AI to a retiree on Tuesday and design an agent harness architecture on Wednesday. Those are not different kinds of work. The depth is what makes the simplicity possible.
Over time, that became a bigger part of how I work. I care a lot about creating sessions where people with very different starting points can get engaged, think more clearly together, and leave with something real to build on.
Most people do not need a tutorial, a course, or a generic workflow. They need someone who listens, understands their situation, and helps them find the fastest path to something genuinely useful.
You may not have started at all. You may be deep in agent workflows already. I will meet you where you are.
This is why the individual lane still matters to me. It is direct, useful work with real people in the middle of real friction. And it is also part of what taught me how to design sessions that work in a room.
Operator first. Advisor second.
A lot of my career has revolved around the same underlying challenge in different forms: getting people, teams, and strange power structures to move.
I have done that through consulting, inside startups, across product and machine learning work, in leadership settings, and in decentralized governance environments where progress depended on more than having a good idea. It depended on getting people with different incentives, different context, and different language to align well enough to actually do something.
That became a kind of secret sauce for me early on. Across designing systems, shaping products, growing companies, advising leaders, and building from the inside, I kept coming back to the same thing: using facilitation, structure, and live working methods to make decisions faster, create clarity, and build momentum.
Over time, I became a serious practitioner of methods like Atlassian's Playbook, Design Sprints, Lightning Decision Jams, and Liberating Structures, not because I liked workshop theater, but because they helped groups move. They gave structure to something I was already learning firsthand: the room is often where progress either unlocks or stays stuck.
I have worked on machine learning systems, startup operating problems, leadership and strategy work, and decentralized governance situations where meaningful resources were stalled until people could align well enough to act. I have been directly involved in helping unlock over $100 million in that broader kind of movement.
That kind of background changes how you see things. You stop believing that technical correctness is enough. You learn that trust, sequencing, facilitation, incentives, and judgment are often the real work.
I find patterns that produce structure.
The main thing I am building for this business is the AI Activations Playbook: a modular methodology for designing team sessions that actually move people. It gives shape to the work through arcs, plays, and moves that help groups engage quickly, think more clearly together, and leave with useful outputs and next steps.
That is the most directly client-facing expression of something I have been doing for years: using structure, facilitation, and well-designed working formats to turn ambiguity into clarity and momentum.
I also build other systems for fun that come from the same instinct.
Caret^ is an open-source semantic notation for agent workflows in Markdown. It is my way of making prompting and orchestration more expressive, structured, and efficient without requiring heavyweight tooling.
CapacityOS is a modular agent-based operating system I use to run my own work. It is a personal harness I have been refining over multiple generations to keep work bounded, sequenced, and easier to steer.
They are different kinds of projects, but they come from the same place. I like building systems that create clarity, preserve momentum, and help useful work hold its shape.
Useful work funds principled work.
I wanted my work to make sense as a whole.
On one side, I help people and teams get practical with AI. That work is immediate, useful, and grounded in real life. It lets me help directly, and it keeps me close to the tools that are changing how people work, learn, coordinate, and make decisions.
On the other side, I care deeply about bigger questions: how groups govern themselves, how incentives shape behavior, and how you build systems people can actually trust over time. Those are long-term problems, and they are central to what I want my life's work to be about.
To me, those are not separate worlds. The practical work keeps me close to reality. The principled work keeps me honest about what reality needs.
That is also why I choose to work independently. I want to advance humanity-first technology in a way that does not let my judgment get bent by the wrong incentives. After years working across startups, governance, fraud detection, incentive design, and international onchain organizations, I became convinced that long-term systems work cannot stay honest if it is forced to serve short-term pressure all the way down.
So the sessions side of my work is not a detour. It is part of the model. It lets me do useful work for real people, stay close to the changing edge of these tools, and fund the deeper work I care about without pretending the two should be separate.
If you are here because something in that resonates, there are two paths depending on what you are trying to move.
If you are trying to get yourself ahead, saving time, getting comfortable, and finding the workflows actually worth your attention, start here.
If you are trying to get your team moving together, building buy-in, identifying useful opportunities, and getting aligned on what is worth doing first, start here.
If you want to see how the team work is structured before reaching out, the playbook walks through it.