Good Ideas make for Bad Designers — (Part 1 or 3)

<p>A few years ago, when testing a prototype made during a jam by a group of coworkers, I noted the game was cool but had some pacing issues. One of the programmers then noted that he wished they had a designer on the team. To which another instantly interjected, &laquo;I don&rsquo;t see why; we had a lot of ideas by ourselves.&raquo;</p> <p>Okay, so, first of all, ouch, obviously. Surely designers do more for a project than just having ideas and writing them down into documents that no one wants to read, right? &hellip;right?</p> <p>This perception of the designer&#39;s role (having ideas) is quite common, even among aspiring and young designers. As a matter of fact, it is one I have held for years. One that made my job more difficult every time I did. And yet, I still happen to be drawn to it, to doubt myself and others around me based on this belief. So I&rsquo;m writing this to convince myself. Convince myself that this belief is indeed false, misguided, and counterproductive. And if I&rsquo;m lucky, this might convince a few people who might need to hear it, too.</p> <p><a href="https://leolesetre.medium.com/good-ideas-make-for-bad-designers-part-1-or-3-1a94fdbcf12e"><strong>Website</strong></a></p>
Tags: Bad designers