3 jaren geleden · df9a5c5108
--- a/cache/2021/68f3b87ebf1ae01bccc75fc648ac9201/index.html
+++ b/cache/2021/68f3b87ebf1ae01bccc75fc648ac9201/index.html
@@ -0,0 +1,205 @@
 <!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>
  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>Data isn’t oil, so what is it? (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="#f0f0ea">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f0f0ea">
 <!-- 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://howtomeasureghosts.substack.com/p/data-isnt-oil-so-what-is-it">

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

 <article>
  <header>
    <h1>Data isn’t oil, so what is it?</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://howtomeasureghosts.substack.com/p/data-isnt-oil-so-what-is-it" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <p>In 2011, Stanford researchers Paul Thibodeau and Lera Boroditsky <a href="https://www.nationalgeographic.com/science/article/is-crime-a-virus-or-a-beast-how-metaphors-shape-our-thoughts-and-decisions">published research</a> that showed how the way we talk about crime changes our ideas about what to do about it. They asked two groups of students to read reports about crime in their area - one using a metaphor of crime as a ‘beast’ that was rampaging through the neighbourhood, and one describing crime as a ‘virus’ that had to be stopped. Their research showed that students shown the ‘virus’ metaphor were more likely to favour policy that looked at the root causes of crime, such as social deprivation, whilst students who read the ‘beast’ metaphor story favoured enforcement policies.</p>

 <p>In <a href="https://storythings.com">my day job</a>, we spend a lot of time thinking about the metaphors we use to help shape people’s understanding of complex issues, and hopefully drive change. In fact, I know about the study above from a podcast we produced a few years ago called <em><a href="https://diffusion.network/2019/06/02/episode-01-a-paintbrush-is-a-pump/">This Will Change Your Mind</a></em>, looking at how the ideas that shape public thinking are developed and adopted. In <a href="https://diffusion.network/2019/06/10/episode-02-not-actually-a-hole/">my favourite episode</a>, the hosts try and find out how the phrase ‘hole in the ozone layer’ emerged, a particularly successful climate metaphor that drove global efforts to cut CFC emissions.</p>

 <p>It’s an odd metaphor, as there isn’t really an ozone layer, and the hole wasn’t really a hole, but the metaphor caught on with scientists, policy makers and the public. One of the reasons for its success might have been the visceral image of a hole in the earth’s atmosphere, and the associations of breached defences that created. This was the era of early video games like Space Invaders and Missile Command, where the player had to defend the earth by stopping alien attacks raining down. I was a kid in the 80s, and the hole in the ozone layer felt as terrifying as these pixellated invaders.</p>

 <p><hr></p>

 <p>Back in the early 2000s, I was working at the BBC on a project to imagine what the organisation would do with our user’s personal data. At the time, there were only a few websites that asked you to create personal accounts, and most of the data we captured was relatively anonymous server logs. I developed a <a href="https://test.org.uk/2007/05/04/a-manifesto-for-data-literacy/">list of principles</a> that I thought should inform the BBC’s approach to managing user data, and commissioned a <a href="https://www.liveworkstudio.com">service design agency</a> to develop prototypes of what this might look like as products or services.</p>

 <p>I was then asked to present this to the BBC’s executive committee, and gave probably the worst presentation of my life. It didn’t help that I started the presentation by explaining that this work might be important in a ‘post licence fee world’, before being softly chided by then Director General Mark Thompson that this wasn’t the place to discuss that kind of idea.</p>

 <p>But more than that gaffe, I think the biggest problem was that I couldn’t really describe what personal data actually <em>was</em>. Not in a technical sense - the BBC ExCo in the mid-2000s wasn’t very technically savvy anyway - but as something that <em>mattered</em>, and was important to a vision of what public media could do in this new century. I had lots of fine statements about what we could do with data, and how it could bring value to our audiences, but the thing itself was immaterial, a poltergeist only visible through the things it moved.</p>

 <p>Over the next decade, the most dominant metaphor for personal data ended up being ‘<a href="https://www.economist.com/leaders/2017/05/06/the-worlds-most-valuable-resource-is-no-longer-oil-but-data">oil</a>’. As the platform giants of Facebook, Google, Amazon and Apple built empires of products and services that tracked our every activity, data has been discussed as a vast, untapped resource, ideal for extraction and processing into cold, hard cash.</p>

 <p>But in the last few years, there has been a backlash against this extractive metaphor. In 2018 Cory Doctorow described Facebook’s data as an empire of low quality ‘<a href="https://locusmag.com/2018/07/cory-doctorow-zucks-empire-of-oily-rags/">oily rags</a>’, recasting the metaphor to one of industrial waste, not liquid gold. In a <a href="https://twitter.com/DigitalEU/status/1390660489261330440">recent speech</a>, EU Vice President Margrethe Vestager tried to reposition data as a ‘reusable resource’, a more ecological metaphor that suggests ways of extracting value that doesn’t pollute the public sphere.</p>

 <p>All these metaphors imagine public data as a huge, passive, untapped resources - lakes of stuff that only has value when it is extracted and processed. But this framing completely removes the individual agency that created the stuff in the first place. Oil is formed by millions of years of compression and chemical transformation of algae and tiny marine animals (<a href="https://www.bbc.co.uk/bitesize/guides/z27thyc/revision/1">sorry, not dinosaurs</a>). Data is created in real time, as we click and swipe around the internet. The metaphor might work in an economic sense, but it fails to describe what data is as a material. It’s not oil, it’s <em>people</em>. </p>

 <p><hr></p>

 <p>At the moment the big platforms and governments are ramping up the battle over our personal data - <a href="https://whyisthisinteresting.substack.com/p/the-apple-att-edition?token=eyJ1c2VyX2lkIjoxNjMsInBvc3RfaWQiOjM0OTMxMjk4LCJfIjoiVGlXUkMiLCJpYXQiOjE2MjEwOTM3ODUsImV4cCI6MTYyMTA5NzM4NSwiaXNzIjoicHViLTcwMDAiLCJzdWIiOiJwb3N0LXJlYWN0aW9uIn0.2zQKhes6JmkNlPLp5YuQHWv5b-xBZw16zjTRtyohhck">who can collect it</a>, <a href="https://gdpr.eu">what they can do with it</a>, and <a href="https://mobile.twitter.com/markscott82/status/1393203850560032770">where they can send it</a>. But this is happening at a level far above our individual experience of data. The battle rages above us, like the missiles and aliens in the video games of my 80s youth.</p>

 <p>The discussions around data policy still feel like they are framing data as oil - as a vast, passive resource that either needs to be exploited or protected. But this data isn’t dead fish from millions of years ago - it’s the thoughts, emotions and behaviours of over a third of the world’s population, the largest record of human thought and activity ever collected. It’s not oil, it’s history. It’s people. It’s <em>us</em>.</p>

 <p>If you’ve been on the internet for a while - let’s say 5-10 years - you’ve probably felt the visceral kick of seeing someone or something in your data history that caused you pain. It could be Facebook’s ‘on this day’ feature sending you a memory of a traumatic event, or scrolling through your photo library to find a photo of a deceased relative or friend. Or it could be a moment of joy - the  online store where you bough a much loved item of clothing, or that perfect gift for a friend.</p>

 <p>After a year of lockdown, seeing reminders of life before the pandemic in our camera rolls and social media updates has felt especially melancholic. Groups of us cramming together in a bar or park to get into the shot, or hugging each other at a football game. That intimacy is what our personal data records, an intimacy that seems doubly ironic when it is played back to us, isolated in our homes, through the same devices we’ve relied on to connect us during the lockdown. </p>

 <p>This is not a passive archive - these are records of how we live now, and how people live in our memories. They can be recalled with a touch, and brought back to life, even if they are bittersweet memories. We need metaphors for data that capture the agency and visceral emotions that our personal data can generate. Metaphors that link it directly into our lives and relationships, that help us recognise that this is <em>us</em> - <em>we’re</em> the ones being traded and sold and stored and analysed and processed.</p>

 <p>Perhaps then we’d understand how we can handle this data in a more responsible way. A metaphor that puts our personal experience at the forefront will help us find out where to draw lines in how our lives are stored and processed, and to understand that the lines will need to be different for different people. I don’t know what the right metaphor is - memory and history are the concepts I’ve been mulling over, but they have already been used in computing in ways that blur and dull them.</p>

 <p>Maybe we should be very explicit, and refer to data as our <em>lives</em>. Imagine if a service had to ask you permission to ‘track your life’ or ‘share information about your life with other providers’. Already that feels grittier, more visceral, than just ‘data’.</p>

 <p>We urgently need to come up with metaphors like this, that bring the discussion over data down from the skies above us and locate it in the minutiae of our everyday lives. Because that, after all, is what this data actually is.</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.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> RSS</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>
    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>
--- a/cache/2021/68f3b87ebf1ae01bccc75fc648ac9201/index.md
+++ b/cache/2021/68f3b87ebf1ae01bccc75fc648ac9201/index.md
--- a/cache/2021/f5a7f2346b8c7317be12857b52321f52/index.html
+++ b/cache/2021/f5a7f2346b8c7317be12857b52321f52/index.html
@@ -0,0 +1,182 @@
 <!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>
  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="#f0f0ea">
 <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
 <meta name="theme-color" content="#f0f0ea">
 <!-- 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">

 <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> RSS</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>
    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>
--- a/cache/2021/f5a7f2346b8c7317be12857b52321f52/index.md
+++ b/cache/2021/f5a7f2346b8c7317be12857b52321f52/index.md
--- a/cache/2021/index.html
+++ b/cache/2021/index.html
@@ -67,6 +67,8 @@
      
        <li><a href="/david/cache/2021/5705e6d03ee8dd0ce21ba8467c7d6f73/" title="Accès à l’article dans le cache local : Bref, je suis inquiet">Bref, je suis inquiet</a> (<a href="https://n.survol.fr/n/bref-je-suis-inquiet" title="Accès à l’article original distant : Bref, je suis inquiet">original</a>)</li>
      
        <li><a href="/david/cache/2021/f5a7f2346b8c7317be12857b52321f52/" title="Accès à l’article dans le cache local : I helped pioneer UX design. What I see today disturbs me">I helped pioneer UX design. What I see today disturbs me</a> (<a href="https://www.fastcompany.com/90642462/i-helped-pioneer-ux-design-what-i-see-today-horrifies-me" title="Accès à l’article original distant : I helped pioneer UX design. What I see today disturbs me">original</a>)</li>
      
        <li><a href="/david/cache/2021/c8678419b1c96d90ea066a3f6f6e3479/" title="Accès à l’article dans le cache local : When Are We Back To Normal?">When Are We Back To Normal?</a> (<a href="https://inessential.com/2020/12/31/when_are_we_back_to_normal" title="Accès à l’article original distant : When Are We Back To Normal?">original</a>)</li>
      
        <li><a href="/david/cache/2021/60b5a14eec9d72fe274143aa3ccca32f/" title="Accès à l’article dans le cache local : avant le tremblement">avant le tremblement</a> (<a href="https://www.la-grange.net/2021/03/31/tremblement" title="Accès à l’article original distant : avant le tremblement">original</a>)</li>
@@ -377,6 +379,8 @@
      
        <li><a href="/david/cache/2021/eef2b3e3085a9b71cd7fe64f21fa0453/" title="Accès à l’article dans le cache local : Anxious feelings about optimisation through complexity">Anxious feelings about optimisation through complexity</a> (<a href="http://interconnected.org/home/2021/02/12/optimisation" title="Accès à l’article original distant : Anxious feelings about optimisation through complexity">original</a>)</li>
      
        <li><a href="/david/cache/2021/68f3b87ebf1ae01bccc75fc648ac9201/" title="Accès à l’article dans le cache local : Data isn’t oil, so what is it?">Data isn’t oil, so what is it?</a> (<a href="https://howtomeasureghosts.substack.com/p/data-isnt-oil-so-what-is-it" title="Accès à l’article original distant : Data isn’t oil, so what is it?">original</a>)</li>
      
        <li><a href="/david/cache/2021/9f3a8d345963dac24bef4df547fef72c/" title="Accès à l’article dans le cache local : Why light text on dark background is a bad idea">Why light text on dark background is a bad idea</a> (<a href="https://tatham.blog/2008/10/13/why-light-text-on-dark-background-is-a-bad-idea/" title="Accès à l’article original distant : Why light text on dark background is a bad idea">original</a>)</li>
      
        <li><a href="/david/cache/2021/5243221f38525040d87e7407b08e1ff5/" title="Accès à l’article dans le cache local : log : vol. 11, num. 19, mar. 30 mars 2021, vanuatu">log : vol. 11, num. 19, mar. 30 mars 2021, vanuatu</a> (<a href="http://shl.huld.re/~f6k/log/vol11/19-vanuatu.html" title="Accès à l’article original distant : log : vol. 11, num. 19, mar. 30 mars 2021, vanuatu">original</a>)</li>