Skip to content
/ALMANAC

Dated writing

Journal

  1. From Activity-First to Strategy-First

    I observe one clear pattern. Most work is activity-first. People start doing before they define what winning looks like. Meetings happen. Tasks move.

  2. The Founder Is the Loop

    On April 29, 2026, I was thinking about founders who described an AI strategy while remaining personally distant from the tools and decisions involved.

  3. Presence as Architecture: Why BUSYness Is a Structural Fault

    [A Note from the Architect] On April 23, 2026, I am auditing a specific failure of leadership presence. The failure is quiet, structural, and expensive.

  4. Inside their weather

    Two people can describe the same disagreement accurately and still misunderstand what is at stake for each other. One is discussing a delayed reply.

  5. The Barrel OS: Architecture of Human Velocity

    On April 13, 2026, I was examining a distinction associated here with Keith Rabois and Khosla Ventures: people who can carry an ambiguous objective to an outcome, and people who execute well within clearer direction.

  6. Ten Laws of Strategic Command

    On April 12, 2026, I was reviewing ten elements that can strengthen a strategy.

  7. The Sovereign Codex: Principles of Command

    On April 11, 2026, I was trying to connect several frameworks I had been developing. The useful structure was not an operating system for existence.

  8. The Strategy Loop

    Strategy is not finished when the deck is approved. It remains a loop between intention, evidence, action, and revision. The strategy loop 1.

  9. The Architecture of Respect

    On March 23, 2026, I was reflecting on behaviours that can contribute to respect. Respect is neither a script nor a guaranteed output.

  10. Logic still needs a bridge

    Logic still needs a bridge. A sound idea can fail to travel when it is delivered without warmth, timing, or regard for the person receiving it.

  11. Authority without rank

    In 2023, I brought a CXO into my team to lead a significant business function. His title gave him full formal authority.

  12. What repetition makes easier

    I have noticed that repetition does more than improve a skill. It also makes a response easier to reach.

  13. Empathy without absorption

    I have sometimes confused empathy with taking another person’s distress into myself. The impulse looks caring.

  14. A founder is one influence on the company

    On March 14, 2026, I wrote that a founder cannot hire their way out of their own flaws.

  15. The Architecture of Certainty: Engineering the Loop

    On March 11, 2026, I was examining how practice and evidence affect confidence. Confidence is not a calculated product of evidence, story, and action.

  16. The Algorithm of Fortune: Engineering Systemic Serendipity

    On March 10, 2026, I was thinking about how preparation and relationships affect what we later call luck.

  17. Small acts keep relationships alive

    Relationships are often sustained through small acts. The important moments are not always large favors or long conversations.

  18. The Learning Machine: Hardening the Ray Dalio Principles

    In March 2026, I was revisiting ideas from Ray Dalio’s Principles about reflection, learning, and systems.

  19. The Cognitive Debugger: 12 Logic Leaks

    In March 2026, I noted that all-or-nothing thinking was a recurring trap for me. The broader list came from common descriptions of cognitive distortions.

  20. The Cognitive Firewall: Architecture of the Wheel

    In 1997, I moved away from the CA and CS path I had been following. That experience made me more attentive to assumptions presented as obvious.

  21. The iceberg is a prompt, not a law

    The iceberg model is useful because it interrupts the first explanation.

  22. The Illusion of the Castle: Strategy as Scaffolding

    Strategy is the art of subtraction.

  23. Use RACI for work, DACI for decisions

    RACI and DACI solve related problems, but they are not interchangeable. RACI is useful when a group needs clarity about how work will be carried out.

  24. What a team hears under pressure

    A team listens differently when something has gone wrong. The server has failed, a client has left, or a deadline has been missed.

  25. The Category Error: Vector vs. Integrity

    Stop using "Strategy" and "Systems" as synonyms. It is a lethal category error that collapses the architecture of your life and your business. I.

  26. Make room to reconsider

    A schedule can stay full long after the reason for parts of it has weakened. The work continues because stopping to examine it feels like falling behind.

  27. Make the first move testable

    A team can agree on a plan and still leave the meeting with nothing it can attempt. The goal is clear enough to discuss but too large to act on.

  28. What repeated choices can change

    We do not choose our initial conditions. I see this in the world around me, including the different forms of poverty and privilege into which people are born.

  29. Learn from the next error

    A test is useful when a result can change the decision. Producing an error and calling it learning is not enough.

  30. Test one boundary

    Growth often begins with a small test beyond what has become familiar.