Skip to content
/ALMANAC

Subject in the Almanac Index

Systems Thinking

Systems, relationships, feedback, boundaries, and second-order effects.

  1. What should healthcare remember?

    A systems architect asks what care must carry forward: decisions, uncertainty, sources, and follow-up. A working hypothesis about memory, AI, and human judgment.

  2. The loop you are standing inside

    A loop you have not named is a loop you are standing inside.

  3. Path-Goal Theory in AI-Native World

    Path-goal theory for AI-native teams: when agents can build, human leadership shifts from tasking work to clearing the path.

  4. Action Without Captivity

    I have spent much of my life interested in action. How do people build capability?

  5. The board you cannot see

    Imagine this. At 11:47 p.m., the office was dark except for one meeting room.

  6. A multiplier does not repair a broken loop

    Speed is attractive because it is easy to see. A task takes 2 hours instead of 2 days. A report appears in seconds.

  7. The Atomic Thinking Protocol

    The Atomic Thinking Protocol makes consequential judgment visible, testable, and correctable: a reality-contact practice for high-stakes decisions.

  8. Does Your Project System Deliver Status or Evidence?

    A status tells you what happened. Evidence helps you decide what should happen next.

  9. The KNOLt Framework

    The KNOLt Framework uses six movements to examine a knowledge object, its evidence, limits, and context before it becomes advice, principle, or operating rule.

  10. You Cannot Compel Self-Management

    An organization cannot command people to self-manage and continue making every consequential decision for them.

  11. When Not to Use Scrum

    Scrum is useful when the work is uncertain and a capable team can turn short cycles into evidence.

  12. The Advantage

    Health is not the opposite of smart. It is the transmission. From the Architect, 09 August 2026.

  13. Scrum Exposes Problems. It Does Not Solve Them.

    My Scrum blog then said, "Scrum exposes problems. It does not solve them." I still think this is one of the most useful things I wrote about the framework.

  14. The DLMx Protocol

    The DLMx Protocol examines how work moves from intent to outcome through doing capacity, leadership clarity, management discipline, and multipliers.

  15. The Backlog Is a Map of Uncertainty, Not a Feature List

    A backlog can make a team look certain long before the team has earned certainty. The list is long. The items are estimated. Priorities are numbered.

  16. What Does Done Mean in a Startup?

    Four people can look at the same work and declare it done for four different reasons. The developer says it works. Operations says it has been released.

  17. What Scrum Still Gets Right

    I no longer see Scrum as the answer to how work should be done.

  18. Indifference is not always hostility

    I have observed that indifference can feel like hostility when we are already prepared for an attack. A customer does not respond.

  19. Find where delay enters the system

    Find where delay enters the system A version was published on LinkedIn on July 29, 2026. The export does not establish the timezone or first-publication venue.

  20. The Toll Before the Reward

    From the Architect. 21 June 2026. Written at the edge of a decision I made before the evidence was in. STATION ONE: The Misread Most people overestimate talent.

  21. Staying centered

    Equanimity is staying centered when everything else is not. This sounds simple until the surrounding volatility is personal.

  22. Carnegie for Gen Z: A Systems-Level Re-Read

    [Note from the Architect: 01st June 2026] Dale Carnegie wrote How to Win Friends & Influence People in 1936.

  23. Source, Not Resource

    On May 29, 2026, I was examining how the language of “resources” shapes management.

  24. 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.

  25. 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.

  26. 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.

  27. The Sovereign Strategy Stack: Architecting the Board

    Tools can improve execution, but they cannot decide which problem deserves attention.

  28. Empathy without absorption

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

  29. Systems Thinking

    Systems thinking begins by resisting the urge to solve the problem too quickly.

  30. 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.