{"id":912,"date":"2021-09-04T10:58:18","date_gmt":"2021-09-04T08:58:18","guid":{"rendered":"http:\/\/chlovis-old.localhost\/?post_type=project&p=912"},"modified":"2021-09-04T11:08:00","modified_gmt":"2021-09-04T09:08:00","slug":"new-york-times","status":"publish","type":"project","link":"http:\/\/chlovis-old.localhost\/projects\/new-york-times\/","title":{"rendered":"New York Times"},"content":{"rendered":"
\n
\n
\n
\n
\n

The New York Times’ Intranet<\/h1>\n
    \n
  • service design<\/li>\n
  • user experience<\/li>\n
  • ux design<\/li>\n <\/ul>\n

    Goals : <\/h2>\n
      \n
    • empower employees through the intranet<\/li>\n
    • onboarding easily new hires<\/li>\n
    • change their current stream of communication<\/li>\n
    • 150 hours of work<\/li>\n<\/ul>\n<\/div>\n <\/div>\n
      \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n<\/div>\n\n
      \n
      \n
      \n \n\n

      To align their new human resources vision, The Times wanted to rethink their intranet. Our mission was to identify useful features around internal tools, while making it useful for employees.<\/p>\n\n <\/div>\n <\/div>\n<\/div>\n\n

      \n
      \n
      \n \n\n

      Reflecting the new organization<\/h2>\n\n\n\n

      It took us some time to figure out how the intranet was organised today, and how it reflected the current organisation. Historically, the Newsroom was separated from the other teams. The Times wanted to change the communication flow, to increase communication between all teams.<\/strong>

      How to transform their current space radically and still make it feels natural for employees?<\/strong><\/p>\n\n <\/div>\n <\/div>\n<\/div>\n\n

      \n
      \n
      \n \n\n
      \"\"<\/figure>\n\n <\/div>\n <\/div>\n<\/div>\n\n
      \n
      \n
      \n \n\n

      A place for Empowerment<\/h2>\n\n\n\n

      One of the sub-challenges was to “empower employees” with this new intranet. 
      I put a lot of energy into that question.
      How can an intranet, from a company, really empower employees?<\/strong><\/p>\n\n\n\n

      Here are some of my suggestions: <\/p>\n\n\n\n

      • A Search tool, starting with its label itself : “How can we help ?” <\/li>
      • Categories highlighting the key issues for people, like health insurance questions, or “feeling stuck in your career?” questions. <\/li>
      • Days off you can benefit highlighted clearly<\/li>
      • Company’s position on diversity and inclusive writing as journalists<\/li><\/ul>\n\n\n\n

        Each categories would lead to Evergreen content to help employees with those daily struggles, or questions.
        Display those categories as a company means “those questions are okay, and yes, we can talk about it.”<\/strong><\/p>\n\n <\/div>\n <\/div>\n<\/div>\n\n

        \n
        \n
        \n \n\n
        \"\"<\/figure>\n\n <\/div>\n <\/div>\n<\/div>\n\n
        \n
        \n
        \n \n\n

        Easy Onboarding for new hires<\/h2>\n\n\n\n

        When entering a new workspace, everyone remember the moment you have to take care of getting your internal tools ready: <\/strong><\/p>\n\n\n\n

        • Email address<\/li>
        • internal authorisations,<\/li>
        • joining the Slack spaces,<\/li>
        • …all this stuff that leaves you out of the real company life if you don’t take care of it. <\/li><\/ul>\n\n\n\n

          With bigger companies comes longer process for this.<\/strong><\/p>\n\n\n\n

          For this new intranet, we came up with the “checklist” page, to keep track of your set-up. <\/p>\n\n <\/div>\n <\/div>\n<\/div>\n\n

          \n
          \n
          \n \n\n
          \"\"<\/figure>\n\n <\/div>\n <\/div>\n<\/div>\n\n
          \n
          \n
          \n \n\n
          \"\"<\/figure>\n\n <\/div>\n <\/div>\n<\/div>\n\n
          \n
          \n
          \n \n\n

          A customizable Dashboard<\/h2>\n\n\n\n

          The company built several tools for the employees, but not all of those tools are useful to everyone.
          That’s why we created a quick access system<\/strong>, tools that you can see all the time on your dashboard. <\/p>\n\n\n\n

          Employees can select useful ressources links or specific tools they use often. 
          Because we wanted something simple enough to be done in a few seconds, after a few rounds of iterations, we decided to go with the “switch” element for each link. <\/p>\n\n <\/div>\n <\/div>\n<\/div>\n\n

          \n
          \n
          \n \n
          \n
          \n
          \n
          \n \"\"\n <\/div>\n
          \n \"\"\n <\/div>\n
          \n \"\"\n <\/div>\n <\/div>\n
          \n \"Prev\"\n <\/div>\n
          \n \"Next\"\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n<\/div>\n\n
          \n
          \n
          \n \n\n
          \"\"<\/figure>\n\n <\/div>\n <\/div>\n<\/div>\n\n
          \n
          \n
          \n \n\n

          Intranet redesign is something I like a lot, for once it’s not about selling something, but rather to try to build something useful for people. <\/p>\n\n <\/div>\n <\/div>\n<\/div>","protected":false},"template":"","yoast_head":"\nNew York Times, case-study: How to make a useful intranet - Chlovis Lobre<\/title>\n<meta name=\"description\" content=\"The New York Times' current tools weren't reflecting their internal changes. We worked on service design opportunities to empower employees.\" \/>\n<meta name=\"robots\" content=\"noindex, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"New York Times, case-study: How to make a useful intranet - Chlovis Lobre\" \/>\n<meta property=\"og:description\" content=\"The New York Times' current tools weren't reflecting their internal changes. We worked on service design opportunities to empower employees.\" \/>\n<meta property=\"og:url\" content=\"http:\/\/chlovis-old.localhost\/projects\/new-york-times\/\" \/>\n<meta property=\"og:site_name\" content=\"Chlovis Lobre\" \/>\n<meta property=\"article:modified_time\" content=\"2021-09-04T09:08:00+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/chlovis-old.localhost\/wp-content\/uploads\/nyt_flows.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"http:\/\/chlovis-old.localhost\/projects\/new-york-times\/\",\"url\":\"http:\/\/chlovis-old.localhost\/projects\/new-york-times\/\",\"name\":\"New York Times, case-study: How to make a useful intranet - Chlovis Lobre\",\"isPartOf\":{\"@id\":\"http:\/\/chlovis-old.localhost\/#website\"},\"datePublished\":\"2021-09-04T08:58:18+00:00\",\"dateModified\":\"2021-09-04T09:08:00+00:00\",\"description\":\"The New York Times' current tools weren't reflecting their internal changes. We worked on service design opportunities to empower employees.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\/\/chlovis-old.localhost\/projects\/new-york-times\/\"]}]},{\"@type\":\"WebSite\",\"@id\":\"http:\/\/chlovis-old.localhost\/#website\",\"url\":\"http:\/\/chlovis-old.localhost\/\",\"name\":\"Chlovis Lobre\",\"description\":\"I do interaction design & ux consulting for video games, start-ups and agencies.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\/\/chlovis-old.localhost\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"New York Times, case-study: How to make a useful intranet - Chlovis Lobre","description":"The New York Times' current tools weren't reflecting their internal changes. We worked on service design opportunities to empower employees.","robots":{"index":"noindex","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"og_locale":"en_US","og_type":"article","og_title":"New York Times, case-study: How to make a useful intranet - Chlovis Lobre","og_description":"The New York Times' current tools weren't reflecting their internal changes. We worked on service design opportunities to empower employees.","og_url":"http:\/\/chlovis-old.localhost\/projects\/new-york-times\/","og_site_name":"Chlovis Lobre","article_modified_time":"2021-09-04T09:08:00+00:00","og_image":[{"url":"http:\/\/chlovis-old.localhost\/wp-content\/uploads\/nyt_flows.png"}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"http:\/\/chlovis-old.localhost\/projects\/new-york-times\/","url":"http:\/\/chlovis-old.localhost\/projects\/new-york-times\/","name":"New York Times, case-study: How to make a useful intranet - Chlovis Lobre","isPartOf":{"@id":"http:\/\/chlovis-old.localhost\/#website"},"datePublished":"2021-09-04T08:58:18+00:00","dateModified":"2021-09-04T09:08:00+00:00","description":"The New York Times' current tools weren't reflecting their internal changes. We worked on service design opportunities to empower employees.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/chlovis-old.localhost\/projects\/new-york-times\/"]}]},{"@type":"WebSite","@id":"http:\/\/chlovis-old.localhost\/#website","url":"http:\/\/chlovis-old.localhost\/","name":"Chlovis Lobre","description":"I do interaction design & ux consulting for video games, start-ups and agencies.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/chlovis-old.localhost\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"}]}},"acf":[],"_links":{"self":[{"href":"http:\/\/chlovis-old.localhost\/wp-json\/wp\/v2\/project\/912"}],"collection":[{"href":"http:\/\/chlovis-old.localhost\/wp-json\/wp\/v2\/project"}],"about":[{"href":"http:\/\/chlovis-old.localhost\/wp-json\/wp\/v2\/types\/project"}],"wp:attachment":[{"href":"http:\/\/chlovis-old.localhost\/wp-json\/wp\/v2\/media?parent=912"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}