Eiffel Over

Tag: CalNewport

  • Lowest common denominator design team communication

    Imagine a system of design team communication that supplies the right level of information and enables the appropriate level of understanding within a suitable timeframe. A way of communicating with our work colleagues that is effective. A process that doesn’t overwhelm us.

    With the digital and analogue tools at our disposal, such a way of communicating is entirely possible. But it takes time to propose, implement, and improve.

    As Cal Newport argues in World Without Email, what usually happens is we don’t make time for this work, and so we revert to the lowest common denominator – in the case of his book, it’s email. However, I think that the lowest common denominator of communication, email has been surpassed by WhatsApp.

    Now, WhatsApp works so well because of its ubiquity – setting up a shared channel is quick, and communication can start almost immediately. But by my counts for successful design team communication, it falls short because:

    • The quality and quantity of information shared vary wildly.
    • There is no checking of understanding (the blue ticks just confirm receipt).
    • Information can arrive at any time (including in the middle of the night or at the weekend).
    • There is rarely any protocol agreed about how the information should be shared, organised, and responded to.
    • Messages come in a stream along with updates from a dozen other projects – not to mention the four other corners of your life. And as it is vastly easier to send group messages than to read them all, we have a recipe for information overwhelm.

    At the start of a project, the quick answer to the question of how to communicate is to set up a WhatsApp channel.

    However, probably the more effective answer is to spend time thinking about and testing a good process for communicating – in other words, designing your design team’s communication.

    If, as a result of that design process, you discover specific cases when a team WhatsApp is a good answer (see my post tomorrow), that answer should be the result of a design process, rather than the default.

  • Think of a world without any email

    This post has moved.
    It now lives on the Constructivist blog: read the updated version →

    Eiffel Over is now my stage for engineering-related clowning, singing, dancing and writing — you’ll find my professional writing on design and regenerative thinking over at Constructivist.

    This came up in a workshop yesterday so I am sharing it today. There will be a time in the future for a longer set of posts on how engineers and other humans can cope with email, but now is not the time.

    So instead, I recommend reading ‘A World Without Email’, by Cal Newport*. I have even considered making reading this book as a prerequisite for entering into new collaborations.

    There is some irony in writing about a world without email on a blog post that is summarised in a weekly email digest. But ultimately it comes down to intentional communication design.

    Hopefully, if you signed up to this list, you did so with the intention of hearing from me (and you can change your settings here). But the problem with email and other forms of instant communication is how easy it is to fall into unintentional communication.

    Dealing with unintentional communication, and the sense of overwhelm it can cause us, feels important because if we are overwhelmed, we have haven’t got space to think. If we can’t think, we don’t have the capacity to imagine a thriving future. And if we can’t imagine it, it makes it much harder to build it.

    *Newport, C. (2021) A world without email: reimagining work in an age of communication overload. London: Penguin Business.