{
  "author": {
    "name": "Dylan Fitzgerald",
    "url": "https://dylanfitzgerald.net/"
  },
  "blyg": "0.4",
  "changelog": [
    {
      "at": "2022-07-29T02:36:00Z",
      "note": "Imported from the Ctrl+Shift archive",
      "version": 1
    }
  ],
  "content_hash": "sha256:85cf0e9494785f4948920914ef9fb21edfbca874c860ad9b93ad84e84ca9ea04",
  "content_html": "\u003ch1\u003eYou probably need less process.\u003c/h1\u003e\n\u003cp\u003eWhat do you want out of your team processes?\u003c/p\u003e\n\u003cp\u003eThis seems like a straightforward question: enable you to achieve your goals, or Create Excellence, or something similarly vague and tactically meaningless.\u003c/p\u003e\n\u003cp\u003eBut what do you \u003cspan class=\"underline\"\u003eactually want\u003c/span\u003e out of your team processes? What specific effects do you want them to have? What guidance and constraints? Just as important: what \u003cspan class=\"underline\"\u003edon\u0026rsquo;t\u003c/span\u003e you want?\u003c/p\u003e\n\u003cp\u003eIt\u0026rsquo;s tempting to throw process to the wind and just announce: We\u0026rsquo;ll Aim For The Goal And Hit It. There are some teams that can pull this off! They\u0026rsquo;re usually very small, very talented, and very self-motivated. If you think you have one, you should try it! But you should also be prepared for the likely outcome that you\u0026rsquo;ll be setting your team up for disappointment, and be ready to re-add some scaffolding.\u003c/p\u003e\n\u003cp\u003eEspecially in response to team disappointment, chatter, chaos, and the like, it\u0026rsquo;s also tempting to define a process for \u003cspan class=\"underline\"\u003eeverything\u003c/span\u003e. You pre-define deliverables, dates, each communication step, enforce squash merges on your Git host, have an SLA on Slack messages with a rotating on-call person to respond to them with a specific script, have recurring agenda-led meetings to discuss the agenda for other ceremony meetings, and so on. Your primary communication tool is JIRA. This inevitably creates so much overhead that you\u0026rsquo;re all stuck doing so much metawork that you don\u0026rsquo;t do any actual work, and delivery grinds to a halt.\u003c/p\u003e\n\u003cp\u003eThe prescription: add enough process to define the bare minimum someone would have to do to not get fired for sheer incompetence. When you find the need to adjust, do so reflectively and responsively, not as a reaction to prevent a mistake from recurring. The solution to someone making a mistake in isolation is better team communication, not an otherwise meaningless ceremony that creates overhead in perpetuity.\u003c/p\u003e\n\u003cp\u003eProvide a floor to people\u0026rsquo;s work, not a ceiling.\u003c/p\u003e\n",
  "content_md": "# You probably need less process.\n\nWhat do you want out of your team processes?\n\nThis seems like a straightforward question: enable you to achieve your goals, or Create Excellence, or something similarly vague and tactically meaningless.\n\nBut what do you \u003cspan class=\"underline\"\u003eactually want\u003c/span\u003e out of your team processes? What specific effects do you want them to have? What guidance and constraints? Just as important: what \u003cspan class=\"underline\"\u003edon't\u003c/span\u003e you want?\n\nIt's tempting to throw process to the wind and just announce: We'll Aim For The Goal And Hit It. There are some teams that can pull this off! They're usually very small, very talented, and very self-motivated. If you think you have one, you should try it! But you should also be prepared for the likely outcome that you'll be setting your team up for disappointment, and be ready to re-add some scaffolding.\n\nEspecially in response to team disappointment, chatter, chaos, and the like, it's also tempting to define a process for \u003cspan class=\"underline\"\u003eeverything\u003c/span\u003e. You pre-define deliverables, dates, each communication step, enforce squash merges on your Git host, have an SLA on Slack messages with a rotating on-call person to respond to them with a specific script, have recurring agenda-led meetings to discuss the agenda for other ceremony meetings, and so on. Your primary communication tool is JIRA. This inevitably creates so much overhead that you're all stuck doing so much metawork that you don't do any actual work, and delivery grinds to a halt.\n\nThe prescription: add enough process to define the bare minimum someone would have to do to not get fired for sheer incompetence. When you find the need to adjust, do so reflectively and responsively, not as a reaction to prevent a mistake from recurring. The solution to someone making a mistake in isolation is better team communication, not an otherwise meaningless ceremony that creates overhead in perpetuity.\n\nProvide a floor to people's work, not a ceiling.",
  "created": "2022-07-29T02:36:00Z",
  "id": "29s7e0eaty3ax592d79pg8ykf9",
  "kind": "thread",
  "media": [],
  "origin": "https://dylanfitzgerald.net/blyg/",
  "page": "https://dylanfitzgerald.net/blog/you-probably-need-less-process/",
  "transclusions": [],
  "updated": "2022-07-29T02:36:00Z",
  "version": 1
}