jasonclewis Operator's Log

About

Operator first. Advisor by extension. Founder by instinct.

I've spent my career close to consequential technology decisions—helping leaders reason through them, building the systems behind them, and living with what happens after the slide deck.

The operating arc

My work sits at the intersection of AI, data, business strategy, and execution. I've led startup and frontier AI support at AWS, held leadership within Gartner's global Data & Analytics practice, built and exited technology ventures, and advised leaders from the boardroom to the build room.

That range matters because the hardest AI and data decisions are rarely technical decisions alone. They are choices about operating models, capital, talent, risk, timing, and what an organization is prepared to become.

Today, I work selectively with founders, executives, boards, investors, and PE/VC teams. I also co-founded a technology company in July 2026 with an established industry leader. We are building quietly.

From operator to advisor to founder

I don't see these as separate identities. Advising is useful when it is grounded in operating context. Building is sharper when it is informed by patterns across industries and stages. Writing forces the judgment behind both to become explicit.

That is also the role of Operator's Log: a weekly publication that turns live operating patterns into useful decisions.

Working principles

How I approach the work.

Make the decision legible.

If a strategy cannot name the tradeoff, owner, signal, and exit condition in plain language, it is not ready to operate.

Prefer adaptable bets.

The environment will change. Build enough reversibility into the decision that new evidence can improve it instead of invalidate it.

Stay close to the work.

Executive altitude is useful only when it remains connected to what teams can actually ship, sustain, and learn from.