{
  "author": {
    "name": "Dylan Fitzgerald",
    "url": "https://dylanfitzgerald.net/"
  },
  "blyg": "0.4",
  "changelog": [
    {
      "at": "2026-11-17T19:58:00Z",
      "note": null,
      "version": 1
    }
  ],
  "content_hash": "sha256:8f26b4951f457b623d6f908c90e5f4b95ba72ee5d5d7637dfabbf5e6b5963e64",
  "content_html": "\u003ch1\u003eProcess and Protocol and Plumbing\u003c/h1\u003e\n\u003cp\u003eI\u0026rsquo;ve been long a fan of actually thinking about your SDLC. Enterprise Bad Agile has been a pet peeve of mine for a decade; spending time with teams and figuring out their work cadence actually feels like, and what their actual needs are, and bringing in the right elements from agile, Shape Up, Kanban, anarchy, interfaces, and just plain home-rolled process was long my happy place, especially when teams or organizations engaged with wanting to work \u003cspan class=\"underline\"\u003ebetter\u003c/span\u003e and not just check a box or \u0026ldquo;Increase Efficiency\u0026rdquo; of someone else.\u003c/p\u003e\n\u003cp\u003eAgent-speed and -scale work breaks most of the underlying assumptions about what work even is and where the costs lie. As an industry and arguably as a society we haven\u0026rsquo;t figured out even the first \u0026ldquo;new way\u0026rdquo; that actually works; mostly we\u0026rsquo;re shoehorning in old processes and letting the agents figure it out.\u003c/p\u003e\n\u003cp\u003eBut we\u0026rsquo;re starting to grasp at some threads where we might orchestrate work. It\u0026rsquo;s not just going to be a different shape\u0026ndash;it\u0026rsquo;ll be a different abstraction layer. And we might not have the tools or even the mental models to do it yet.\u003c/p\u003e\n",
  "content_md": "# Process and Protocol and Plumbing\n\nI've been long a fan of actually thinking about your SDLC. Enterprise Bad Agile has been a pet peeve of mine for a decade; spending time with teams and figuring out their work cadence actually feels like, and what their actual needs are, and bringing in the right elements from agile, Shape Up, Kanban, anarchy, interfaces, and just plain home-rolled process was long my happy place, especially when teams or organizations engaged with wanting to work \u003cspan class=\"underline\"\u003ebetter\u003c/span\u003e and not just check a box or \"Increase Efficiency\" of someone else.\n\nAgent-speed and -scale work breaks most of the underlying assumptions about what work even is and where the costs lie. As an industry and arguably as a society we haven't figured out even the first \"new way\" that actually works; mostly we're shoehorning in old processes and letting the agents figure it out.\n\nBut we're starting to grasp at some threads where we might orchestrate work. It's not just going to be a different shape--it'll be a different abstraction layer. And we might not have the tools or even the mental models to do it yet.",
  "created": "2026-11-17T19:58:00Z",
  "id": "3g42fqff6bswgdkcykz8d0xjx2",
  "kind": "thread",
  "media": [],
  "origin": "https://dylanfitzgerald.net/blyg/",
  "page": "https://dylanfitzgerald.net/blog/process-and-protocol-and-plumbing/",
  "stub_of": {
    "cited": {
      "author": "Protocols for Business",
      "excerpt": "Process management is over. Manage protocols. For thirty years, managers have been told that the process is the business. Map it, measure it, redesign it. In 1990 Michael Hammer told them not to autom",
      "retrieved": "2026-11-16T23:46:38Z",
      "source": "Protocols for Business",
      "url": "https://protocolsforbusiness.com/blyg/t/0cncz177ac6r4aqrvtcjemzq0d/"
    },
    "id": "0cncz177ac6r4aqrvtcjemzq0d",
    "origin": "https://protocolsforbusiness.com/blyg/",
    "version": 2
  },
  "transclusions": [],
  "updated": "2026-11-17T19:58:00Z",
  "version": 1
}