Learn
Knowledge without execution is intellectual vanity.
Frameworks and mental models from 19+ years of building systems across technology, education, agriculture, and governance.
- 208 articles
- 4 learning paths
- Practitioner-grade
- From real engagements
Domains
Four disciplines, one system.
Each domain is a lens on the same underlying question: how do you design systems that survive contact with reality?
Systems Thinking
See the whole system, identify leverage points, and design interventions that compound over time.
Leverage points, feedback loops, mental models
Governance Design
Build operating systems for organizations — decision frameworks, quality gates, and structural enforcement.
Quality gates, decision frameworks, compliance
Execution Architecture
Turn strategy into delivery. Pipeline thinking, delivery governance, and accountability structures.
Delivery pipelines, stage gates, scope management
Agricultural Technology
Apply systems thinking to Filipino agriculture — cooperatives, supply chains, and sustainable intervention design.
Cooperatives, supply chains, technology intervention
Recent Essays
From the recent archive.
The 6 most recent essays. The full archive of 208 is at /writing.

From Assistants to Agents: What Agentic AI Changes for Operations
An assistant suggests and a human acts. An agent acts within bounds. That single shift moves AI errors from bad advice to direct consequences — and changes what governance has to do.

When AI Fails in Production: An Incident Response Playbook
AI failures are silent, plausible, and propagate through automated downstream actions. This is the operational sequence for the first hour, the rollback, the postmortem, and the readiness you build before the first incident.

The True Cost of AI in Production: A TCO Framework
The license fee is the smallest line item in running AI in production. A total cost of ownership framework for the inference, review, monitoring, and failure costs that surface only at scale.

Build vs. Buy for AI Capabilities: A Decision Framework
Most teams get the AI build-vs-buy question backward — building commodities and buying differentiators. A framework for deciding by strategic value, rate of change, and where a capability sits in its lifecycle.

The Founder Bottleneck Is a Governance Problem, Not a Delegation Problem
Every founder who has tried to scale past the point of personal review has encountered the same failure mode. The conclusion most founders draw — delegate better — is wrong. The problem is the absence of a governance layer that makes delegation reliable.

The Operating Model Problem: How to Run Multiple Ventures Without Losing Control of Any
Running eighteen ventures across unrelated domains requires an operating system — a shared governance layer that applies the same structural discipline across the entire portfolio without requiring the operator to reinvent it for each new venture.
Philosophy
How systems thinkers learn.
Three principles that inform everything on this site \u2014 and every system I design.
Structure over memory
Build systems that enforce correctness by design. If a rule depends on someone remembering it, the rule will be broken. Structural enforcement — gates, pipelines, automated checks — makes the right path the default path.
Evidence over opinion
Every claim should have a verification method. "Quality is acceptable" is opinion. "These five tests pass" is evidence. Systems that run on evidence scale. Systems that run on opinion degrade with every new person.
Compounding over speed
A well-placed structural change produces returns for years. A parameter adjustment produces returns until the next cycle. Invest in the interventions that compound — even when they take longer to show results.
Continue
Explore the full archive.
All 208 essays \u2014 organized by domain, searchable by topic.
Browse all 208 essays