Be fast or best, not both.
Pick a lane. Move quickly and learn in public, or commit to best-in-class at a slower cadence. Optimizing for both produces confused direction and mediocre output.
A decade building products across data, AI, and platform ecosystems — in environments where complexity is the constraint.
Execution keeps getting cheaper; what stays scarce is judgment in messy, high-leverage decisions. That's the work.
I've spent a decade building and scaling products in environments where complexity is the constraint — multi-billion-dollar platforms, dense stakeholder maps, and heavily regulated domains.
The work has always been the same shape: turn data, AI, and platform strategy into durable business outcomes, not just shipped features.
What separates product leaders in AI-shaped markets isn't more process — it's knowing what to build, when to say no, and where to concentrate scarce attention. The seven I return to most often.
Pick a lane. Move quickly and learn in public, or commit to best-in-class at a slower cadence. Optimizing for both produces confused direction and mediocre output.
A precise system — even if slightly off — can be tuned. An imprecise one is noise. Sharp goals and unambiguous criteria make strategy adjustments surgical instead of chaotic.
Experiments aren't a hobby. Timebox tests, set kill/ship thresholds upfront, watch the ratio, and treat consecutive losses as a signal to pivot — not a sunk-cost excuse to continue.
People reach for painkillers before supplements. Solve acute, expensive problems first; you earn permission to add delight later, and compounding trust along the way.
A process is a checklist people follow. A system is an engine that produces outcomes even when you're not in the room. Invest in incentives and feedback loops, not more templates.
Rebuilding to arrive at the same place is waste. Reinvention is justified when it raises the bar by an order of magnitude — on reliability, speed, economics, or strategic control.
Activity is not progress. The goal is maximum business and customer impact for the least necessary work. Focus teams on the delta you create in the world — behaviour changes, economics, resilience — not features shipped.
Walk as far as you can see — then decide and learn. Suddenly, you can see a bit further.
My work sits at that intersection — designing harnesses, orchestration layers, and unit economics that make AI both reliable and viable.
Most AI agent projects don't fail because the model is weak — they fail because the system around the model isn't designed to handle failure.
Drawing on biomimicry, I focus on harness engineering: feed-forward and feedback guides, guardrails, and sensors that govern what happens when agents go wrong, so the system fails gracefully instead of catastrophically.
The next advantage won't be "who has the best model?" — it'll be who owns the layer that routes across many models with the right economics and reliability.
That means treating AI infra like a portfolio: separating training capex from inference COGS, defining the true unit of value, and engineering routing, caching, and model choice so contribution margins improve as usage scales.
The real product opportunities lie where infrastructure is breaking: power and compute bottlenecks, memory and data exhaustion, networking and transmission limits, the missing safety layer for physical AI and trust rails for agentic commerce, and the architectural gaps in digital twins and fusion-scale systems.
I'm drawn to problems where solving the underlying architecture — rather than adding another wrapper — creates durable advantage for decades.
Every job is task plus judgment. AI speeds the task. Your judgment just got leverage.
A few recent pieces that best capture how I think — on LinkedIn, where most of the conversation actually happens.
Three things: empathy for real users, understanding the system around the product, and naming the bet under ambiguity. Execution keeps getting cheaper — judgment in messy, high-leverage decisions is what stays scarce.
AI makes pedestals easy to build: prototypes, agents, demos. In Atlassian's State of Product 2027 survey, 80% of product professionals say AI helps them ship faster, yet customers see value no sooner. The monkey is the assumption the bet depends on. Test it first, in the smallest credible way.
Whatever the requirements say, the bridge has to stand. Requirements are a lossy compression of judgment, and when an AI executes them, the spec is met and the outcome still fails. Intent-as-Source: one small, human-owned layer of intent, compiled into the requirements.
On AI agents and harness engineering — why the real challenge isn't model quality, but designing systems that fail well. Inspired by biomimicry and benchmark gains from changing the harness, not the model.
A frontier model plans, decomposes and reviews; a quantized 9B model on a laptop GPU does the routine work. About a third of my nine billion tokens now run locally, at near-zero cost per token. Stanford's MinionS runs the same split, and NVIDIA's small-model paper argues for it.
An alumni talk — "Power Tools for Your Ambition" — on the next tool transition in product work. The premium moves to problem framing and decision quality; gunafood was the live example: define the product, make the calls, judge what ships.
Judgment compounds when it meets reality. A personal lab, run on my own time.
Thirty-plus product-management frameworks, packaged as an AI skill. PM judgment, encoded.
Intent as the source file, requirements as the build output.
Code measurement an agent calls as it works. Every number carries its evidence and stays unconfirmed until an independent recompute agrees.
A research-grounded org simulator — 500 in-browser Monte Carlo runs that stress-test a structure before you staff it. Structure, not headcount.
A disciplined buying method an AI agent can run — independent-evidence clustering, per-claim confidence, counterevidence kept in view.
Decision assist on a 0.4B model, fine-tuned twice: one reviews product claims, one reads maintenance sensor flags, both on synthetic scenarios. Narrow models for narrow calls.
How a business runs, mapped: APQC's 13 process categories and 72 process groups, against 257 ranked software vendors.
A 234-node, XBRL-mapped P&L ontology with a live explorer — the financial structure every FP&A team rebuilds, encoded once.
VQE on tungsten–hydrogen binding, run on real IBM quantum hardware — a calibrated read on where quantum stands for hard chemistry.
The wider lab — skill runtimes, MCP servers, models, works in progress → github.com/gtm-k ↗ · huggingface.co/gtm-k ↗
I focus my giving on expanding the circle of dignity and opportunity — from animal welfare and direct cash transfers, to children's futures and anti-corruption work that enables healthier economies.
Open to senior product leadership roles, advisory conversations, and opportunities at the intersection of AI, platforms, and complex systems. The best way to reach me is through LinkedIn.