Jeff Johnson

Jeff Johnson

My career has not followed a straight line and that has turned out to be an advantage.

I began with a degree in finance and accounting, a path that turned out to be a better education than a vocation. A reboot into decision sciences followed (what we now call data science and machine intelligence) but the world wasn't ready for it yet, and the job market reflected that. I filed the thinking away and found my footing elsewhere.

That elsewhere turned out to be hospitality. A decade in hotel management — working daily to serve guests, and then to lead and develop the people who did. It was formative in ways that no classroom could replicate. You learn what culture actually means when you're responsible for it at 3am on a Tuesday when everything is going sideways. You learn what good judgment looks like when you watch someone make the right call in a situation no policy anticipated.

That operational experience attracted an invitation I didn't expect: to join the technology team at Marriott International, where I spent fifteen years working across the bridge between technology and customer service delivery. The mandate was to bring the real-world texture of hospitality operations into how technology was built and deployed, to keep the guest experience understandable to the engineers and the technical possibilities visible to the operators. It was, in hindsight, exactly the kind of work I had been preparing for without knowing it.

Fifteen years ago, I moved into independent consulting. Since then I have worked with a broad range of organizations - large corporations navigating complexity, smaller companies trying to grow without losing what made them worth growing - helping them adapt to changing markets, build strategic clarity, and operate with more intentionality than most organizations manage by default.

The decision sciences chapter of my career, the one that seemed like a false start, has turned out to be more relevant than ever. The questions I was asking about machine intelligence decades ago are now the questions every organization is asking about AI. The difference is that I have spent the intervening years inside the organizations that will be most affected - understanding how culture travels, how alignment breaks down, and what it actually takes to build something durable.


How I Think About This Work

The through-line in everything I do is intentionality. Most organizations are reactive by default, responding to market forces, competitive pressure, and internal friction as it arrives. The ones that navigate complexity well are the ones that have been deliberate about who they are, what they're building, and how they want to operate. That clarity doesn't prevent disruption. It determines whether disruption is survived.

On consulting itself: I have a strong belief that the best outcome of any engagement is a client who no longer needs me for that problem. Too much of the consulting industry is structured around the opposite incentive - embedding deeply, creating dependency, ensuring that the revenue relationship outlasts the value it delivers. I find that model both ethically uncomfortable and strategically shortsighted. Organizations that learn to fish catch more fish. That is what I am here to help with.

The work I find most meaningful sits at the intersection of strategy and culture - the places where what an organization says it is and what it actually does either align or diverge. In my experience, almost every persistent organizational problem can be traced back to that divergence. Getting the answer right requires honesty about both sides.


Advisory Engagements

Engagements are structured around where your organization actually is - not a fixed package applied uniformly. The right starting point depends on the clarity you already have and the specific challenge you're facing.

"The right engagement is the one that fits where you are. If you're not sure which of these makes sense, that's a reasonable place to start the conversation."

Begin a Conversation