Learn
Knowledge without execution is intellectual vanity.
Frameworks and mental models from 19+ years of building systems across technology, education, agriculture, and governance.
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
Archive
More reading.
18 Ventures, 1 Operating System: How Modular Architecture Scales a Solo Operator
18 ventures, one operator, no scaling team. The modular architecture — shared monorepo, UI, database, governance — that replaces headcount with structure.
Teaching AI to Graduate Students: Bridging Theory and Execution
Graduate students I supervise at PCU keep producing perfect project plans with no execution behind them. The problem is not the students. It is what the curriculum rewards.
40-70% Delivery Reduction: What Applied AI Actually Looks Like
Forty to seventy percent delivery reduction across Bayanihan Harvest, CapitalWizards, Rico KMS, MrPetLover, and DioshLequiron. The system is not the AI. It is the governance around the AI.
Why Resilient Systems Beat Efficient Systems Under Real Conditions
Efficiency optimizes against modeled conditions. Resilience survives real ones. Why resilience-first design outperforms in delivery operations, with evidence from enterprise programs and portfolio operations.
Why Governance Survives Leadership Changes Only When It Is Structural
Governance that depends on institutional memory dies with the people who hold it. Structural portability — enforcement in tooling, lessons as artifacts — is what makes governance survive transitions.
Recovery Architecture: How to Design Systems That Fix Themselves Without Heroics
Most systems do not fail cleanly. They degrade, and humans compensate quietly until the compensation breaks. Recovery architecture makes systems fix themselves without requiring heroes on call.
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 articles, frameworks, and mental models \u2014 organized by domain, searchable by topic.
All Writing