<?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 Marie van Boxel on Medium]]></title>
        <description><![CDATA[Stories by Marie van Boxel on Medium]]></description>
        <link>https://medium.com/@marievanboxel?source=rss-4bbd49802144------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*u-i6J7OPiC3rjqU3FfBJ-w.jpeg</url>
            <title>Stories by Marie van Boxel on Medium</title>
            <link>https://medium.com/@marievanboxel?source=rss-4bbd49802144------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:56:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marievanboxel/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[Talking about research ops with Tomomi Sasaki]]></title>
            <link>https://medium.com/articles-by-central/talking-about-research-ops-with-tomomi-sasaki-dbf8beee4655?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbf8beee4655</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[digital-design]]></category>
            <category><![CDATA[researchops]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Tue, 12 Jun 2018 17:25:38 GMT</pubDate>
            <atom:updated>2018-06-12T17:25:38.248Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OmZkSmBsNQoI7slvLrxnkA.jpeg" /></figure><blockquote>We are <a href="https://central.team/">Central</a>, a design team that creates digital products such as websites and applications. We also regularly organize Umami Talks:<em> </em>live interviews with people who create digital products for a living. So far, we’ve interviewed CEOs, CTOs, product managers, developers, user researchers and designers. Our goal is to get product people together to exchange ideas.</blockquote><blockquote>This article is a slightly edited version of the chat we had with <a href="https://twitter.com/tzs">Tomomi Sasaki</a>.</blockquote><p>Tomomi is a partner at AQ, which is a digital design studio made up of 9 to 12 people working in Paris and Tokyo. Tomomi, who currently lives in Paris, is a UX Designer with an affinity for user research.</p><h3>Hi Tomomi, how did you end up becoming a designer at AQ?</h3><p>I joined AQ as a Project Manager. I realized that the secret to more successful projects, which is what I wanted as a project manager, was for me to understand UX design and to raise everyone’s expertise in design. So I made opportunities for myself to learn UX on the job. I did a lot of studying on my own so I’m kind of an old school UX designer in that way.</p><p>I also do research. At AQ, we don’t call ourselves ‘researchers,’ but we do research as part of our design practice. We do quite a bit of our research to help American and European companies figure out what to do in the Japanese market.</p><h3>How do you go about doing that?</h3><p>It depends on where the company is in the product’s life cycle. If they already have a product, we might just go and see what the feedback is. It’s the same as any UX research except you’re in a culture that the product team probably doesn’t understand. So we try to see how we can translate the feedback that we’re getting. A lot of times, it’s not unique to Japan, it’s just bad UX.</p><p>I&#39;m often asked ‘Does this icon work in your visual culture?’ and the answer sometimes is ‘No, it’s just a bad icon in general.’ So that&#39;s kind of part of figuring out what’s good design and what’s impacted by the visual culture. Of course, there’s a limit to what you can change in a product. We’ve gotten quite good at assessing what’s customizable in a product and giving our advice in terms of what can be fixed right away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R8RY2z_WqxPWvL6ukCP1nw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vRcZinW-uCwDUAacG_VE9w.jpeg" /><figcaption>Craft beer and insightful exchange. Perfection.</figcaption></figure><h3>What kind of struggles have you noticed when companies try to internalize user research?</h3><p>I think user research is always hard to do. We all believe that we should speak to humans and meet people, because that’s what designers are here to do. But it’s not always easy to integrate that into our processes.</p><p>First, because the timelines within a project can be quite different. If you’re doing 2 one-week sprints, a two-month research project will get reactions like ‘Oh, we don’t have time for that.’ So there’s this kind of mental model of different time spans that are hard to integrate into the pace of the company.</p><p>Second, research is inherently cross-disciplinary. You can’t just go do research and be done. We need to use whatever we learn. Unless that lands somewhere, unless we know how to work with a different department or a different discipline, there’s kind of no point. Organizations tend to be very siloed. So, it’s not just research that has a hard time. I think every discipline really needs to be able to work with others in order to be valuable.</p><h3>Why did you decide to invest time in changing the way user research is done and how the results are presented?</h3><p>I have plenty of horror stories. A way that a typical user research project would be assigned is that researchers would say ‘We’re thinking of doing 15 interviews to figure this thing out, here’s the list of questions, here’s who we want to talk to, here’s the deadline. You can expect a report and a presentation.’ This is a pretty typical setup, right? It’s very, very waterfall.</p><p>This is the way we used to design when I started. A lot of times, there&#39;s this reveal at the end where you say ‘This is what we found out.’ And then people say ‘Oh, we weren’t trying to answer that question’ or ‘We knew that.’ It’s so detached from the process of the organization that it ends up being frustrating, uncomfortable and pointless. It also makes it hard for people to do more research because it’s not landing. That&#39;s kind of always been in the back of my head. Also, since we want to advocate for user-centered design, how can we make user research more accessible, inclusive and more valuable? We’ve been experimenting with 3 things.</p><p>The first is <strong>making the process more democratic</strong>. What are different ways in which we can start to share what we’re learning so that it can reach more people within the organization? It doesn’t have to be a huge thing. Maybe it’s just small insights that will make people think in a slightly different way.</p><p>We try to involve more people in the process at different points. Not everyone can always go to the field and talk to users, but if they can, that’s great. We always encourage our clients to go to interviews and be an active part of the research team even if they’re not researchers. We do a lot of workshops to get to what it is that we’re going to report, and do the analysis together.</p><p>The second idea is <strong>diversifying modes of delivery</strong>. We’ve always had this idea of MVD (minimum viable documentation). I don’t like writing reports, but there’s this business culture of being evaluated based on the thickness of your report. Especially if you’re on the consulting side. That’s a really deliverable-based business. But it takes a lot of energy and coffee to deliver that and then few people read the PDF and then it’s lost forever. I really hate that.</p><p>We’ve experimented with delivering via websites like Tumblr to share what we’re learning during field work. It’s available to everybody in the company and we tag information so people can look for specific topics, people, or segments of customers.</p><p>There’s also an idea I really like that I heard about through a design research company called <a href="https://www.stby.eu/">STBY</a> (pronounced ‘standby’). On their website, they talk about fast and slow knowledge sharing. It’s based on Daniel Kahneman’s book, <em>Thinking, Fast and Slow</em>, on how your brain has both fast and slow modes. So the fast sharing could be a Tumblr that you check once in a while. And the slow sharing could be a bigger presentation at the end of a 6-week project.</p><p>The third one is about <strong>visualizing</strong>. I was complaining about writing reports but not everything has to be text. How can we take the insights and turn them into a model, or a map, instead of 10 pages of text? In the UX field, we have models like journey maps, which is a great start. But there are different models and ways of abstracting findings. A lot of this exists in sciences like psychology, in which they have the frameworks for expressing various ideas. I&#39;m always interested in learning from these existing models that academic researchers have figured out over decades. Designers don’t always have to be working on a journey. And researchers need to be able to communicate what they find in other ways than bullet points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P4FA3s9w1rMUMAoCG_sXqQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-YnWs0bS2aC2tSihebf4w.jpeg" /></figure><h3>Can you give us an example of a research project that you delivered using this fast and slow approach?</h3><p>We did a foundational research project in Japan for a job-search site that was looking into how people look for jobs and how employees place ads online to look for people. It’s a fairly broad topic and it was a pretty long research project.</p><p>We had workshops in a room that was quite visible within the client organization. People would come in and hear the debrief and together we would start mapping and synthesizing. Everybody could contribute to making the links between what we found so they could already start using our findings. Sometimes, they’d come in with a completely different topic and then we could go out and explore some more. That iterative process was a lot of fun for everybody. It also meant that different people that were visiting the office, from headquarters for instance, could just join and that would already disperse the knowledge in a way that wouldn’t be possible with a report delivery.</p><p>In general, we try to make posters out of the models we make. We try to figure out what visual models the clients can really take for themselves and refer to in various conversations. Things to reference to is super important.</p><h3>How do you combine user research with design sprints?</h3><p>For a design sprint to happen, you need 2 bits of research. The first bit of research happens before the sprint itself, and is oftentimes delivered as a presentation or experts coming in to share their knowledge. It’s very short but very powerful to get everyone on the same page about what the problem is and what we’re trying to do. A design sprint has to start with understanding whom it’s trying to serve and in what context. You shouldn’t do a design sprint unless you have these insights. Otherwise, you’re not working around evidence of what problem you’re trying to solve. And it doesn’t have to be research especially done for the sprint. It can be past bodies of research.</p><p>The second bit of research happens at the end. It’s validation. I think what was so revolutionary about design sprints is that you have to validate your results with actual customers or someone who’s as close as you can get to an actual customer. This is usually done in the form of interviews where you show people the prototype and you see if your hypothesis was correct or not. That’s part of the process.</p><h3>Could you tell us more about the Slack community for research ops?</h3><p>Sure! There’s a <a href="http://www.katetowsey.co.uk/a-slack-channel-for-researchops/">public Slack group for researchers</a> interested in the topic. I think it started in March. The people who created this group wanted to scale research, and especially qualitative research because it is quite resource intensive. I found this really interesting because, in our field, we need to understand people in parallel to data. Without context, we don’t know what to do with data. I think there’s been quite a sharp increase in interest in research. That wasn&#39;t really there before. The mentality was more ‘Oh, we know what we need to know.’ But there’s now a general acceptance that actually, we don’t know, but let’s find out!</p><p>All kinds of companies, not just in tech and digital, are starting to incorporate qualitative research within their organizations. But because it’s so resource intensive, it’s hard to scale. So people have started to experiment and build a lot of knowledge around how to do research in different contexts. The idea of the Slack community is to get together and share what we know because we’re not moving fast enough to actually address problems and have the impact that we want to have.</p><h3>And you’re organizing a workshop on that topic in Tokyo, right?</h3><p>There’s a <a href="https://medium.com/researchops-community/researchops-community-a-series-of-global-workshops-d48058ece814">global series of workshops</a> that are going to happen over the next couple of months where volunteers in various cities will have meet-ups and there will be a canvas that everyone will share. They&#39;ll discuss what they think research ops is (there is no strict definition) and define it together. People will also be able to share the challenges they’re currently working on and what they need help with. The idea is to get input from practitioners and have a working definition of what it means and what we can learn from each other so we don’t all make the same mistakes. We’re really treating it as a research project. I think this is a brilliant idea.</p><p>I and my colleague raised our hands to run the Tokyo workshop. One of the principles of the community is to be global. These conversations tend to be quite US-centric. I live in Paris but I really wanted Japan to be part of this conversation. I’m really excited to get different perspectives on this topic of research. We do quite a commercial version of it at AQ. But if we get people who are doing research in a civic context, who are meeting immigrants to see what their needs are, this is a completely different set of challenges that we don’t have. I think we can learn a lot from each other.</p><h3>You and a colleague recently created a Slack bot called Meekee, as a side project. Can you tell us more about Meekee and your take on side projects?</h3><p><a href="http://www.meekee.io/">Meekee</a> is short for ‘meeting keeper’. If you integrate your Google calendar with your Slack, it will look at your calendar and notify you 3 minutes before your next meeting starts. I was really insistent that it be 3 minutes. If it’s 5 minutes, you just ignore it, you forget, and then you’re late to that meeting. If it’s 1 minute, it’s not enough time. So it’s just this tiny bot that we built.</p><p>What was really important about that project is not the bot itself. As an agency, as an external design team, we need to be experimenting at a faster pace than our client work allows. A lot of the value that we bring as an external team is that we’ve worked on lots of projects. We can bring in all those sources of inspiration. It’s really important to switch between exploration and exploitation. Sometimes we can’t do something on a client project because it’s too risky. Maybe I’m just not good enough yet. Maybe I want to use this tool, but I’m not completely sure. There’s always this balance to be found: we need projects to succeed but we need to keep trying different approaches and keep learning.</p><p>I think as an agency, some of that just needs to happen outside of client work and that’s really hard to sustain. The minute there’s a client deadline, that project is pushed to the side. We’ve had so many zombie projects that people just pretend they’re going to work on one day but they know they’re not. This is quite harmful, I think, especially if it’s your baby.</p><p>A side project also needs to be linked to learning that makes sense for the business. It can’t just be a personal passion project because that interest needs to be shared by at least 1 or 2 other people. So Meekee was really interesting for us because it gave us the chance to explore bots. It was a big topic when we started. It was something we needed to look into and we couldn’t afford to wait for a client to ask us to design a bot because by that time, it would be too late. And all the reading in the world is not going to teach you how to design an interaction without a screen.</p><p>We managed to make Meekee despite the many client deadlines that stopped us from working on it for certain periods of time. We kept that interest alive by expanding our knowledge. The goal was not just to launch a bot but to explore everything around it.</p><h3>How did you share what you learned with the rest of the team?</h3><p>To share what we learned with the whole team, we organized an ‘ask me anything’ session. I think we always share less than we want to because it’s yet another thing that we have to do. It’s hard enough getting that project out the door, do I need to prepare a presentation for my colleagues? So this is one of the things we tried, where we didn’t have to really prepare anything. We also have a meet-up that’s very similar to Umami Talks and that’s encouraged many of our colleagues to present their ideas as well. That’s part of leading a team: creating an environment where sharing and learning happen naturally (or look like they’re happening naturally).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ys-v0ExddiY283ZjfXXz_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4DD41QxVHox4VVEjEn2Qmw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jihVZY-Q4uKv-Qq1z1Laew.png" /><figcaption>We had porchetta for dinner thanks to <a href="https://twitter.com/qtdlbl">Quentin</a>!</figcaption></figure><p>Thank you very much to <a href="https://twitter.com/tzs">Tomomi</a> for her great talk. Many thanks to <a href="https://twitter.com/NadiaNadienka">Nádia</a> for making another amazing <a href="https://twitter.com/centraldesign/status/988444382075543552">Umami portrait</a>.</p><p>Want to attend an Umami Talk? Register on <a href="https://www.meetup.com/Umami-Design-Talks/">Meetup</a> and check out our <a href="http://umami.central.team/">Umami website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbf8beee4655" width="1" height="1" alt=""><hr><p><a href="https://medium.com/articles-by-central/talking-about-research-ops-with-tomomi-sasaki-dbf8beee4655">Talking about research ops with Tomomi Sasaki</a> was originally published in <a href="https://medium.com/articles-by-central">Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inclusion-first design]]></title>
            <link>https://medium.com/articles-by-central/inclusion-first-design-b75d6ffb12a9?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/b75d6ffb12a9</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Tue, 24 Apr 2018 15:43:37 GMT</pubDate>
            <atom:updated>2018-04-24T15:43:37.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dUOZg_9s5ethEqkU-Y49WA.png" /><figcaption>Photo by <a href="https://www.pexels.com/@leah-kelley-50725">Leah Kelley</a> from Pexels.</figcaption></figure><p>Inclusion is a fundamental part of good design. Inclusive products are usable by everyone, regardless of their economic means, education, skills, location, age, or ability (<a href="https://www.w3.org/WAI/intro/usable"><em>Web Accessibility Initiative</em></a>). In other words, inclusion is everything you’d think of when hearing the terms “accessibility” and “usability,” and a little bit more. In my opinion, products need to be inclusive for one simple reason: fairness.</p><p>As <a href="https://careerfoundry.com/en/blog/ux-design/the-importance-of-usability-and-accessibility-in-design/">Spencer Ivey</a> puts it: “A great beach that nobody can access isn’t really a great beach at all.” What’s the point of creating a wonderful experience, if no one can benefit from it? Granted, very few experiences are actually blocked off from everyone. But what if you were one of the few people who didn’t have access to this perfect beach? It just wouldn’t seem fair, right? When badly designed products run rampant, we could all struggle to access what we need or want.</p><h3>Everyone can have inclusion issues</h3><p>Every single one of us could experience inclusion issues at some point. For example, as we grow older, our eyesight gradually fades. That is to say, most of us will be affected by some kind of visual impairment eventually. When this happens, reading websites with small fonts will become more difficult. But even if you luckily never have vision problems, you’ll probably use your phone in bright sunshine someday. A larger font and starker color contrasts will likely make it much easier to see what’s on your screen.</p><p>Digital products that require precise gestures could also be a problem for any one of us. If you’ve ever had a broken wrist or carpal tunnel syndrome, you know how difficult certain seemingly easy gestures can become. Simplifying gestures and broadening the tap/click areas in our designs can help us all navigate the digital world more easily. So, inclusion issues are actually universal issues. But how can we make sure the products we design are inclusive? How can we keep these issues in mind? One method is to use an inclusion-first approach.</p><h3>Inclusion-first design</h3><p>I’m a big fan of the “mobile-first” and “content-first” mottos in design. They help me keep my priorities straight. At <a href="https://central.team/">Central</a>, we’ve been using these mottos and the approaches they designate for a while now. But we’ve also been tackling our recent design projects with an inclusion-first mindset. The logic is that if you cater to the needs of power users, to the needs of inexperienced users, and to those of impaired users, all your ‘standard’ users will be just fine. (I found this idea thanks to Dan Formosa who was interviewed in <a href="http://documentaryheaven.com/objectified/">Objectified</a>).</p><p>Balancing the needs of different types of people is not always easy. During a recent project, we tackled this challenge by creating personas: archetypes representing different groups within a target audience. We had 4 personas in total, but throughout the project we focused on 2 main ones. The first was a user who wasn’t too comfortable with digital products. The second was someone who knew more about the product than anyone else. By designing specifically for these 2 extremes, we were able to create interactions that would guide inexperienced users, and allow experts to be productive.</p><p>We addressed some of the needs of impaired users by tackling every text-related question with our accessibility goggles on. For instance, we listened to the copy using a screen reader. This made us a lot more sensitive about missing alt-texts, unusual abbreviations, unclear links, etc. Accessibility wasn’t an afterthought. It was the filter we used to validate every single idea we suggested. As this project progresses beyond wireframes and towards visual design, we’ll encourage our client to continue working with an inclusion-first approach.</p><h3>Inclusion is at the heart of design</h3><p>Sometimes, inclusion gets forgotten in the midst of technical and aesthetic questions, but it is a core element of good design. In fact, it naturally stems out of 3 of Dieter Rams’ 10 principles of design: “Good design makes a product useful,” “Good design makes a product understandable,” “Good design is unobtrusive.” If a product is useful, understandable and unobtrusive for whoever uses it, it must be inclusive.</p><p>Of course, creating inclusive products requires some knowledge and practice. I, for one, am definitely still learning. While I do that, I’ll share a couple of my favorite resources with you:</p><ul><li><a href="http://accessibility.voxmedia.com/">Accessibility Guidelines</a> for designers, engineers, project managers, quality assurance professionals and copywriters.</li><li><a href="https://www.atalan.fr/agissons/en/index.html">Digital Accessibility: How Can We Help</a> is a website designed to help people better understand some of the disabilities that impact digital-product use.</li></ul><p>Thanks for reading! I’m a UX Writer at <a href="https://central.team/">Central</a>, a digital design studio based in Brussels. If you’d like to chat about inclusion or UX writing, get in touch on <a href="https://twitter.com/Marie_van_Boxel">Twitter</a> or by leaving a comment below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b75d6ffb12a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/articles-by-central/inclusion-first-design-b75d6ffb12a9">Inclusion-first design</a> was originally published in <a href="https://medium.com/articles-by-central">Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fighting master narratives with digital projects]]></title>
            <link>https://medium.com/@marievanboxel/fighting-master-narratives-with-digital-projects-a4219709812?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4219709812</guid>
            <category><![CDATA[digital-design]]></category>
            <category><![CDATA[digital-public-history]]></category>
            <category><![CDATA[history]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[counter-narratives]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Fri, 20 Apr 2018 19:56:57 GMT</pubDate>
            <atom:updated>2019-06-24T13:28:57.855Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OD66fDRrZTXYk_-cBmsk0g.png" /><figcaption>©<a href="http://www.bbc.co.uk/arts/multimedia/dickens/index_popup.shtml">BBC</a></figcaption></figure><p>Ever heard of Digital Public History? It’s a dull-sounding phrase, but it designates an exciting discipline. A good way to understand what this domain is all about, is to break its name down into two parts. <em>Public History </em>is the endeavor to share history with the general public. <em>Digital</em> Public History (DPH), is the branch of Public History that focuses on sharing information digitally. DPH projects include social media accounts such as <a href="https://twitter.com/RealTimeWW1">@RealTimeWW1</a> which are dedicated to specific historical events, audiovisual models such as <a href="https://news.cnrs.fr/articles/sound-18th-century-paris">The Sound of 18th-Century Paris</a>, or augmented reality projects such as <a href="https://www.hackingtheheist.com/">Hack the Heist</a>.</p><h3><strong>Historical material is not benign</strong></h3><p>Discovering the field of DPH, through a class at the University of Luxembourg, has given me a new angle from which to approach digital design. In essence, it has further opened my eyes to the need for diversity and the right amount of complexity in the works we produce. Let me give you a bit more context.</p><p>History is a sensitive topic. The way in which one presents historical knowledge can easily be influenced by one’s worldview and agenda. In turn, viewing historical information can have an impact on the audience’s mindset. Ronald Takaki, the late and great American historian, <a href="https://www.youtube.com/watch?v=o1Kj1sNlxqY">explains</a> that buying into a specific historical narrative can build barriers in people’s minds. For example, teaching students that the U.S. is a nation of white Anglo-Saxon immigrants sometimes makes them assume that people of color “are not, and cannot” be American.</p><p>Not only does the master narrative of the white pilgrims populating America create prejudice, it’s also biased. The ancestors of many white Americans arrived on the continent later than those of many Asian, Latin and African Americans. The fact that we often forget this demonstrates that biased History feeds biased beliefs. The U.S. is a diverse country, but its ‘official’ history often isn’t.</p><h3><strong>Repetition is powerful</strong></h3><p>The strength of official History, the one taught in schools and written on monuments, is its ubiquity. Seeing the same master narrative over and over again engrains it in our minds. It becomes a part of how we understand the world. That’s why History, whether it is presented online or in museums, should present more holistic narratives. We should learn and teach the History of all the social groups that make up our communities and nations. This will help us better understand our countries, our roots, and our roles.</p><p>We can all play a part in sharing this comprehensive story. That’s the beauty of digital. Whether or not we’re involved in Digital Public History, we all use the internet. Many of us share information on social media, some of us blog or vlog, others create websites and applications. If we all tried to share and create more diverse content, we would minimize the power of the biased master narrative we are taught in schools. The beauty of digital is that we can use repetition for good. We can show how relevant counter narratives are, and perhaps even influence the way official History is told. Many people are already building projects that challenge the status quo. Take a look at <a href="http://webapp.themissingchapter.co.uk/login.php">The Missing Chapter: Black Chronicles</a>, <a href="http://makinggayhistory.com/">Making Gay History</a>, and <a href="https://www.nytimes.com/interactive/2018/obituaries/overlooked.html">Overlooked</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fu1c8p3K8p38140seVHHTg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*58Xsmd4ErC_9dwNrL7rqOw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xv4mFqOC-wJE744nCriPw.png" /><figcaption>The Missing Chapter ©<a href="http://themissingchapter.co.uk/">Autograph ABP</a> | Making Gay History ©<a href="http://makinggayhistory.com/">Eric Marcus &amp; Sara Burningham</a> | Overlooked ©<a href="https://www.nytimes.com/interactive/2018/obituaries/overlooked.html">The New York Times</a></figcaption></figure><p>Such projects display the essential need to avoid simplification. The world does not always reflect our mental models. If we dig a little deeper, we’ll find people and events that don’t fit our pre-conceived ideas. This lesson is striking when looking at History, but it can also be applied to digital design.</p><h3><strong>Simplicity and digital design</strong></h3><p>In digital design, simplicity often feels like a good solution. It allows people to easily understand how to use a product. It also shortens texts so people can quickly scan through pages. But, when repeated enough times, simplicity can lead to a biased perception of the world. The trick is to simplify without oversimplifying; keeping just enough detail to represent the diversity and complexity of the world. To illustrate my point, let’s take a look at “<a href="http://www.bbc.co.uk/arts/multimedia/dickens/index_popup.shtml">Surviving Charles Dickens’ London</a>,” a BBC game created in the early 2000s (the exact date is unclear).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WECSIcaVCS98Haw-L0t09Q.png" /><figcaption>©<a href="http://www.bbc.co.uk/arts/multimedia/dickens/index_popup.shtml">BBC</a></figcaption></figure><p>I came across “Surviving Charles Dickens’ London” while looking for online narratives on the Victorian era, a historical period that fascinates me. The game tells the story of a young boy named Kit who is trying to gather 12 shillings to take the coach to Rochester, where he’ll meet Dickens. Kit spends most of his time in slums, meeting characters who are worse off than he is. Judging from the graphics and the tone of voice, this game was created for preteens.</p><p>The first few screens of the game onboard the player by explaining the controls: use the arrows to move, click on the objects and people you want to interact with. The game’s ease of use makes it accessible and engaging, especially for the target audience. The player can start playing relatively fast without having to struggle with complicated rules. That’s all wonderful!</p><p>However, the simplicity of the game also permeates the narrative. As the characters Kit meets are all white males, the game makes Victorian London seem almost devoid of diversity. The only mention of women appears when the narrator tells the player about Little Nell, a character out of Dickens’ <em>The Old</em> <em>Curiosity Shop</em>. Little Nell plays no role in the story; she’s simply cited. Granted, the Victorian era was dominated by white men. The 19th century witnessed high levels of misogyny, racism, homophobia, elitism, and other types of discrimination. However, it is not because certain social groups were deemed inferior during a historical period that they were unimportant to the cultural and industrial development of the age.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wEq4NyAZVCEFjsoH2U65OA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LAEQy4G5-Exc38OkJbowWw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JaHnobimq03vLMfaO5dT_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YdTAl28VLQ4EjIScg5MQSg.png" /><figcaption>©<a href="http://www.bbc.co.uk/arts/multimedia/dickens/index_popup.shtml">BBC</a></figcaption></figure><p>It shouldn’t have been too difficult to diversify the cast of characters. In keeping with the theme of the game, Kit could have met individuals who, despite being perceived as inferior at the time, fought for the rights of the working class. What about <a href="https://www.bl.uk/romantics-and-victorians/articles/elizabeth-barrett-browning-social-and-political-issues">Elizabeth Barrett Browning</a>, <a href="http://www.bbc.co.uk/history/historic_figures/besant_annie.shtml">Annie Besant</a>, and <a href="http://www.bbc.co.uk/history/historic_figures/cuffay_william.shtml">William Cuffay</a>? Since the game is about Dickens, why not include his wife, Catherine, or his later love Ellen Ternan? Information about individuals other than white males would have doubtless given players a more holistic view of Dickens’ London.</p><p>Studying Digital Public History, and coming across “Surviving Charles Dickens’ London” has reminded me of the need to be conscious of the power we wield when building the content available on internet. Discrimination still exists, in part because we repeat the master narrative that has engendered it. It’s up to us to create projects that reflect the diverse world in which we live. Let’s stop using images and texts that further feed the master narrative. Digital History projects like <a href="http://webapp.themissingchapter.co.uk/login.php">The Missing Chapter: Black Chronicles</a>, <a href="http://makinggayhistory.com/">Making Gay History</a>, <a href="https://www.nytimes.com/interactive/2018/obituaries/overlooked.html">Overlooked</a> are great examples. <a href="http://alexjs.com/">Alex</a>, a tool that allows you to check your texts for potentially insensitive language, is another valuable initiative.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4219709812" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doing user research for a financial product: A chat with Colleen Carroll]]></title>
            <link>https://medium.com/articles-by-central/doing-user-research-for-a-financial-product-a-chat-with-colleen-carroll-74f2d7d17ed5?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/74f2d7d17ed5</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Thu, 15 Mar 2018 10:35:26 GMT</pubDate>
            <atom:updated>2018-03-15T10:35:26.020Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pz04F9GJPAfl7Ed91TyAMg.jpeg" /></figure><blockquote>We are <a href="https://central.team/">Central</a>, a design team that creates digital products such as websites and applications. We also regularly organize Umami Talks:<em> </em>live interviews with people who create digital products for a living. So far, we’ve interviewed CEOs, CTOs, product managers, developers and designers. Our goal is to get product people together to exchange ideas.</blockquote><blockquote>This article is a slightly edited version of the chat we had with Colleen Carroll.</blockquote><p>Colleen is a User Researcher at <a href="https://digit.co/">Digit</a>, a San Francisco-based company that helps people “save money without thinking about it”™. More specifically, Colleen tries to understand users’ financial lives to make Digit as useful as possible. Her path to the Silicon Valley was unusual. After graduating with a Master’s degree in European politics and European political economy, she started doing research in global governance at the University of Leuven, Belgium. Meeting more and more people from the private sector, she became an independent contractor specialized in research strategy and research design. Eventually, Colleen decided she wanted to work on a long-term research project and Digit offered her the kind of challenge she was looking for.</p><h3>Hi Colleen, can you tell us what Digit does exactly?</h3><p>The best place to start is with our goal. Digit’s goal is to democratize personal finance. The idea is that financial health shouldn’t be something that’s accessible only to the wealthiest people who have access to financial advisors and a support system to feel financially stable. With that in mind, the Digit team has created a product that uses machine learning and artificial intelligence to study people’s spending and income habits and to help them save money that they wouldn’t otherwise realize they could save. That can fluctuate from a couple of cents all the way to $50 or $60. It just depends on the person’s spending and income habits. So this core savings product is kind of the starting point.</p><p>That said, we’re trying to reach all the elements of the financial health ladder. Savings is just a small part of that. We see ourselves growing into other aspects of financial health over the next couple years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0uoLDuEE09Ng1CMtzMmWJg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yq5XnUByoKBPUrJ5JNb80w.jpeg" /></figure><h3>What do you do on a daily basis?</h3><p>I’m there to represent the voice of the user. And that means that I’m doing everything I can to understand their personal lives, the context in which they’re interacting with policy, with the product, the service, and I advocate for them within a team of makers.</p><p>My day-to-day at the moment includes everything from designing surveys, and sometimes speaking on the phone for hours interviewing people from across the U.S. Sometimes, I organize focus groups or invite people for user interface (UI) testing. I often sit together with our different product teams, relay any insights and work with them to answer questions they might have about our users.</p><h3>What would you say to people who think that user research is too expensive and too slow?</h3><p>You often have a choice. You could either innovate and move as quickly as possible. Or, you could take a more tempered approach. There are pros and cons to both.</p><p>Research is often what’s really needed to move a product forward. Sometimes you just have to move fast and hope that you’re not going to fail. That’s tech, that’s innovation. But research can really support that effort. It doesn’t have to be anything profound. You can do “gut checks” which are smaller, quicker research projects. But to think about research as a luxury is a little bit of a misnomer in my opinion. Design often gets put into that category, and so does content. They’re just thought of as polish. But it’s really a trade-off. The company has to ask itself the question: what’s the best investment? If you’re in that situation, take a step back and really think about it.</p><h3>What is a gut check?</h3><p>A gut check can be a really quick research project where we get 5 to 10 users on the phone for a 5 to 10-minute call. We ask them a pointed question and we come back with specific feedback. We typically run something like this when we have a very small question about something in particular. We don’t use it for major product or UI changes. But if there’s something small happening with an icon or something like that, we can do a gut check.</p><blockquote>One day’s worth of work could save 6 days’ worth of work. If we don’t do a gut check, we might have to back-track, re-code, re-program and then communicate that to our users.</blockquote><p>We can advocate for and sell gut checks to our other team members a lot more easily than full-on research projects. What often happens is that after a gut check, they realize that a more in-depth research project might actually be the right way to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N9dDiL5tRRWwRZOxJO7tAg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ah9wFBTF_V5CBq0fRY1w2w.jpeg" /></figure><h3>How does the collaboration between research and design happen at Digit?</h3><p>We’re super lucky at Digit because our teams are very cross-functional. We try to organize ourselves around different products generally speaking. Of course, this fluctuates because we’re a 30-person company so it can’t always be that simple. But when we do organize ourselves around a product or some element of the product, there’s always an engineer involved, or 2 or 4. Our CEO is usually involved too. He’s very hands-on and kind of drives products for us. I or my colleague Kristin, who’s also a user researcher, will be involved. And then we’ll include a designer and our Head of Content. Sometimes people are incorporated in different phases of whatever work the team is trying to execute. That being said, working with designers is pretty much inherent to everything we do.</p><p>To kind of really ferment and solidify that relationship, we sit together with our designers and our Head of Content every week and we walk through all the projects we’re working on (whether it’s together or separately) and we make sure that we’re aligned across the board. That’s just been extremely foundational to helping us build a solid working relationship and to making sure that we’re all working with the same set of principles in mind.</p><h3>Can you share an example of when research really had a huge impact on one of Digit’s products?</h3><p>I’m currently working on one of our newest features. It focuses on debt. Many Americans struggle with debt and debt management. Sometimes, they’re indebted for valiant reasons like pursuing an academic education at the highest level. Sometimes it’s for less valiant reasons... In any case, debt is stressful and scary. Getting out of debt and managing that in a way that doesn’t put you into further financial trouble is a serious problem. It’s part of becoming financially healthy.</p><p>The research team came in at a very early stage of this product’s development and we’ve been working extremely closely with a set of Beta users for the last 6 months. So I’ve had conversations with the same set of 30 users after their first month of use of this particular Beta feature, their second month, third month etc. We’ve also run surveys and different types of diary studies to understand how debt fits into people’s lives. Thanks to that research, we’ve been able to see what we need to do for people to feel comfortable turning over their debt management to Digit. So we’ve been able to drive a lot of major changes.</p><p>An example would be that users are really looking for a saving tool that can make payments for them. If you see you have $150 in your Digit account and it’s technically saved to pay off your debt, but that money’s accessible to you, that could just as easily be dinner with your friends over the weekend. So one of the things that users said would be super helpful, was for Digit to make that payment to the bank for them. On our end, that’s incredibly complicated but it’s something that the company is willing to invest in because we’ve heard users ask for it so clearly throughout this series of research projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHGRpXvaEc7YTBOrSgrq5w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*brXUB3henoXHp9zEqeJLaA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YjC_nJ6UTz4nMvmh7ddGRw.jpeg" /><figcaption><a href="https://twitter.com/geoffdlbl">Geoffroy</a> making pizza for everyone who came to our Umami Talk. All hail Geoffroy!</figcaption></figure><h3>How do you make sure your research yields actionable results?</h3><p>Having cross-functional teams plays a big part in this. At the start of any project, we decide which question we’re going to tackle as a team. Whether it’s about something pretty straightforward like testing a flow in our new app rebuild, or whether it’s something more foundational like understanding our users’ larger financial lives, we sit together with the team that’s involved. It’s usually a handful of engineers, content creators, designers and somebody in operations who deals with the financial side of things. The important part here is that we sit together and define the question as a team. I might draft a research plan as a point of departure, but we discuss that plan. We make sure that everyone is on the same page and that the question is clear.</p><p>From there, we can define what success looks like for this project. So maybe I won’t have 15 people pick up the phone when I call them, but I can take the conversations or surveys that I do have, and turn those into a set of deliverables or points that the team members can use. Engineers may need to turn the results into a minimum viable product (MVP), our Head of Growth may need to do a design thinking exercise based on the feedback that we received from qualitative research exercises.</p><p>I can’t emphasize enough how important it is to have actionable results. We have to sell user research internally. We have to make sure it is valuable and useful. If we can’t produce something that’s valuable for our team members, there’s no point in having us there. So making sure that they’re on board from the get-go is really key.</p><p>I’d say the second part of that is actually making sure that the people we’re doing research for are involved in the process. Not just in defining what actionable output looks like for them but having them sit in on the phone calls, watch our focus groups, walk through survey questions with us, help us design diary studies… It really needs to be a collaborative process so there’s buy-in and so that the results are something that can be acted upon immediately.</p><h3>Would you say companies should have a specific research team or that research can be done as part of another job?</h3><p>I’ve worked across many different types of companies and organizations. Some have been very small in size and it was just not feasible to have someone fully dedicated to user research. Even in larger organizations, it’s often difficult to have a new role created. It’s too time-consuming, there’s a whole bureaucratic process you have to go through. I definitely understand that it’s not always going to be possible to have someone who’s specifically dedicated to this type of work. That being said, building up the skills within the team to execute some of these research-related tasks and strategies is absolutely possible.</p><p>I’d say it has to be a reflective process within that team, company or organization about where they need to dedicate their resources. If they need to move really quickly, I can see why research might fall to the wayside. But if there’s time to think about it a bit more, and really consider the long-term investment of adding a research function, of course I’d encourage anyone to advocate for that. Not only for the time gains in the future but also for the type of insights that can really color your product and improve everyone’s work. The insights that you can use to fuel development are immeasurable sometimes. But it depends on a couple of things.</p><p>First of all, do you have a solid product? If you don’t or if you’re still in very early stages of development, then maybe investing in research at this particular time isn’t the best move. Hopefully, you’ve done some market research and you’ve already found that there’s some kind of demand. But maybe getting to know your users just yet, isn’t as essential.</p><p>A second thing to think about is how different your users are from the people who are actually building your product. At Digit, for example, we’re 30 people. We live in San Francisco, and most of us are deeply embedded in the tech world and have some sort of tech background (me being the odd exception). But we’re not somebody in the Midwest who’s 27 years old, just bought a house, still has student debt and living a very different lifestyle. Or even somebody who’s in San Francisco but not working in the tech sector. We’re inherently different from our users. So, having some sort of notion as to how similar or different you are from your end-user base, not just now but also in the future, is the second strong consideration.</p><p>The third thing to think about is how ready your company is to actually act on the insights that you gain from user research. You could have somebody employed on this full-time, but if you don’t have the resources, if you don’t have the staff or the time to act upon those insights, then it’s kind of a loss on both ends. It can be super demotivating for the person who’s working on research to see the work just sit in some box or digital cloud. On the opposite side of the spectrum, it can be very difficult for your engineers and designers to constantly have this input coming at them and to know full well that they don’t have the capacity to act on those insights and suggestions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dVol0_-62qKFjAlVcVgZAw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MFx5SlGlQSC2B7UuMgG_LA.jpeg" /></figure><h3>What are the essential skills needed to be a good researcher?</h3><p>You should ideally be genuinely interested in people. It’s a bit of a difficult role if you’re not comfortable having conversations that can sometimes honestly be very awkward. So you have to be genuinely interested in people and be capable of relating to people who are different from you. So I think from a meta-level, and probably from a very obvious angle, that&#39;s skill #1.</p><p>Skill #2 would be communication skills. If you gather all this information and can’t communicate it, then all is lost. It’s a wasted investment. So it’s crucial to focus on storytelling, igniting collaborative discussions, and really thinking creatively about how you can communicate with people who may not speak the same language as you do (maybe because they come from a coding background or because their mother tongue is not the same as yours). It’s very important to invest in communication and to understand when to use visual, oral or written language to communicate insights.</p><p>If you can master these 2 skills, or are dedicated to making sure you’re constantly developing them, then the rest will follow. You can learn how to write great research questions (there are heaps of books about that), you can learn how to find the statistical significance of a survey, you can learn about A/B testing, you can learn how to interview. But if you need a starting point, I’d say start by definitely being interested in people and being open to different means of communication.</p><h3>How important are math skills to be a good researcher?</h3><p>I wouldn’t say it’s essential. I’ve been really lucky in the sense that most of the engagements I’ve been a part of had somebody dedicated to data. But I think if you’re comfortable with data and statistics, even on the most basic level, it allows you to leverage a lot more of what’s already there. It really improves communication to present some sort of statistical data with qualitative insights.</p><p>For example, if I’m trying to tell a story about what happens in users’ lives and the user tells me “I get paid on the 1st of the month and the 15th of the month and then I have to pay all my bills on the 31st”, I can visualize that as a calendar. But if I compare that to the data we have in our system about this user’s spending and income habits, I can actually see what it means to have to pay your bills at the end of the month while getting paid on the 15th. I can look at all the other fluctuations and demands and put everything together to tell a more complete story. So not being afraid of data would be a good thing. To be capable of creating hierarchical Bayesian models is absolutely not necessary. Even some basic statistics is a nice to have, not a need to have.</p><h3>I’ve heard that you take New Year’s resolutions seriously. Could you share one of your professional resolutions for this year?</h3><p>I do take New Year’s resolutions very seriously. This year, my big professional goal is trying to work on share-outs: trying to find new ways to share the information that I collect. Not just with my project team but with Digit as a whole.</p><p>We often collect tons of information. Some of it is extremely useful and directed to what we’re trying to achieve with a research project. But we have all this other information that can really color our understanding of what we’re trying to do more generally. So at the moment, and this year on the whole, I’m looking for ways to share that information and engage other people in this process.</p><p>The first step has been working really closely with our support team. They’re actually the people who have the most contact with our users. They have all of this feedback that they’re getting on a daily basis. I’m trying to process that and organize it so I can make sure that everyone is engaging with this feedback in a positive way. I’m also trying to come up with more creative and visual ways of getting people involved with all this information. Partly to try to drive home the point that user research is incredibly valuable, but also to make sure that people have a solid understanding of what we’re designing for.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F259870087&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F259870087&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F688706674_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e668be714d185b9729b5e80f0ea55b9/href">https://medium.com/media/1e668be714d185b9729b5e80f0ea55b9/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dBC-Wrn2Ul4yq5tVBYVP3w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gv4tnWnFOEXntU40PDTt6w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bg3_yod6dG8viPjkwQA8wA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zW8GZPq57Jm1jUF4dqV1ZQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5F1WSmrJT01tiIGr1P3hQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bOzM9ReUoFPGVFNWwUeioA.jpeg" /><figcaption>Some (moving) images to show you what the talk was like. | ©<a href="https://twitter.com/pvermaer">Peter Vermaercke</a></figcaption></figure><p>Thank you very much to <a href="https://www.linkedin.com/in/collcarr/">Colleen</a> for her incredibly interesting talk. Many thanks to <a href="https://twitter.com/NadiaNadienka">Nádia</a> for helping us keep up the <a href="http://sketchbookpages.tumblr.com/post/165196527897/umami-talks-digital-speaker-portraits-umami-talks">Umami portrait tradition</a>. We’re also very grateful to <a href="https://twitter.com/pvermaer">Peter</a> for taking beautiful pictures of the event and making an amazing video.</p><p>Want to attend an Umami Talk? Register on <a href="https://www.meetup.com/Umami-Design-Talks/">Meetup</a> and check out our <a href="http://umami.central.team/">Umami website</a>.</p><p>👋 P.S. We’re looking for a <a href="https://central-team.workable.com/j/1C669F2017">freelance User Researcher</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74f2d7d17ed5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/articles-by-central/doing-user-research-for-a-financial-product-a-chat-with-colleen-carroll-74f2d7d17ed5">Doing user research for a financial product: A chat with Colleen Carroll</a> was originally published in <a href="https://medium.com/articles-by-central">Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chatting with Benjamin De Cock: Design Lead at Stripe]]></title>
            <link>https://medium.com/articles-by-central/chatting-with-benjamin-de-cock-design-lead-at-stripe-82466be0c260?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/82466be0c260</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[events]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Thu, 30 Nov 2017 16:03:26 GMT</pubDate>
            <atom:updated>2017-11-30T16:03:26.151Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R8-T8Lxoqn4ScFrRsQzdZg.jpeg" /></figure><blockquote>We are <a href="http://www.central.team/">Central</a>, a Brussels-based team specialized in designing digital products. Every month, we organize Umami Talks:<em> </em>live interviews with people who create digital products for a living. So far, we’ve interviewed CEOs, CTOs, start-up founders, product managers, developers and designers.</blockquote><blockquote>This article is a slightly edited version of the chat we had with Benjamin.</blockquote><p>Benjamin is Design Lead at <a href="https://stripe.com/">Stripe</a>. The company was officially launched in 2011 and has since grown into a 900-people company. Their main aim is to allow individuals and companies to easily set up payments for their online shops. Aside from working for Stripe, Benjamin is a member of the CSS Working Group.</p><h3>Hi Benjamin, thanks for being here. Can you tell us a bit more about what you do at Stripe?</h3><p>I’m the Design Lead of the communication team. In practice we design and build the site for Stripe. We try to explain what Stripe offers in a nice and easy way by making the information obvious and natural to navigate. We also work on the brand and the identity so that people can easily identify and trust the brand.</p><h3>Stripe is based in San Francisco and you work here in Belgium. What methods do you use to make that work?</h3><p>There are a few things in place that make collaboration with remotes easier. For example, we strongly promote Slack, email and sharable documents over verbal decisions. To be clear, that’s not only useful for remotes, it’s also an easy way to document every decision we make without introducing too much friction. We also have quite a lot of conference calls using a service called <a href="https://www.bluejeans.com/">BlueJeans</a>, which works really well. All the meeting rooms are equipped with all the hardware needed to make that possible. I also travel quite a lot to mitigate the time difference because, honestly, no matter what you do a 9-hour time difference is a very hard problem to solve. So, overall it’s just a big pile of hacks but it’s been working surprisingly well so far.</p><h3>Do you prototype your designs before you implement them?</h3><p>Yes, we do. For the dashboard, the interactions can be quite complex, the navigation can be very deep and we have a lot of edge cases. So usually, our UX people build pretty comprehensive prototypes so you can really feel if the solutions might work or not. For the site, we don’t prototype as much. We usually just build the real thing and iterate on that. It’s mostly because our designers are pretty technical and it’s usually faster and more productive to jump right into the real thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l3pjq62e5SqgJVMoMQhJ-Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7xj_vxExJ2DGJGP1qh8L1w.jpeg" /><figcaption>How do you introduce a designer as talented as Benjamin? Not an easy feat.</figcaption></figure><h3>A few years ago, Stripe did not have a design style guide. What are the pros and cons of that?</h3><p>You know what developers like to say about premature optimization being evil? I think that also applies to design. Building a solid style guide is quite a big undertaking and honestly a relatively big distraction for a small team. Now that our design team is much larger, it definitely makes sense to invest in documenting our visual language in a style guide. But we tend to keep our style guide rather light. We have a lot of shared styles, a lot of rules about typography and button treatment, a very detailed color palette and stuff like that. But we only specify the things that deeply contribute to creating a consistent look and feel without locking ourselves into a rigid template.</p><p>I think that the danger and the risk with style guides is that many designers end up creating a very strict set of rules and they end up with a site that looks like a big CMS. That’s obviously not what you want. You want to have the freedom to experiment on every new page and get the chance to refresh your style with every release. So, I think a minimal set of rules is crucial, but doing more than that is counter-productive.</p><h3>Why did you decide to work for Stripe?</h3><p>It’s hard to pin-point one specific reason. It’s a mix of a fascinating culture, working on a product that solves a real problem, the fact that I joined early enough that I could still make a big difference as opposed to joining large companies like Facebook for example. The founders are also the smartest people I’ve ever met. But if I had to pick just one thing, I would probably go for the culture. I remember being really impressed since day one about their craftsmanship and the level of excellence they were looking for in every single aspect of the company. For example, I remember many discussions in which everyone was trying to ignore all the technical problems and challenging assumptions… That passion for doing the right thing really resonates with me. I think that’s the main reason I joined Stripe. It’s not because I’m a huge sucker for online payments.</p><p>At Stripe, everyone goes the extra mile, tries to polish the product, wants to do what’s best for the user, to reduce the friction in every single step. We want people to be able to start accepting payments in literally 5 minutes. That’s our goal. I like it when companies try to kill all the crap and try to make things nice for the end-user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*voVzYdLvo6KRnKlSGQoP5Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lXdNem01k4nzxxXZqybB_Q.jpeg" /><figcaption>Great speaker, great crowd.</figcaption></figure><h3>Is there a specific person you’ve learned a lot from professionally? What did you learn from him/her?</h3><p>In terms of user interface (UI) design, I think I learned a lot from Apple. I realize it sounds very cliché to say that, but 10 years ago UI design, as a specialization, was not really a thing yet. I think back then, macOS was a masterpiece of consistency, visual polish, clever interactions, making interactions super obvious for the vast majority of users while allowing power-users to still feel at home. I think that some of the things they did after that were questionable, but back then I was really inspired by the kind of system they created and I really tried to apply these best practices to the web where we have zero consistency in rules and guidelines.</p><p>These days, I honestly mostly learn from my co-workers who are all better than me in every possible way. Some of these people have a lot of experience in different companies like Facebook, Pinterest, Apple, etc. They tend to bring a lot of setup and workflow around our work and that’s fascinating. Then, in terms of execution and visual polish I think that some of the things they do are just incredible. I definitely learn a lot just by looking at their work.</p><h3>You’re part of the CSS Working Group. Can you tell us what that is?</h3><p>The CSS Working Group is responsible for creating, developing and fixing CSS (a coding language). This group is part of the World Wide Web Consortium (W3C). The goal is to create standard specifications that all major browsers agree on. Most of the members are employees from Google, Microsoft, Apple and Mozilla. The main benefit for the end-user is that no matter what device or browser is being used, the end result will be the same.</p><h3>What are the hottest topics being discussed in the CSS Working Group right now?</h3><p>Most of the topics we discuss are far from being exciting to be honest. It’s pretty unusual for us to contemplate potential new features. It obviously does happen; a few weeks ago we introduced a new gap property which is roughly the same as the grid gap property that you have in CSS grid and would apply to Flexbox and multi-column. Right now, I’m also trying to introduce a new border property but it’s pretty hard to convince other people, so we’ll see. We have to come up with examples and use-cases to show that the suggestions brought forward are necessary.</p><p>But honestly, most of the discussions we have are about fixing bugs in the specs or discussing what to do when we don’t have interoperability. What does that mean? We often see edge cases looking different in different browsers and that might be because the spec was not perfectly clear or because there was an implementation bug in the browser. But even in that case, we often end up changing the spec based on the behavior of the browsers instead of requiring the browsers to change the behavior because that may break a lot of sites. So most of the work is not very glamorous, but the group is very thoughtful about what goes in the specs or not and it sets the right priorities, in my opinion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jDe7RpkRUrp1KUsjDwFNlA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cQmDkcI-DtPGPn1TP-twVQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kBBBQGo996N5dVcKsdi9uQ.jpeg" /></figure><h3><a href="https://dribbble.com/bdc">Your Dribbble account</a> includes icons, detailed illustrations and page views. How did you become so proficient in such a wide array of skills?</h3><p>I guess I just like all things design. I’m just as fascinated by industrial design, photography and architecture as I am by digital design. The other thing is that, early in my career, I started working on my own app with a friend. It turns out building an app requires a lot of different skills. So I had to learn how to design an icon, how to code, how to draw big illustrations for the announcement blog post, etc. It led me towards various areas that I would probably not have dealt with otherwise. Building that app really taught me a lot. My first icons were absolutely horrible…</p><h3>You’ve said somewhere on the web that you suffer from imposter syndrome. Is that still the case? If so, how do you deal with it?</h3><p>Yes, I absolutely still have that. It makes my life harder in the sense that every time I start a new project I’m kind of paralyzed by the idea that I won’t succeed. Every other month, I feel like I’m going to get fired because I’m not good enough. It’s mentally taxing. That being said, I now realize that it does help me a little because I still need to prove that I’m capable of designing and building decent web products. It pushes me out of my comfort zone and it’s a nice way for me to keep learning. So I would say it’s both the worst and the best thing to have.</p><h3>Where do you find your drive?</h3><p>The thing we just said about imposter syndrome really pushes me to go the extra mile. As I mentioned earlier, I get to work with extremely talented people and that helps me grow. I really want to be on the same level as my co-workers so it’s a big motivating factor for me. Another thing is that I still truly love the web. I think the technologies we have now are absolutely fantastic and it makes me a little sad to see all the crap that you can find online. I want to fight mediocrity and create rich, fast, playful and easy-to-use interfaces. The internet still fascinates me and I want to treat it well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-SNjD8wOOEvJAAJVEb1FJQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xc9arSUGWpwaKJnkS_Z_vg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t2LhQWtpfntuyCSy9kCl-w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NBnRNPD9w4vl0VHDgV1nxQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zXXNx4gMQG4nPufml57XBA.jpeg" /></figure><p>Thanks so much to <a href="https://twitter.com/bdc">Benjamin</a> for sharing his thoughts with us, to <a href="https://twitter.com/pvermaer">Peter</a> for borrowing our camera for the evening and to <a href="https://twitter.com/NadiaNadienka">Nádia</a> for the amazing <a href="https://twitter.com/centraldesign/status/918378057630670849">portrait</a>!</p><p>Want to attend an Umami Talk? Follow us on <a href="https://twitter.com/centraldesign"><strong>Twitter</strong></a> to find out about our next ones.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82466be0c260" width="1" height="1" alt=""><hr><p><a href="https://medium.com/articles-by-central/chatting-with-benjamin-de-cock-design-lead-at-stripe-82466be0c260">Chatting with Benjamin De Cock: Design Lead at Stripe</a> was originally published in <a href="https://medium.com/articles-by-central">Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A new way of making slides: Talking with Ludus’ CTO]]></title>
            <link>https://medium.com/articles-by-central/a-new-way-of-making-slides-talking-with-ludus-cto-a6d06e0825ab?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6d06e0825ab</guid>
            <category><![CDATA[events]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[presentation-design]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Tue, 14 Nov 2017 15:59:37 GMT</pubDate>
            <atom:updated>2017-11-14T15:59:37.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M-bH_SN9XXQiVR6w9Zz40g.jpeg" /></figure><blockquote>We are <a href="http://www.central.team/">Central</a>, a design studio that helps organizations create digital products and instil design culture internally. Every month or so, we organize an <a href="http://meetup.com/Umami-Design-Talks/">Umami Talk</a>: an event during which we have a casual interview with a digital product professional and a Question &amp; Answer session with our friendly audience. This article is a shortened and slightly edited version of the chat we had with <a href="https://twitter.com/vinchbat">Vincent Battaglia</a>.</blockquote><p>Vincent is the CTO and co-founder of <a href="http://www.ludus.one/">Ludus</a>, a tool that aims to change the way we create presentation slides and share knowledge. Before founding Ludus, Vincent studied Computer Science in Mons (Belgium) and then specialized in development. He then took his first steps as an entrepreneur and co-founded an SEO company called <a href="http://woorank.com/">WooRank</a> and a design agency called <a href="http://1md.be/">1MD</a>. A few handshakes later, he got the opportunity to work for start-ups like <a href="https://storify.com/">Storify</a> and <a href="https://www.instaply.com/en/">Instaply</a> in San Francisco. In 2015, he moved to Barcelona to open Instaply’s European Head Quarters and decided to stay (we think jamón ibérico must have something to do with it).</p><h3>Welcome Vincent! You’ve built 3 companies so far. What have you learned as a founder?</h3><p>Of course, you always have to build a great product (or do great work, generally speaking) if you’re a service provider. But I think what’s most important is to create a great company culture. People need to be happy. I know a lot of companies that say ‘customers first.’ I would tend to say ‘employees first and customers second.’ If your employees are happy, they will do great work and your customers will be happy. And ultimately, your investors and your shareholders will be happy too. It’s often overlooked, but it’s important. Many companies focus on the product and don’t care about the people. The ‘customer first’ ideology can sometimes be an excuse to make your employees’ lives miserable.</p><p>I’m still learning but I think it’s important to hire the best people and give them as much freedom as possible. Then, great things will happen. The most difficult part is hiring the best people. When I hire, I want someone who is better than me at one or multiple things. It’s stupid to hire people who are not as good as you. It’s an ego thing. Many people want to hire people whom they can manage. It makes more sense to hire someone who’s better than you and who will elevate the level of your company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3STg0uizQOa-mg9uzSOa8Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q2FxrAP2dDiVPU2HVNyUFQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hlCrhsaoIgVJUTL2sHSwVA.jpeg" /></figure><h3>Now you’re CTO and co-founder at Ludus. Could you tell us what Ludus is about?</h3><p>Ludus is a new web-based presentation tool for designers. We like to call it the <a href="https://www.sketchapp.com/">Sketch</a> of presentations. We noticed a lot of problems with existing tools so we decided to build this one. We called it Ludus because we eventually want to revolutionize knowledge-sharing. In Latin, ‘<em>ludus</em>’ is an ambiguous word that can mean playing and learning. That’s what we want to achieve with Ludus: learning while having fun. It’s proven that it’s the best way to learn. We found this term in a book called <em>Ready Player One</em>. Steven Spielberg is working on a movie adaptation of it. The characters in the novel live in a virtual world and Ludus is the name of the planet where they go to school.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F220509828&amp;dntp=1&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F220509828&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F638539204_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/31cb356e59c0c63f54d0f6460323beab/href">https://medium.com/media/31cb356e59c0c63f54d0f6460323beab/href</a></iframe><h3>Ultimately, you want Ludus to be used in schools?</h3><p>Yes, that’s the idea. We know that the education field is a little old-school, if I may use that expression. So, at first, we’re focusing on designers because we’re solving a problem for them. We know that education is difficult to disrupt, so we need to come with a proven solution before widening the target audience.</p><h3>What’s your role at Ludus?</h3><p>Being a CTO means that I’m responsible for technical stuff but also that I’m responsible for the technical vision of the company. I need to know where we want the company to be in 10 years, even if that’s difficult to predict because there will be changes in technology. If you ask me to define myself, I wouldn’t say I’m a CTO. I’m a product engineer. What I like to do is work with technology, but not for technology’s sake. I’m not in love with Python or React. I just like those tools because they help me build great products. I won’t participate in debates about React vs. Angular. They’re just tools to build products. I choose them to do what I want to do.</p><p>On a day-to-day, I code a lot. I think I’ll always code a lot. I also work on the product. We don’t have a CPO. The CPO is the both <a href="https://twitter.com/blobinabottle">Lionel</a> and me. We don’t really have a process. It’s very organic. We all work together at one point or another.</p><h3>What are the weaknesses you found in PowerPoint, Keynote and other presentation tools?</h3><p>PowerPoint, Keynote and other desktop applications have 3 main issues. The first is <strong>sharing</strong>. For example, if you want to share a presentation with a big video, you’ll most likely have to share it through WeTransfer or other tools and it’s a nightmare. The second is <strong>compatibility</strong>. If the person you want to share your presentation with has an older version of the software or doesn’t have the fonts, it’s an issue. The third one is <strong>collaboration</strong>. Even though Google Slides kind of solves these 3 issues, it doesn’t provide features that designers want. If you ask designers whether they like Google Slides, they’ll probably say no. What we already provide that Google Slides doesn’t are things like blend modes, color overlay, uploading fonts, etc. Another thing that Google Slides doesn’t do well is integration. The only integration they currently have is YouTube*. We started Ludus 6 months ago and we already have more than 20 integrations such as Framer, InVision and CodePen. It’s really stupid for them not to take advantage of being on the web.</p><p><em>*Note: A few days after our Umami Talk, Google created a few new integrations in Slides. Coincidence? We think not ;)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WmFDYNaUCA3RdXOIjZPTqQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kxQT0COs_Y2FMWWnvEjWdw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TfEiqqeC32ec4SdaKqkHPA.jpeg" /></figure><h3>From a design standpoint, how do you re-invent something that already exists without getting bogged down by what’s out there?</h3><p>It may seem counter-intuitive but we avoid using tools that already exist. We don’t want to be negatively influenced by what they do. Our biggest source of inspiration is Sketch, which is not a presentation tool but a graphic editor. We do that because all the tools that try to kill PowerPoint, like <a href="https://www.canva.com/create/presentations/">Canva</a> or <a href="https://slides.com/">Slides</a>, copy what already exists. We want to invent something new. Of course, we’ll be inspired by software we like, but not by our direct competitors.</p><p>It’s sometimes difficult for users because they expect to see features that we don’t provide. For example, they want templates but we have a different approach. We want to provide a blank sheet and let people be creative. We don’t want to be creative for people. It’s like the difference between a box of LEGO blocks and a Barbie doll. With a Barbie doll, you can just play Barbie. With LEGO blocks, you can create whatever you want.</p><h3>You launched in May in private Beta and you came on top of the <a href="https://www.producthunt.com/posts/ludus">Product Hunt list</a>. How did you do that?</h3><p>You’ll see a lot of Medium articles that say: if you want to get to the top of Product Hunt, do this, this and that. We kind of followed that but ultimately if you have a shitty product, it’s not going to work. The important thing when you launch on Product Hunt is to have a good product that solves a problem. After that, you can optimize a little. For example, we made a good video which helped with promotion. We also contacted a famous hunter. If you’re helped by a hunter with a lot of followers, then you’ll have more exposure. But if you did that and had a shitty product, it wouldn’t work anyway. You need to have a product that solves a real problem. There’s no magic trick you can use to be the first product in the list.</p><h3>What has the reception been like so far?</h3><p>It’s been very good. For us, that’s more important than the numbers. We like to see that people are enthusiastic about the tool. They know the product is not perfect but they don’t hold it against us because they know that we already make their lives easier and that we‘ll continue to improve.</p><p>Users help a lot. It’s great to build that kind of community so fast. That’s what we’re the most proud of. It’s nice to be able to put ‘3000 votes’ and ‘11,000 users’ on a slide, but what we really care about is happy users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iLnjQVAxxnhrogGgxyUM4A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xgyFl-Op_Mg82bIS3ZzCPA.jpeg" /></figure><h3>How do you integrate all the feedback you get?</h3><p>We don’t have a strict workflow. We have a 1-year roadmap that we try to keep updated. After that, it’s pretty much dictated by user feedback and our internal discussions. We don’t implement everything that people ask for. Sometimes, it’s not in line with our vision. We don’t implement the feedback directly but it helps prioritize the tasks. If we see that a lot of people have a problem with a specific thing, we try to fix it. We also try to use analytics. We can see how people are using the product. For example, if we notice that many people have a problem with the same step when signing up, we’ll try to take care of that.</p><h3>Reading your blog, I noticed that you have a very positive view of the future. You seem to be a techno-optimist. Can you tell us a bit more about that?</h3><p>I try to see the big picture. If you take a step back and look at the way people lived 100 years ago, you’ll see that we have lives today that even the richest people back then couldn’t have dreamt of. If you extrapolate, things should be better in 100 years than they are now. Also, I see a lot of things that make me optimistic: breakthrough innovation in the field of transportation, in renewable energies, education, the blockchain, etc. I think we could see the end of nations, capitalism and democracies as we know them. I know I can sometimes be a little idealistic. But again, if you look at how it was in the past, I don’t see why it wouldn’t be better in the future. I think it’s really important to have utopian ideas; that’s how we’ll improve the world. If you’re pessimistic, you won’t want to do anything anyway. I think that’s why I’m an entrepreneur. I see a lot of things that can be improved in education, transportation, energy. There are so many things to do. Why spend your time doing something that will not ultimately fix those issues?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wOpI6yG61lYVY2AD0d6xVQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wjikuDuGKyGq5YAeSusbIg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*34UlXmG-9S4SJ4uco70E-A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bahNOpG7DtQKw9o2AjmaQw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kSpxhytbEI1r5LOpmP_u0g.jpeg" /><figcaption>These beautiful pictures were taken by <a href="https://twitter.com/PaulReulat">Paul Reulat</a>. Thanks Paul!</figcaption></figure><p>We want to thank <a href="https://twitter.com/vinchbat">Vincent</a> and the entire <a href="https://twitter.com/ludushq">Ludus</a> team for sharing so much with us. More thanks go to <a href="https://twitter.com/NadiaNadienka">Nádia</a> and Delphine for helping us make this event a success. We’re also very grateful to <a href="https://twitter.com/PaulReulat">Paul</a> for sharing his pictures with us.</p><p>Want to attend an <a href="http://meetup.com/Umami-Design-Talks/">Umami Talk</a>? Follow us on <a href="https://twitter.com/centraldesign">Twitter</a> to hear about our next ones!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6d06e0825ab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/articles-by-central/a-new-way-of-making-slides-talking-with-ludus-cto-a6d06e0825ab">A new way of making slides: Talking with Ludus’ CTO</a> was originally published in <a href="https://medium.com/articles-by-central">Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chatting with Jeremy Le Van: Co-founder of Sunrise]]></title>
            <link>https://medium.com/articles-by-central/chatting-with-jeremy-le-van-co-founder-of-sunrise-d9445cdad2e6?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9445cdad2e6</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Tue, 31 Oct 2017 10:48:59 GMT</pubDate>
            <atom:updated>2017-11-02T14:32:35.884Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUHXqB6OlLFbGeKq1Eeg2Q.jpeg" /><figcaption>Thanks to <a href="https://twitter.com/pvermaer">Peter Vermaercke</a> for the photo!</figcaption></figure><blockquote>We are <a href="http://central.team/">Central</a>, a design studio that helps organizations create websites and apps. Every month or so, we organize an <a href="http://meetup.com/Umami-Design-Talks/">Umami Talk</a>: an event during which we interview a digital product professional in front of a friendly audience. This article is a shortened and slightly edited version of the chat we had with <a href="https://twitter.com/jeremylv">Jeremy Le Van</a>.</blockquote><p>Jeremy is Design Director at Outlook Mobile. Before working for this tech giant, he co-founded Sunrise with <a href="https://twitter.com/pierrevalade">Pierre Valade</a>. After 2 years, they sold their popular calendar app to Microsoft for $100 million.</p><h3>Thank you so much for being here Jeremy. Can you tell us how you got to where you are now?</h3><p>I’m originally from Brussels, Belgium. I got into design pretty late. I was never really good at drawing compared to other designers. I fell into design in a way. I started studying graphic design when I learned that a friend of mine started advertising at Saint-Luc in Brussels. I didn’t know it was a thing. So I started studying graphic design here in Brussels at the College of Art and Design (CAD), which is a private school. Then, after my first internship at a small ad agency, I decided to keep on learning. I wanted to learn more about the web. I decided to go for another degree in San Francisco. At first, I was supposed to study motion design. This was in 2005; there was no real mobile design yet. When I applied to the school, which thankfully wasn’t too expensive, they told me that the program was no longer offered because there weren’t enough people interested in it. They told me I had to pick something else but I had no clue what to pick. They said: ‘There’s something called Interactive Media Design. It’s kind of related… There’s some Flash.’ I thought: ‘Ok, why not.’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ya2pfQdzR4D0HoB7PMdj4Q.jpeg" /><figcaption>Chatting before the talk.</figcaption></figure><p>So in 2007, I landed in San Francisco and didn’t know anyone. There were almost no Belgians compared to today. Now we’re well-represented. I slowly started meeting people at design and development meet-ups. After a while, I decided to join a start-up in San Francisco which at the time was called Seesmic. It was an aggregator of Twitter, Facebook, and LinkedIn timelines and it eventually got acquired by Hootsuite. From one experience to another I decided to move to New York. I had heard there were a lot of great things happening there design-wise and start-up-wise. Tumblr started in New York, Foursquare and other companies were there. I wanted to check it out. I landed a job at Foursquare and that’s where I met Pierre, my co-founder. We started Sunrise a year and a half after joining Foursquare; so, rather quickly. But we felt ready to start something on our own.</p><h3>When you started Sunrise, you wanted the workflow to be just right. Can you tell us about the methods you decided to implement?</h3><p>We actually started Sunrise <em>because</em> of the workflow. Obviously, we also started it because we wanted to create a product but even more so because we were frustrated with working at Foursquare. So we looked at our past experience, for me in San Francisco and for Pierre in France and New York. His background is in engineering so we’re very complementary. We looked at how people worked remotely, how people worked in teams, how we could optimize design time and engineering time. We wanted to apply our own methodology to a product.</p><p>Then we found the specific idea by looking at our phones. It was back when Spotify was replacing iTunes and all these third-party apps were replacing the apps installed by default on phones. We looked at the calendar and thought: ‘This is a piece of shit. Let’s fix it.’ It wasn’t working well. The syncing was bad. No one was really paying attention to it. Besides Google Calendar, there was no real innovation. We didn’t know if this was going to be successful or not. But that’s why we were doing it. And we just fell in love with the idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_06SVYcgtt1QZbw23VzoHw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ksd6VyxQCqBA5rfidGNXVw.jpeg" /><figcaption>We had beer and homemade pulled pork after the talk. #mouthwatering</figcaption></figure><h3>Your team was split between Paris, New York and San Francisco. How did you make that remote collaboration work?</h3><p>At the time we didn’t have all of the tools that are available today. It’s not that long ago but I feel like today I see tools that tell you your colleagues’ time zones, and this and that. I feel like everything is even more optimized for working remotely. But for us, what worked really well was the fact that there was a lot of trust in the team. We tried to hire people who were really autonomous. For instance, when we hired Arnaud, our first employee in Paris, he worked by himself. The good thing was that sometimes he would work pretty late so we could catch up with him at night, which was very useful. But we tried to set up a system that was asynchronous, meaning that Arnaud wouldn’t be blocked if we were asleep or gone and vice versa. We were always trying to get the ball rolling. One way of doing that was through GitHub issues.</p><p>We could’ve used something else but we used GitHub issues because it allowed us to track issues, save code and store to-dos about anything from sprints and releases to lunch and printing t-shirts. For people who don’t know how GitHub works, it has different repositories (repos) which are essentially different projects. So you could have a project called ‘Team’ which is everything related to team communication, etc. And another repo about food or lunch. It’s kind of like a channel on Slack. So we “hacked” GitHub issues for our own needs. We wanted to have one single tool. When you have a start-up, there’s the danger of having too many tools because you want to optimize and be the best. Eventually, you get lost and use a lot of different solutions instead of using one tool really well.</p><p>I did a presentation about that in New York a few years ago and we had a few start-ups reach out to us and say: ‘This is amazing! We’re using GitHub issues for everything now and it works for us.’ We’re glad that people were able to use it the same way we did. We didn’t find a perfect solution but we felt like it was the closest one to filling our needs. Actually, one of my ex-colleagues is now working on a better version of GitHub issues with time-zone support for remote working, etc.</p><h3>What were your days like at Sunrise?</h3><p>Since my background is product design, I focused on UX/UI, user stories, leading design research, etc. We hired a friend, who now works at Facebook, as a design researcher. She was more of a psychologist. She would go talk to people, do surveys, do NPS (Net Promoter Score: you ask people to rank your product to give you an idea of whether they like it or not). So I was overseeing that with her. I was also working with the product designers on features and improving the product. Since Pierre has a background in engineering, he was more involved in that. If there were any high-level tech decisions to be made, I wouldn’t touch them. Pierre and the rest of the engineering team would make those decisions. I was more on the product/design side of things. I spent a lot of time brainstorming, drafting user experiences in Sketch and doing other kinds of hands-on work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*n4hLL2JdfOr_mbfESQCnxA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*77hoDcOkT-aG7Dooloy0rQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*IGybmNWKCYAHQWCpn_O7mg.png" /><figcaption>Some views of Sunrise | <a href="http://blog.sunrise.am/">©Sunrise</a></figcaption></figure><h3>If you could re-do Sunrise’s handoff to Microsoft, would you change anything? If so, what?</h3><p>I’m going to be candid and honest. Some things were amazing. First of all, everyone was really nice. There was so much happiness. People were genuinely willing to help. But there are things I would potentially change. On-boarding a small entity (we were 15) into a bigger ecosystem is very complicated. For instance, at Sunrise, Pierre and I did a lot of different things. I took care of some accounting, finance and marketing, finding a new office space, finding contractors; a lot of things that weren’t necessarily related to design per se. All of a sudden you get told: ‘Oh actually, you’ll just be working on this, this and that. That’s it.’ And you’re thinking: ‘Well, I used to do this and that too.’ It can be frustrating at times. But there are a lot of services you get access to all of sudden and that’s amazing.</p><p>So I would say that if we had to re-do things, I would have spent more time learning how Microsoft operates and about the people. Suddenly, you’re told: ‘This manager does this, and that one is leading that’. And then they have acronyms… You can get lost in the midst of all that. Another thing is that in a start-up, you’re used to working very fast. In bigger corporations, things take time, there are legal agreements that need to be reviewed before shipping code, etc.</p><p>Basically, it would’ve been good to better understand the entity itself. And I think it has to come from the acquirer and from the start-up too. The relationship goes both ways.</p><p>Other than that, it went well. Now our team is fully integrated in Microsoft. Some people got promoted. There’s definitely a learning process and I think that as long as people keep learning, it’s good, it’s healthy. There are opportunities in bigger companies. It’s just not always easy for everyone to find their place. And then there are people who just don’t fit in large organizations while others do. It’s very personal.</p><h3>Now you’re Design Director at Outlook Mobile. What design challenges is your team facing?</h3><p>A major one is to make sure that we communicate with the other teams within Microsoft, and first and foremost within Outlook. Outlook Mobile is essentially a proof of concept. If something works really well on mobile, they can say: ‘Look, this works well on mobile. Now we can do the same with all the other products.’ We’re kind of like a showcase within Microsoft even for other teams like Skype, etc. It’s great that we get to be a positive example within the company. Sometimes people give us hard looks because we’re changing things. It’s part of the process. But it’s all for the better in a way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VlLxh1IqxY68tM_HDGgcA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2JBob_YhoOvlG5odkPQ6nw.jpeg" /></figure><h3>What are some useful processes you use to keep your team efficient?</h3><p>We’re trying to keep our milestones small and to ship on a weekly basis. It’s better to ship something, even if it’s small, than not to ship anything at all. Instead of going directly at a big project or feature, we slice it into smaller, more manageable chunks and focus on one at a time. It’s ok if you don’t finish it, you can always push it back to next week but at least there’s some type of goal and everyone is trying to work towards it. We’re trying to keep the momentum going. That’s something we had at Sunrise and that we kept at Microsoft. Before, they used to ship on a 6-month basis.</p><p>We also try not to have too many catch-up meetings. We try to meet at the beginning of the week and announce what we’re going to be working on. Unless there’s a blocker, we don’t feel the need to catch up again. I know there are the Agile/Scrum huddles but we feel that we’re already busy enough. Let’s design, code and write. There’s a lot to do, so let’s focus on that and collaborate without having too many meetings in the process. Sometimes we do have to meet, obviously. We’re just trying to make sure we don’t end up in a meeting with 2 people talking while the others are just on their phones or trying to work. But it’s really hard for big companies to fundamentally change. I think it’s great that the CEO and management at Microsoft are really trying to embrace more start-ups.</p><h3>How do you take care of design quality checks?</h3><p>The designer of the feature is responsible for quality assurance (QA). I think it’s kind of like support. Support is not always fun but you should be grateful for hearing from your customers who took a minute or 20 minutes out of their day to tell you that your product sucks. Even if they’re mad, they’re still taking the time to write. They’re not just uninstalling the app. Sometimes we had people get back to us weeks or months later saying ‘Oh you fixed it. Now it’s great!’ Sometimes they end up loving you.</p><p>I think that within a product team, everyone should be confronted with support and QA. It’s not just one person’s role. In start-ups, many people view support and QA like doing the dishes. They say: ‘Oh no, I have to do support/QA…’ No, it’s making your product awesome and better. So let’s all collaborate and let’s try to be positive about it. I think it’s just about changing the mentality. I know there’s more than one way of doing things but the solution we tried was the best I’ve experienced. I’ve read about other teams doing it differently and it worked for them. So I think it depends on the dynamics of the team and the people within it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SS0fzSZqX2JGqzQttr4maQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aEyiZCqtM8C6tOJorRwS1w.jpeg" /><figcaption>We had such an amazing audience. Next mission: more chairs!</figcaption></figure><h3>What is, in your opinion, the best way to handle handoffs between designers and developers?</h3><p>We’ve been using <a href="https://zeplin.io/">Zeplin</a>, a tool that allows you to upload your Sketch file and allows the engineer on the other side to make sure he doesn’t mess with it. It’s been working great for us. On the other hand I feel you get the best quality of work when a designer and an engineer are sitting next to each other and getting things done. I know the engineer doesn’t always want to do it. But then sometimes engineers want things that designers don’t want to do. So I think it’s about building great relationships between engineers and designers.</p><p>We shouldn’t just assume that engineers don’t want to be involved in design and vice versa. We had 2 engineers who became full-time UX designers and they’re great at it. One of them actually became a lead designer. He knows how to code and went through the pain points of learning how to design and he’s a great asset to the team. I wish we had more people really trying to embrace the other side. If it’s possible, I think it’s really great to have that communication going.</p><h3>Microsoft wants to create applications that can be used on different devices. As designers how do you tackle the process of designing for devices with different constraints?</h3><p>First of all, it’s very new for a company like Microsoft to design for something else than just its own devices. Microsoft embraced the App Store and the Play Store. We’re glad to be a part of that change, it’s very big. They understood that business and users are everywhere, not just in one place. It’s pretty remarkable for a company of that scale.</p><p>To answer your question, we’re always trying to take a holistic approach to the platform we’re designing for. Google has guidelines, Apple has guidelines, the web has guidelines (though they’re more open). Something we talk a lot about at Microsoft is the balance between brand and platform. How do you design something that feels like an iPhone app? I would say that the Skype app on the iPhone is one of the best examples. At one point it looked like a Windows phone app on the iPhone. Microsoft learned from that. We’re glad they did because now when we have that conversation they say: ‘Yeah, of course, that’s how Apple does it so we need the tab bar at the bottom.’</p><p>We’re always trying to find the right balance between the feel of the device and an impression of cohesion between the platforms. It’s also something we tried to do at Sunrise on a smaller scale. We thought about the experience of a user who uses a mac and then goes to an iPad and then to an Android. How does the experience feel across the different devices?</p><p>I would also say tone is very important. Alice, who worked with us on marketing, started working on the app descriptions and we actually got a lot of 5 stars because people loved the app descriptions. When you update an app it usually says ‘fixing bugs’ and things like that. Alice added some jokes and people loved it. I think it’s about finding the little things that make people stick.</p><h3>Where do you find your drive?</h3><p>I would say it’s mostly something I learned back in graphic design school: trying to be a sponge, trying to absorb as much as I can. I think that’s why after living in San Francisco for a while, I wanted to explore someplace else. It doesn’t necessarily have to mean moving from Brussels to Paris or New York. I think it’s just the fact of being exposed to other things. You can talk to lawyers or people in finance and you’ll learn something new. For me, it’s mostly about learning as much as possible. I think that’s why I love New York so much because it has a variety of individuals: people in design, fashion, advertising, law, finance. But you also have that in Paris, Berlin, London and even in Brussels.</p><p>For me it’s also been about trying to think about new ideas and new concepts. Wanting to figure out why something is so broken. Essentially looking at sometimes mundane things that I use every day and trying to think about them in a different way. There will always be haters saying things like: ‘Oh, why are you creating a new calendar?’ Well, guess what? I think the current one is a piece of crap so I’m going to try to fix it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ZD2Bx_izka0XFBa31WihUA.png" /></figure><p>An enormous thank you goes to <a href="https://twitter.com/jeremylv">Jeremy</a> for speaking at our Umami Talk despite being jet-lagged. We also tip our hats to <a href="https://twitter.com/NadiaNadienka">Nádia</a> for the gorgeous portrait she made for our invitation, and we thank everyone who helped us make this a wonderful event. For those who got stuck on the waiting list, we’re sorry you didn’t get to join and we hope to see you soon!</p><p>Want to attend an Umami Talk? Follow us on <a href="https://www.linkedin.com/company/221010/">LinkedIn</a> and <a href="https://twitter.com/centraldesign">Twitter</a> to hear about our next ones!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9445cdad2e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/articles-by-central/chatting-with-jeremy-le-van-co-founder-of-sunrise-d9445cdad2e6">Chatting with Jeremy Le Van: Co-founder of Sunrise</a> was originally published in <a href="https://medium.com/articles-by-central">Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A start-up in education: Talking to Sutori’s CEO]]></title>
            <link>https://medium.com/articles-by-central/talking-to-sutoris-ceo-bfac98534e59?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfac98534e59</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Tue, 11 Jul 2017 11:40:37 GMT</pubDate>
            <atom:updated>2017-07-11T11:42:20.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LMFma4ekNG-y8EmBI6jprA.jpeg" /></figure><blockquote>We are <a href="http://www.central.team/">Central</a>, a design studio that helps start-ups and multinationals create websites and apps. Every month or so, we organize an <a href="http://meetup.com/Umami-Design-Talks/">Umami Talk</a>: an event during which we have a live interview with someone who creates digital products for a living. This article is a shortened version of the chat we had with Thomas Ketchell.</blockquote><p>Thomas is the CEO and co-founder of <a href="https://www.sutori.com/">Sutori</a>, an online tool used to create interactive stories. Designed for teachers and students of all grades and subjects, it is also accessible to any other type of user. In addition to running Sutori, Thomas is an Entrepreneur-in-Residence at the University of Massachusetts, Boston, where he helps students launch new ventures.</p><h3>Thanks for being here, Thomas. Could you tell us how Sutori works?</h3><p>Sutori is a storytelling platform primarily used by teachers and students. By ‘storytelling’ we mean a linear sequence of events. Sutori is very visual: you can add pictures, videos and quiz questions. The big differentiator is that it can be used collaboratively, like a Google Doc. Teachers use it as an alternative to PowerPoint, and they get students to create their own stories through project-based learning. It can be used in any subject from History all the way to Math.</p><p><em>Note: If you want to see some examples of Sutori stories, check out this one on </em><a href="https://www.sutori.com/story/pink-floyd"><em>Pink Floyd</em></a><em> or this one on the </em><a href="https://www.sutori.com/story/the-french-revolution-eb10"><em>French Revolution</em></a><em>.</em></p><h3>How did you start your company?</h3><p>We came up with the idea about 4 years ago. I was living in China at the time. My business partner and I were thinking of ways to engage a new audience in talking about how bad Beijing’s air pollution is. We decided to look back on history and one event that stood out was the London Great Smog of 1952. Twelve thousand people died in 5 days in London because the air was so polluted. Not many people knew about that event, so we created a fictional character who woke up in 1952 and started tweeting as he was living through the Great Smog. We compared that to Beijing today. It was just a one-off Twitter event. That’s how we started re-creating historical events. From there, the idea evolved into an educational tool because we felt this could be very beneficial for teachers and students.</p><h3>City Police on Twitter</h3><p>RT @GreatSmog: .@CityPolice are spending much time diverting traffic through this #GreatSmog</p><h3>Many people advised you not to create an education-related company. Why did you decide to do it anyway?</h3><p>I think it’s because we were really naïve. I have 2 co-founders: my brother Jonathan (who is a teacher) and Yoran (who is a developer and our CTO). When we looked at the actual scope of what was out there in EdTech, we noticed that products were really outdated, kids hated using them and they would always run on Flash. So we had this idea of building a consumer-like product for education. That’s kind of been our driving mission since we started. We still get told that we shouldn’t be spending so much time in education because it’s such a hard market. But we just keep going.</p><h3>What are the challenges of working in EdTech?</h3><p>There are loads. For example, we originally wanted to create and sell educational content about history. When we moved from China back to Europe, we decided to start our platform in Belgium. But Belgium is split. There’s a different curriculum in the North, the South and Brussels. So we thought of doing European History. But Europe is also fragmented and teaches different histories. So we decided to go for one big market and moved to the US. We thought American schools would all teach the same history: American History. But the curriculum is different from state to state. So it’s really difficult to build an educational platform that sells and provides content. That’s why we switched to letting the students and teachers create the content themselves so we wouldn’t get stuck by district standards.</p><p>A second challenge is technology. Some schools have iPads and Chromebooks, but some still don’t have any tech. And a lot of schools have a very low bandwidth. The actual Internet connection isn’t very good. That’s also difficult for applications like ours.</p><p>The last challenge is budget. Teachers are getting larger budgets for technological products but often, schools still use a top-down approach. A school administrator or principal purchases the products, which are traditionally textbooks. It’s very difficult to sell to a district when you’re competing against million-dollar companies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bq_S-RTAOg6Hn0WCA4DU1A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c7YM_7_TxkijmNqvdNJpDA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JTQsu6Hdn1PiUyMHOweTGQ.jpeg" /><figcaption>Enjoying drinks and chats before our Umami Talk.</figcaption></figure><h3>You’ve gone through a few accelerators. What’s their take on design?</h3><p>It’s very limited. What matters most for accelerators is how you look on Demo Day. The whole image of an accelerator is how the companies present. They have a strong impetus on the design of your pitch deck, your presentation, your slides. In terms of the product, I don’t feel like many of them put a lot of effort into it. It depends on the kind of product you’re building, but having a clean presentation is very important to them.</p><p>We’ve been part of 3 accelerators. One of them is LearnLaunch in Boston. They did a UX workshop in which they got an agency to work with each company for 2 or 3 hours. That was really helpful, but the accelerator didn’t really help too much with visual identity.</p><h3>You eventually hired a designer. When and how did you decide to do that?</h3><p>In our founding team, there’s no real eye for design. But we realized the importance of it. Your product has to be functional but it has to look good too. It has to be visually appealing, especially for students. We toyed around for the first year working with small agencies and freelancers, but we weren’t really getting the right fit. It was difficult because we had certain expectations. Then, in the end, we found <a href="https://twitter.com/PierreStoffe">Pierre Stoffe</a> and he joined the project. He’s got a full-time job but he was working with us one day a week. Having a designer on the team really changed the whole mindset for us.</p><p>Our company was called HSTRY but we evolved into Sutori. With the rebrand, we hired a second designer: <a href="https://twitter.com/makehauk">Alexis Jossart</a>. He built up the visual identity of the product and Pierre moved on to a UX role. A lot of investors and companies look at us and say “Hey, who’s doing your design? It’s really cool.” And we say “Yeah, they’re part of the team.”</p><blockquote>We often joke that we have more designers than business people. Design is very important to us.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gWXapEhTCb99skbIHA3osQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6EneHUjMCxuuhixeMHCRkQ.jpeg" /></figure><h3>What UX challenges have you faced in trying to build a product for students of all ages?</h3><p>When we first started building the product, we thought we’d make it very general: for elementary school, middle school, high school and even college students. But they’ve all got different needs. Elementary school students need the product to be very visual without too much text. But at the same time, we want college students to use Sutori as well. It’s been difficult to find that balance. So what we’ve been doing is we’ve built our product with a middle school student in mind. If we have more and more students from elementary, we’ll keep making our product simpler. We keep taking feedback on, so if a school or a teacher has issues, we put that into a spreadsheet and discuss every month how we can make Sutori better.</p><h3>How do you gather feedback and what do you do with it?</h3><p>We have different structures in place. Jonathan takes care of all the customer interactions. We have surveys and we take all of that feedback and do a presentation internally, using Sutori. We then discuss the key pain points brought up by the comments. What usually happens next is that we present that data to our UX designer, Pierre. Then we try to figure out how to improve the process and prevent teachers and students from making mistakes when using our product.</p><p>Another thing we’ve done is work with a school in California. We were going into a classroom every Tuesday for 2 hours to test Sutori with groups of kids between the ages of 8 and 12. That’s the best way to test your product because you see kids who just click everywhere. We were seeing issues ‘live.’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l1NDfa7M2IWcwbWl7sTc0Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A5eJDLBJdh1FYlHvq_AL-w.jpeg" /><figcaption>Our studio a few minutes before the talk. Looks cozy, doesn’t it?</figcaption></figure><h3>You also tested your product in the Netherlands, right?</h3><p>Yes, we did. When we first started we had no users. We just had this idea of Twitter in the classroom. So we emailed people in Belgium, the Netherlands and France. One of the schools that got back to us was a Steve Jobs School where they use iPad-based education. We went to the school and tested Sutori. We translated the product entirely in Dutch, which was a lot of work for us. But it was really worth it because it was that use case that got us to move to the US. People were like “Hey, there’s this cool thing happening in the Netherlands at a Steve Jobs School.” That’s what got us to Boston and what got us initial funding. It played a big role in the evolution of the company.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLBVHRYrmzWbAX5-c83td328P10Ss9CAW3&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBS0gflL_vW4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBS0gflL_vW4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/78a56069375d2a4973f7ea25b19b3211/href">https://medium.com/media/78a56069375d2a4973f7ea25b19b3211/href</a></iframe><h3>How do you create new features?</h3><p>We use a lot of Scrum methodology. We have strategy meetings where we do a road map for 3 months. It’s flexible, we adapt to the users and the feedback that we get. In this 3-month strategy, we establish what we need to accomplish. Then we split the 3 months into 2-week sprints which are led by the CTO with design, UX and business. It works well. We switch to 1-week sprints when we have a tight deadline. For example, when we were rebranding we only had about 6 weeks ahead of us so we switched to 1-week sprints. Now we do stand-ups every day across the team. Having the sprint format really works well, especially when you’re working with designers because they can clearly see the road map and what’s coming up.</p><h3>We like to ask speakers one last question (inspired from Ways We Work): Why do you do what you do?</h3><p>I’ve always wanted to build something. The more users we get, the more I feel like we can get millions and millions of users. That’s what’s really motivating me to keep going. And then it’s the educational values of what we’ve been doing. Now, we’re actually seeing kids who are doing better in their exams because they’re using Sutori. That kind of efficacy is driving us as we have a greater social impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tW0gwAMaQzSE-4ETyEPJfg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84Wcv62cqqSF1l9YqFGQtA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cbj1x8HYvvJQSNuSH2fKAw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jgqC7Fgkuzf_wRBcPQ-ajQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wo5VVjlWIZb74jsKrMdHTA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b_QCkl5Yk94mFD02FkD5oA.jpeg" /></figure><p>We are very grateful to <a href="https://twitter.com/tomketch">Thomas</a> for telling us about <a href="https://www.sutori.com/">Sutori</a>’s journey and approach to design. And, as always, thanks to <a href="https://twitter.com/NadiaNadienka">Nádia</a> for the awesome <a href="https://twitter.com/centraldesign/status/877793485373493248">portrait</a>.</p><p>If you want to come to our next Umami Talk, join us on <a href="https://www.meetup.com/Umami-Design-Talks/"><strong>Meetup</strong></a>. We’ll gladly welcome you to <a href="http://central.team/">our design studio</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfac98534e59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/articles-by-central/talking-to-sutoris-ceo-bfac98534e59">A start-up in education: Talking to Sutori’s CEO</a> was originally published in <a href="https://medium.com/articles-by-central">Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chatting with Tim Van Damme, Head of Design at Abstract]]></title>
            <link>https://medium.com/articles-by-central/chatting-with-tim-van-damme-head-of-design-at-abstract-c8431b17d690?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8431b17d690</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Thu, 11 May 2017 10:43:29 GMT</pubDate>
            <atom:updated>2017-11-15T08:10:52.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGPI7XqC7C-mhun54e07KQ.jpeg" /><figcaption><a href="https://twitter.com/maxvoltar">Tim</a> chatting with our UX Designer, <a href="https://twitter.com/loucaspapa">Loucas</a>. | <a href="https://twitter.com/pvermaer">©Peter Vermaercke</a></figcaption></figure><blockquote>We are <a href="http://www.central.team/">Central</a>, a design team that creates new digital products and improves existing ones. Every month, we organize Umami Talks:<em> </em>live interviews with professionals from the product design world. So far, we’ve interviewed start-up founders, product managers, developers and designers. Our goal is to get product design aficionados together to exchange ideas.</blockquote><blockquote>This article is a slightly shortened version of the chat we had with Tim. If you’d like to watch the whole interview, there’s a video of it at the bottom of this page.</blockquote><p>Tim has had a pretty impressive career path. He left Belgium 6 years ago to join the design team at Gowalla in Austin. He then went on to Instagram and Dropbox in San Francisco. Now, he’s Head of Design at <a href="https://www.abstractapp.com/">Abstract</a>: a new app that will hopefully change the way web professionals collaborate.</p><h3>It’s a pleasure to have you Tim. Could you tell us a bit about yourself? What are you doing these days?</h3><p>These days I’m a product designer, a community manager, a product managing person... The life of a designer in a small start-up is that you have to do whatever needs to be done. The first thing we do when we come into the office is to open Intercom, look at all the new support requests that have come in and start replying, trying to help people, trying to figure out if they’re experiencing a bug or a human error. That’s most of our mornings. Besides that, we’re also actively building the product: fixing things, adding new features, trying to get the word out. We’ll do our public launch later this year so we’re preparing blog posts and interviews with some of our testers.</p><h3>In one line, what is Abstract?</h3><p>Abstract is a tool that allows the proper versioning of design files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sHmvWMX48xamQ5iXpUPdEw.png" /><figcaption>A screenshot of Abstract, a.k.a. Git for designers. | <a href="https://www.abstractapp.com/">©Abstract</a></figcaption></figure><h3>For those who may not know, what is versioning or version control?</h3><p>Version control is typically based on Git. Instead of just duplicating files and everyone working separately, you create your own workspace from this ‘source of truth,’ this master set of files, and you apply changes to it. Once the changes have been approved, you bring the changes back into the master files. The cool thing is that there can be an infinite amount of people working in an infinite amount of workspaces. Because you only track the <em>changes</em>, it’s usually pretty easy to merge the modified files with the master files.</p><h3><strong>In Abstract, you use development terms like branch, commit and merge. Can you explain some of these terms?</strong></h3><p>A <strong>branch</strong> is a workspace. It’s a virtual duplication of the main folder where you can do whatever you want. You make your changes and when you’re done, you can delete that branch or merge it back into the master files. Or you can create yet another branch off of it. So, a branch is <em>where</em> you work.</p><p>The <em>way</em> you work is by creating commits. You create a commit<strong> </strong>whenever you feel like you’ve done something you can say something about. A <strong>commit</strong> is a snapshot of the work you’re doing. If you wanted to update button styles on a screen, you’d go into Abstract if you’re a designer, or Git if you’re an engineer, and write ‘I’ve updated all the button styles on this screen.’ From that moment on, you can go back to that point and open the files at the state they were in when you made the commit. So the idea is that you do multiple commits on a branch until you’re ready to reach out to your team for feedback. They’ll give you feedback, you’ll make changes (which means more commits), and at some point you’ll get approval to merge your work with the master files. Approval might come from your manager, from a coworker, or, if you’re working alone, it might come from you. When you <strong>merge</strong>, you take all the things that have changed and apply them to the master files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LdJxInVekY5hKS2dTOTeyA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wyD7jhhCXEFLRwp3QWkn1Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SWiAqqEEk6Evi9z6a8AQxA.jpeg" /></figure><h3>What are the benefits of all this?</h3><p>You create this very rich history of why screens look the way they do. Right now, you’d need to go to the original designers of the work and ask them why this screen looks the way it does. Design lives inside the minds of people. Maybe that designer already left the company. That’s why history-building is so important. It allows you to go back in time and see how a certain icon came to be. With Abstract, you can see all the commits that happened, you can read the comments, and the feedback that was given on the work.</p><h3>Was it a conscious choice to keep the terminology developers use?</h3><p>Originally the team was split in half as to whether we should keep the Git terminology or do something new. For a long time, I myself was gravitating towards doing something new. People don’t know what commits and branches are. But then Kevin, our CTO, brought up the fact that in the coming years designers and developers will work together more and more. So both parties need to be speaking the same language.</p><p>But we did simplify a bunch of things. Instead of manually pushing and pulling, we automatically push commits to the server. That means that when someone else makes a commit, it automatically gets pulled down so you’re always looking at the most recent version of the design work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uEMy4RYEIvnFzITp-Fae0Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D7AM15G9K2Omt8OqYHUV_Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yzDBflcYMzGWJD0dwxvMFw.jpeg" /></figure><h3>Now you’re in an Alpha version. What’s the feedback been like so far?</h3><p>It’s been very positive. Obviously we can’t win them all. Some teams are in the middle of a big project and they don’t want to be distracted by adopting a new tool. Other people don’t immediately get the Git workflow. We’re working on doing a better job of explaining how that works.</p><p>We’ve also heard from freelancers who have given their clients the ability to look at their work while it’s in progress and give their feedback on it. But the biggest positive results we’ve seen are for big product teams with multiple people working on the same files. They can now collaborate in a structured way without walking on each other’s toes or having duplicates of files. They just go into the app and they instantly see what everyone is working on, which is fun because it’s new. It shouldn’t be new because engineers have been doing this for over a decade. But for designers, it’s completely new.</p><h3>Why did it take so long to create a collaborative tool specifically for designers?</h3><p>It took a while for all the technologies we needed to line up. We use <a href="https://libgit2.github.com/">libgit</a>, which is the same thing that GitHub uses, to do the Git part of it. The Sketch file format just got a lot simpler (but it was already pretty easy to parse and translate into something versionable).</p><p>Abstract is a web app running in <a href="https://electron.atom.io/">Electron</a> (an open source framework maintained by the people at GitHub who used it to build their code editor called Atom). So it’s all web views, running inside this native wrapper that gives you access to the file system. What that means is that we didn’t have to look for 6 really talented Mac engineers, which is pretty much impossible to find. Instead, we’re using a technology that has been tested and tried over the past decade. Someone with a basic understanding of front-end code can jump in and do meaningful work in there. That allowed us to speed up the entire process. But it still took us a year to get to where we are now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGIA8U8QaNYxq-sXylW-6Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6yorQmefpbTeqrLeaYn4zA.jpeg" /></figure><h3>So it’s been a year now. How did it all start?</h3><p>Before it officially started, Kevin (our CTO) did a bunch of work on Sketch plug-ins. By doing that, he got a really good understanding of how Sketch works. So one day, he looked at the Sketch file format and noticed that it was pretty much code. Being an engineer, he was like ‘Well, I have a Sketch file which is code, and then I have Git. What if we merged them?’ So he built this really rough proof of concept. It was a native Mac app combined with 2 or 3 other apps.</p><p>I still remember, he had an orange button on an artboard and he created 2 branches. On one branch he made the button green, and on the other branch he gave the button a drop-shadow. And he said ‘Now I’m gonna merge them!’ and I was like ‘That’s not gonna work.’ But he merged them. It was the new color with the shadow and it was still a Sketch file he could open.</p><blockquote>That blew my mind and I quit my job at Dropbox the next day.</blockquote><p>From there, we knew it was technically possible to do versioning for design files. It took us a year or a year and a half to figure out the right flow to do this. No one had ever done it at this level before. I think <a href="https://gigaom.com/2012/10/03/layervault-aspires-to-be-a-designers-best-friend/">LayerVault</a> had done versioning with Photoshop files which basically means that every time you’d save, they’d upload the entire version to their servers. And then there were a couple of other similar services. But this is brand new, which makes it hard to build because there isn’t a lot of inspiration out there.</p><p>On the UI side, we built 3 prototypes. We do a lot of talking with users and different types of teams so we can build something that a lot of different teams can use. But even with all that data, our first prototype was still really rough. We learned from that, we didn’t throw it away. We just put it aside and built a second version which was slightly better. We kept testing with people and it still didn’t feel like it was something we could ship and expect a lot of adoption. It was only when we built the third prototype that we had this feeling it had the potential to be shipped. That’s the version we’ve been working on for the past 9 months now. And it’s the version we’re going to ship publicly later this year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XSOZYgzRKnVZU5rihv7k2A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8MuDerXlytLS5JBEaFitUQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D-shFx70SM-NAld7tvsuiA.jpeg" /></figure><h3>Do you know when you’ll publicly release Abstract?</h3><p>No, I could make something up but it would probably be wrong. We’re in private Alpha right now, still gathering a lot of feedback and working on performance, adding some big and small features. The next step is probably going to be a public Beta where people can sign up. But it’s still going to have a little Beta sign meaning ‘Use at your own risk.’ You won’t lose any work but bugs may happen. And then hopefully sometime this year we’ll do a public launch and then we’ll start charging. Maybe we’ll charge already in Beta, I don’t know. We’ll see.</p><h3>In your career, it seems you’re always at the right place at the right time. Could you share your story?</h3><p>I’ve always been a big fan of American design. Six years ago, the most consistent design work was coming from the U.S. I’m not saying the best design work came from there but it was consistent. And there were big design teams with many well-known names. I dreamt of working in the U.S. for a bit. So I reached out to Gowalla. We did a 2-week tryout, just contract-based. I redesigned their website while I was at their office in Austin and they gave me a job offer. At that point I was like ‘Alright, I need to get a visa, and I need to get married so my girlfriend can move with me.’ And I think from that point on, that ball has not stopped rolling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/228/1*PtjkgqfF9v7X2byzpwAazg.png" /></figure><p>I joined Gowalla a year later, full-time. I spent 12 months there and basically the company ran out of money. There was a big fight between Foursquare and Gowalla. In the end, years later, Foursquare won. But Gowalla ran out of money so they were looking for companies to acquire them. Facebook came along and they had job offers for about 6 out of 36 people. Not me. I think it was because I was very vocal about not liking Facebook. And I was also very inexperienced back then. Problem was, my wife was 8 months pregnant. In the U.S., if you don’t have health insurance, which you get from the company you work for (otherwise you pay $1000 a month for it), giving birth can be anywhere from $25,000 to $75,000. So I needed a job. What I did at that point was: I looked at my phone and tried to figure out which apps I enjoyed using and where I thought there was an opportunity to help with design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/128/1*ImsegpmuCAFmxKIzeE61aw.png" /></figure><p>Instagram wasn’t looking for a designer because they were growing so fast they didn’t have the time to put together a job description. I just picked them. The founder was following me on Twitter and I sent him a DM saying ‘Hey, I’m in Austin. I’m Belgian and I have a work visa. Do you need a designer? I’m a big fan of the product.’ And they were like ‘Yeah!’ So I spoke on the phone with the founder, I spoke on the phone with the co-founder and then maybe the Head of Engineering and they sent me a PDF which I e-signed and I started working for them. That was a couple of days after our first daughter was born.</p><p>Later, I flew over to San Francisco to actually meet the team and I went on a weekend with some ex-Gowalla people. At the end of the weekend, we were driving back to San Francisco and I was like ‘I don’t like San Francisco. I wanna move back to Austin and back to Belgium at some point.’ Then I got a phone call from the Instagram founder saying ‘Can you come in tomorrow at 8am?’ And I thought ‘This is San Francisco, no one comes into the office at 8 in the morning.’ I thought they were going to fire me. So I get there super early and the entire team was there. I was like ‘Cool, they’re not gonna fire me.’ He called everyone around. We were a team of about 12 or 13 people. He was like ‘Alright, we’ve had tremendous growth in the past few months, it’s all been great... We’re being acquired by Facebook for a billion dollars.’ That was a crazy day.</p><p>The acquisition was made official 6 months later. I was still working for Instagram but legally I was employed by Facebook for 9 months. It was a dream job. The pay was phenomenal, I had a ton of stock in the company and our team got support from Facebook. They would come in saying ‘We can help you with performance and this and that’ and we would help them with photo-related issues. It was great. But the design team was still growing and I wasn’t confident that I could help it grow. I didn’t have the experience to do that. So I made the tough decision to leave Instagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/128/1*ockqwghC0kFuuLgNkaCAkw.png" /></figure><p>I started working for Dropbox, a company which I knew had a very talented design team: a large set of designers whom I could learn from. If you’re working in a small team it’s hard to learn new things. At a bigger company, you have the luxury to take some time to learn. You work with people who know more than you do. Just by working with them, you pick up a ton of stuff. Looking back at it, I would make the same decision in an instant. I spent 2 and a half years learning about building products at scale, hiring people, and just working with others. And then Kevin gave me a demo and I was like:</p><blockquote>‘Fuck it, here we go again.’</blockquote><h3>With all that experience, what advice would you give to people working in product design?</h3><p>When I left Instagram, when I made that tough call, I saw a bunch of people stay for the money. I understand because it was a lot of money. But they didn’t grow for a couple of years, which in the end made it hard for some of them to find new jobs outside that company.</p><blockquote>In this industry, whether you’re an engineer, a designer or a manager, you need to be learning every single day.</blockquote><p>New technologies are coming out every day, new work flows are coming out every day. If you don’t educate yourself, you won’t be able to find a job in a few years.</p><h3>There’s one more question we usually ask our speakers: Why do you do what you do?</h3><p>I enjoy creating products. I enjoy creating things that I know people will use, whether it’s for entertainment or for productivity. Things that will hopefully make people’s lives nicer. But not in some bullshit way. I’ve worked on social products. I don’t think I would do that again because you basically design something to grab people’s attention and then you sell that attention. I don’t like that. But I like building products like Dropbox. Someone stores photos on this and they can go back through years of history and then maybe stumble upon a photo they had forgotten about. For them, that’s worth paying for, which makes me feel good. It makes me happy to be a part of that.</p><p>I like playing with new tools, I like following up on new technologies, I like interacting with the people in that space. There are a lot of really smart people, way smarter than I will ever be, and they’re just fun to work with. There are some assholes too, obviously. But the whole community is very open. There’s always someone available to help, which I guess is my hook to this type of work. But in the end, I want to feed my family. I’m pretty good at drawing rectangles and circles, so I guess that’s how I’ll feed them.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F215701648&amp;src_secure=1&amp;url=https%3A%2F%2Fvimeo.com%2F215701648%2Fbba5eb1d33&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F632504819_1280x720.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/297222d23e4e7951072715a8f31db6b4/href">https://medium.com/media/297222d23e4e7951072715a8f31db6b4/href</a></iframe><p>Thanks a million to <a href="https://twitter.com/maxvoltar">Tim</a> for sharing so generously, to <a href="https://twitter.com/pvermaer">Peter</a> for lending us his photography and filming skills and to <a href="https://twitter.com/NadiaNadienka">Nádia</a> for another amazing <a href="https://twitter.com/centraldesign/status/851820290829164544">portrait</a>!</p><p>Want to attend an Umami Talk? Join our <a href="https://www.meetup.com/Umami-Design-Talks/"><strong>Meetup</strong></a> group and you’ll get notified when we schedule the next one. Hope to see you soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8431b17d690" width="1" height="1" alt=""><hr><p><a href="https://medium.com/articles-by-central/chatting-with-tim-van-damme-head-of-design-at-abstract-c8431b17d690">Chatting with Tim Van Damme, Head of Design at Abstract</a> was originally published in <a href="https://medium.com/articles-by-central">Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Discussing eDemocracy with CitizenLab’s CEO]]></title>
            <link>https://medium.com/articles-by-central/discussing-edemocracy-with-citizenlabs-ceo-26b58417f936?source=rss-4bbd49802144------2</link>
            <guid isPermaLink="false">https://medium.com/p/26b58417f936</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[democracy]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[civictech]]></category>
            <dc:creator><![CDATA[Marie van Boxel]]></dc:creator>
            <pubDate>Thu, 27 Apr 2017 10:42:02 GMT</pubDate>
            <atom:updated>2017-04-27T10:42:02.842Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rcvrQdHumc5af1DL2SOCzw.jpeg" /></figure><blockquote>If you haven’t come across <a href="http://www.central.team/">Central</a> before, here’s a little introduction: we’re a design team specialized in creating user-friendly apps and websites. We also organize casual monthly events, called <a href="https://blog.central.team/central-umami-db84cef2ed2b"><strong>Umami Design Talks</strong></a>,<strong> </strong>during which we have a live interview on product design and management, share some homemade food and drink local beer. Our goal is to get the conversation going. We want to boost the digital product industry in Belgium and thereby help companies build better, more competitive products thanks to great design.</blockquote><p>In March, our Umami guest was <a href="https://twitter.com/WietseVR">Wietse Van Ransbeeck</a>, CEO of <a href="https://www.citizenlab.co/">CitizenLab</a>. Here’s an edited version of the chat we had.</p><h3>Hi Wietse, thanks for being here. Let’s start by setting the scene. Could you tell us what CitizenLab is?</h3><p>CitizenLab is a SaaS company which provides local governments with a platform through which they can collect input from their citizens. We made the decision to collaborate mostly with municipal governments because we think it’s usually at city-level that concrete ideas can be implemented. Some of the cities we work with are: <a href="http://kapermolen.hasselt.be/">Hasselt</a>, <a href="https://oostende.citizenlab.co/">Oostende</a>, and <a href="http://www.reinventonsliege.be/">Liège</a>. When cities decide to use CitizenLab, they can customize the platform to suit their policy processes. In general, the main actions that can be taken on our platform are: posting an idea, commenting on other people’s ideas, and voting for or against suggestions. Based on this information, government officials can see which ideas have the most support and update their action plans accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n5qjuxvVI_uAKmS0WAqhCA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eX_yanw9wJc2lVVYMEk1QA.jpeg" /></figure><h3>At Central, we’ve designed debate platforms and noticed that often, a couple people take over the entire discussion. How do you prevent a few individuals from hogging your platform?</h3><p>Getting people to participate online is always hard. According to Jakob Nielsen <a href="https://www.nngroup.com/articles/participation-inequality/">participation in online communities is not distributed equally</a>. On average, 90% of online platform users are lurkers (simply browsing through), 9% of them post content once in a while, and 1% participate actively. At CitizenLab, we use design to try to get more people involved.</p><p>This starts with an interactive onboarding process. When people sign up to use our platform, we get them to post a first idea. Once people have engaged with the platform once, they are more likely to participate again. Another way we try to increase participation is making sure our platform is inclusive. To help us reach that goal, we follow the <a href="https://www.w3.org/WAI/WCAG20/glance/">Web Accessibility Guidelines</a> which have been studied to meet the needs of individuals with physical and cognitive disabilities. Lastly, we organize user testing nights to help us improve our user experience and further increase our retention rates.</p><p>That being said, promoting user participation is a responsibility we share with the governments who use our service. If our data reveals that residents of neighborhood X do not participate on CitizenLab, the government can focus its communication efforts on making sure residents of that neighborhood voice their opinions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VsPkvPVnsRX8lxsU2DFTag.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4BEDPXRy3BoZpKCA12fDIQ.jpeg" /><figcaption><a href="https://twitter.com/alinemuylaert">Aline Muylaert</a>, CitizenLab’s co-founder, also participated in our Umami Talk. Thanks Aline!</figcaption></figure><h3>Can you give us some examples of ideas that came to life thanks to CitizenLab?</h3><p>Our favorite success stories so far happened in Hasselt. The city decided to implement a few ideas suggested by CitizenLab users. One of them is enlarging a park to include a nearby river. Another is setting up modular benches and wifi in the park so people can work outside in the summer.</p><h3>On your website, you praise Open Public Data (a.k.a. Open Government Data). Can you tell us a bit more about this concept?</h3><p>Open Public Data is basically freely publishing all the data that governments use daily. For instance, a government could decide to share all its data on bike paths throughout the city. Another example is sharing all council decisions online. This is already being done, but its impact could be amplified by creating an API that would allow developers to directly use this data in their applications and websites in real time. The Flemish government is currently working on this. They call it ‘<a href="http://2017.openbelgium.be/blogpost/next-phase-transparency-5-star-linked-open-council-decisions">Open Linked Decisions</a>.’ With this kind of system, people could get notified whenever decisions are made on a topic they care about. This would probably lead to a massive rise in citizen participation.</p><h3>What are the next steps for CitizenLab?</h3><p>Our medium-term plan is to go to the Netherlands, which tends to embrace participation, and to France, which is the home of many civic tech initiatives. On the long-term, we’d like to spread to other countries in Europe. Our dream is to become the biggest eDemocracy platform on the continent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YsAaYLRg55qFfQd9wCvrWQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WuRafeGzVhWgCgtcmwEsUQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iRtPDsdOLEzY5y7EenxD5Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B9rzFdJh_J8gf4gXphrLQw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-5n_a9lkqBQPQCiIZVjzLQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*twDqd7my-Tf-TlWmv2P9-Q.jpeg" /></figure><p>Many thanks to <a href="https://twitter.com/WietseVR">Wietse</a> and <a href="https://twitter.com/alinemuylaert">Aline</a> for giving us insight into <a href="https://www.citizenlab.co/">CitizenLab</a>’s journey.</p><p>If you’d like to attend an upcoming Umami Talk, please <a href="https://www.meetup.com/Umami-Design-Talks/">sign up on Meetup</a>. We’d love to see you at <a href="http://www.central.team/">Central</a> soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26b58417f936" width="1" height="1" alt=""><hr><p><a href="https://medium.com/articles-by-central/discussing-edemocracy-with-citizenlabs-ceo-26b58417f936">Discussing eDemocracy with CitizenLab’s CEO</a> was originally published in <a href="https://medium.com/articles-by-central">Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>