Most AI consulting is done from the outside. Someone walks in, runs a workshop, leaves a deck, and the team goes back to doing things the way they always have.
I don't consult from outside the problem. I still work inside a large corporate, navigating the same procurement cycles, data security rules, and approval chains my clients deal with every day. I know what's actually going to get through, what's going to stall, and what's going to quietly die in a compliance review.
That's the difference. When I build a workflow for your team, it's built for the environment you actually work in, not a whiteboard version of it.
I started my professional career as a researcher. I spent years studying what drives and hinders the uptake of new technology, specifically clean energy tech, in a market dominated by fossil-fuel electricity generation. I found that the barriers aren't technical. They're organisational, behavioural, and procedural. The biggest driver on the other side was that clean energy tech is scalable: technology that needs smaller budgets and few approvals moves faster than anything else.
Turns out the same pattern sits underneath AI adoption in corporate teams today. The tech exists. The barriers aren't technical, and the fastest way in is small: starting with the tasks that drain your team's energy, not the ones that need a committee.