Communication channels

Previously I assumed, that most people read the email they get, and have they actionable emails readily available. I use email as my primary mode of messaging, regularly empty my inbox, and and it works very efficient. Then I saw the inbox of a friend, and realised how wrong my assumption were.

Emails can be received to an inbox, or to a stream of information. In the latter case actionable items may drown, og get missed. This also made me understand, why some people, prefer to communicate on facebook, whatsapp, telegram, twitter, linkedin, etc.

This also made me curious: what is your primary means of communications?

My current primary communication tools are:

  1. email
  2. sms / phone
  3. riot.im
  4. github
  5. web (i.e. blogs of friends, etc.)
  6. facebook, twitter, linkedin, couchsurfing, slack, etc. (very irregularly)

Actionable messages that gets to my email, stays right in my face until I answer them. sms, phone, and riot.im also are quite sure to get answered, but if there is a long-term actionable item, I usually transfer it to email, or add it to my backlog. The rest is check once in a while.

This also makes me realise, that if I want to communicate more effectively, a simple optimisation is: to use the primary communication channels of the receiver.




Notes and projects, - mainly for own use/reference.

index
preview
writings
notes
404
2017 08 25 js ipfs mini hackathon
2017 08 11 yourself as your personal assistant
2017 08 11 time schedule
2017 08 04 status update
2017 07 31 communication channels
2017 07 30 what matters
2017 07 30 purposeful computing
2017 05 17 react material design
2017 05 10 passion projects vs income projects
2017 05 10 jekyll site development
2017 04 28 1001 nat
2017 04 24 heavenly menu icon
2017 04 23 master of orion
2017 04 23 geopolitical dodecahedron
2017 04 20 mainstream code
2017 04 20 code infratructure
2017 04 18 easy publish
2017 04 11 generic backend server
2017 04 11 future proof webapps
2017 04 10 simple javascript
2017 04 07 new site note
2017 03 09 building for the future browser
2017 03 02 herkules
2017 02 27 www.solsort.com landing page
2017 02 24 stream of consciousness and book idea
2017 02 08 user interfaces as pure json data
2017 02 08 shell ipfs notes
2017 02 07 contango
2017 01 31 thoughts about distributed cloud
2017 01 25 copenhagen
2017 01 15 my startup
2017 01 15 linux mac keyboard
2017 01 11 deploying with github travis and unpkg
2017 01 09 toastmaster talk
2017 01 03 checklists
2017 01 02 songs
2016 12 30 my calendar early 2017
2016 12 29 metode til daglig motion
2016 12 29 javascript features in modern browsers 2016
2016 12 22 review 2016 direction 2017
2016 12 21 bootstrapped clojurescript
2016 12 15 extending others webservices
2016 12 07 sprint off practical
2016 12 05 blog editor notes
2016 11 20 data calculator
2016 11 19 virtual machine revisited
2016 11 16 virtual machine memory layout for a functional language for embedded systems
2016 11 16 setting up android development react native under linux
2016 11 15 important javascript features
2016 10 30 quarterly review 2016q3
2016 10 21 notes
2016 10 20 bibliotekernes udviklernetvaerksmode