<?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[EYEDEA - Medium]]></title>
        <description><![CDATA[Saving the world by replacing humans with software. - Medium]]></description>
        <link>https://medium.com/eyedea-io?source=rss----78b701ee965d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>EYEDEA - Medium</title>
            <link>https://medium.com/eyedea-io?source=rss----78b701ee965d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:16:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/eyedea-io" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[We need to slay the Beast]]></title>
            <link>https://medium.com/eyedea-io/slaythebeast-7c08861edf00?source=rss----78b701ee965d---4</link>
            <guid isPermaLink="false">https://medium.com/p/7c08861edf00</guid>
            <category><![CDATA[information]]></category>
            <category><![CDATA[knowledge]]></category>
            <category><![CDATA[beast]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Jędrzej Wojnar]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 06:16:00 GMT</pubDate>
            <atom:updated>2019-04-24T07:33:55.036Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y4k4pHObmhkszfYcskcE3g.jpeg" /><figcaption>By Alphonse de Neuville — Hetzel edition of 20000 Lieues Sous les Mers, p. 400. [1], Public Domain, <a href="https://commons.wikimedia.org/w/index.php?curid=40090">https://commons.wikimedia.org/w/index.php?curid=40090</a></figcaption></figure><h4>His trembling tentacles everywhere, its contours blurred from constant motion, its burden on your shoulder</h4><p>When you sleep, he flows in your dreams. When you rest, you are overwhelmed by him. When you work, you are terrified of him.</p><p>His name — Chaos. His kin — the thick darkness. His children — Wastage, Loss, and Failure. Chaos — a real king of the world, an evil tyrant whose ties bind you at every step.</p><p>Chaos demands victims, every day new ones. Never repleted, takes your strength, takes your money, <strong>takes what you have most precious — time.</strong> One can not beg him or bribe him. He can not be deceived; you will not pass unnoticed. When you think that this time you have succeeded — he tightens the loop again.</p><p>How to defeat the Beast, which you can not look into the face because it has too many? Which derives its force from the guiding principle of the universe — entropy? Which is part of ourselves — because it grows out of nature and is its main ingredient?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o0F0jUYYlqMYCxvEE1JAGA.jpeg" /></figure><h3>The answer is simple — you can’t</h3><p>That’s why, in the whole wide world, in every office and every workspace you will hear the question “What’s going on?”.</p><p>This is a question you ask yourself when you join a team involved in a project. This question is asked by the project manager who would like to know at what stage the works are. Every new employee asks about it.</p><p>And there are also customers, investors and a lot of other people who need to find out what is happening to the project, what has already been done or how much has to be done. They want to have all API Documentation at hand; they need accesses, links to external tools and everything that makes up a full, comprehensive and detailed information resource about the project.</p><h4>Everyone wants to have less chaos, yet again they have the same amount of it</h4><p>What about information? Could the increasing amount of information be the right answer? Let’s produce more and more information, let everyone have full insight at every detail, let them know everything about everything. Let’s have a solid temple made out of data squeezed out of every tiny component of the project.</p><h3>That just doesn’t work</h3><p>The information does not reduce the area of ignorance. Quite the opposite — adding information to the cauldron with chaos is like putting out a fire with gasoline.</p><p>Is it hard to imagine? Sure. We did not believe either.<br>But we did the research. People from <a href="https://eyedea.io/">Eyedea</a> took part in it (of course), but to expand the field of vision a little, we’ve joined our friendly IT company — <a href="https://www.pionerlabs.com/">Pioner Labs.</a></p><p><strong>Here’s what came out:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*4pfbSc0wGoEP129mj-URlw.jpeg" /></figure><p>Two essential conclusions arise from this study.<br>First of all — there is no real shortage of information. Second — there is a lack of knowledge.</p><h3>Nope. No contradiction here</h3><p>This statement may seem contradictory, but this contradiction is only apparent. Information is not knowledge — it is just one of its components. Knowledge, besides information, also consists of context and experience.</p><p>Therefore, it looks like the problem lies not in collecting data resources, but rather on their proper connection and distribution. Putting it simply — what turns information into knowledge is the structure.</p><p>So to slaughter the Beast, or at least to make his blood, we need a way to effectively and quickly combine information, the context of action and experience in knowledge — and to make this knowledge as familiar as possible.</p><h3>Ok, don’t you have enough of this whole philosophy?</h3><p>Let’s talk about particulars. If anyone of you, my dear readers, had the opportunity to be involved in the process of building a digital product, probably knows the story.</p><p>Here it is: There is a company, the company has an office, the developers are sitting in the office, and they are doing something. Very, very important something.</p><p>What exactly are they doing?</p><p>It is not easy to find out — developers usually do not have time to explain; they are overwhelmed with work. At most, they will provide you with vanilla information, strictly limited to the component they are currently working on. And what about the rest of the elements?</p><p>Maybe you will set up the meeting, and do some planning? You will hear a lot of jokes about the corporate manner of wasting time on stupid meetings. Plus, of course, expect a lot of ostentatious exasperation in the meantime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jq2Bj0ZWz2_YeNRvl1pkkw.jpeg" /></figure><p>So maybe you should take a tour from desk to desk and ask questions? You will not know anything, except that you are a deadbeat who walks around the office and bothers serious people.</p><p>At some point, getting knowledge seems almost impossible, even if it is not about your personal curiosity. There are people in the world who have ordered this project. They pay for it. They have the right to know.</p><h3>Hold my beer!</h3><p>Anyway, this is not about that the everyone should confirm every step with a memo; it does not make sense. The point is that working on extensive, complex projects (let’s face it — other projects are not that attractive) was not an obnoxious chore caused by things that can be solved.</p><p>Nothing kills creativity more, like a daily struggle with all the nonsense that makes you feel tired just thinking about them.<br>It’s about eliminating chaos. It’s about slaying the beast — no more, no less.<br>It has to be done — and we will do it.<br><strong>You’ll see.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c08861edf00" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eyedea-io/slaythebeast-7c08861edf00">We need to slay the Beast</a> was originally published in <a href="https://medium.com/eyedea-io">EYEDEA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving problems, instead of creating apps]]></title>
            <link>https://medium.com/eyedea-io/solving-problems-instead-of-creating-apps-19e4f3b57952?source=rss----78b701ee965d---4</link>
            <guid isPermaLink="false">https://medium.com/p/19e4f3b57952</guid>
            <category><![CDATA[booking]]></category>
            <category><![CDATA[di̇bs]]></category>
            <category><![CDATA[problems]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[solutions]]></category>
            <dc:creator><![CDATA[Jędrzej Wojnar]]></dc:creator>
            <pubDate>Thu, 11 Apr 2019 08:58:40 GMT</pubDate>
            <atom:updated>2019-04-15T12:17:56.821Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>It seems that perfection is attained, not when there is nothing more to add, but when there is nothing more to take away.— </em>Antoine de Saint-Exupéry</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WzHV5CiM8sacF1erPVa1uw.jpeg" /></figure><p>A tool close to perfection? Regular hammer. All its features result only from its function. Such a tool is transparent in a sense. When you hammer a nail, you just hammer a nail — you do not operate the hammer.</p><p>We decided to make a journey towards a tool of similar simplicity. In this case, the word ‘journey’ is not accidental here. I did not mean to move from A to B. <strong>Covering path is a value in itself.</strong><br>I will tell you about it.</p><h4>Let’s get wise!</h4><p>Two things are the cause of misery and evil: correcting what worked well and getting used to what is wrong.<br>And what does it mean to do wisely? That is, to be able to distinguish between what doesn’t need to be improved and what needs to be refined.</p><p>You can learn to act wisely. I’ll show you how we do it in Eyedea. Let’s use an application that we work on for some time as an example. I will try to show you whole path — more or less.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IUeuz1hwUCNXFcXaTJ6SOA.jpeg" /></figure><h4>Does this problem exist at all?</h4><p>Let’s sketch the situation: we have a cool, functional office in a good location. We share it with few other companies, there are also several freelancers here — thanks to this, one can create an atmosphere of creative, unconventional thinking and just nice cooperation.</p><p>But there are also inconveniences: each of us sometimes needs a quiet place to talk. One has to meet with the client, organize a meeting of project members, or talk to a job candidate — all this requires calm and some discretion. And how many conference rooms do we have?<br><strong>Three.</strong></p><h4>What really works here?</h4><p>It generates — it must generate — difficulties. This question arises in most offices I know — how to check which room is free? Just walk from door to door knocking? And how do you see when a room with the projector will be finally unoccupied? And if there are more people — when and where can I meet them without crowding? How do you book one of the rooms?</p><p>In my previous job (a large company) there were some paper forms and you could write in when you need a room. It worked poorly. Here, in Eyedea, we use the google calendar — it’s basically ok, but it lacks functionality, especially the intuitive interface.</p><p>Only several rooms, but the trouble is real! Maybe the fate of the planet does not depend on its solution, but everyday irritation with trifles is completely unnecessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kn7KiFgZSctfAV-OGRHhXw.jpeg" /></figure><h4>What to do with this?</h4><p>It all starts with the question “what for?” Why did we want to improve something that somehow worked? Come on — we are not a corporation, we will manage to share these rooms after all…<br>Brand sprint answered quite well on this question (and on the few more).7</p><p><strong>First of all — time</strong>. Of course — taping the room is just a moment, but synchronizing calendars of all interested parties and matching them to the timetable of the room is quite a bit of gymnastics. It should be much easier to do!</p><p><strong>In addition, the eternal struggle with pressing chaos</strong>. Our work environment is very fluid. A certain amount of chaos is imminent. Therefore, we can not afford to mess up where it can be avoided. Previewing the occupancy of rooms, scheduled meetings and their participants gives the possibility of better planning.</p><p>Thinking more broadly — this type of tool allows you to better adjust your resources to your needs. What equipment do users need most? In which room would a projector be useful? All this kind of information will be served like on a plate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7WnoXk5Td1-UXdKWfrwJZw.jpeg" /></figure><p><strong>There is still an important issue that arose during the brand sprint</strong> — that is, fun. Although it is difficult to expect explosions of ecstatic laughter while reserving a room for a meeting, it is important that this process is not a complicated path through torment. In other words — we are looking for a transparent tool.</p><h4>What now?</h4><p>Since we’ve already tracked the problem, and we even know what to expect from a potential solution, it’s time to think about how it would look like. The classic solution using the form at the door dropped out at once — to say that they can not be viewed remotely, it is not saying anything.</p><p>Swapping those paper forms for tablets? When we will have shares in some tablet manufacturing company — maybe, who knows?</p><h4>There’s no app for that!</h4><p>Okay, there’s no use to pretend anymore — it’s known that in a technology company, an app is always the solution to all problems. But come one, in this case, it’s a really good idea!</p><p>Imagine a simple system — a small sticker with a QR code at the door of the room, and your phone where you have all the information — when the room will be occupied, which room is equipped with a projector or computer or printer, where the twenty-member team will fit and so on.</p><p>At any time, you can reserve what you need, for as long as you want. And everyone can easily check what meetings are scheduled for today and where they are held. Or which of the rooms will be released in the first place and when exactly will it take place — all in an easy to use, well designed and free-as-air application.</p><p>Sounds good, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*PQWT4IxmiNiLld4xwZ6FTQ.png" /><figcaption>You can read about what came out of this idea…</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19e4f3b57952" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eyedea-io/solving-problems-instead-of-creating-apps-19e4f3b57952">Solving problems, instead of creating apps</a> was originally published in <a href="https://medium.com/eyedea-io">EYEDEA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Use the force, and get it done]]></title>
            <link>https://medium.com/eyedea-io/use-the-force-and-get-it-done-f6a5fda382b0?source=rss----78b701ee965d---4</link>
            <guid isPermaLink="false">https://medium.com/p/f6a5fda382b0</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[golden-circle]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Jędrzej Wojnar]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 13:20:33 GMT</pubDate>
            <atom:updated>2019-03-29T16:40:53.716Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What can you do when a task requires knowledge you don’t have?<br>Go back or go forward — if you only know how.</strong></p><p>Hackathons are always different. Some tasks to solve can be really difficult. For example, recently at <a href="https://hackone.co/">HackONE Silesia</a> in Katowice, two teams (in the Internet of Things category) withdrew without presentation of the concept. Though, huh?</p><p>The crew from the <a href="https://www.facebook.com/explorerhqbialystok">Explorer HQ Białystok</a> team composed of Michał Jurowczyk (Eyedea) and Konrad Kotelczuk (Aitwar) had a hard time from the very beginning. <strong>Electronic engineer from their team backed out just before the party.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3lGv2sOt3t9Q-u6m2172ZA.jpeg" /><figcaption>©Konrad Kotelczuk</figcaption></figure><h4>The challenge</h4><p>One can easily imagine how much his competencies were needed — the task of hackathon sounds:</p><blockquote>“Imagine that we have lighting infrastructure of a production or storage hall, connected using a wireless protocol (let’s say it’s Bluetooth, but it can be anything else). You can connect something to the luminaires (maybe sensors, maybe cameras, maybe beacons, maybe something else?).</blockquote><blockquote>The goal is to create new functionality, a new product that would solve a specific problem of a production or warehouse company “</blockquote><p>The team from Białystok was joined by Marek from Katowice, who is not even close to electronic engineering, but regulations clearly says that minimum size of the team was three people, so there was no sense to be picky.</p><p>From the very beginning, a very strong emphasis was placed on the fact that the <strong>proposed solution should not only be an elegant concept, but it should bring real benefits for the client</strong>. The task description explicitly stated that this hypothetical recipient of the idea is a person open to innovation, favorable to new solutions, but extremely rational and focused on real benefits.</p><h4>Let’s make it done</h4><p>In other words, the concept was not only to look good but above all to work well and be within sensible and comprehensible budget limits.<br>Well, because chickening out at the beginning was not an option, they had to deal without electronic engineer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7XbkLu6ZI5uAaezshu0oQQ.jpeg" /><figcaption>©Konrad Kotelczuk</figcaption></figure><p>So — brainstorming and deep research. Hours on the Internet, hours on the phone (because, as it turned out, not all devices have a detailed specification available — especially those cheaper ones). Electronic engineers have such information in mind, but the electronic engineer in the team was missing…</p><p>There were plenty of ideas for solving the task, too many of them actually. The Golden Circle method, which is well-known to Michał, came to help. We use it a lot (and also improve it) in Eyedea. <strong>First of all, thanks to a precise response to WHY, HOW, WHAT, concepts that did not exactly correspond to the topics raised in the challenge were sifted away</strong>.</p><p>The idea that went through all the screens was a control panel based on a model for providing lighting as a service. Thanks to this panel, the operator of the lighting system have full insight into the state of all system components, which helps prevent failures with potentially serious consequences.</p><h4>Small detail, huge loss</h4><p>One must realize that the failure of lighting in a large production hall does not only mean that somewhere there will be a little darker. <strong>Insufficient lighting can mean stopping production until the failure is removed — for reasons of work safety and regulations related to it</strong>. And that will cost real money.</p><p>Therefore, knowing which light sources are close to the limit of their lifetime, where the luminaire overheats, or at which point in the system anomalies was found cannot be overestimated.</p><p>An additional element of the proposed solution was the use of machine learning. Thanks to this, the whole thing is easily scalable, it is also easy to evaluate the price of the final product depending on the level of its complications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A3ZGUf2UmXSZf6a67Mad1w.jpeg" /><figcaption>©Konrad Kotelczuk</figcaption></figure><h4>What innovation means?</h4><p>Our lads honestly say that it is not like there are no similar solutions in the world. They are, of course. But it is worth remembering that these are mostly closed systems that can not be easily and cheaply adapted to specific needs, and whose components are expensive.</p><p><strong>The proposal presented at HackOne was very well thought out not only in terms of technology but also — and perhaps above all — in terms of business</strong>. A scalable system based on cheap components has been proposed, thanks to which this type of service can become available to those users who can not afford to use the solutions of great players.</p><h4>Does it work?</h4><p>Since you already know all this, it’s time to ask yourself about the place you have taken — after all, Hackathon is a competition. There can only be one answer — the first!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*HkF6KDv69Jf6GRp7764EmQ.jpeg" /></figure><p>This clearly shows how <strong>flexible mind, cooperation and appropriate, tried and tested methods of solving problems can break up any issue</strong>, even if the team lacks certain key competencies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6a5fda382b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eyedea-io/use-the-force-and-get-it-done-f6a5fda382b0">Use the force, and get it done</a> was originally published in <a href="https://medium.com/eyedea-io">EYEDEA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How slack could avoid logo reception failure, or: how to test your logo design?]]></title>
            <link>https://medium.com/eyedea-io/how-slack-could-avoid-logo-reception-failure-or-how-to-test-your-logo-design-562d5aeed1f1?source=rss----78b701ee965d---4</link>
            <guid isPermaLink="false">https://medium.com/p/562d5aeed1f1</guid>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[logo]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[brand-strategy]]></category>
            <dc:creator><![CDATA[Maciej Korsan]]></dc:creator>
            <pubDate>Thu, 17 Jan 2019 14:25:34 GMT</pubDate>
            <atom:updated>2019-01-19T08:35:28.399Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How Slack could have avoided logo reception failure, or: how to test your logo design?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vxToYABqaecqELEWUpDDtg.png" /></figure><p>Yesterday Slack launched a new logo, as they’ve started to refresh their look in general. It was the work of the in-house design and brand team, together with Michael Bierut and the team from <a href="https://www.pentagram.com/work/slack">Pentagram</a>. People from Slack loved the old one, but it was created before the company started, and as they say, because of 11 different colors, it was also easy to get wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JpDuii8abxVpTKY8wLDhRw.png" /><figcaption>Old, recognizable logo</figcaption></figure><p>Slack started to create a new visual identity. They used a simpler color palette which works better in many places.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1GaJuER0KVY1bp2_kOS8QQ.png" /><figcaption>New, controversial logo</figcaption></figure><p>Unfortunately, the new logo didn’t receive a good reception, and people went on a rant on social media.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*xc3oX0qsAYIT1qg5IfqAOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*6BU6BBd-mR1rVnVg1cpo0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*T1FI2H5aUmT9OsXm3WssuQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*p21KKAi6vmC5cS-I1Npdgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*jDbj-Z6UE9ZgkvbsbQ1rHA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*msKiCQ1remSZu7mnZYHDYQ.png" /><figcaption>Ooops… <a href="https://tinyurl.com/yap63kzf">source</a></figcaption></figure><p><strong>So, what just’ve happened?</strong></p><p>Nothing special. Welcome to the Internet — people don’t like radical changes of things they’re using. Everytime Facebook introduces a new version of the existing features, there’s always a group of unhappy users saying they’ll remove their accounts because of that change. After two weeks most of them forget how it looked before. That is, unfortunately, a perfectly normal behavior. Changing existing branding is always a bigger challenge than creating a fresh one.</p><p>So could this svastika/d(i|u)cks thing could be avoided? Maybe. There are at least two ways of making a new branding. We don’t say that Slack didn’t test their new branding, but maybe the testing group wasn’t big enough? In our branding work, we focus on testing a lot, because we believe that branding has a lot in common with software. Before releasing it to the general audience, software must pass some tests. The same should go with the branding. Before you launch a new visual identity, you need to ask people what they think about it. Relying only on the board’s / owners decision might not be the best idea.</p><p><strong>How to test your logo design?</strong></p><p>We are a small product house, building web-based products. In Eyedea, we believe that it is better to make a decision based on science and statistics than on so-called common sense.</p><p>So what’s our way? At first, we are scheduling a one-day brand sprint meeting with the product owners/founders and our team. The brand sprint consists of 7 steps. Every step is done in the note and vote way.</p><p><strong>1. A 20-years roadmap.<br></strong>Most teams focus on what they’re doing now, which makes sense. But if your company is successful, your brand will last a long time. So in the first exercise, you look into the future and think about what your company might be doing 20 years from now.</p><p>Nobody will expect you to stick to the 20-Year Roadmap — that’s not the point. The point of the 20-Year Roadmap is to get your team thinking about the lifetime of your brand. A great brand will last until the year 2039 — and beyond.</p><p><strong>2. What, how, why?<br></strong>This exercise is based completely on Simon Sinek’s “Golden Circle”, see Sinek’s TED talk. Sinek’s premise is basically this: You need to know why you’re in business — and talk about it. When a company has a strong motivation and that motivation shines through, customers buy the product. It’s easy to find supporting examples. Sinek points to Apple, but companies like Nike, Patagonia, Airbnb, and LEGO obviously fit the bill.</p><p><strong>3. Top three values.<br></strong>Next, you make your “why” more specific by listing and ranking your company values. I know “company values” sounds like consultant baloney, but it’s just another way of saying “stuff that really matters to us” or, even better, “decision-making principles”.</p><p><strong>4. Top three audiences.<br></strong>In this exercise, you list all your possible audiences, then figure out who’s the most important.</p><p>Who qualifies as an “audience”? Customers, for sure, but you can think more broadly by asking this question: Whose opinion do you care about?</p><p><strong>5. Personality sliders.<br></strong>In this exercise, you position your company’s “sliders” between pairs of brand extremes.</p><p>There are good reasons to be on the left or right of any of these lines, and it’s even okay if some of your sliders end up in the middle. But it’s helpful to be strongly opinionated on at least one or two ranges.</p><p><strong>6. Competitive landscape.<br></strong>In this exercise, you position your company’s into the competitive landscape, now and in the future.</p><p><strong>7. Goals.<br></strong>In this exercise, you will determine what is required to move towards the 5-year goal you established at the beginning of the day.</p><p>After completing the steps described above, our graphic designer gets the results from the brand sprint, and he’s working on up to three logo propositions. Then we are creating a survey. We are putting designs and some questions related to the brand sprint to check how the logos fit requirements of the brand sprint. And here comes the power of the crowd. We are surveying people — in person and online — to get the feedback. Most of them are from the previously specified target group of the product, but we’re also experimenting with persons “from the outside”. Sometimes we receive a surprising result. For example, when we were examining new logo for the software company, some people told us that one of the concepts looks like a logo of the SPA resort. Next, we’re analyzing the results using our statistical algorithms to find the best one. The result of the analysis is presented to the product owners/founders. After that, we’re doing another iteration of design work to polish the logo concept and, if it’s needed, another round of surveys. In the end, you have a validated idea that matches initial values.</p><p>Of course, you’ll never make everybody happy, but having this kind of logo validation could prevent lots of negative comments that Slack got lately.</p><p>PS. We’re going to write more articles about our processes, so feel free to follow us :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=562d5aeed1f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eyedea-io/how-slack-could-avoid-logo-reception-failure-or-how-to-test-your-logo-design-562d5aeed1f1">How slack could avoid logo reception failure, or: how to test your logo design?</a> was originally published in <a href="https://medium.com/eyedea-io">EYEDEA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>