<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Julien Chenat on Medium]]></title>
        <description><![CDATA[Stories by Julien Chenat on Medium]]></description>
        <link>https://medium.com/@tanek?source=rss-d459035fa9b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xJ8_AR0qWat_6Ve8CKbO7Q.jpeg</url>
            <title>Stories by Julien Chenat on Medium</title>
            <link>https://medium.com/@tanek?source=rss-d459035fa9b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:50:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tanek/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What I learned from visiting the best-known Product Companies in the Silicon Valley.]]></title>
            <link>https://medium.com/blablacar-design/what-i-learned-from-visiting-the-best-known-product-companies-in-the-silicon-valley-1faf250d0ce6?source=rss-d459035fa9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1faf250d0ce6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[silicon-valley]]></category>
            <dc:creator><![CDATA[Julien Chenat]]></dc:creator>
            <pubDate>Thu, 27 Oct 2016 09:15:40 GMT</pubDate>
            <atom:updated>2016-10-27T09:18:23.602Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BokgfUaVJDIe0Y0Zd8-LcA.jpeg" /></figure><p>Last May, I was lucky enough to have the opportunity to visit the Bay Area with some of my <a href="http://www.wired.co.uk/article/blablacar">BlaBlaCar</a> colleagues. The idea was to meet product company whose lead their market and share some “fail &amp; learn” on projects, organisation, or product. <br>Below you’ll find a quick synthesis of <strong>Product Designer’s interviews at Google, Facebook, Airbnb, LinkedIn, Adobe, SmartRecruiters</strong>… A big thanks to them for accepting the sharing session.</p><p>I was focused on 3 points:</p><ul><li>Organisation &amp; Methodology</li><li>User research</li><li>Consistency</li></ul><p>These are not small things. On the contrary, they are key for the growth of a design department.</p><h4>Stay focus.</h4><p>For each interview, my 1st question was: <strong>What’s a typical journey for a Product Designer at [<em>company</em>]?</strong> <br>And the answer was not UX oriented, very surprising and always the same:</p><blockquote>Meetings! <br>We’ve many meetings. Too many meetings. <br>We try to limit them. But..you know..by the way, it’s complicated because they are all useful…</blockquote><p>It’s interesting to observe this typical damage from a Product Company. <br>The desire is sharing as much as possible so that everyone else has the same level of information, that everyone understands the constraints of each, that everyone is warned when a part of the product evolves. <br>This means not only sharing with people who do the same job (for example, designers), but also sharing with people who work on the same projects (engineers, PM, etc.) and communicate results for the other teams. <br>And remember that all these companies operating in agile methods, which which certainly doesn’t help with the number of meetings!</p><p>To deal with this problem, <strong>every company has created their own rules</strong> and guidelines:</p><ul><li>Edit the settings in Google Calendar for 30 min meeting as default time. And not 1hour.</li><li>Block day without meetings (1 per week). The employee can choose to work at home or in the office. And progress on their projects without being disturbed.</li><li>Each meeting has a defined goal and a quick report.</li><li>Each week, an All-hands meeting with the whole company.</li></ul><p>You’re right. Nothing new. Nothing extraordinary. Nothing dedicated to UX Design. But we all know that’s it’s not a detail.</p><h4>Keep our agility.</h4><p>Most of the designers interviewed are integrated in a <br>multidisciplinary team. And not in a design team. This is something that massively impacts the way they work:</p><ul><li>They mostly work on one single project. They dig into the <em>why</em> (with the User Researcher, 1 per team), the <em>what</em> (with the Product Manager) and the <em>How</em> (with content designer, engineers, etc.)</li><li>As they stay focused on a single project, they are working very deeply (with a lot of iterations), but also on the final “deliverable” (with a very high fidelity prototype, similar to the reality).</li><li>Like the rest of the team, Designers work in <em>sprint</em> (often 2 weeks) and are in daily contact with the engineering team.</li><li>Not to be too tight on <em>delivery</em>, they keep 2 sprints ahead of the rest of the team.</li><li><a href="https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas/dp/150112174X">Sprint’s Google Venture book</a> is the bible of Silicon Valley right now. Adobe’s team has adapted the method in the following way: <br>1st week: Sprint Planning (Monday) → User Test (Friday)<br>2nd week: Iterate according User Test → Review (Friday)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O7Izjqw3Io4TRkGfaS2IxQ.jpeg" /></figure><h4>Share guidelines for consistency.</h4><p>At BlaBlaCar, we’re already <a href="https://medium.com/blablacar-design/stop-designing-interfaces-start-designing-experiences-d82def0b802c#.xscia182y">obsessed with consistency</a>. And it’s only the beginning. But we’re still far from the Bay Area:</p><ul><li>Every company has a dedicated team of designers who work on product guidelines.</li><li>Personally, I really like the name set up by LinkedIn: The Pattern Team.</li><li>By the way, you can also read this article on <a href="https://medium.com/@hellostanley/design-doesnt-scale-4d81e12cbc3e#.lcntz3eqe">Spotify</a> and how they deal with consistency.</li></ul><p>On this topic, each company has his own tips for sharing consistency:</p><ul><li>With Airbnb, the guidelines are available to all, and on Github so that designers and developers can make specific demands on each component.</li><li>Facebook has developed a Sketch Plugin for every designer uses the same library (a kind of custom Craft Plugin).</li><li>LinkedIn simply share a large file with all assets.</li></ul><h4>Share by reviewing.</h4><p>What is certain is that the consistency is obtained by sharing with peers.</p><ul><li>For example, each of the 100 designers at LinkedIn has a buddy in the famous Pattern Team, who attends each review, with whom they can discuss all projects, and validate designs.</li><li>Finally, there are quite a few workshops or brainstorms organized (with 4 designers max at each session).</li><li>The review is done with all members involved in the project (engineers, PM, stakeholders, …)</li><li>No review with all the other designers. It’s not a scalable solution. That’s why the “Pattern Team” exists.</li><li>On each project, there are 3 reviews: Beginning (project scope, problem solving), Middle (1st screens, different iterations), end of the design phases (high-fidelity prototype).</li></ul><h4>It doesn’t matter what tools you use.</h4><p>Finally, through all these interviews, what pleases me most is that tools and software were discussed very briefly. It does not represent the bulk of the work of a designer.</p><ul><li>They all start to paper and quickly switch to <a href="https://www.sketchapp.com/">Sketch</a> (except the Adobe’s team).</li><li>The wireframing (digital) phase is less used.</li><li>With <a href="https://redpen.io/">redpen.io</a> , they can comment and add some feedback on mockups.</li><li><a href="http://invisionapp.com/">Invision</a> or <a href="https://marvelapp.com/">Marvel</a> is the 1st step of prototyping, after they finalize interactions with Origami, among others.</li><li>Even if they work with agile methods, they do not use a task tracking tools like <a href="https://atlassian.com/software/jira">Jira</a>.</li><li>Except <a href="https://lookback.io/">Lookback</a>, no tool is unanimous for the User Research. The best way to find insight is calling or skype. By the way, User research is built empirically. There is no magic recipe. This is on a case-by-case basis.</li><li>With Lookback, you can directly sharing the passages of videos relevant to the team to make a clear summary. Because it’s essential to involve everyone working on this project.</li></ul><p>Necessarily all this points mentioned lead a virtuous circle. Since remaining focus, you can get ahead, so be proactive and able to impact the next projects of the roadmap and prioritizing the real problems to solve.</p><p>By exchanging with all these designers, I was really impressed with their maturity level, their seniority.</p><p>What makes besides their strengths is their mindset, very positive which embeds the entire team behind his ideas. This skill of facilitator is essential.</p><p>Nevertheless, through these exchanges, I mostly learned that nothing is insurmountable. We are already aware of many things. Everyone can, in line with their own size and scale, reproduce these working methods that have been proven in Silicon Valley.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nozkPcxUX4HnpcvDhoMDsQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PjuhnHej1pEsVszx9FhIjg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zKo-tYCpd7LUnoA7xEPDwA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wfT1a3BGVy1xcLF0cnRtZQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QPbvpYDhO9gJ439zU30FfA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*13yNyzOzV93C0E8ZX4D8wg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hP6a2WODrYGHKb52E9Sh-A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yOjtWR8p5YUVqZCC-t2HjA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5_zpgBDhSLnwKDcyMxOx8g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FeWjv8CVKofhQ_nrH0WnbQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GitiPA430tivFu3HSNp0gA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GsgSy31kbBJnqGNABZZ4kQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HaexZiGLgc575IjxJzclbA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c45KUHzt1THrAeJM9I1huw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8m5-K5FNXGAcPYNPKl1rag.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZLbAH3BGKtoflDA5Rfoow.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*444IxaCgLggzhOwqesK2lA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xl8DfTjuR59cQ_ybkjFCOg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MU0w1pKj9GqfVo97Wt8rxQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dTzZvde-9nq8pHTLPJ5UDw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1faf250d0ce6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blablacar-design/what-i-learned-from-visiting-the-best-known-product-companies-in-the-silicon-valley-1faf250d0ce6">What I learned from visiting the best-known Product Companies in the Silicon Valley.</a> was originally published in <a href="https://medium.com/blablacar-design">BlaBlaCar Product &amp; Experience</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Disruptors Release Party]]></title>
            <link>https://medium.com/blablacar-design/design-disruptors-release-party-54eebac544d3?source=rss-d459035fa9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/54eebac544d3</guid>
            <category><![CDATA[invision]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Julien Chenat]]></dc:creator>
            <pubDate>Fri, 05 Aug 2016 14:10:29 GMT</pubDate>
            <atom:updated>2016-08-05T14:10:29.448Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hur3heITFTjydBPJvStApA.jpeg" /></figure><p>Last Thursday (21 July), <a href="http://www.wired.co.uk/article/blablacar">BlaBlaCar</a> was pleased to present the French premiere of <a href="https://www.designdisruptors.com/">Design Disruptors</a>, a documentary produced by <a href="https://www.invisionapp.com/">Invision</a>.<br>Despite the summer heat, the room was packed for the event — and just for that, we want to say thank you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ny9gnlKd1_V7NW9d_m5KxA.jpeg" /><figcaption>Introductory speech from Frédéric Mazzella (BlaBlaCar’s founder)</figcaption></figure><h4>The film</h4><p>It’s difficult to summarize the film without spoiling it for those who have not yet seen it. At BlaBlaCar, opinions are divided. To give a short-cut version of a movie review, I would say: <strong>the film dragged a bit at times, but still provides a good dose of positive vibes.</strong></p><p>In any case, if you are new to design and if working all day on one single product seems weird, then this film will give you a good first glimpse into the field. And besides, the film is a beautiful visual experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QV6tGSGCDIPaHnsxlmmPEA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*26lp48ypJ2lkvNyOzDqheg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D0KwxhlGpPT1Ykaj9MYoYQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lIPRoftEWOR3u675ouKLog.jpeg" /></figure><h4>Talks</h4><p>Following the documentary, three members of our Design Team explained what it means to them to be a Product Designer.</p><ul><li><strong>User Research</strong>. <br>Carolyn opened the discussion by explaining how user research could provide valuable and actionable insights that can impact the product roadmap.</li><li><strong>Iteration</strong>. <br>Charly used the example of ID verification to illustrate the point that a product is not built without iteration. A Designer must be close to the data and understand what is not working in order continuously improve.</li><li><strong>Consistency &amp; Simplicity</strong>. <br>Nicolas closed the evening by detailing our design-process. The idea was to emphasize key concepts for a growing team: consistency, simplicity &amp; scalability. By the way, I invite you to <a href="https://medium.com/blablacar-design/stop-designing-interfaces-start-designing-experiences-d82def0b802c#.lrcu5jc2s">read his article about it</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8j-qXDWvRDoIYEpNFsY0Xg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c2EYaaTuagc5eKYiKxR3oA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cHVBGs88MyY6dL6TEyuuFQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AsYdizwJ_jNU0Ul40B6Z6g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YLIAenMg3Kb0mPsSSm64kQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wTnLnlnuGBTj_xe6IvK0Yw.jpeg" /></figure><h4>And to wrap it all up: Pizzas, Beers &amp; you.</h4><p>For this event, we were looking forward, just like you, to enjoying the film. But in the end, the highlight of the evening was actually the discussions we were able to have by getting everyone together. It was particularly great to meet so many passionate and fascinating people. So once again, we really enjoyed the evening — thanks to those who attended</p><p>We feel lucky to be part of such a community and think that we should take advantage of it more often. We’re ready to start again and are already thinking about our next party. Your ideas for topics or guest speakers are welcome!</p><p>Should we plan to meet again in September?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xh3qOyc59oS9RvzAMCFstQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d5cJJ1CeXslc8jvsvjfKxQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXngMNXvIPaFLkFtvFhJoA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JCI4dP8y3a28Q2kRPh4HbA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0E5uWE1IjkK36cUsLqlZA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4OdADD61bE0kC39vHJjmOw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s-QA3yd5D-BC1EWDX0IZDA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8uTSuEOdJ3WWCLJPmk6IRA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5FNirbJiiHGaNEu6PrUdSg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vv2leMWcsk50d8JeSmehCg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8t4496grCcBdHKBc7sAAgA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ol6luOpOhOkCUB9tpRIRdA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3LE_eGWFs337RB7TJCwg_g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xn40MxQ9vLUdP_eM6J9DUQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jpbb0lzo8biDZbDydZk4pg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dnPJQEEVVVMZL21g_2Cdig.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pnf_o1UIS6BUBvklQh6uAQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54eebac544d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blablacar-design/design-disruptors-release-party-54eebac544d3">Design Disruptors Release Party</a> was originally published in <a href="https://medium.com/blablacar-design">BlaBlaCar Product &amp; Experience</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to implement User Feedback Database?]]></title>
            <link>https://medium.com/blablacar-design/how-to-implement-user-feedback-database-52f35d12f5c2?source=rss-d459035fa9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/52f35d12f5c2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Julien Chenat]]></dc:creator>
            <pubDate>Fri, 13 May 2016 08:51:27 GMT</pubDate>
            <atom:updated>2016-05-13T08:51:27.987Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tibdK778X6duM3qmDb0KBg.jpeg" /></figure><p>In my <a href="https://medium.com/blablacar-design/developing-user-research-within-a-startup-be57548e22f6#.d7xrhju32">previous article</a>, I wrote about user research and more precisely about user testing. As I said, at Blablacar, automation &amp; scalability are our key metrics. <br>In addition to this approach, we are developing a methodology to better use what we already have : user feedback.</p><p>Of course, we can’t compare with user-testing, because these are declarative inputs and not behavioral ones. Nevertheless, the insights can be precious.</p><p>We are lucky with our community because they often comment on GooglePlay or the AppStore and they have frequent contact with our Member Relations Team.</p><p>But today, we don’t really use them. That’s why we are trying to implement a user feedback database which can help us to track, measure and solve the problems.</p><h4>How?</h4><p>When a Member Relations Agent is contacted by a member, the agent can <strong>complete a Google form </strong>with :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1g8r05JFwyzA6yqcLUs51Q.png" /></figure><ul><li>The content of the ticket</li><li>The type of user (Driver, Passenger, Not a member)</li><li>The country of the member</li><li>The devices and the platform used</li></ul><p>All the answers are forwarded automatically into a spreadsheet. <br>The <strong>2nd step is to make sense of the raw data</strong>. And we have only 2 items to fill in:</p><ul><li>The problem.</li><li>The team who has to deal with the problem.</li></ul><p>Yes. The core idea of this spreadsheet is to be <strong>problem-oriented</strong>. <br>Consequently, when users submit ideas of solutions or propose new features, we try to understand the problem or need it would be solving, rather than simply taking the idea directly. This helps us to be more creative when looking for new solutions, and to not be limited by the ideas already proposed.</p><p>At this time, we’ve defined a closed list of 35 problems.</p><p>Then, with 2 or 3 simple formulas, we <strong>created a dashboard for the global view </strong>with <strong>:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e2OBq5gGL6RADyHKYXq9Dw.png" /></figure><ul><li>Top 10 problems,</li><li>Distribution of problems by devices, country, kind of users, …</li></ul><p>It’s a big picture and it’s only quantitative data. So we have to<strong> zoom in each problem</strong>. After selecting the problem, we can watch :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WeSU3dT-VyifmQdCLzlGxA.png" /></figure><ul><li>the same previous dashboard (but filtered by this problem).</li><li>Sentences written by our users (and the translation).</li></ul><h4>What to retain?</h4><ul><li>Use. Use. Use. At the moment, the database works. But consulting this document before starting a project is not yet a reflex.</li><li>Looking at graphs of quantitative data is sexier than reading sentences. But in my opinion, a user feedback database (even if it’s a database) and every user research document have to showcase qualitative information.<br>Sometimes the words of our users can speak louder and be more memorable than graphs.</li></ul><h4>And what comes next?</h4><ul><li>Trying to insert this database at the beginning of our design workflow. Therefore, communicating on it. Or, deleting this database if it’s useless.</li><li>Also adding the feedback of the user tests (With <a href="https://medium.com/@tsharon/the-atomic-unit-of-a-research-insight-7bf13ec8fabe#.u1awmqpxc">nuggets Method</a>?)</li></ul><p>As with the user testing article, the goal of this article is to share with you a work in progress tool in an agile environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52f35d12f5c2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blablacar-design/how-to-implement-user-feedback-database-52f35d12f5c2">How to implement User Feedback Database?</a> was originally published in <a href="https://medium.com/blablacar-design">BlaBlaCar Product &amp; Experience</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developing User research within a startup.]]></title>
            <link>https://medium.com/blablacar-design/developing-user-research-within-a-startup-be57548e22f6?source=rss-d459035fa9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/be57548e22f6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Julien Chenat]]></dc:creator>
            <pubDate>Thu, 21 Apr 2016 09:27:37 GMT</pubDate>
            <atom:updated>2016-04-21T09:36:21.053Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*5fSi4E5wsKDaEl6aXSIefQ.jpeg" /></figure><p>At <a href="http://www.wired.co.uk/magazine/archive/2015/05/features/blablacar">BlablaCar</a>, the UX Team is still pretty young but it has a rapid growth. In fact, within a year, we went from only 1 designer to a team of 9. <br>It is a great and very stimulating work dynamic. Having a big and organized team, allows us to improve our methodology and put things into perspective. While previously the designer single handedly focused on emergencies.</p><p>For a designer, taking a global view means to focus more on User Research. As it is such a vast topic, we’ve decided to first concentrate on user testing (a kind of MVP), and more precisely on <strong>how we can automate it</strong>.</p><p>Indeed, it is no secret that user testing is expensive in terms of time and energy. In fact, in 2015 “only” ten users were invited to our tests making the objective for the next year very clear: <br><strong>How can we meet around 300 users in the most effective way in order to test prototypes, current flow or any ongoing projects ?</strong></p><p>Sticking to the intense rhythm is the key to automation, meaning a huge simplification of the process and killing heavy methodology (sorry for the purists):</p><ul><li>One session per week. Every Thursday, 6 members of our community are invited in a very similar approach to Google Venture.</li><li>No criteria in our recruiting panel (or almost). We have only 2 groups : members &amp; non-members.</li><li>Simple scenarios. Only 1 sentence to describe the context. After which we observe the behavior of the testers during their task. In the end, we can ask a few questions to deal with a more in depth understanding of their experience.</li><li>Light technical set-up. As 95% of our tests are on mobile, we use <a href="https://lookback.io/">Lookback</a> to capture screens, faces, voices and the touches on a device. By the way, our meeting rooms are equipped with <a href="https://www.lifesize.com/">Lifesize</a> which makes everything easy to broadcast. But you can also use Hangout or Skype, which have the advantage of being 100% free.</li><li>Restitution of the collected information in the form of a table. 1 row per KPI &amp; 1 column per participant.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7nmkBrcHk6LMhHdfQg4tSw.png" /></figure><ul><li>On every Friday, share via mail the previous table, some quotes, only <br>raw data without any advice or recommendation.</li><li>Weekly iteration of our process. Each week’s progress was maximized compared to the last. And I hope next Thursday, we will be even better.</li></ul><h4>What are the 1st lessons we have learned ?</h4><ul><li>Even with bias, one test is always more powerful than none.</li><li>The rhythm is THE lever.</li><li>If each project is tested, lots of superfluous conversations are avoided.</li><li>With this system, we can iterate very quickly each week.</li></ul><h4>What’s next ?</h4><p>We’ve invested in quantity, rhythm &amp; frequency. Now, it’s time to improve the quality. Here, some tracks :</p><ul><li>Optimize non-members recruiting.</li><li>Define the goal of each test more carefully.</li><li>Improve internal communication.</li><li>Compile all feedback within a database. Remember not to forget precious insights which are not directly linked to the topics tested.</li><li>Avoid solely testing in our headquarters in Paris by coming in contact with users from various countries where BlablaCar is implanted ( India, Brasil, Turkey,… ).</li></ul><p>I hope to come back soon with fresh news, simplified processes and enriching insights.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be57548e22f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blablacar-design/developing-user-research-within-a-startup-be57548e22f6">Developing User research within a startup.</a> was originally published in <a href="https://medium.com/blablacar-design">BlaBlaCar Product &amp; Experience</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clap de fin.]]></title>
            <link>https://medium.com/@tanek/clap-de-fin-2ea2ef1f31b2?source=rss-d459035fa9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ea2ef1f31b2</guid>
            <dc:creator><![CDATA[Julien Chenat]]></dc:creator>
            <pubDate>Wed, 22 Oct 2014 12:49:14 GMT</pubDate>
            <atom:updated>2014-10-28T10:05:27.842Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vnBerPb-S44GUKuHVeprZQ.jpeg" /></figure><h4>Retour sur 3 ans en tant qu’UX Designer chez l’annonceur.</h4><p>Voilà maintenant plus de 3 ans que je travaille chez Viadeo, en tant qu’Interaction Designer, dans le pôle UX.</p><p>J’estime avoir beaucoup de chance de faire partie des premières “vagues” d’UX Designer et j’ai d’autant plus de chance d’avoir trouvé une place rare chez l’annonceur.</p><p>Mais faire partie des premiers signifie aussi essuyer les plâtres en commettant quelques bourdes.<br>Petit moment d’introspection en vous révélant mon top 5 des erreurs commises (que j’espère ne plus refaire).</p><h3>1/ Tu n’iras pas plus vite que la musique</h3><p>Ton CDI fraichement signé, plein de nouveaux collègues te tombent dessus, impatients, te semble-t-il, que vous attaquiez ensemble de nouveaux projets.<br>Tu pars donc bille en tête sur les nouveaux sujets. Tout est neuf, tu adores.</p><p>Puis les mois passent. Les projets s’enchainent. Et tu as l’impression qu’en voulant tirer sur plusieurs fils en même temps, la pelote de laine s’est encore plus emmêlée.</p><p>Tu ne prends pas le temps de te poser. Tu ne prends pas le temps de regarder les stats globales. Tu ne prends pas le temps de faire un audit global de l’existant. Et encore moins d’organiser des tests-utilisateurs<br>(et je ne vous parle pas des personas !)</p><p>Tu raisonnes fonctionnalité par fonctionnalité, avec aucune vision d’ensemble.<br>Au final, les problèmes transverses persistent. Certes, l’interface s’améliore. Mais pas l’expérience utilisateur.<br>Toute cette phase de recherche utilisateur est passée à la trappe.<br>Dommage, c’est la base de ton métier.</p><p><strong>La prochaine fois, tu poseras les fondations avant de t’intéresser à la couleur de la moquette.</strong></p><h3>2/ Tu feras preuve d’humilité</h3><p>AH ! La puissance du regard neuf !<br>“ Mais ?! Comment ont-ils pu faire quelque chose d’aussi horrible ! Pourquoi n’ont-ils pas pensé à ça ?! Enfin ! ”</p><p>Et bien, si. Ils y avaient pensé. Et bien si, ils avaient essayé de le faire. Mais il y a toujours des aléas au projet, toujours un historique.</p><p>Mais toi, nouvel arrivant, tu ne comprends pas. Tu en rigoles, tu prends même un petit ton prétentieux. Au risque de blesser et de te mettre à dos les équipes en place.</p><p>Car oui, dans une grosse structure les torts sont partagés, mais les critiques sont toujours prises personnellement.</p><p><strong>La prochaine fois, tu sauras que les idées ont déjà été proposées et qu’au lieu de critiquer la réalisation, tu dois contribuer au renouvellement de cette réalisation.<br>Parce que oui, tu ne dois pas dire “ils” mais “nous”.</strong></p><h3>3/ Tu oublieras tes idées reçues</h3><p>Un beau matin, tu es appelé dans une réunion. On demande ton avis d’expert.</p><p>Tu viens d’arriver, mais étant donné que tu as déjà bossé dans des agences avant, sur plein de projets, c’est toi l’expert.<br>On te pose des questions sur l’interface.<br>Ni une ni deux, tu te bases sur ton vécu, ton expérience.</p><p>Tel un wannabe UX, tu débarques avec tes idées reçues.<br>Et tu commences à dire : “Nan mais ça, je l’ai déjà fait, les gens comprennent très bien. Tous les sites font ça aujourd’hui”.</p><p>Sauf qu’en vrai, chaque contexte est différent. Les utilisateurs aussi.<br>Tu ne peux pas théoriser, tu ne peux pas généraliser.<br>Il faut tester. Vérifier tes intuitions. Et apprendre de tes utilisateurs.</p><p><strong>La seule expertise que tu aies, c’est la connaissance des méthodes de Design. Tu es capable d’expliquer ce qu’est l’expérience utilisateur.<br>C’est ton rôle. Tu dois être dans la pédagogie pour que tes collègues, tes managers, et toutes les équipes adoptent cette façon de concevoir et en oublient leurs idées reçues.</strong></p><h3>4/ Le wireframe n’est pas LA solution</h3><p>À la fin de chaque réunion de lancement de projet, tu es super motivé. Tu t’empresses te courir dans l’openspace pour te jeter sur ton ordi.<br>Car oui, forcément, tu aimes faire des wireframes.<br>Tu aimes tellement ça que tes wireframes, c’est du pixel perfect. Quitte à empiéter sur le travail du DA.</p><p>D’ailleurs, si tu devais expliquer ton travail, tu dirais qu’il est fait à 50% de conception (wireframes) et 50% de tests utilisateur.</p><p>FAUX.</p><p>(Du moins chez l’annonceur) on est plus proche de 25% de conception, 25% de tests, et 50% de facilitation.</p><p><strong>Oui, tu as un travail de support, où tu dois catalyser et stimuler les idées, optimiser la communication entre les différents pôles, avec des livrables adaptés, tout en restant pédagogique.</strong></p><p>Qui t’as parlé de faire du wireframe ? Va plutôt coller des post-it.</p><h3>5 / Tu seras positif</h3><p>Si on reprend la définition, on est d’accord que l’UX Designer doit répondre à un problème donné ? Il doit donc apporter des solutions.</p><p>Mais comment veux-tu apporter des solutions et que les équipes y adhérent si tu dénigres la stratégie produit (sans proposer d’alternative) ? Si au lieu de remettre en question les choix de tes prédécesseurs, tu privilégies un ton accusateur ? Si t’essayes de te dédouaner à chaque mise en ligne en déclarant “ils ne m’ont pas écouté” ? Ou encore si tu préfères rester seul derrière ton ordi, plutôt que d’organiser des workshops ?</p><p>Tu dois tirer les projets vers le haut. Tu dois être moteur.<br>Encore une fois, ce n’est pas toi contre le reste du monde.</p><p><em>Comme vous pouvez le constater, au delà du savoir-faire acquis, c’est surtout au niveau du savoir-être que j’ai pris ma plus grande claque.</em></p><p><em>Alors oui, j’ai forcé le trait. Mais nous sommes trop nombreux à commettre une ou plusieurs de ces erreurs.<br>L’idée de cet article est de réellement insister sur des éléments qu’on ne voit pas assez dans les livres ou les conférences, et qui pourtant font partie de notre quotidien.<br>Ces éléments qui pourtant nous semblent logiques, faits de bon sens et que tout le monde pense éviter.</em></p><p><em>D’un point du vu perso, je file vers de nouveaux horizons, en conservant un poste d’UX, avec davantage de contenu et plus orienté Produit.<br>Et je souhaite bien sûr une belle réussite à l’équipe en place chez Viadeo.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ea2ef1f31b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Comment expliquer, à sa mère, son métier d’UX Designer ?]]></title>
            <link>https://medium.com/@tanek/comment-expliquer-a-sa-mere-son-metier-dux-designer-cf8171377b36?source=rss-d459035fa9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf8171377b36</guid>
            <dc:creator><![CDATA[Julien Chenat]]></dc:creator>
            <pubDate>Fri, 24 Jan 2014 15:07:10 GMT</pubDate>
            <atom:updated>2014-01-27T14:45:26.647Z</atom:updated>
            <content:encoded><![CDATA[<h4>En fait, c’est pas si simple.</h4><p><em>(Extrait d’une conversation lors d’un repas de famille)</em></p><h4>UX Designer ?!?<br>Mais tu ne m’avais pas dit Architecte de l’informatique ?</h4><p>Architecte de l’information, Maman. De l’information !<br>Bon déjà t’as retenu ça, c’est bien. Mais aujourd’hui, l’intitulé de mon poste, c’est UX Designer.</p><h4>Mais … ?</h4><p>Oui en gros, UX Designer, c’est un peu le terme à la mode. C’est plus court. Plus vendeur. Plus Marketing. Mais un peu faux.<br>Si tu veux, sur le papier, UX Designer c’est comme Architecte de l’information et comme Ergonome…</p><h4>Ah oui, Ergonome, je m’en souviens, tu m’en avais déjà parlé !</h4><p>Après dans la vraie vie, c’est différent. Chacun a ses petites particularités.<br>Si tu lis des blogs spécialisés, tu comprendras qu’il y a même plein d’autres dénominations.</p><p>Si je veux faire simple, je te dirai que pour être Ergonome, il faut un diplôme d’Ergonomie. C’est une science qui te permet de bosser dans n’importe quel secteur d’activité. Que ce soit pour les sites web, pour des postes de travail, pour des chaises, etc. L’intérêt est de valider que ton site, ton objet, ton produit est utilisable et facile à utiliser par l’utilisateur.</p><p>L’architecte de l’information, quant à lui, travaille avec du contenu (texte, visuel, vidéo, ...). Il le classe, le range, le positionne pour que l’utilisateur trouve facilement ce dont il a besoin.</p><h4>Ah. Et le X Designer ?</h4><p>UX Designer, tu veux dire ? Oui, alors petite définition. Commençons par le plus facile. L‘intitulé “ UX Designer” est d’abord composé du mot <strong>Designer</strong>.<br>Beaucoup de gens te diront qu’en France, on emploie mal ce mot. Que le design, c’est pas seulement le côté esthétique.<br>Ils te citeront même Steve Jobs (le fondateur d’Apple, oui Macintosh si tu préfères) :</p><blockquote>“ Le design, ce n’est pas seulement l’apparence et le style. Le design, c’est comment ça marche. ”</blockquote><p>Prenons l’exemple d’une maison. Et bien l’UX Designer serait l’<strong>architecte</strong>. C’est lui qui fait les plans pour que ça réponde à ton budget, à tes attentes (une cuisine américaine et les chambres à l’étage), aux contraintes (Normes antisismiques etc.)</p><p>De mon côté, je ne vais pas te livrer des plans de maison, mais des <strong>wireframes</strong> (entre autre).<br>Les wireframes, c’est des maquettes moches, toutes grises.</p><p>Et vu que je travaille en binôme avec un graphiste (qui a aussi plein de jolis noms comme Directeur Artistique, Visual Designer, Webdesigner, etc.), il reprend les wireframes mais en leur donnant vie. C’est à dire qu’il rajoute la couche esthétique en respectant une charte graphique.<br>Si on reprend la comparaison avec la maison, c’est un peu notre Architecte d’intérieur.</p><h4>Mais vous êtes 2 à faire ça ?</h4><p>Oui. Après comme dans tous domaines, il y a des gens très doués capables de faire les 2. Et comme dans tous domaines se professionnalisant, il y a aussi des structures qui ne peuvent pas se permettre d’avoir 2 bouches à nourrir.</p><h4>Et du coup, UX, ça veut dire quoi ?</h4><p>Ah oui, effectivement, j’oubliais le plus important, mais aussi le plus délicat à expliquer.</p><p>Le “UX” de UX Designer signifie “User Experience”. Donc l’<strong>Expérience Utilisateur</strong> en français dans le texte.</p><p>Mon travail consiste donc à toujours penser à l’utilisateur. En le mettant au centre de notre réflexion. En se focalisant sur ce qu’il voudrait faire, sur la façon dont il le fait, sur son ressenti. Et c’est pour ça que l’on parle d’<strong>expérience</strong>. Il faut prendre en compte cette <strong>couche émotionnelle</strong>.</p><h4>Ouais, enfin quand je vais sur LeBonCoin, il y a pas de blabla, de fioritures et toute ton histoire d’émotions !</h4><p>Bon ok, j’avoue que c’est très conceptuel et théorique. Sauf que dans la vraie vie, si tu retournes tous les jours sur leboncoin, c’est parce que ton expérience a été positive. Tu es dans la cible. Ils ont adapté le site pour toi.<br>Regarde par exemple, t’as pas besoin de te créer de compte, c’est simple. C’est pas beau mais le formulaire pour poster une annonce, est super basique, tu ne peux pas te tromper. Donc tu ne t’énerves pas, donc tu trouves le site pratique, donc tu l’utilises.</p><p>Mais l’expérience, c’est aussi une notion transverse qui ne se limite pas qu’à l’interface, qu’au site Web.<br>Sur le bon coin, ton expérience va jusqu’à la rencontre avec le vendeur. Si celle-ci est bonne, tu auras l’impression d’avoir fait une affaire, tu recommanderas le site. Si celle-ci se passe mal et que tu contactes leur service clients, ils peuvent te faire une ristourne, être agréable avec toi, pour que tu sois au final, satisfaite du service.</p><h4>Ok, mais c’est toi qui fait tout ça ?</h4><p>Non, et c’est pour ça que j’aime pas l’intitulé d’UX Designer.<br>Car une seule personne ne peut pas être garante de toute l’expérience d’un site, d’un produit. C’est tous les employés qui doivent y contribuer, que ce soit le développeur, le chef de projet, le responsable SAV, le livreur, etc.</p><p>L’UX Designer a un rôle pédagogique, il doit transmettre la bonne parole pour que tous les employés se disent que le plus important, c’est l’<strong>utilisateur</strong>.</p><h4>Mais comment vous faîtes pour vous mettre d’accord sur ce que pense et fait l’utilisateur ?</h4><p>Merci pour la transition, Maman. En gros, mon métier est fait de 2 phases :</p><p>La 1ère, c’est celle qu’on vient de voir, c’est la phase de Design, de <strong>Conception</strong>. Avec les wireframes, tout ça, tu t’en souviens ? Bon y a tout plein de choses, dans cette phase, comme des brainstorms, des parcours-utilisateurs, mais on verra ça plus tard hein.</p><p>Et bien la 2nde, c’est la phase de tests. De <strong>tests-utilisateurs</strong> pour vérifier qu’on a bien fait notre travail dans la 1ère phase. Si ce n’est pas le cas, on recommence la 1ère. Etc. Jusqu’à ce que ce soit bon. C’est ce qu’on appelle une <strong>méthode itérative</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OwL_Pr2ildQEDepg87Kq-g.jpeg" /></figure><p>Bref, durant cette phase de tests, nous faisons venir des vrais gens, des vrais utilisateurs pour leur montrer notre site. Et on observe ce qu’ils pensent, ce qu’ils font, et comment ils le font.<br>Je vais pas rentrer dans les détails, mais ils y a plusieurs méthodes pour cela. D’ailleurs, on fait parfois des tests avec de l’<strong>eye-tracking</strong>. (En français, on appelle ça Oculométrie, prends note, c’est bon pour le scrabble). Pour simplifier, c’est une machine avec des capteurs qui suit le mouvement de tes yeux. Et on peut vérifier si les éléments les plus importants sont bien visualisés.<br>C’est parfois très surprenant. Car même si on pense à l’utilisateur, on n’est pas l’utilisateur.</p><p>Voilà, à défaut d’avoir été bref, j’espère avoir été assez clair ?</p><h4>Oui oui , c’est bon, j’ai tout compris. Tiens, d’ailleurs, on a plus Internet à la maison, la LiveBox clignote. Tu sais d’où ça peut venir ?</h4><p>Hum.</p><p></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf8171377b36" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>