News for hackers. Stuff that matters.
Re:Encouraging a culture of written communication by aspaceman on Monday May 11, 2020 @02:47PM (#23145547)
If after “resolving” something you can’t actually write down what was accomplished, nothing was resolved.

I’ve had a lot of 1on1s meant to “get us all on the same page” where a boss just blithers and blathers for an hour without communicating anything. The value in writing is working through the mistakes your brain makes during communication. Going to talking just makes it easier to ignore errors.

Re:Encouraging a culture of written communication by mandelbrotwurst on Monday May 11, 2020 @05:07PM (#23147084)
> If after “resolving” something you can’t actually write down what was accomplished, nothing was resolved.

It's possible to "resolve" something / determine what to do next without writing anything down.

Often the ideal outcome is simply an agreement that Person X will move forward with approach Y.

Re:Encouraging a culture of written communication by cmwelsh on Monday May 11, 2020 @06:32PM (#23147930)
On my last team that would result in a JIRA ticket containing the details so approach Y was documented and the reasons behind it were recorded. Then the ticket is assigned to Person X and they go ahead with the work.
Re:Encouraging a culture of written communication by wnevets on Monday May 11, 2020 @05:19PM (#23147214)
>Often the ideal outcome is simply an agreement that Person X will move forward with approach Y.

Which you can write down if you so desire.