{
  "author": {
    "name": "Dylan Fitzgerald",
    "url": "https://dylanfitzgerald.net/"
  },
  "blyg": "0.4",
  "changelog": [
    {
      "at": "2024-10-30T04:09:00Z",
      "note": "Imported from the Ctrl+Shift archive",
      "version": 1
    }
  ],
  "content_hash": "sha256:393b00451e10c1c44ceb88c1d5405d25d87ddabba91886a542d794ce1a9e03bd",
  "content_html": "\u003ch1\u003eRecognizing Resistance\u003c/h1\u003e\n\u003cblockquote\u003e\n\u003cp\u003e\u0026ldquo;We\u0026rsquo;re not ready to start on that yet\u0026hellip;\u0026rdquo;\n\u0026ldquo;I don\u0026rsquo;t think I\u0026rsquo;m the right person for this task\u0026hellip;\u0026rdquo;\n\u0026ldquo;We need to do more research before moving forward\u0026hellip;\u0026rdquo;\u003c/p\u003e\n\u003c/blockquote\u003e\n\u003cfigure\u003e\u003cimg src=\"https://dylanfitzgerald.net/ox-hugo/daltoris_six_software_developers_at_their__2c9b6955-884c-4e40-a592-723f53cb3011_0.jpeg\"\n\t\t\talt=\"six software developers at their keyboards, halfway submerged in molasses\" width=\"50%\"\u003e\n\u003c/figure\u003e\n\n\u003cp\u003eAre you hearing the cries of Resistance from your team?\u003c/p\u003e\n\u003cp\u003eI don\u0026rsquo;t mean defiance. I mean big-R Resistance of the \u003ca href=\"https://stevenpressfield.com/books/the-war-of-art/\"\u003eStephen Pressfield\u003c/a\u003e variety: the working-through-molasses sensation, when everything feels hard to start and impossible to finish on time. This in spite of knowing that your team has the skillset to perform and the history of pulling it off.\u003c/p\u003e\n\u003cp\u003eWhat should you be looking for?\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eHigher distractability. A bug bash is great, but if your whole team\u0026rsquo;s focus is shifting towards smaller keep-the-lights-on tasks rather than meatier deliverables, they may be facing Resistance.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003ePerfectionism blocking delivery. Code that gets stuck in review is never fun; code that gets stuck in review for weeks is a sign that something\u0026rsquo;s off. If your team is getting bogged down in the details, they may be facing Resistance.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eAversion to starting new tasks. If your team is finding reasons to delay starting on new projects, they may be facing Resistance.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eChallenges in finishing tasks. If your team is finding reasons to delay finishing projects, they may be facing Resistance.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eAversion to feedback.\u003c/strong\u003e (Much more on this in another post soon after this Resistance focus.) If your team is finding reasons to avoid feedback, they may be facing Resistance.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eIndecisiveness and seeming fear or avoidance of commitment. If your team is finding reasons to avoid making decisions, they may be facing Resistance.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eA general sense of malaise, low engagement: silence in meetings that had once had participation, lack of organic collaboration. If your team is finding reasons to avoid engaging with each other, they may be facing Resistance.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eIt\u0026rsquo;s worth being able to recognize and identify Resistance. Everyone experiences it, individuals and teams alike. And, crucially, it\u0026rsquo;s not a sign of weakness or incompetence. It\u0026rsquo;s a sign that something is off in the system.\u003c/p\u003e\n\u003cp\u003eWhen you recognize Resistance, you\u0026rsquo;ll want to make some changes. But let\u0026rsquo;s start with what won\u0026rsquo;t help: laying out blame and guilt across your team. They\u0026rsquo;re going to need some leadership, grit, and momentum-building, and the worst way to start this is by being further discouraging.\u003c/p\u003e\n",
  "content_md": "# Recognizing Resistance\n\n\u003e \"We're not ready to start on that yet...\"\n\u003e \"I don't think I'm the right person for this task...\"\n\u003e \"We need to do more research before moving forward...\"\n\n{{\u003c figure src=\"/ox-hugo/daltoris_six_software_developers_at_their__2c9b6955-884c-4e40-a592-723f53cb3011_0.jpeg\" alt=\"six software developers at their keyboards, halfway submerged in molasses\" width=\"50%\" \u003e}}\n\nAre you hearing the cries of Resistance from your team?\n\nI don't mean defiance. I mean big-R Resistance of the [Stephen Pressfield](https://stevenpressfield.com/books/the-war-of-art/) variety: the working-through-molasses sensation, when everything feels hard to start and impossible to finish on time. This in spite of knowing that your team has the skillset to perform and the history of pulling it off.\n\nWhat should you be looking for?\n\n-   Higher distractability. A bug bash is great, but if your whole team's focus is shifting towards smaller keep-the-lights-on tasks rather than meatier deliverables, they may be facing Resistance.\n\n-   Perfectionism blocking delivery. Code that gets stuck in review is never fun; code that gets stuck in review for weeks is a sign that something's off. If your team is getting bogged down in the details, they may be facing Resistance.\n\n-   Aversion to starting new tasks. If your team is finding reasons to delay starting on new projects, they may be facing Resistance.\n\n-   Challenges in finishing tasks. If your team is finding reasons to delay finishing projects, they may be facing Resistance.\n\n-   **Aversion to feedback.** (Much more on this in another post soon after this Resistance focus.) If your team is finding reasons to avoid feedback, they may be facing Resistance.\n\n-   Indecisiveness and seeming fear or avoidance of commitment. If your team is finding reasons to avoid making decisions, they may be facing Resistance.\n\n-   A general sense of malaise, low engagement: silence in meetings that had once had participation, lack of organic collaboration. If your team is finding reasons to avoid engaging with each other, they may be facing Resistance.\n\nIt's worth being able to recognize and identify Resistance. Everyone experiences it, individuals and teams alike. And, crucially, it's not a sign of weakness or incompetence. It's a sign that something is off in the system.\n\nWhen you recognize Resistance, you'll want to make some changes. But let's start with what won't help: laying out blame and guilt across your team. They're going to need some leadership, grit, and momentum-building, and the worst way to start this is by being further discouraging.",
  "created": "2024-10-30T04:09:00Z",
  "id": "3vvcbp03rnpfwqtjm9zmvpgsb7",
  "kind": "thread",
  "media": [],
  "origin": "https://dylanfitzgerald.net/blyg/",
  "page": "https://dylanfitzgerald.net/blog/recognizing-resistance/",
  "transclusions": [],
  "updated": "2024-10-30T04:09:00Z",
  "version": 1
}