{
  "author": {
    "name": "Dylan Fitzgerald",
    "url": "https://dylanfitzgerald.net/"
  },
  "blyg": "0.4",
  "changelog": [
    {
      "at": "2022-07-12T02:56:00Z",
      "note": "Imported from the Ctrl+Shift archive",
      "version": 1
    }
  ],
  "content_hash": "sha256:d634f1cf26cb750f76f4d53e4c65c22df38cd04c8dab2a3147c2c363841ffcd2",
  "content_html": "\u003ch1\u003eMeet your client where they are\u003c/h1\u003e\n\u003cp\u003eDo you recall the last time you got a question or demand from your client or customer that not only didn\u0026rsquo;t make sense, but it left a mark on you emotionally? Lingering frustration, a sense of disconnection or even insult\u0026hellip;\u003c/p\u003e\n\u003cp\u003eAn \u003ca href=\"https://news.ycombinator.com/item?id=32056969\"\u003eHN thread from earlier today\u003c/a\u003e is illustrative of these interactions. A builder or producer or engineer supplies a piece of data without questioning what it\u0026rsquo;s for or the context; the recipient hears something they didn\u0026rsquo;t want and reacts strongly; everyone comes away with no more information than they had before, but feeling worse. Nobody wins.\u003c/p\u003e\n\u003cp\u003eOf course, it\u0026rsquo;s possible that the real, actual information being communicated was really, actually that disappointing, enraging, and awful, and that a strong emotional reaction without further qualification was the only reasonable response.\u003c/p\u003e\n\u003cp\u003eBut probably not.\u003c/p\u003e\n\u003cp\u003eMore likely, this is folks feeling like they\u0026rsquo;re not seen \u0026amp; not understood\u0026ndash;because they\u0026rsquo;re not being seen, and aren\u0026rsquo;t understood. The folks building a thing have a full grasp of all the nuance and effort and complexity that goes into building the thing, and are rightly sensing that their client doesn\u0026rsquo;t grasp that. The client has specific needs they\u0026rsquo;re trying to satisfy, and are rightly sensing that their service provider, employee, contractor, etc. is focused on the deliverable, not on seeing their problems.\u003c/p\u003e\n\u003cp\u003eSomeone needs to break the impasse \u0026amp; ask the right questions, both to actually get the information about their counterparty\u0026rsquo;s needs and to demonstrate that they see them\u0026ndash;to help their counterparty feel seen. Until that happens, there\u0026rsquo;ll be tension remaining, even after delivery.\u003c/p\u003e\n\u003cp\u003eIf you ask me (and you\u0026rsquo;re on my site, after all), in a consulting relationship, this is the consultant\u0026rsquo;s profession and responsibility. The client is by definition the expert on their own needs. You\u0026rsquo;re the expert on bringing good questions to bear\u0026ndash;this is more important than delivery! And that means swallowing your pride for a few uncomfortable minutes so you can really get curious about why your client feels they way they do.\u003c/p\u003e\n\u003cp\u003eWork with people you like and want to help. Meet them where they are, even if that\u0026rsquo;s not where you want them to be. Care enough that you want them to get to a better place of their own accord, knowing that you may have the honor of walking alongside them. That\u0026rsquo;s where your job starts.\u003c/p\u003e\n",
  "content_md": "# Meet your client where they are\n\nDo you recall the last time you got a question or demand from your client or customer that not only didn't make sense, but it left a mark on you emotionally? Lingering frustration, a sense of disconnection or even insult...\n\nAn [HN thread from earlier today](https://news.ycombinator.com/item?id=32056969) is illustrative of these interactions. A builder or producer or engineer supplies a piece of data without questioning what it's for or the context; the recipient hears something they didn't want and reacts strongly; everyone comes away with no more information than they had before, but feeling worse. Nobody wins.\n\nOf course, it's possible that the real, actual information being communicated was really, actually that disappointing, enraging, and awful, and that a strong emotional reaction without further qualification was the only reasonable response.\n\nBut probably not.\n\nMore likely, this is folks feeling like they're not seen \u0026amp; not understood--because they're not being seen, and aren't understood. The folks building a thing have a full grasp of all the nuance and effort and complexity that goes into building the thing, and are rightly sensing that their client doesn't grasp that. The client has specific needs they're trying to satisfy, and are rightly sensing that their service provider, employee, contractor, etc. is focused on the deliverable, not on seeing their problems.\n\nSomeone needs to break the impasse \u0026amp; ask the right questions, both to actually get the information about their counterparty's needs and to demonstrate that they see them--to help their counterparty feel seen. Until that happens, there'll be tension remaining, even after delivery.\n\nIf you ask me (and you're on my site, after all), in a consulting relationship, this is the consultant's profession and responsibility. The client is by definition the expert on their own needs. You're the expert on bringing good questions to bear--this is more important than delivery! And that means swallowing your pride for a few uncomfortable minutes so you can really get curious about why your client feels they way they do.\n\nWork with people you like and want to help. Meet them where they are, even if that's not where you want them to be. Care enough that you want them to get to a better place of their own accord, knowing that you may have the honor of walking alongside them. That's where your job starts.",
  "created": "2022-07-12T02:56:00Z",
  "id": "1mt6pnvf2rj39zw7sh1k56myee",
  "kind": "thread",
  "media": [],
  "origin": "https://dylanfitzgerald.net/blyg/",
  "page": "https://dylanfitzgerald.net/blog/meet_your_client_where_they_are/",
  "transclusions": [],
  "updated": "2022-07-12T02:56:00Z",
  "version": 1
}