See all of the options.

The first step isn't building — it's mapping the full solution space so you know what you're choosing between. Business objectives are achieved through tangible work products, and each one carries its own cost/benefit profile.

Optimize the cost/benefit tradeoff.

Accuracy, interpretability, speed to production, regulatory burden — every business decision is a multi-dimensional tradeoff. "Most accurate" or "highest ROI" is rarely the best answer. Twenty years across analytics, strategy, and operations have revealed which tradeoffs in which contexts actually matter.

The Complexity Tax →

Execute efficiently.

Whether it's a model build, a platform migration, or a product rollout — the skill is the same: decompose, sequence, find the bottleneck, solve it. The right sequencing means early deliverables generate value while the rest are still being built.

Make it land.

Analytics is only as valuable as the decision it changes. Board and C-suite audiences don't need to understand the methodology — they need to understand the implications, the tradeoffs, and recommendations.

  1. Lead from the front. I personally understand the complexities, constraints, and opportunities of the systems I lead. I don't manage from a remove.
  2. Respect the decisions that got us here … Established approaches exist because someone made a reasonable tradeoff with the information they had. Understanding why things are the way they are is a prerequisite to changing them.
  3. … Then change them. "We've always done it this way" is not a reason to keep doing it. Objectives evolve. Constraints shift. The work is knowing when the old tradeoff no longer holds.
  4. Trust in my team scales with demonstrated judgment. I give people as much autonomy as they've earned. The management job is calibrating how much independence each person can handle — and then staying out of the way.
  5. Build the 30-page appendix so the 3-page executive summary is bulletproof. I want to know every detail that could matter — not to present all of it, but so that when someone challenges a conclusion, I'm not guessing.

Contracts Are Load-Bearing Infrastructure, Not Documentation

Personal

When independent agents share a codebase, the question isn't how to make them coordinate. It's what minimum shared structure makes coordination unnecessary. The answer is contracts.

AIMulti-Agent SystemsLeadershipSoftware Architecture

One Agent's Entire Job Is Auditing the Other Seven

Personal

Convention compliance and documentation don't happen by accident — on human teams or agent teams. The solution is the same: make it someone's entire job.

AIMulti-Agent SystemsLeadershipSoftware Architecture
All writing →