Governance design, architectural decision-making, and lessons from real execution across technology, agriculture, and ventures.
Org charts show formal structure. Organizational maps show how decisions actually flow. Five layers — formal structure, functional authority, information flow, influence network, accountability alignment — reveal governance failures before they become crises.
Dashboards drift from decision tools to performance management theater through four mechanisms: metric proliferation, vanity capture, lag-without-lead, and audience confusion. Governing them requires a structured architecture.
Meeting overload is a governance symptom, not a time management failure. Four governance problems produce most unnecessary meetings — and fixing them reduces meeting volume more reliably than any calendar policy.
Most process documentation serves the documenter's memory, not a new person's onboarding. Five structural criteria determine whether a process document survives when the person who wrote it leaves.
Governance debt accumulates the same way technical debt does — incrementally, invisibly, and with compounding interest. How it forms, how to assess it, and what remediation actually requires.
Operating models designed for stability become brittle when the environment keeps changing. Four design principles for operating models that absorb change without restructuring every six months.
Decision matrices are built and then ignored because they are designed to document decisions already made, not to produce decisions. Four structural conditions determine whether a matrix will actually be used.
The pattern that repeats: organizations build PMOs to improve delivery. Delivery gets worse. Why this happens structurally, what PMOs actually do well, and what a functional one looks like — from someone who founded two.
Most organizations confuse roles (decision authority) with responsibilities (task ownership). The confusion produces accountability gaps that no amount of RACI charting resolves — and the structural fix.
Applying governance thinking to the management of your own ideas and published positions — the intellectual debt that comes from publishing faster than you are thinking.
Most retrospectives produce team bonding, not transferable knowledge. The Generalization Test (situation type, causal mechanism, team vs. work finding, rule formulation) identifies which retrospective findings can travel beyond the room — and what facilitation conditions make that possible.
Most failure documentation is produced under conditions that systematically undermine honesty. The Failure Documentation Protocol (timeline reconstruction, contributing condition analysis, decision point audit, counterfactual assessment, forward implication) distinguishes cause-finding from blame-finding.
Advisory and consulting for organizations navigating complexity.