davidbgk
/
larlet-fr-david-cache


			
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225
							<!doctype html><!-- This is a valid HTML5 document. -->
<!-- Screen readers, SEO, extensions and so on. -->
<html lang="fr">
<!-- Has to be within the first 1024 bytes, hence before the `title` element
  See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
<meta charset="utf-8">
<!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
<!-- The viewport meta is quite crowded and we are responsible for that.
  See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
<meta name="viewport" content="width=device-width,initial-scale=1">
<!-- Required to make a valid HTML5 document. -->
<title>Writers and talkers and leaders, oh my! (archive) — David Larlet</title>
<meta name="description" content="Publication mise en cache pour en conserver une trace.">
<!-- That good ol' feed, subscribe :). -->
<link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
<!-- Generated from https://realfavicongenerator.net/ such a mess. -->
<link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
<link rel="manifest" href="/static/david/icons2/site.webmanifest">
<link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
<link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
<meta name="msapplication-TileColor" content="#f7f7f7">
<meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
<meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
<meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
<!-- Is that even respected? Retrospectively? What a shAItshow…
  https://neil-clarke.com/block-the-bots-that-feed-ai-models-by-scraping-your-website/ -->
<meta name="robots" content="noai, noimageai">
<!-- Documented, feel free to shoot an email. -->
<link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
<!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<script>
    function toggleTheme(themeName) {
        document.documentElement.classList.toggle(
            'forced-dark',
            themeName === 'dark'
        )
        document.documentElement.classList.toggle(
            'forced-light',
            themeName === 'light'
        )
    }
    const selectedTheme = localStorage.getItem('theme')
    if (selectedTheme !== 'undefined') {
        toggleTheme(selectedTheme)
    }
</script>

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://everythingchanges.us/blog/writers-and-talkers-and-leaders/">

<body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick" data-instant-intensity="viewport-all">


<article>
  <header>
    <h1>Writers and talkers and leaders, oh my!</h1>
  </header>
  <nav>
    <p class="center">
      <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="https://everythingchanges.us/blog/writers-and-talkers-and-leaders/" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <p>I ONCE OBSERVED a small group of leaders gather a bunch of their team together to hash out some big changes to their organization’s mission. They rented space away from the office, flew the right people in, cleared everyone’s calendars. They booked a big table at a very good restaurant. And then they proceeded to talk. They, and the other folks they invited in, talked for the better part of two days. There were breakout groups and there were plenty of breaks, mind you. Coffee and snacks and bottled water and some very good meals were on hand. But the activity everyone had gathered to participate in was talking.</p>

<p>These leaders were <em>talkers</em>. At the end of the second day of this, they were amped up and excited about the plans that had been hashed out and the new vision they’d aligned on and the potential for really amazing change that was afoot. There might have been high fives as they grabbed their coats and headed home. There were definitely some excited DMs and several <em>that was so great!</em> messages sent from the trains and planes that carried them off.</p>

<p>What they didn’t realize was that among the talkers who had been gathered were several <em>writers.</em> The writers were on the whole befuddled and exhausted; they weren’t sure what had been decided on, and when they tried to reflect on all that talking, it was a blur. They could feel the energy of the room was such that something exciting had happened but they didn’t quite know what to think of it. They were uncertain if they had made themselves clear; they were uncertain of what they had wanted to make clear. They wondered if they were missing something, but they couldn’t articulate what it was. They too sent thanks and thumbs up emojis, but they went home with a vague sense of dread.</p>

<h1 id="modes">Modes</h1>
<p>Are you a writer or a talker?</p>

<p>That is, when you need to think about something, do you generally reach for something to write with, or look for someone to talk to?</p>

<p>I first encountered this concept in Peter Drucker’s good and very short <em><a href="https://aworkinglibrary.com/reading/managing-oneself">Managing Oneself</a></em>. He refers to <em>readers</em> and <em>listeners</em>—that is, to preferred modes of learning. I’m turning that around to look at modes of <em>thinking</em>, because in my experience, it’s those different modes of thinking that give rise to some of the most unattended to but tricky workplace conflicts. But both perspectives are useful. Readers learn by reading and think by writing; listeners learn by listening and think by talking.</p>

<p>Most people default to one or another behavior but rarely use them exclusively. Writers will often benefit from talking things out when they get stuck; and talkers will find that occasionally writing something down helps solidify their thoughts. Both strategies can be learned. Whether you’re a writer or a talker isn’t about your inability to do one or the other so much as it is a preferred or optimized mode.</p>

<p>This is, incidentally, a much more valuable way of understanding different working styles than the old maker vs manager canard. Both talkers and writers make things (including <a href="https://aworkinglibrary.com/writing/making-decisions">decisions</a>), but they means by which they make things—and the needs they have in relation to their colleagues—are not the same.</p>

<h1 id="power-talks">Power talks</h1>
<p>In most orgs, talkers are overrepresented among the leadership. This is not because talking offers any advantages over writing in terms of thinking power. Rather, it’s that most of our models for leadership—meetings, town halls, presentations, interviews—privilege talkers. Writers who move up in organizations that make strong use of these models have to either become adept at working outside their comfort zones or else influence the organization to become more writer-friendly. Since the latter requires interrupting the existing structures of power, it’s by definition more challenging to pull off, and less likely to be the route that any eager writer will take.</p>

<p>The result is that a great many orgs have talkers at the top and writers down below, but because power obscures difference, the talkers are very rarely aware of this setup.</p>

<p>What the leaders I observed did was optimize for their own mode of thinking. This isn’t a bad strategy per se, and it’s something that most leaders need to do at least some of the time in order to be effective. But in the course of that optimization, they effectively disenfranchised most of the writers among them. They left a lot of good brain power and potential alignment on the floor, and they didn’t even realize it was there as they stepped over it on the way out the door.</p>

<h1 id="bothand">Both/and</h1>
<p>I’m a writer more than I’m a talker, but I’m not here to argue for one mode over the other. I’m quite certain good thinking happens in both modes. What I am here to do is point out that whichever mode you gravitate to, you work with someone else who leans the other way. And if you do not acknowledge that and work through it, you are wasting a lot of time.</p>

<p>If you, a talker, have a close peer who is a writer, but every time you need their input you put time on their calendar to talk it out, you are not getting their best thinking. Your peer is likely to become convinced that you are confusing and challenging to work with.</p>

<p>If you, a writer, report to a talker, but you insist on communicating primarily through documents, you are—and I say this with affection, because lo, I have been there—fucked. Your manager will never fully grok what it is you’re trying to do, and you will never understand your manager.</p>

<p>If a talker responds to lack of alignment by scheduling time for discussion, but doesn’t also provide a space for the writers to work out their thoughts in writing, whatever alignment seems to have emerged in those meetings will have a half life of hours.</p>

<p>If, on the other hand, a writer tries to build alignment by bombing a bunch of talkers with a well-outlined set of docs, I wish them well but also encourage them to get ready to run. Because as soon as the talkers open their mouths, the message from those docs is going to diverge, and if the writer doesn’t follow them into those discussions, they will be left in the dust.</p>

<h1 id="inquiry-over-process">Inquiry over process</h1>
<p>Okay, so once you know about these different modes, what do you do about it?</p>

<p>Talkers need to recognize that not everyone loves to think out loud, and that giving space for writing is part of what it means to make use of the best brains around you. Writers need to remember that writing isn’t some perfected ideal of thinking and that making space for the messy, chaotic, and improvisational work of talking things out is often exactly what a team needs to create change. Whichever mode you prefer, it’s not feasible to abstain from the other; doing good, collaborative work requires that you practice both modes.</p>

<p>Here is where I could propose some tactics and techniques that work to close the gaps. And, sure, I can do that: you can foreshadow a scheduled discussion by dropping some questions or ideas that you want to talk out into a doc, and ask everyone to write up a few notes ahead of time. Or instead of drafting a whole-assed copyedited and formatted document to share, first write up an outline or a few short notes about the thing you intend to draft, and then open that up for input—both in the doc itself and in some short synchronous conversations.</p>

<p>But more than any specific process I want to posit that the real trick to getting the best out of all the brains around you is to <em>ask what people need</em> and then draw from whichever tactic will meet that need in that moment. Get in the habit of asking questions like: has everyone had a chance to think this out? Do you need more space to talk or write or something else? Can you share what you understand has been decided here today, and why? And then respond without judgement to whatever emerges.</p>

<p>The goal here isn’t some idealized set of processes that perfectly enfranchises everyone on the team every time. The goal is a collective sensitivity and maturity to the different modes and to the circumstances of the topic that lets people safely inquire into what they and their teammates need, and then to productively negotiate the best way to attend to those needs.</p>

<p>You may be thinking that this is going to take a lot more time but I’m here to tell you it will not. If at the moment you are haphazardly and unknowingly optimizing for only one mode of thinking, you are also unknowingly optimizing for confusion and misunderstanding and second-guessing. Because the efficiency of communication isn’t solely a measure of the time it takes to move information from one head to another; it’s also the time <em>and energy</em> required to build and sustain collective understanding.</p>

<p>And here’s the best part: if you and your team strengthen some muscles for asking after what people need when it comes to thinking through a plan or decision or whathaveyou, you will have simultaneously developed a new set of superpowers for building clarity and navigating change and working through conflict. And it’s so easy to start: just say to the next person you interact with, “Hey, when I need to think about something, I like to [talk/write] about it. How about you?” Then talk out whatever they tell you.</p>

<p>Just kidding, go put that information in a doc where it belongs.</p>
</article>


<hr>

<footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
      </svg> Accueil</a> •
    <a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-rss2"></use>
      </svg> Suivre</a> •
    <a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-user-tie"></use>
      </svg> Pro</a> •
    <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-mail"></use>
      </svg> Email</a> •
    <abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-hammer2"></use>
      </svg> Légal</abbr>
  </p>
  <template id="theme-selector">
      <form>
          <fieldset>
              <legend><svg class="icon icon-brightness-contrast">
                <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-brightness-contrast"></use>
              </svg> Thème</legend>
              <label>
                  <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
              </label>
              <label>
                  <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
              </label>
              <label>
                  <input type="radio" value="light" name="chosen-color-scheme"> Clair
              </label>
          </fieldset>
      </form>
  </template>
</footer>
<script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
<script>
    function loadThemeForm(templateName) {
        const themeSelectorTemplate = document.querySelector(templateName)
        const form = themeSelectorTemplate.content.firstElementChild
        themeSelectorTemplate.replaceWith(form)

        form.addEventListener('change', (e) => {
            const chosenColorScheme = e.target.value
            localStorage.setItem('theme', chosenColorScheme)
            toggleTheme(chosenColorScheme)
        })

        const selectedTheme = localStorage.getItem('theme')
        if (selectedTheme && selectedTheme !== 'undefined') {
            form.querySelector(`[value="${selectedTheme}"]`).checked = true
        }
    }

    const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
    window.addEventListener('load', () => {
        let hasDarkRules = false
        for (const styleSheet of Array.from(document.styleSheets)) {
            let mediaRules = []
            for (const cssRule of styleSheet.cssRules) {
                if (cssRule.type !== CSSRule.MEDIA_RULE) {
                    continue
                }
                // WARNING: Safari does not have/supports `conditionText`.
                if (cssRule.conditionText) {
                    if (cssRule.conditionText !== prefersColorSchemeDark) {
                        continue
                    }
                } else {
                    if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
                        continue
                    }
                }
                mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
            }

            // WARNING: do not try to insert a Rule to a styleSheet you are
            // currently iterating on, otherwise the browser will be stuck
            // in a infinite loop…
            for (const mediaRule of mediaRules) {
                styleSheet.insertRule(mediaRule.cssText)
                hasDarkRules = true
            }
        }
        if (hasDarkRules) {
            loadThemeForm('#theme-selector')
        }
    })
</script>
</body>
</html>