Essays and case studies.

Why most AI-in-product is shipping the wrong shape. The case for autonomous systems with real audit logs over polite co-pilots that ask permission for every step.

Screens are cheap. The contract — the spec, the state machine, the agreement — is what compounds. The PM work that pays you back in three years.

A regulator emails about a transaction from eight months ago. In one company that's two weeks of forensic work. In another it's 90 seconds. What separates the two is one habit.

Same industry, different muscle. Selling to banks is a different game from selling to consumers — and it changes everything about the job.

Three regulators, same goal, three architectures. What each one is right about, wrong about, and what cross-jurisdictional PM work actually looks like.

Two engineers argued about a roadmap for forty minutes. I went to the whiteboard and drew the eight boxes that mattered. The argument ended in five.

A four-layer architecture, graduated autonomy, and 20 scheduled tasks — a personal operating system for the AI-era PM job.

A high-level case study on the tension between local-market specifics and platform universality. Detail bounded by what eOS has chosen to publish.

Positioning, the white-label site, the Chrome extension, gamification, communities, retention — the founding-PM arc, end to end.

The four architectural calls — idempotency, load shedding, smart retries, hosted checkout — that made a single URL replace a payments integration.