davidbgk
/
larlet-fr-david-cache


			
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179
							<!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>I helped pioneer UX design. What I see today disturbs me (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)">
<!-- 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.fastcompany.com/90642462/i-helped-pioneer-ux-design-what-i-see-today-horrifies-me">

<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>I helped pioneer UX design. What I see today disturbs me</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.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="https://www.fastcompany.com/90642462/i-helped-pioneer-ux-design-what-i-see-today-horrifies-me" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <div><p>When user experience design broke out of the research labs and into a full-blown industry 20 years ago, the future looked so bright. UX went from the obscure interest of a handful of practitioners to a burgeoning industry demanding thousands of new recruits seemingly overnight. And ever since, the story has been one of more success, ever-increasing influence, and, most important, happier users.</p></div>
<div><p>I was there for some big parts of that story. In 2001, I cofounded a design agency, Adaptive Path, that turned out to be on the forefront of a huge wave of change for digital products: the arrival of user experience and user-centered design. Many of the tools and concepts we developed became a standard part of the many UX programs that have sprung up since. These days, as a coach to UX leaders, I am having continual conversations with them about the direction of the field. And over and over again, the question I hear is: Where did we go wrong?</p><p>That might sound strange, because in some ways things have never been better for UX. The field is huge and growing. And much of the actual design work is higher quality than it’s ever been. But to those who have been in the field a while, there’s a cloud behind all those silver linings.</p><p>The implicit promise of UX for many of us was a burgeoning philosophy of management by inquiry and insight, in which new creative explorations would lead to new questions about human behavior, which in turn would drive the definition of new product and value opportunities. The culture of UX also seemed to necessitate a degree of respect, compassion, and simple humility toward the people who use what we make, and the ways in which their lives and experiences may shape their behavior to look very different from our own. More exposure to this kind of thinking, the theory went, would lead to more demand for it, and the rising tide of human-centered design would pave the way for human-centered enterprises.</p></div>
<div><p>That, to put it bluntly, did not happen.</p><p>Instead of challenging teams to stretch their thinking to address deeper and subtler user needs, product design practices have become increasingly less insight-driven. UX processes in many organizations these days amount to little more than <a href="https://www.spydergrrl.com/2020/05/ux-theatre-poster.html" target="_blank" rel="noopener noreferrer">“UX Theatre”</a> (an idea developed by Tanya Snook in 2018): creating the appearance of due diligence and a patina of legitimacy that’s just enough to look like a robust design process to uninformed business leaders and hopeful UX recruits alike.</p><p>Too many UX leaders have seen the field’s language and ideas co-opted and corrupted by outsiders who never knew or cared about the principles underlying the practices. We thought we were winning hearts and minds, but we were really setting ourselves up for exploitation, as businesses cherry-picked the bits of UX most compatible with their existing agendas and eschewed the parts that might lead to uncomfortable questions that could influence more than the color of a button on a screen.</p></div>
<div><p>One such agenda is that of “agile transformation,” which promises to remake organizations to optimize their processes for developer efficiency. This is a win for developers tired of businesses that can’t articulate what they want, but, perhaps more important, it’s a win for businesses trying to wring maximum productivity out of their growing armies of engineers. However, in the rush toward transformation, something has been lost.</p><p>What got lost along the way was a view of UX as something deeper and more significant than a step in the software delivery pipeline: an approach that grounds product design in a broad contextual understanding of the problem and goes beyond the line-item requirements of individual components. Also lost along the way were many of the more holistic and exploratory practices that enabled UX to deliver that kind of foundational value.</p><p>Talk to any highly experienced UX practitioner these days, and most have a favorite method or practice that they’d like to see revived (or restored to its former glory). Research-driven persona development. Concept models. Cocreation sessions. Task flows. These things didn’t get cut out of UX processes because they were unnecessary. They simply didn’t fit a development process that demands clear accountability for every activity and has no space for foundational work that can’t be predictably packaged up into two-week units.</p></div>
<div><p>Agile’s success at the expense of UX is just one manifestation of a deeper truth: Businesses want scaling. And foundational UX work doesn’t scale. It doesn’t lend itself to predictable, repeatable processes and generic cookie-cutter roles. It can’t, because by definition it deals with unknown, slippery, hard-to-define problems that characterize the leading edge of an organically evolving business.</p><p>The same things that make agile a great fit for scaling engineering work—regular sprint tempos; clearly articulated outcomes to be produced; breaking down the complex, unfolding experience of users into concrete elements that can be tied to code—are the very things that make it a terrible fit for foundational UX work. The holism necessary to do foundational UX is antithetical to the assembly-line chunks of user behavior agile requires.</p><p>Focusing on production-level UX allows organizations to check the “UX” box without having to deal with the messiness that sometimes results when you hire people who are charged with asking questions that have never been asked—questions senior leaders may not know the answers to, or may not want to. The factory floor prefers interchangeable, replaceable parts.</p></div>
<div><p>Foundational UX is where the stuff that makes people really care about UX happens: the human insights, the collaborative exploration, the creative experimentation. For people joining the field, the disjunction between the dream and the reality can feel like a terrible bait and switch. Sold in school on UX as a noble and creative pursuit, they hit the job market to find roles where every chance for nobility and creativity has been carved out and cleaned away in the name of shipping product.</p><p>It would be fair to say the blame for the current state lies squarely at the doorstep of UX practitioners themselves, who have been slow to create the room for foundational UX by failing to tell a compelling story about the value of that work and build the necessary credibility to get it funded. If UX has failed to live up to its promise to deliver more than production-level value, maybe it was a bad promise in the first place. In other words, what if—just hear me out—what if we were all wrong?</p><p>Or UX’s current malaise could simply be the product of the collective midcareer burnout of its first generation of practitioners, who may have underestimated how slow and messy a grassroots revolution can be. The disgruntlement seems to go up the longer someone has been in the field: The more seasoned and experienced a UX person is, the more likely they are to be asking whether realizing user-centered values is even possible under capitalism. These are definitely questions worth asking and conversations worth having as a community.</p></div>
<div><p>What no one is saying, interestingly enough, is that UX is struggling because all of the juicy problems have been solved. Despite the accumulation of standards, best practices, and conventional wisdom that comes with any field growing up—not to mention the continual pressure from business to make UX practices simpler and more digestible—the messy complexity of humanity continues to challenge us around the edges. And the organizations looking for more than UX theater are still creating new opportunities there.</p><p>For those new to the field, it’s surely disconcerting to see its elders handwringing over its direction, like an airline pilot announcing that maybe Albuquerque isn’t the best destination for this flight after all. But it’s a sign of the field’s health that questions of its values and intentions are even being raised from within. An actual erosion of the field’s values would be marked by considerably less self-awareness.</p><p>The truth is that UX is now far too big to be considered a single community or even a single set of methods or practices. It used to sort of mean something about an organization that it even had a UX team. Now it can mean anything, or nothing at all. UX now means whatever organizations choose it to mean, for better or worse. For those still fighting the good fight for hearts and minds, influencing how that meaning gets defined is now the heart of the challenge.</p>
</div>
</article>


<hr>

<footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs.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.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.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.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.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.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>