davidbgk
/
larlet-fr-david-cache


			
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223
							<!doctype html><!-- This is a valid HTML5 document. -->
<!-- Screen readers, SEO, extensions and so on. -->
<html lang="en">
<!-- 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>Teaming is hard because you’re probably not really on a team (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://www.strategy-business.com/article/Teaming-is-hard-because-youre-probably-not-really-on-a-team">

<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>Teaming is hard because you’re probably not really on a team</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://www.strategy-business.com/article/Teaming-is-hard-because-youre-probably-not-really-on-a-team" title="Lien vers le contenu original">Source originale</a>
      <br>
      Mis en cache le 2024-01-29
    </p>
  </nav>
  <hr>
  <p>We’ve been thinking a lot about teams lately. As more companies release formal policies around hybrid and remote work, leaders are telling us that remote work has made working together, or teaming, difficult and has frayed the culture of their organizations. Of course, many companies, including our own, PwC, have long embraced remote work, with great success. And if we listen carefully to the types of problems leaders and workers say they’re encountering with teaming, the reality is that most of these issues existed prior to the pandemic.</p>

<p>Many, if not most, workers are frustrated with the groups of people they work with. Leaders and members struggle with long hours, inefficient ways of working, lack of accountability, and frustrating group dynamics. The COVID-19 pandemic didn’t create a teaming crisis. It exposed deficiencies in the in-person model while introducing even more complexity.</p>

<p>In the course of our work with clients across various industries, we have identified several issues that contribute to this frustration. But the most basic one is this: in many cases, people are not and have never been on real teams, nor should they be.</p>

<h3>If not teams, then what?</h3>

<p>Teams don’t exist simply because someone puts some names in boxes on an org chart and assigns a leader. Quite the opposite. Teams exist for specific reasons and have specific supporting structures. Our colleague <a href="https://www.strategyand.pwc.com/gx/en/insights/katzenbach-center.html?utm_campaign=sbpwc&amp;utm_medium=site&amp;utm_source=articletext" target="_blank">Jon Katzenbach</a> defines a real team as a small group of people with complementary skills who are committed to a shared purpose, who succeed or fail together, and who hold one another accountable.</p>

<p>If you feel that your group is missing any one of these ingredients, you might not be part of a real team. This isn’t inherently a bad thing. But it does prompt the question: what should you call the group of people you work with every day?</p>

<p>We can typically break down collaboration groups into three types:</p>

<p><strong>• Real teams</strong> are all about solving the hardest, most complex problems. A diverse set of perspectives and skills is required to untangle these sorts of problems, for which there is no obvious solution. Members of a real team trust one another and work toward a common goal. Real teams are thoughtful. Team members argue, and they push one another to do better. Real teams require nimble leaders who prioritize building connections within the team. They create clear boundaries that reinforce a strong sense of trust. They have a shared purpose and clear norms. And, importantly, they produce a collective output. If you see a group of people focusing intently on solving a single, very complex problem, you’re probably looking at a real team.</p>

<p><strong>• Working groups</strong> are all about efficiency. Most people spend most of their productive time in working groups. We’ll say it again: there is nothing wrong with being in a working group. In fact, working groups are often best suited to the tasks at hand. Managers of working groups focus heavily on techniques to make their collaboration more efficient. Members assign work, share information, and complete tasks individually. Individual accountability is high; emotional commitment and sense of shared purpose are relatively low. If you see people execute a disciplined “five-minute stand-up,” they’re acting like a working group.</p>

<p><strong>• Teams-in-name-only</strong> are groups that claim to be a team, but lack emotional commitment and shared purpose. They are like working groups, but without the efficient processes and individual responsibility. Work gets done, but not always in the most efficient or effective manner. Being on a team-in-name-only requires neither discipline nor commitment, which typically makes it the default mode of working. If a team-in-name-only has a leader, she or he often has minimal leadership skills. Members of a team-in-name-only spend a lot of time talking about their own individual responsibilities, and team meetings become a series of one-on-one conversations between managers and their subordinates. If you aren’t having conversations about how you work, your objectives, and your commitments to the people you work with, there’s a good chance you are functioning as a team-in-name-only. The five-minute stand-up that lasts 90 minutes is a common characteristic of a team-in-name-only.</p>

<p>Although most people are told that they’re part of a team, the reality is that, more often than not, they’re members of a team-in-name-only.</p>

<h3>Why does work feel so much harder now?</h3>

<p>Consider how you probably would have solved a problem or worked through a crisis as recently as February 2020. The process probably would have begun with a manager saying, “Team, I think it’s going to be a long week,” and you and your fellow group members would have responded in kind. You would have rolled up your sleeves, found a place to serve as your war room, and figured out a way to get the task done. You might not have worked together in the most effective or satisfying way, but you would have worked hard and produced a result.</p>

<p>This is a quintessential team-in-name-only experience—a recipe for a result that is acceptable or even good, but not necessarily satisfying or great. As we flash forward to the present, many organizations still haven’t decided to work smarter. Rather, they’ve doubled down on this version of “non-teaming.” Here are two ways the team-in-name-only is manifested today:</p>

<div class="pullquote">
<p>The five-minute stand-up that lasts 90 minutes is a common characteristic of a team-in-name-only.</p>
</div>

<p><strong>1. Meeting bloat.</strong> When a leader avoids making decisions or it’s unclear who should be in the room, the default approach is to have more meetings or invite more people. But what happens when a meeting is no longer confined to a physical space? The ten people who used to max out the available seating in a small conference room can quickly turn into 50 people on a video call, most of whom are unsure of their role, why they were invited, or whether they could have declined the invitation.</p>

<p><strong>2. Excess use of email and chat.</strong> In a pre-pandemic world, managers and colleagues could complement these less-effective communication modes with in-person contact (whether it was planned or spontaneous). Now that in-person connections are not always available, we have overcorrected with a less-than-ideal technology solution.</p>

<p>Both of these outcomes have made work harder and are a direct result of not being deliberate about how to work as individuals and as a collective. So, what are some of the choices and decisions you need to make to be most effective in your work?</p>

<p><strong>Ask whether you need to function as a working group or a real team.</strong> Recognize that those two ways of working together look very different. It’s not impossible to switch between them. But it’s helpful to be clear which mode you’re using and why. Are the problems this group needs to solve sufficiently complex to warrant the expenditure of emotional energy it takes to build a real team? Is the expected output a collective effort that requires active problem-solving? Or is a high-functioning, efficient working group good enough?</p>

<p></p>

<p><strong>Shrink your group size.</strong> We’ve found that the ideal size for virtual teams is actually three individuals, potentially four if the leader isn’t a full-time member of the team. Having more people involved requires significant facilitation and strong norms in order for the group to be effective. Look at any meeting you host, and ask if everyone really needs to be involved. Working groups can often handle a larger size (six to eight participants), as long as the purpose of the meeting is well understood (e.g., information-sharing versus problem-solving).</p>

<p><strong>Make the implicit explicit.</strong> As your teams and groups add and lose members, it becomes necessary to reinforce norms. Don’t rely on informal means of reinforcing teaming behaviors. Be deliberate about discussing matters like when you communicate, how meetings will be run, and the expectations team members have of one another.</p>

<p>These suggestions aren’t silver bullets, but by making deliberate choices about how to collaborate, you can avoid the worst of both worlds: a bloated team-in-name-only that has unclear expectations. After identifying whether your work requires a real team or a working group, you can start taking advantage of remote and hybrid work’s benefits instead of constantly grappling with its downsides.</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>