Ninja First

I came up with the framework because I kept watching smart people fail the same way.

They’d walk into a new industry — or a new company, or a new problem — and immediately start operating like they already understood it. They’d bring their frameworks, their playbooks, the approaches that worked last time. And they’d break things. Not because they were wrong in general, but because they were wrong here, in this specific place, with these specific people and constraints.

The ninja goes first. The ninja learns the terrain, maps the relationships, understands what’s actually moving and why. No authority, no title, no position. Just observation and honest questions. The people who’ve been in the room longest are the ones worth listening to, even when — especially when — they can’t articulate what they know.

Then comes the samurai. Once you understand the system, you can lead it. You know where to apply force and where to hold back. You know which battles matter and which ones are theater. You can move with authority because the authority is earned.

I’ve done this in manufacturing plants and distilleries and tech startups and agricultural operations. The timeline is different every time. Sometimes ninja phase is two weeks. Sometimes it’s eight months. You don’t get to decide in advance — the environment tells you when you’ve learned enough to stop learning and start leading.

The AI conversation needs this badly right now. Every company with a budget is hiring someone to ‘lead AI adoption,’ and most of those people skip straight to samurai. They install tools. They run trainings. They announce strategies. And the workers on the floor — who have thirty years of process knowledge that no prompt engineer has ever thought to ask about — quietly route around everything.

The knowledge is always already there. The ninja’s job is to find it before the samurai tries to replace it.