Monday 12 February 2018

Does someone refusing to email make you suspicious?

Does someone refusing to email make you suspicious?

I have no problem writing my concerns in an email, I do prefer to send PDFs so they can't be changed if there's data or a policy. I also write a lot of notes for formal meetings because I'm more forgetful. Am I alone in this or is it an admission of powerlessness? I don't have a problem having an informal chat but will often follow up with an email if I have action items.
https://freethoughtblogs.com/fierceroller/?p=4010

7 comments:

  1. It is not advisable to send sensitive information over unprotected email. If you can use end-to-end encryption like S/MIME then it is secure. If you can verify that the server communication has been protected by TLS and additional measures like DKIM, SPF, etc. then it is reasonably secure. Also, if you are only discussing trivial matters then you probably don't need much extra security.

    ReplyDelete
  2. I don't like email anymore. Never have, when it comes down to it. People can forward email beyond the prudent scope of a discussion. It creates "trees" where a "forest" view is more relevant.

    I've always liked wikis. Used to see more of them: people have moved on to other tools, Trello, Redbooth and suchlike. I have my own Kanban tool as well, for my own team. I put tons of artefacts into version control as well: it's useful to see how things have evolved over time.

    Email is great, for people who have enough communication discipline to use it effectively - or should I say, impose enough communications discipline upon themselves. And... that's not everyone. I'm extremely guarded when it comes to email.

    ReplyDelete
  3. I use version control only for the source (plain git or Atlassian Bitbucket) and for some documentation (or documentation source files like Swagger specs or JavaDocs i.e. Java interface sources). Distribution artifacts are better kept in repository managers like Sonatype Nexus, Artifactory, or similar, or in plain file system based repositories. For Agile boards, ticketing systems, and online collaboration I prefer the Atlassian stack (JIRA, Confluence) although there are many open source alternatives.

    ReplyDelete
  4. You are both proving the bloggers point. Unknown people who phone then refuse to give a preview or outline of a discussion seem skeevy. I have no problem emailing. I expect it to become a public document hence the pdf format.

    ReplyDelete
  5. I want things in writing. Not just because memories are fallible, but so there is a written record of what transpired. In full. Available to both/all parties. If they insist on only speaking on the phone, fine - on the condition that the entire conversation is recorded. I have that option - but most don't.

    What the author is talking about is a situation where someone who wants to stay off the record wants the other party to go on the record in a way that leaves them open to he said/she said attacks.

    Grievances in writing, or STFU.

    ReplyDelete
  6. Chris Pollard I do allow a first pass over grievances to go unrecorded / undocumented. I only allow it face to face, though - and usually taking a long walk, where we can't be overheard.

    I have a sovereign rule: keep your beefs about the team and the client's people within the team - and preferably confined to me or whoever's the acting team lead. If I catch anyone complaining or gossipping outside the team, that's a firing offence.

    But within the team? I'm not going all formal with my own people when they have a grievance. I can't afford people quitting on me and it's been a very long time since I had to sack anyone.

    But a second pass over a grievance or failure or something of that sort, it's as you say, absolutely, I want it in writing, especially if one of the parties isn't under my control or influence.

    ReplyDelete
  7. In some cases it is preferable to have the conversation. Take the call then document it with a follow up email summarizing everything said. If the person disavows at a later date, then they also have to answer for why they failed to set the record straight when they received the confirmation email from you.

    ReplyDelete