{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreig3prrr47fvx2r5lywkxebf2mne37vf35uk2aqhjnw7shgk6xi3uu",
    "uri": "at://did:plc:z3z6jqozccanxbyig7t3fhpn/app.bsky.feed.post/3mfbwkyajgzl2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreibesaxvhzsy233rkizelp6tnwm223bj5s7rar3vyoiacyovebhsaq"
    },
    "mimeType": "image/png",
    "size": 31047
  },
  "description": "Jargon isn't the same as precision.\n\nFinance professionals defend technical language as if the two are identical. They're not.\n\nSome technical terms are genuinely necessary. Accrual, materiality, going concern. These have specific meanings. Using them with a finance audience is legitimate.\n\nBut most finance jargon isn't like that.\n\nAs per the agreed parameters.\n\nIt should be noted that expenditure has trended upward.\n\nThe position going forward will require careful monitoring.\n\nNone of that is p",
  "path": "/blog/the-problem-isnt-the-reader/",
  "publishedAt": "2026-02-20T10:46:20.000Z",
  "site": "https://www.garybandy.co.uk",
  "textContent": "Jargon isn't the same as precision.\n\nFinance professionals defend technical language as if the two are identical. They're not.\n\nSome technical terms are genuinely necessary. Accrual, materiality, going concern. These have specific meanings. Using them with a finance audience is legitimate.\n\nBut most finance jargon isn't like that.\n\n> As per the agreed parameters.\n\n> It should be noted that expenditure has trended upward.\n\n> The position going forward will require careful monitoring.\n\nNone of that is precise. It's just formal. And formal isn't the same as clear.\n\nThe worst jargon doesn't just obscure meaning. It allows the writer to avoid committing to anything.\n\nSignificant variances have been identified sounds precise. But significant how? Caused by what? What happens next?\n\nIt says a lot without saying anything.\n\nPlain English forces you to be specific. That's why it feels harder to write. You can't hide behind the language.\n\nThe test I use: **could a reasonably intelligent non-specialist understand exactly what I mean?**\n\nIf not, the problem isn't the reader.",
  "title": "The problem isn't the reader",
  "updatedAt": "2026-02-20T10:46:20.000Z"
}