<?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 Cookie Redding - Artist, Designer &amp; Educator on Medium]]></title>
        <description><![CDATA[Stories by Cookie Redding - Artist, Designer &amp; Educator on Medium]]></description>
        <link>https://medium.com/@cookieredding?source=rss-f1dfc0e1956------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I3dui8mfGLQJ79VVPkTo3g.jpeg</url>
            <title>Stories by Cookie Redding - Artist, Designer &amp;amp; Educator on Medium</title>
            <link>https://medium.com/@cookieredding?source=rss-f1dfc0e1956------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:20:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cookieredding/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[Designing for Yourself vs. Designing for Clients: Why the Process Feels So Different]]></title>
            <link>https://medium.com/@cookieredding/designing-for-yourself-vs-designing-for-clients-why-the-process-feels-so-different-0c11b1c7a5cc?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c11b1c7a5cc</guid>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 18:56:02 GMT</pubDate>
            <atom:updated>2026-11-02T18:56:02.223Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pscUE88d5jVb_ab-3jefBg.png" /></figure><p>Designing for yourself can be surprisingly harder than designing for somebody else. With client work, you usually have something to respond to. There is a project, an audience, a deadline, some kind of goal, and probably a list of things that need to be included. Even when the brief is messy or the client is not completely sure what they want, there is still a problem sitting in front of you that you are supposed to solve.</p><p>Personal work can be much more open. You can use whatever colors you want, make whatever format you want, change the idea halfway through, or abandon the whole thing and start something completely different. That freedom sounds great until you realize you are also responsible for making every single decision. There is nobody else telling you the logo needs to work at a certain size or the poster needs a particular piece of information. You have to decide what the project is, what it needs to do, and when it is finished, which can make personal work feel harder even though technically you have fewer restrictions.</p><p>I think constraints are one of the biggest differences between the two. Client work comes with them automatically. There is usually a budget, a timeline, an audience, a format, existing branding, or some other boundary around the project. You may complain about those limitations while you are working, but they also give you something to push against.</p><p>With personal work, it can help to create some of those constraints yourself. Give the project a format, pick a limited palette, decide you are only going to use one typeface, make three versions instead of endlessly tinkering with one, or set a point where you are going to call it finished. You are not trying to make personal work feel like another client job. You are just giving yourself enough structure that all that freedom does not turn into a million open-ended decisions.</p><p>Client work also gives you a clearer way to evaluate those decisions. A design can look great and still be wrong for the project if it does not speak to the audience, communicate the right information, or fit the brand. You have something outside your own taste that helps you decide whether the work is doing its job.</p><p>Personal work does not always give you that. You might make something perfectly competent and still have no idea whether you care about it. There is no brief to check it against, so the question becomes more about whether you are interested in what you made and whether it gave you anything you want to keep exploring.</p><p>That can actually be one of the best things about personal projects. You can make something because you want to test a ridiculous color combination, try a process you have never used, make a poster for something that does not exist, or spend three hours doing something no client would ever pay you to do. It does not have to solve anybody else’s problem.</p><p>I think that kind of work is important because client projects naturally train us to think about other people. You are thinking about what the client needs, what the audience needs, and what communicates clearly. Those are important design skills, but if that is all you ever do, it can become harder to remember what you are personally curious about. Personal work gives you somewhere to follow that curiosity without needing to justify it first.</p><p>The other big difference is feedback. With client work, somebody eventually has to respond. Sometimes that feedback is useful, sometimes it is frustrating, and sometimes you find yourself explaining for the fourth time why making the logo bigger is not necessarily the answer. Either way, another person is part of the decision-making process.</p><p>When you are designing for yourself, you can get stuck in your own head because nobody is there to push back. You can keep adjusting something forever because there is no approval stage forcing you to move on. That is another place where setting your own limits can help. Make a few versions, pick one, and live with the decision for a while.</p><p>It can also help to show personal work to somebody you trust, especially if you have been staring at it too long. You do not necessarily need them to tell you how to fix it. Sometimes hearing another person describe what they see is enough to help you notice what you have been missing.</p><p>I also think personal work and client work can feed each other more than we realize. Personal projects are often where you get to experiment with something before you would ever suggest it to a client. You can test a new process, style, piece of software, or way of working when the stakes are low. Later, some part of that experiment might become useful in professional work.</p><p>Client work can do the opposite. A limitation you would never have chosen for yourself can push you toward a solution you would not have found otherwise. You might discover a type treatment, layout approach, or process because somebody gave you a very specific problem and you had to figure it out.</p><p>I do not really see one as more creative than the other. They just ask different things from you. Client work asks you to solve somebody else’s problem within a set of boundaries, while personal work asks you to decide what problem you want to solve in the first place.</p><p>If your personal projects keep stalling, you may not need more inspiration. You might just need a better brief. Give yourself something specific enough to respond to and enough room to make decisions you would never get away with in client work. And if you spend most of your time designing for other people, it is worth keeping at least a little space for work where you get to decide what matters.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c11b1c7a5cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of Slow Design: Why Speed Isn’t Always Better]]></title>
            <link>https://medium.com/@cookieredding/the-art-of-slow-design-why-speed-isnt-always-better-c4db28ac3c8a?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4db28ac3c8a</guid>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[slow-design]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 16:42:02 GMT</pubDate>
            <atom:updated>2026-10-11T16:42:02.074Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0evH57jMz8PnKO-38nA6fQ.png" /></figure><p>We spend a lot of time trying to get faster at making things. Faster workflows, faster software, faster ways to generate ideas, faster ways to get from sketch to finished piece. Some of that is genuinely useful. If there is a tool that saves me twenty minutes doing something repetitive, I am probably going to use it. But I also think there are parts of creative work that do not necessarily get better when we speed them up.</p><p>Some ideas need time to develop. You make something, look at it for a while, come back to it, change your mind, and eventually start understanding what the project actually needs. That process can look inefficient because there may be stretches where you are not producing much that looks finished, but you are still working. You are looking, comparing, testing, thinking, and figuring things out.</p><p>I think that matters because we tend to measure creative work by visible output. How many pieces did you finish? How many concepts did you generate? How quickly did you move through the project? Those things are easy to track, but they do not necessarily tell you whether the work got more interesting.</p><p>Sometimes moving too quickly means you take the first decent idea and run with it because it works. The composition is fine, the concept makes sense, and you could finish the piece without much trouble. But if you had spent another day sketching or made three more versions, you might have found something better.</p><p>That does not mean every project needs to drag on forever. I am a big fan of working quickly when the project benefits from it. Timed exercises can get you out of your own head, and making ten rough versions can be much more useful than obsessing over one. A quick sketch can tell you whether an idea is worth pursuing before you spend hours on it. The useful part is knowing what needs speed and what needs time.</p><p>Early experimentation can usually be fast. Try the thing, make the rough version, test the material, put a few options next to each other and see what happens. Once something starts becoming more interesting, though, it may need a little room before you decide what it is. You can leave the piece somewhere you will see it for a few days, print the design out instead of only looking at it on a screen, or make another version without immediately deciding which one is better.</p><p>I notice this a lot with design because software makes it incredibly easy to keep moving. You can change a typeface in seconds, move elements around, try another color, duplicate the whole layout, and generate twenty versions before lunch. That is great, but having twenty versions does not automatically mean you spent much time actually looking at any of them.</p><p>Sometimes it helps to stop clicking for a while. Print it out, put it on the wall, walk away from it, and come back later. You may notice something immediately that you completely missed while you were moving things around on the screen.</p><p>The same thing happens in the studio. You can keep adding to a piece because you are there and you have time, but continuing to work is not always the same thing as improving it. There are moments when the better choice is to leave it alone long enough to figure out whether it actually needs anything else.</p><p>I also think slow design has something to do with letting research become part of the work instead of treating it like the annoying thing you have to finish before you get to make something. Looking at references, reading, collecting images, studying how something was made, or spending time with a material can all change what you eventually make. If you rush through that because you want to get to the finished piece, you may end up making the idea you already had instead of finding something you had not thought of yet.</p><p>There is also a lot of pressure to make work and immediately put it somewhere. You finish something, photograph it, post it, move on to the next thing. That pace can make it harder to sit with your own work long enough to decide how you actually feel about it.</p><p>You do not have to share everything the second it is finished. You can live with it for a while, decide you hate it, realize you only like one part, or notice that it belongs with another project you have not made yet. Those things are harder to see if the whole cycle is finish, post, move on.</p><p>I think slower processes can be useful for the same reason. Drawing something by hand, making a print, building something physically, or working with a material that does not have an undo button can make you pay attention differently. You cannot always immediately fix the decision, so you tend to think about it a little more before making the next one.</p><p>That does not make analog processes automatically better than digital ones. I use both, and I like both. They just create different kinds of attention, and I think that is really what slow design is about for me. It is not about making everything take longer. It is about giving the parts of the process that need attention enough time to get it.</p><p>You can work quickly and still be thoughtful. You can also spend months on something and still avoid making any real decisions. Slow is not automatically good, and fast is not automatically bad. What matters is whether the pace is helping the work.</p><p>If you are rushing because you have a deadline, that is one thing. If you are rushing because you are uncomfortable leaving something unresolved, that is worth noticing. If you keep moving because stopping feels unproductive, it may help to remember that looking, waiting, testing, and changing your mind are all part of the work too.</p><p>Sometimes the project needs another version. Sometimes it needs another hour. Sometimes it needs to sit on the wall for a few days before you touch it again. The goal is not to make the process slower just for the sake of being slow. It is to give the work enough time to become what it needs to become.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4db28ac3c8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Hand-Drawn Illustrations Are Trending in a Digital World]]></title>
            <link>https://medium.com/@cookieredding/why-hand-drawn-illustrations-are-trending-in-a-digital-world-0b2edbe04d69?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b2edbe04d69</guid>
            <category><![CDATA[illustration]]></category>
            <category><![CDATA[design-trends]]></category>
            <category><![CDATA[analog-design]]></category>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[handdrawnillustration]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 12:04:13 GMT</pubDate>
            <atom:updated>2026-09-29T12:04:13.922Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3yL-sIPkn5z0ksiMUr2TJg.jpeg" /></figure><p>I’ve been noticing hand-drawn illustration everywhere lately. Weird little characters, scribbly lines, imperfect lettering, wonky shapes, drawings that look like somebody made them with a Sharpie five minutes before the deadline…and I am VERY into it.</p><p>Maybe part of why I’m noticing it is because I’ve been thinking so much about analog work lately anyway. Printmaking, letterpress, collage, drawing, all the things where you can actually see some evidence that a person touched the thing. But I also think hand-drawn illustration feels particularly good right now because we spend so much of our visual lives surrounded by things that are incredibly polished.</p><p>Digital tools are really good at smoothing everything out. Lines can be perfectly straight. Shapes can be mathematically identical. Colors are consistent. Type snaps into alignment. Vector illustrations can be resized forever without changing a thing, and now we can generate incredibly polished imagery in seconds. There’s obviously nothing wrong with precision. I make digital work too and would be deeply unhappy if Illustrator suddenly stopped aligning things for me. (haha!) But when everything around you starts getting smoother, the slightly weird stuff becomes a lot more interesting.</p><p>A hand-drawn line has movement in it. Maybe the pressure changes halfway through or the curve isn’t completely even. Two supposedly identical shapes come out slightly different because an actual hand had to make both of them. Even digital illustration made with a tablet can keep some of that quality if the artist lets the marks stay a little loose. I think we respond to that because you can still see the person in the work.</p><p>There’s personality in the way somebody draws a face, makes a line, writes a word, or completely ignores what a circle is technically supposed to look like. You could give ten illustrators the same simple assignment and get ten completely different versions because their hands, habits, and visual brains all show up in the result. That difference becomes pretty appealing when so much visual culture can start feeling interchangeable.</p><p>I see a similar thing happening in branding. For years there was a LOT of very clean vector illustration floating around. Smooth shapes, nice palettes, friendly little characters, everything beautifully controlled. Some of it was great, but after seeing variations of the same visual language over and over, it started getting harder to remember who actually made what. Bring in a weird little drawing and suddenly there’s something to recognize.</p><p>The hand-drawn approach can make a brand feel more casual, personal, funny, awkward, handmade, or just less corporate depending on how it’s used. It doesn’t need to literally be drawn on paper either. You can draw digitally and still keep the irregular edges, odd proportions, and marks that give the illustration some personality.</p><p>I think that distinction matters because “hand-drawn” doesn’t automatically mean “badly drawn.” There’s often a LOT of skill behind illustration that looks simple or loose. Knowing which details to leave awkward and which ones need more control is part of what makes the style work.</p><p>That comes up with students too. There can be this assumption that getting better at drawing means gradually eliminating every weird line until everything becomes technically perfect. Then I show them illustrators whose entire visual language depends on crooked lines, strange proportions, flattened space, or deliberately goofy drawings and we get to have the much more interesting conversation about style and intention. The difference is whether the wonkiness belongs there.</p><p>I love that because it opens illustration back up for people who think they “can’t draw.” You don’t necessarily need to make some beautifully rendered photorealistic image for drawing to be useful in design. A weird little ink drawing, scribble, hand-lettered word, or chunky marker shape might be exactly what the project needs.</p><p>You can also mix that stuff right back into digital work, which is probably my favorite way to use it anyway. Draw something on paper, scan it, cut it apart in Photoshop, recolor it, drop it into Illustrator, print it back out, draw over it again…eventually nobody knows what category the thing belongs to anymore and I am perfectly happy with that. That back-and-forth keeps some unpredictability in the process.</p><p>It also gives you visual material that is actually yours. Your handwriting is yours. Your goofy little way of drawing a cat is yours. The strange texture you get from your favorite pen dragging across cheap paper is yours. Those tiny quirks are incredibly hard to separate from the person making them, and I think there’s real value in that right now.</p><p>I don’t think the popularity of hand-drawn illustration means everybody suddenly hates digital design or that we’re all going to abandon our computers and start drawing advertisements with crayons. I certainly won’t be. I like having both.</p><p>What interests me is the contrast between them. I like precise typography sitting next to an imperfect drawing. I like a clean grid with one odd handmade element breaking it up. I like digital color combined with scratchy ink marks or a beautifully organized layout with an illustration that looks like somebody scribbled it in the margin of a notebook. There’s enough control to make the design work and enough evidence of the hand to keep it from feeling anonymous.</p><p>And maybe that’s why hand-drawn illustration feels particularly relevant right now. We have no shortage of ways to make something clean, fast, and technically polished. I’m increasingly interested in the things that still show how somebody makes a mark. Apparently the wobbly line is having its moment again, and I am more than happy to let it wobble.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b2edbe04d69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Importance of Visual Play in a World of Digital Precision]]></title>
            <link>https://medium.com/@cookieredding/the-importance-of-visual-play-in-a-world-of-digital-precision-3a47f6fe76a2?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a47f6fe76a2</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[play]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Mon, 16 Mar 2026 11:02:01 GMT</pubDate>
            <atom:updated>2026-09-29T11:59:15.461Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gOzxq6ELsOOlKxn_GwbVvQ.png" /></figure><p>We live in a moment where visual work can get very polished, very quickly. Grids snap into place, alignment tools do their thing, palettes get generated for us, files stay clean, and software keeps getting better at helping us make things faster and more efficiently. I do love that part. I mean, I also complain about it, but I love it. (haha!) The problem is that efficiency can take over really easily.</p><p>When every project has a deadline, an outcome, a purpose, a client, a grade, a post, or some other reason it needs to exist, play starts looking like the thing you should skip so you can get to the “real work” faster. And I think that’s where a lot of creative work starts getting a little too tight.</p><p>I’m using “play” pretty loosely here too. I don’t mean making something childish or unserious. I mean working without already knowing exactly what the result is supposed to look like. Trying something because you’re curious, making a version that might be terrible, pushing a color way too far, combining materials that probably shouldn’t go together, or taking an idea somewhere weird just to see what happens. That kind of messing around is useful because it gets you out of execution mode.</p><p>Digital tools can make it really easy to start refining before you’ve actually explored much. You open a file, set up the artboard, choose the type, align everything nicely, and suddenly the thing looks finished enough that you stop questioning it. It can feel productive because everything is neat and organized, but you might just be polishing the first idea that showed up. I absolutely do this too.</p><p>Play interrupts that a bit. If I’m cutting paper, painting, making textures, moving scraps around, or just making some ugly little composition for no particular reason, I’m much less worried about whether it is correct yet. I’m paying attention to what catches my eye and what feels interesting enough to keep following. That’s usually where the surprises happen.</p><p>And I think surprise matters more than we give it credit for, especially if you’ve been making work for a long time. It is very easy to get good at repeating what already works. You know the tools, you know your habits, you know how to solve certain problems, and eventually the whole thing can start feeling a little mechanical.</p><p>That has definitely been part of my own burnout conversations lately. Sometimes I’m not tired of making. I’m tired of making in the same way over and over again.</p><p>If I already know exactly what the piece is going to look like before I start, there’s not much left to discover. I’m basically carrying out instructions I gave myself. That can be satisfying in its own way, especially when something just needs finished, but I don’t want my entire practice to live there. Visual play gives me an excuse to break some of my own habits.</p><p>Maybe I use a material I haven’t touched in years. Maybe I make something at a scale I normally avoid. Maybe I work with a color combination I would usually reject immediately. Maybe I deliberately make a bad version first just so I stop treating the whole thing like it needs to succeed on attempt one.</p><p>I see this with students constantly too. Some of the most interesting stuff happens when they stop trying to give me the answer they think I want and start poking at the assignment a little. They bend a rule, try something odd, or stumble into a solution that wasn’t anywhere in the original plan. Those are my favorite moments to see because you can usually tell when the student realizes, “Ohhhh, I can do THAT?” And then everything opens up.</p><p>Play also changes your relationship with mistakes. If you are trying to make a polished final piece from the second you start, every weird mark or awkward decision feels like something that needs fixed. If you’re experimenting, the same thing becomes information. Maybe the accidental overlap is more interesting than the original plan. Maybe the ugly color is ugly in a useful way. Maybe the torn edge is better than the clean one you intended.</p><p>That doesn’t mean every accident becomes genius. Plenty of them are still terrible. Haha. But you’re much more likely to find something unexpected if you haven’t eliminated every possibility of being surprised.</p><p>I think physical materials make this especially obvious because they tend to push back a little. Paper tears. Ink smears. Paint behaves differently than you thought it would. Glue wrinkles things. You respond to whatever happened and keep going.</p><p>Digital play can absolutely work the same way, though. Use a brush you normally hate. Distort something too far. Make fifteen versions without worrying about whether any of them are good. Turn off the grid. Scan in some garbage from your desk. Treat Photoshop or Illustrator like a box of materials instead of a machine that expects you to make something polished. I like that way of thinking about tools a lot more anyway.</p><p>The other thing I’m trying to get better about is letting experiments stay experiments. I am very capable of making one weird little thing and immediately asking whether it should become a series, a class, something for the shop, a post, or some other project that now requires a title and a plan. That is a very efficient way to stop the play process. Some things can just be the weird thing I made Tuesday afternoon.</p><p>I don’t have to show it. I don’t have to explain it. I don’t have to turn it into content or justify the time I spent making it. It can exist because I wanted to see what happened when I put those two things together.</p><p>And usually that kind of messing around comes back into the “serious” work eventually anyway. A texture shows up somewhere else. A color combination hangs around in my head. A strange composition turns into the starting point for something larger. I don’t always know what the useful part is going to be while I’m doing it, which is kind of why it works.</p><p>Precision still matters, obviously. I like a clean file. I like good alignment. I like knowing the type is where it is supposed to be. There is a time to tighten everything up and make the final thing actually work. I just don’t think that needs to be the starting point every single time.</p><p>Sometimes I need the neat grid and sometimes I need a pile of scraps on the table, a glue stick, and absolutely no idea what I’m doing yet. The second one usually keeps the first one from getting too boring.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a47f6fe76a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Burnout Is Real…How Do We Stay Passionate About Our Work]]></title>
            <link>https://medium.com/@cookieredding/design-burnout-is-real-how-do-we-stay-passionate-about-our-work-e549fc2adfdd?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/e549fc2adfdd</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[creative-process]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Tue, 10 Feb 2026 13:01:02 GMT</pubDate>
            <atom:updated>2026-09-29T11:56:23.209Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jQp8_C93zmmnmWu3y0DgmA.png" /></figure><p>Design burnout is very real, and I think one of the hardest parts is that it can make you question whether you even like the thing you’ve spent years doing. You sit down to work and nothing sounds interesting. Every idea feels like something you’ve already done. You open the software and immediately want to close it again. Even projects you would normally enjoy start feeling like another thing that needs finished, posted, presented, revised, approved, or turned into something useful.</p><p>That’s usually when I have to remind myself that being tired of the conditions around the work is not necessarily the same thing as being tired of the work itself. For me, burnout tends to show up when everything gets too optimized and too productive. There’s always a deadline, a deliverable, a class, a client, a post, a shop update, a presentation, or some other reason the thing needs to exist. After a while, even creative work starts feeling like a checklist, and that is absolutely when I stop wanting to do it.</p><p>One thing that helps is changing the process instead of immediately deciding I need an entirely new direction in life. Maybe I work on paper instead of the computer for a while. Maybe I start with collage, sketching, printmaking, or something that doesn’t have a clear end point. Sometimes I just need to use a different part of my brain for a bit.</p><p>I also notice a huge difference when I stop constantly producing and actually put something back in. If all I’m doing is making, teaching, posting, answering, revising, and moving on to the next thing, eventually there’s not much left to pull from. That’s usually when I need to go look at stuff: a museum, a weird book, an old design annual, a thrift store, some terrible packaging from 1987, a walk somewhere, anything that has nothing to do with whatever I’m currently supposed to be making. I’m not looking for “content” or trying to turn it into research. I just need to see things that wake my brain up a little.</p><p>Burnout also gets worse when work starts leaking into every part of the day. This is one I am still spectacularly bad at because there is ALWAYS something I could be doing. There’s an email I could answer, a page I could update, something I could grade, a project I could work on for another hour, and that list will happily keep going forever if I let it.</p><p>At some point I have to decide that the existence of more work does not mean I am required to keep doing it indefinitely. I’m getting better at putting limits around what gets my attention, even if I am not always particularly elegant about it.</p><p>The other thing I keep coming back to is making things that have absolutely no job. This has become a bigger deal for me lately because I’m very good at assigning a purpose to everything I make. Could I sell it? Could it become a class? Is it part of a series? Should I photograph it? Does it belong in the shop? Is there a post in this?</p><p>Thinking that way can suck the fun out of something before I’ve even started, so I’ve been trying to leave a little room for things that are allowed to be completely useless. A weird print. A collage that goes nowhere. A book made for no particular reason. Something that never gets posted and doesn’t need to turn into anything else. That kind of making helps me remember why I liked doing this in the first place.</p><p>It also helps to figure out what I’m actually tired of because “I’m burned out” can mean about fifty different things. Maybe I’m sick of staring at screens, tired of revisions, overloaded from making too many decisions, or simply exhausted by being visible and constantly putting work out into the world. Those are very different problems, so it helps to know which one I’m actually dealing with before deciding I need to blow up my entire creative practice.</p><p>If I’m exhausted by client feedback, making something personal might help. If I’m tired of the computer, I probably need to go make something physical. If I’m simply running on empty, the answer might be that I need to stop making for a little while instead of trying to bully myself back into being inspired.</p><p>I don’t really believe you can force passion back by working harder because that has never worked especially well for me. What usually helps is changing the conditions enough that curiosity has room to show back up. Less pressure, a different tool, better boundaries, more input, or something completely pointless that I make because I felt like it.</p><p>When design starts feeling like a chore, I try not to immediately assume I’ve fallen out of love with it. Most of the time, I’m just tired of the way I’ve been doing it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e549fc2adfdd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Design and Design Thinking in the Classroom (Even If You Don’t Teach Design)]]></title>
            <link>https://medium.com/@cookieredding/using-design-and-design-thinking-in-the-classroom-even-if-you-dont-teach-design-a53216616dfa?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/a53216616dfa</guid>
            <category><![CDATA[higher-education]]></category>
            <category><![CDATA[design-education]]></category>
            <category><![CDATA[pedagogy]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 22:24:31 GMT</pubDate>
            <atom:updated>2026-01-26T22:24:31.985Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3Otff1WO4Bpj6dlkwxLcA.png" /></figure><p>When people hear the phrase “design thinking,” they often picture Post-it notes, whiteboards, colorful markers, and maybe a Silicon Valley startup energy that doesn’t always feel like it belongs in a classroom. Especially not in a history course, a science lab, a writing seminar, or a healthcare program. Design gets framed as a specialty skill, something visual, something aesthetic, or something reserved for creative majors.</p><p>But design, at its core, is not about making things look good.</p><p>Design is about <strong>how we approach problems</strong>, how we frame questions, how we move from uncertainty to clarity, and how we test ideas without needing to get everything right the first time. When you strip it down to that level, design thinking becomes incredibly useful across disciplines. Not as a trend. Not as a rigid framework. But as a mindset that helps students think more clearly, work more intentionally, and feel less paralyzed by the pressure to be perfect.</p><p>In the classroom, design thinking isn’t about turning students into designers. It’s about helping them become better thinkers, communicators, collaborators, and problem-solvers in whatever field they’re moving toward.</p><h3>Design Thinking Is a Way of Thinking, Not a Formula</h3><p>One of the biggest misconceptions about design thinking is that it’s a step-by-step process you’re supposed to follow perfectly. Empathize. Define. Ideate. Prototype. Test. Those words show up everywhere, and while they can be helpful, they can also make the whole thing feel rigid or performative.</p><p>In practice, real design thinking is messy. You jump backward. You skip steps. You sit in uncertainty longer than you planned. You revise after you thought you were done. That messiness is actually what makes it so useful in learning environments. When students are taught that learning is linear, they often panic when their first idea doesn’t work. When design thinking is introduced as an iterative process, students start to understand that confusion is not failure. It’s information.</p><p>This shift alone can change the tone of a classroom. Students stop asking, “Is this right?” and start asking, “What happens if I try this?” That question works just as well in engineering, writing, business, education, or healthcare as it does in a design studio.</p><h3>Why Design Thinking Works Across Disciplines</h3><p>At its heart, design thinking prioritizes <strong>process over outcome</strong>. That’s powerful in any field where students are expected to grapple with complex ideas, ambiguous problems, or real-world constraints. For example, in a science classroom, design thinking helps students approach experiments as systems that can be adjusted rather than procedures that must be followed exactly. In a writing course, it reframes drafts as prototypes instead of evidence of skill or failure. In education programs, it helps future teachers design learning experiences with empathy for students rather than defaulting to how they themselves learned.</p><p>Design thinking also normalizes iteration (you all know that’s one of my favorite things to do in class!). Instead of one high-stakes submission, students are encouraged to develop ideas in stages. They test assumptions, get feedback, and revise. This mirrors how work actually happens outside of school, which makes learning feel more relevant and less artificial.</p><p>Another reason design thinking travels so well across disciplines is that it values <strong>multiple kinds of intelligence</strong>. Visual thinking, verbal reasoning, spatial awareness, emotional intelligence, systems thinking… all of these are valid ways of engaging with a problem. When classrooms embrace this, students who might struggle with traditional academic structures often find new ways to participate and succeed.</p><h3>Empathy Isn’t Soft… It’s Strategic</h3><p>Empathy is often the most misunderstood part of design thinking, especially in non-design fields. It can sound vague or overly emotional if it’s framed poorly. But in practice, empathy is about understanding context before making decisions.</p><p>In the classroom, empathy shows up when students are asked to consider who they are designing something for, who is affected by a decision, or whose perspective is missing. This is just as relevant in policy analysis, healthcare, social work, and engineering as it is in graphic design. When students are taught to begin with empathy, they learn to slow down and gather information before jumping to solutions. They learn that their first instinct is not always the most informed one. This builds critical thinking in a way that lectures alone often cannot.</p><p>Empathy also encourages ethical thinking. Students begin to see that choices have consequences, and that good solutions are rarely neutral. This is especially important in fields that deal with public impact, technology, or systems that shape people’s lives in meaningful ways.</p><h3>Framing Problems Instead of Chasing Answers</h3><p>Traditional education often rewards students for finding the correct answer as efficiently as possible. Design thinking flips that emphasis and asks students to spend more time <strong>framing the problem itself</strong>.</p><p>What is actually being asked here?<br> What assumptions are built into this question?<br> Who benefits from this framing?<br> What happens if we reframe it?</p><p>These questions are valuable everywhere. In research, they lead to better inquiry. In business, they prevent costly missteps. In writing, they lead to stronger arguments. In education, they create more inclusive learning environments. When students are allowed to explore multiple ways of defining a problem, they become more comfortable with complexity. They stop seeing ambiguity as something to avoid and start seeing it as something to work with.</p><h3>Prototyping as a Learning Tool</h3><p>One of the most classroom-friendly aspects of design thinking is prototyping. A prototype is simply a version of an idea that exists so it can be tested and discussed. It is not meant to be final. It is meant to be useful.</p><p>In non-design classrooms, prototypes can take many forms. A rough outline. A concept map. A lesson plan draft. A mock presentation. A low-stakes experiment. The key is that students understand the work is unfinished by design. This removes a lot of fear. Students are more willing to try bold ideas when they know they’re not being graded on polish. They become more open to feedback because the work isn’t tied to their identity or self-worth.</p><p>Prototyping also makes thinking visible. Instead of keeping ideas in their heads until the last minute, students externalize their thinking earlier. This gives instructors more opportunities to guide, redirect, and support learning in real time.</p><h3>Feedback as Dialogue, Not Judgment</h3><p>Design thinking reframes feedback as part of the process rather than a final verdict. This can dramatically change how students experience critique, peer review, and assessment. When feedback is introduced early and often, students stop seeing it as punishment. They begin to see it as information they can use. This is especially important for students who have internalized perfectionism or fear failure.</p><p>Instructors can model this by asking questions instead of giving directives. What are you trying to explore here? What feels unresolved? Where do you think this could go next? These questions invite reflection rather than defensiveness. Peer feedback also becomes more meaningful when it’s tied to process. Students learn how to articulate what they see, what they don’t understand, and what possibilities they notice. These are transferable skills that matter far beyond the classroom.</p><h3>Design Thinking Builds Confidence Without Inflating Ego</h3><p>One of the quiet benefits of design thinking in education is how it builds confidence. Not the fragile kind that depends on grades or praise, but the steadier kind that comes from knowing how to work through uncertainty. Students who engage in iterative processes learn that they can recover from mistakes. They learn that not knowing is a temporary state, not a personal flaw. Over time, this reduces anxiety and increases resilience.</p><p>This confidence shows up in how students talk about their work. They become better at explaining their choices, reflecting on their process, and acknowledging growth. These skills matter in job interviews, graduate school applications, and professional practice of all kinds.</p><h3>You Don’t Need to Overhaul Your Course to Use Design Thinking</h3><p>One of the reasons educators hesitate to adopt design thinking is the belief that it requires a complete course redesign. In reality, small shifts often have the biggest impact.</p><p>Inviting students to sketch ideas before writing.<br> Allowing revisions after feedback.<br> Asking students to explain their decision-making.<br> Framing assignments as explorations rather than performances.<br> Making space for reflection alongside content mastery.</p><p>These are design thinking moves, even if you never use the term. Design thinking is less about adding something new and more about <strong>changing how learning unfolds</strong>. It encourages curiosity over compliance, process over perfection, and engagement over efficiency.</p><h3>So… How Do You Actually Use It in Your Classroom?</h3><p>This is usually the moment where design thinking starts to feel abstract again. It sounds great in theory, but translating it into day-to-day teaching can feel fuzzy, especially if you don’t teach something that looks like “design” on the surface. The good news is that you’re probably already doing pieces of this without naming it. The shift is less about adding new content and more about reframing how students move through learning.</p><p>In a writing or humanities classroom, design thinking often shows up through drafting and reframing. Instead of treating a paper as a single polished artifact, the assignment becomes a process. Students start with rough ideas that might be messy or incomplete. They test arguments early, get feedback, and revise with intention. Asking students to articulate who their audience is and what they want that audience to understand introduces empathy without turning it into a buzzword. Writing becomes less about proving intelligence and more about communicating ideas clearly and thoughtfully.</p><p>In history or social sciences, design thinking can shape how students approach research questions. Rather than assigning a narrow topic and a fixed thesis from the start, students can be encouraged to explore context first. What problem or tension existed at this moment in time? Whose perspectives were centered and whose were ignored? How might this issue look different if you viewed it through another group’s experience? This kind of framing slows students down in a productive way and leads to deeper, more nuanced analysis.</p><p>In science and engineering courses, design thinking naturally aligns with experimentation and iteration. When labs or projects are framed as prototypes instead of one-shot performances, students feel more comfortable taking intellectual risks. A failed experiment becomes data instead of a dead end. Reflection becomes part of the learning, not an afterthought. Students start to understand that refining a method or questioning assumptions is part of real scientific work, not a sign they did something wrong.</p><p>In business, marketing, or entrepreneurship courses, design thinking supports ideation and decision-making. Students can be encouraged to test ideas early, gather feedback, and revise before committing to a final direction. This mirrors how work actually happens outside the classroom. It also helps students understand that good ideas are rarely fully formed at the beginning. They evolve through use, critique, and reflection.</p><p>Even in more technical or skills-based courses, design thinking can show up in how assignments are structured. Breaking projects into phases, allowing for revision, and asking students to explain their choices shifts the focus from completion to understanding. When students can talk about why they made certain decisions, they’re demonstrating learning at a deeper level than simply following instructions.</p><p>Across all of these disciplines, one of the most important shifts is how feedback is positioned. Instead of feedback arriving only at the end as a judgment, it becomes part of an ongoing conversation. Students learn that feedback is not something to fear or avoid, but something that helps them move forward. This alone can change classroom culture in powerful ways.</p><p>Using design thinking in the classroom does not require a complete overhaul of your course. It often starts with small changes. Allowing rough work to exist. Making space for reflection. Valuing process alongside outcome. Giving students permission to not know right away. When students experience learning this way, they begin to trust the process. They become more willing to engage, to revise, and to think critically about their own work. And regardless of discipline, that is a skill they will carry with them long after the semester ends.</p><h3>Why This Matters Right Now</h3><p>Students are navigating a world that is increasingly complex, uncertain, and interconnected. They need more than content knowledge. They need ways of thinking that help them adapt, collaborate, and respond thoughtfully to change. Design thinking offers a flexible, human-centered approach to learning that meets students where they are and prepares them for what comes next. It reminds us that learning is not about arriving at the right answer as quickly as possible, but about developing the capacity to ask better questions and build better responses over time.</p><p>When design thinking is integrated into classrooms across disciplines, it doesn’t dilute academic rigor. It deepens it. It makes learning more meaningful, more inclusive, and more connected to the realities students will face beyond school.</p><p>And maybe most importantly, it reminds students that their thinking matters… not just the final product they turn in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a53216616dfa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Power of Process: Teaching Students to Think Like Designers]]></title>
            <link>https://medium.com/@cookieredding/the-power-of-process-teaching-students-to-think-like-designers-0edc80949c0a?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/0edc80949c0a</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[design-pedagogy]]></category>
            <category><![CDATA[design-teaching]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Wed, 12 Nov 2025 17:24:58 GMT</pubDate>
            <atom:updated>2025-11-12T17:24:58.714Z</atom:updated>
            <content:encoded><![CDATA[<p>Here we go! This month’s topic is one of my favorites because it’s where everything clicks in the classroom. When students learn to think like designers, the work changes, the conversations change, the confidence changes. You start to see that shift from turning in assignments to building ideas. The Power of Process sounds lofty, but at its core it is simple. We teach students to notice, to name, to test, to revise, and to share. We help them slow down just enough to see what they are actually making and why it matters.</p><p>Thinking like a designer is not about perfect software skills or a specific aesthetic. It is about how you move through a problem. It is the mindset that says<em> let me understand the context before I jump to a solution… let me try a few directions before I fall in love with the first one… let me invite feedback and use it… let me document my steps so I can learn from them next time.</em> When you center your course on process, you give students something they can carry into any medium and any career. The tools will change. The platforms will come and go. A strong process stays useful.</p><p>I like to begin by naming the habits we are actually building. Curiosity. Observation. Framing a clear problem. Research that is more than a quick search. Sketching to think, not just to show. Iteration that produces visible change. Feedback that is specific and kind. Reflection that is honest and short. These are not lofty ideals tucked into a syllabus. They are small repeatable moves we practice every week. I tell students that their best work will come from letting the work lead from noticing what the work is asking for to responding to what is actually on the page or screen, not the idea in their head. That noticing is a skill. You cultivate it by making, by looking, by talking out loud about what you see.</p><p>Process needs structure, so I map the arc of a project with clear milestones. Discover, Discuss, Design. In Discover, we set the stage. What is the problem. Who is it for. What are the constraints. What are three different directions that could be valid. We collect references with intention and write down what we are learning. In Discuss, we bring early versions into the room. We talk through choices. We ask: what is working right now and why? Where do you want this to go next? In design, we commit to a direction and push it forward, documenting changes as we go. The point is not to slow everything to a crawl. The point is to give students a rhythm so they do not panic or stall or rush to polish too soon. A simple rhythm lets them focus on the making.</p><p>You can teach this rhythm with very small tasks. Ten minute composition studies with only three shapes. A color remix where the goal is to change the mood of an image using only value and saturation. A typography sprint where you try three different visual hierarchies for the same content, then talk through what each one emphasizes. Short challenges like these teach students to explore on purpose. They learn that speed is useful when it gathers options, not when it rushes a final. They learn to separate generating from judging. They also learn to see that there is never just one answer. That idea alone takes so much pressure off. If there are many valid solutions, then the job is to make a strong case for one and be able to show how you got there.</p><p>Critique is an anchor for process, but it has to be built with care. I coach students to describe before they evaluate. Ex: tell me what you see, tell me how your eye moves, tell me where the hierarchy is strong and where it collapses. Then we can talk about intent:<em> what did you want the viewer to notice first? What did you want them to feel? What action did you want them to take?</em> The critique becomes a shared investigation rather than a quick verdict. I also ask for small, specific next steps. Not a full redesign… just one change that will move the work forward. Then one more. When students leave the room with a clear next step, they are more likely to keep going.</p><p>Documentation is often the missing piece, so I make it part of the grade. It does not need to be fancy. A simple process journal works. One page per work session with a date, a sentence about the goal for that session, a screenshot or photo of what changed, and a sentence about what you learned. That is it. Over a few weeks, that journal becomes gold. Students can see their progress and they can track decisions. They can return to abandoned ideas that might be perfect for a future project. When they build a portfolio, that journal gives them language for their case studies. Employers love to hear how you think, not just what you made.</p><p>Assessment shifts when you value process. I still care about outcomes… we all do. But I make room for growth. If a student takes a messy start and turns it into a thoughtful final through consistent iteration, that improvement counts. If they can explain why they made a choice and show me the alternatives they tested, that counts. You can design rubrics that reflect this balance. Weight clarity of problem framing, quality of exploration, responsiveness to feedback, and strength of final execution. Name those categories in class so everyone knows what matters. You get fewer surprises at grading time and more focus across the project.</p><p>Constraints help. Students sometimes think that creativity is a blank page, when in reality constraints are what get us moving. Limit the color palette. Set a type system. Fix the aspect ratio. Cap the number of elements. Give them a clear audience or scenario. The constraint is not a cage, it is a prompt. Once they start to work within a boundary, they learn how to push against it with intention. They also see that design is about choosing, not adding. Most of the time, the best move is subtraction. Fewer styles. Fewer focal points. More space. Cleaner relationships. When students experience the relief that comes with editing, they begin to trust the process.</p><p>Because our tools are digital and analog, I ask students to move between them. Sketch on paper, then translate to screen. Print the in progress version at actual size and mark it up with a pen. Photograph a layout and squint to check hierarchy. Read your headline out loud. Put your phone six feet away and glance at the work like a passerby. Each shift of medium or viewing distance reveals something new. Process is not just a timeline but as a set of repeated vantage points. You teach students to cycle through those vantage points on purpose.</p><p>Feedback can come from more than the teacher. I build short peer reviews with guardrails. Two minutes to explain your intent. Two minutes for the peer to describe what they see. Two minutes together to name one concrete change to test before the next class. That is it. Quick and clear. I also encourage students to ask one question with their work. Not what do you think (that is too broad). Ask:<em> is my focal point obvious in the first three seconds, or does this color palette support the mood I described? </em>A focused question leads to a focused answer. Over time, students learn to generate better questions and that is a core design skill.</p><p>Reflection is the last move before submission. I keep it short. Three sentences. What did you change since the last critique and why. What still needs work if you had more time. What did you learn here that you can carry to the next project. Those reflections are small but powerful. They help students close a loop not just hit upload. They also give you useful insight into how they are thinking. You can respond to their reflections in the margins and keep the conversation going.</p><p>If you are teaching across a semester, you can weave process into a bigger arc. Early projects build vocabulary and comfort with iteration. Mid semester work adds research and audience awareness. Late projects ask for stronger concept and more independent decision making. By the end, students can show three things. I can define a problem with clarity. I can explore multiple directions and make reasoned choices. I can deliver a final that communicates effectively for an audience. When they can show those three things, they are ready for most creative environments.</p><p>One of the myths I like to unlearn is that creativity is a flash of inspiration that hits at random. Students wait for the perfect idea and then feel stuck when it does not arrive. The antidote is process. You start with a small move and another and another. You build a set of options and ideas emerge from doing the work. You listen to the work. It tells you what it wants whether it be a shift in scale, a calmer color, a bolder type choice, etc. When students experience that dialogue, they stop waiting and start making. That is the moment where their confidence grows.</p><p>Technology fits into this story as a set of tools, not the star of the show. I teach software with a purpose. We learn a technique because it solves a problem we have named. We try two ways to achieve the same result and talk about tradeoffs. We look at how a design system can speed up iteration. We talk about file organization and versioning so that process is manageable. Tools should support decision making. If a tool gets in the way, we simplify. There is no prize for using the most complex method.</p><p>Equity sits at the heart of process too. Not every student comes in with the same background or the same access to resources. A process based class makes room for many paths to a strong result. You can meet students where they are and help them move forward. You can value effort and growth without lowering standards. You can give students multiple ways to show what they know via sketches, annotated screenshots, and voice memos that explain a choice. When you widen the ways students can work through an idea, you unlock voices that might have stayed quiet.</p><p>If you want to build a culture around process, start with your own modeling. Narrate your thinking out loud. Show a messy first pass. Bring a failed attempt and explain why it failed and what you would try next. Students need to see that design is not a straight line. They also need to see an adult handle critique with curiosity instead of defensiveness. When you show that posture, they mirror it. The room gets kinder and braver at the same time.</p><p>I also find it helpful to connect projects to real audiences when possible. A poster for an on campus event. A small identity system for a student club. A social post for an arts program. When the work has a home, the process feels grounded. Students practice asking better questions at the start because the answers will affect a real person. They practice iteration because the client needs options. They practice presenting because someone outside the class will review the results. The energy changes and students see how their decisions land in the world.</p><p>If you are wondering how to get started, you do not need to overhaul your whole course. Choose one project and add two or three process checkpoints. Ask for a problem statement. Require three distinct directions before converging. Build a mini critique with one clear next step. Add a one page reflection at the end. That is enough to feel the shift. You will see more thoughtful choices and fewer last minute scrambles. You will have richer conversations. You will have an easier time grading because you saw the work evolve.</p><p>The Power of Process is not a slogan. It is a daily practice. It teaches students to trust that they can find their way through ambiguity. It reduces the drama around perfection and replaces it with momentum. It turns your classroom into a studio where ideas are tested in public and improved together. When students leave a course like that, they take the habits with them into internships, into jobs, and into their own creative practice. They know how to begin (how to keep going!) and also how to finish with intention.</p><p>If you are already teaching this way, keep refining your rhythm. If you are just starting, try one small change and watch what happens. When we teach students to think like designers, we are teaching them how to make decisions, how to communicate, and how to stay curious. That is the real power of process. It shapes the work, but more than that… it shapes the person who makes the work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0edc80949c0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Bauhaus Movement: Why It Still Shapes Your Social Media Feed Today]]></title>
            <link>https://medium.com/@cookieredding/the-bauhaus-movement-why-it-still-shapes-your-social-media-feed-today-b5298ff896a9?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5298ff896a9</guid>
            <category><![CDATA[design-education]]></category>
            <category><![CDATA[design-history]]></category>
            <category><![CDATA[bauhaus]]></category>
            <category><![CDATA[modernism]]></category>
            <category><![CDATA[graphic-design]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Fri, 24 Oct 2025 21:50:35 GMT</pubDate>
            <atom:updated>2025-10-24T21:50:35.335Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever scrolled through your feed and stopped on a clean layout with bold type, sharp geometry, or a perfectly balanced grid, you’ve quietly thanked the Bauhaus. You might not realize it, but that little moment of “ah, this looks good” is the work of an idea that started more than a century ago. We started our chats about this in my classes last week, and I thought it’d be fun to chat about here as well. So let’s just jump in!</p><p>The Bauhaus wasn’t just a school. It was a mindset. Founded in 1919 in Weimar, Germany, it grew out of a need to rebuild after the First World War. The world had been shaken, and artists and designers were asking what role creativity should play in a society that was trying to start over. Their answer was simple but radical: art and design should be for everyone.</p><p>That idea might sound obvious now, but at the time, art was still divided into “fine” and “applied.” You painted or sculpted and were taken seriously, or you made furniture and wallpaper and were not. The Bauhaus broke that barrier wide open. It said that a chair or a typeface could be as meaningful as a painting. That philosophy changed everything about how we see design today.</p><p>If you look at your phone screen, that minimal app icon layout, or the clarity of the text in your favorite productivity app, you’re looking at Bauhaus thinking in motion. The clean lines, limited color palettes, and geometric simplicity that we associate with modern design are direct descendants of what Walter Gropius and his students were doing in the 1920s. They stripped design down to function and balance.</p><p>The Bauhaus believed that beauty came from usefulness. It wasn’t about decoration or style for its own sake. It was about how something worked in harmony with its form. That principle is baked into the interfaces and brand systems that rule the digital world. Every “simple” thing on your screen has gone through countless decisions based on that same logic: make it clear, make it purposeful, make it easy to understand.</p><p>Typography is one of the clearest examples. When you see bold sans serif fonts in clean black and white compositions online, you’re seeing echoes of Herbert Bayer’s experiments at the Bauhaus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*RxpWQsKACAz3cUodH-CA7A.jpeg" /><figcaption>By Fred the Oyster, CC BY-SA 4.0, <a href="https://commons.wikimedia.org/w/index.php?curid=35903282">https://commons.wikimedia.org/w/index.php?curid=35903282</a></figcaption></figure><p>He designed type to be readable and universal. No frills, no hierarchy between uppercase and lowercase. Just text as communication. That idea still drives how designers think about readability in everything from Instagram stories to website headers.</p><p>Color theory too. Johannes Itten’s color wheel and his emotional approach to hue are still part of every design education. The way you use contrast to make a post pop or maintain balance across a layout connects straight back to his lessons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*9PsIIxxIo2ooxSlU6enRgQ.jpeg" /><figcaption>source: <a href="https://www.getty.edu/research/exhibitions_events/exhibitions/bauhaus/new_artist/form_color/color/">https://www.getty.edu/research/exhibitions_events/exhibitions/bauhaus/new_artist/form_color/color/</a></figcaption></figure><p>What he taught wasn’t just about color combinations but how color creates feeling and rhythm. That’s why so many brands lean into limited palettes with intention… a quiet nod to the Bauhaus insistence that restraint leads to clarity.</p><p>Even the way you organize information on a social post or website grid carries that lineage. László Moholy-Nagy’s experiments with photography and graphic composition built the foundation for modern visual hierarchy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*gcQPVSJYihXZmCjBnbtFiw.jpeg" /><figcaption>By Sailko — Own work, CC BY 3.0, <a href="https://commons.wikimedia.org/w/index.php?curid=65430650">https://commons.wikimedia.org/w/index.php?curid=65430650</a></figcaption></figure><p>The idea that you can guide someone’s eye through composition (in this case, not by shouting for attention but by arranging information logically and visually) is a Bauhaus inheritance that lives in every scroll and swipe.</p><p>The irony is that what began as an anti-elitist, communal experiment in a small school in Germany has become the global aesthetic standard for billion dollar tech platforms. The clean minimalism that feels “modern” or “premium” started as a rebellion against clutter and excess. It was a move toward honesty in materials and design. Now it shows up in everything from the Apple website to your favorite wellness brand’s Instagram grid.</p><p>But the deeper reason the Bauhaus still matters goes beyond visuals. It’s the way it treated creativity as a bridge between art, technology, and life. The Bauhaus believed that the designer’s job was to connect people to the world around them in meaningful ways. That connection… the desire to make something functional and beautiful at once… is still the challenge every creative faces. Whether you’re laying out a zine, posting a digital collage, or editing a video for your portfolio, you’re solving the same question: how can design communicate clearly without losing its soul?</p><p>Every generation rediscovers the Bauhaus because its ideas feel timeless. Its minimalism isn’t just a trend. It’s a reflection of the ongoing search for balance between clarity and emotion, logic and play, structure and spontaneity. The Bauhaus didn’t just define a look. It gave us a framework for thinking about design as a living language… one that still evolves, pixel by pixel.</p><p>Next time you post something and notice how the layout feels “just right,” remember that you’re part of that conversation. Every choice you make about type, color, and composition carries traces of a century old dialogue between artists who believed that good design could make the world better.</p><p>And maybe, just maybe, it still can.</p><p><strong><em>Interested in digging in a bit more on the Bauhaus and design? Here’s some further reading:</em></strong></p><p><a href="https://www.thriftbooks.com/w/the-abcs-of-bauhaus-the-bauhaus-and-design-theory_ellen-lupton_princeton-architectural-press/838414/?resultid=15993099-3342-406e-81c4-7e118e5becd1#edition=3310174&amp;idiq=27776776"><em>The ABCs of Bauhaus: The Bauhaus and Design Theory</em></a> by Ellen Lupton and J. Abbott Miller — a really accessible, design-forward look at how Bauhaus thinking shows up in typography, layout, and education today. (one of my favs to share in class, too..so win/win!)</p><p><a href="https://a.co/d/hwMTTzT"><em>Bauhaus Women: A Global Perspective</em> </a>by Elizabeth Otto and Patrick Rössler — the Bauhaus wasn’t just about Gropius and the big names. This one gives space to the women who were often written out of the story but whose work shaped textiles, photography, and more.</p><p><a href="https://a.co/d/eFXzE4G"><em>Bauhaus (updated edition)</em></a><em> </em>by Magdalena Droste — probably the most comprehensive and beautifully illustrated overview. It walks you through the school, the key figures, and the experiments that shaped modern design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5298ff896a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I Still Teach Visual Hierarchy First]]></title>
            <link>https://medium.com/@cookieredding/why-i-still-teach-visual-hierarchy-first-5e10ba1ae6de?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e10ba1ae6de</guid>
            <category><![CDATA[graphic-designer]]></category>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[design-teaching]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Thu, 11 Sep 2025 12:13:04 GMT</pubDate>
            <atom:updated>2025-09-11T12:13:04.385Z</atom:updated>
            <content:encoded><![CDATA[<p>When I walk into a new semester and meet a fresh group of students, I always know the question that’s sitting just below the surface. They’re wondering when we’re going to dive into the fun stuff. They want to learn the tools, the software, the tricks that will make their work look polished and professional. And don’t get me wrong…I get the excitement. Who doesn’t want to learn how to use Photoshop or Illustrator or figure out how to make their work look like what they’ve been saving on Pinterest? But before we touch any of that, I bring the class back to something much more basic. We start with visual hierarchy. Every time.</p><p>Visual hierarchy might sound dry compared to color or typography or branding. It doesn’t have the same flash. But it’s the backbone of design. Without hierarchy, design is just decoration. It doesn’t communicate. It doesn’t guide anyone through an idea. It doesn’t hold together. And what I’ve seen over and over , both in my own work and in the classroom, is that when students grasp hierarchy, everything else starts to click.</p><p>I teach hierarchy first because it’s the one concept that ties everything else together. It doesn’t matter if you’re building a website, designing a poster, laying out a book, or even setting up a social media graphic. If the hierarchy isn’t there, the message falls apart. People don’t know where to look. They don’t know what matters most. They get lost in the noise. But when hierarchy is working, it feels almost invisible. The eye moves naturally from one thing to the next, and the design carries the message without the viewer even realizing it.</p><p>In class, I see students light up the first time they notice this. I’ll put two versions of the same layout side by side . The first one is where the text all looks the same and everything competes for attention, and another where the scale and placement have been adjusted to lead the eye. Suddenly, they see it. They realize that hierarchy isn’t about rules or restrictions. It’s about clarity. It’s about giving the viewer a path. It’s about deciding what matters and making sure that message comes through.</p><p>There’s a tendency, especially for beginners, to get caught up in decoration. They want to throw in textures, add extra shapes, use the fanciest fonts they can find. And sometimes they resist hierarchy because they think it’s too simple. They think bigger headlines and smaller text is obvious. But what they don’t realize yet is that hierarchy is what makes all that other stuff work. Color and type and images don’t mean anything if the viewer can’t figure out where to start.</p><p>In my own work, I notice this too. Whether I’m putting together a lecture slide, designing something for CPAD, or making art for my studio practice, I find myself leaning on hierarchy almost instinctively. It doesn’t matter how experimental or playful the piece is…there’s always a question of what needs to be seen first, second, and last. Hierarchy keeps me grounded when I want to push the edges. It’s the structure that allows experimentation to actually be legible.</p><p>I’ve had colleagues ask me why I don’t start with color theory, or why I don’t lead with typography since type is the basis of so much design. Those things are essential, and we get to them quickly. But hierarchy is the framework that holds them up. You can know all the color rules in the world, but if everything in your design screams at the same volume, the colors won’t save it. You can use the most beautiful typeface, but if you don’t organize the information, the words won’t land. Hierarchy is what makes those choices meaningful.</p><p>Sometimes students push back. They’ll say that in the real world, people break hierarchy all the time. And they’re right. A lot of contemporary design plays with flattening hierarchy or intentionally disrupting it. But here’s the thing: you can’t break hierarchy well until you understand it (just like grids!). If you start from chaos, it’s just noise. If you start from clarity, then you can bend and stretch it in interesting ways. That’s where it becomes a tool for expression instead of just a rule you’re following.</p><p>Hierarchy also translates beyond design. It’s something students can use in any creative or professional setting. When you write an email, when you make a presentation, when you put together your resume …hierarchy is what guides people through your ideas. I’ve had students tell me later that they finally understood why their social media posts weren’t working, or why their presentations didn’t land, and it all came back to hierarchy. Once they learned to control it, everything else started to feel less overwhelming.</p><p>I think part of the reason I still teach hierarchy first is because it’s also the most democratic of design principles. You don’t need fancy software to learn it. You don’t even need a computer. You can grab a piece of paper, sketch out blocks of text and images, and experiment with order and emphasis. You can cut things out and rearrange them. You can try it with handwriting. Hierarchy belongs to everyone, no matter their resources. And that makes it an accessible entry point, especially in classrooms where not every student has access to the same tools.</p><p>When I look back at my own education, I can see how hierarchy shaped my understanding of design long before I even had the vocabulary for it. As a kid making flyers or zines, I didn’t know I was practicing hierarchy, but I was figuring out what needed to stand out, how big the headline should be, and how to make sure people noticed the important information. Later, when I had formal training, it felt like someone finally handed me the language for what I’d already been experimenting with. That’s why I think it’s so important to pass it on to my students early. It gives them the language for something they’ve probably already sensed but haven’t articulated.</p><p>Even after years of teaching, it still surprises me how quickly hierarchy changes student work. The first projects always show the biggest leaps. In one week, you can see someone go from flat, confusing layouts to designs that actually communicate. And that change doesn’t come from learning new software features or memorizing technical steps. It comes from learning to see. That shift in seeing …just even understanding how the eye moves across a page, how scale and contrast work together…that’s what sticks with them.</p><p>Design trends will always change. Tools will evolve. Right now it’s Figma and Canva, before that it was InDesign and Photoshop, and before that it was paste-up boards and X-Acto knives. But hierarchy doesn’t change. It’s timeless. It’s as relevant to an Instagram story as it is to a Renaissance manuscript. And that’s why I still put it first. Because when students leave the classroom and enter a design world that’s constantly shifting, they’ll need something stable to hold onto. Hierarchy gives them that.</p><p>At the end of the day, my job as an educator is to prepare students not just to make something that looks good, but to make something that works. And design that works starts with hierarchy. That’s why I’ll keep teaching it first. Not because it’s flashy, not because it’s trendy, but because it’s the foundation that everything else builds on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e10ba1ae6de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nope, Comic Sans Isn’t Evil. It Just Needs Better PR.]]></title>
            <link>https://medium.com/@cookieredding/nope-comic-sans-isnt-evil-it-just-needs-better-pr-4af232c2a8a2?source=rss-f1dfc0e1956------2</link>
            <guid isPermaLink="false">https://medium.com/p/4af232c2a8a2</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[graphic-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[graphic-designer]]></category>
            <dc:creator><![CDATA[Cookie Redding - Artist, Designer & Educator]]></dc:creator>
            <pubDate>Sun, 20 Jul 2025 15:34:35 GMT</pubDate>
            <atom:updated>2026-09-29T11:53:10.015Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Debunking a design myth that won’t die.</em></strong></p><p>There are few things that unite designers quite like hating Comic Sans. It’s become a design-world punchline. You see the font, and you already know the reaction …mockery, judgment, maybe even a full-body cringe.</p><p>But if you stop and really think about it, what did Comic Sans actually do wrong? It didn’t crash your computer. It didn’t spread malware. It didn’t force anyone to use it in a memorial slideshow. It’s just a typeface. And it wasn’t trying to be cool. It wasn’t trying to be Helvetica. It was trying to be friendly.</p><p><strong>So where did things go sideways?</strong></p><p>Comic Sans was created in 1994 by Vincent Connare at Microsoft. It was designed to be used in speech bubbles within a software called Microsoft Bob, a short-lived user interface that aimed to make computers more accessible — especially to kids and casual users. Connare noticed that the typeface being used in the software’s cartoon dogs and playful UI was Times New Roman, which, even back then, felt wildly out of place. So he made something more appropriate…something casual, approachable, and comic-inspired. Hence, Comic Sans.</p><p>It was <em>never</em> intended for resumes, tombstones, or hospital signage. But once it made its way into the core font pack of Windows 95, it spread like wildfire. Suddenly, Comic Sans was everywhere. And that’s where the trouble began.</p><p><strong>The backlash wasn’t about the typeface itself.</strong><br> It was about its misuse. Its overuse. Its weird placement in situations that called for anything <em>but</em> goofy round letters. It became a visual marker of poor design decisions, and designers, being designers, had opinions.</p><p>Design forums flamed it. Tumblr posts went viral. “Ban Comic Sans” became a campaign. It turned into shorthand for “this person doesn’t know what they’re doing.”</p><p>And while I understand the impulse to distance your work from that chaos, I also think it’s worth pausing to ask… what are we actually saying when we treat Comic Sans as the ultimate sin?</p><p>We’re not just saying “this typeface is awkward.” We’re reinforcing a culture that shames people who weren’t taught the language of design. We’re mocking those who picked a font not because it was “wrong,” but because it was available, legible, and looked kind of fun.</p><p>And here’s the deeper problem with that:<br> <strong>When we mock “bad design” without teaching better design, we gatekeep.</strong></p><p>Comic Sans is a perfect example of how we mistake taste for knowledge. If you know to avoid it, you’re seen as having good taste. If you use it, you’re marked as clueless. But taste doesn’t exist in a vacuum. It’s shaped by exposure, by education, by who had access to the tools, the terms, the time.</p><p>So instead of defaulting to disdain, maybe we start by asking a better question: <em>Why was this font chosen?</em> And what other options were available?</p><p>Because here’s the thing …Comic Sans isn’t useless. It’s incredibly legible for young readers and people with dyslexia. It was created with accessibility in mind. It’s informal, warm, and inviting when used <em>where that tone makes sense.</em></p><p>No one is saying it belongs in a law firm’s logo. But maybe it does belong in a children’s story, or a casual classroom sign, or a visual aid designed for someone with reading challenges. If we really care about design, we have to care about context. A typeface is not “bad” because of how it looks. It’s “bad” when it doesn’t support the message or meet the needs of the audience.</p><p><strong>So maybe the issue isn’t Comic Sans. Maybe it’s the idea that good design is obvious, and bad design is laughable.</strong> That attitude discourages experimentation. It creates fear around making choices. It keeps people from even trying.</p><p>The solution? Stop shaming and start explaining. Teach what makes typefaces effective. Share why visual tone matters. Help people see the connection between form and function and how the shape of a letter can shift the meaning of a message.</p><p>Because when we do that, we’re not just elevating fonts. We’re expanding design literacy. So no, Comic Sans isn’t evil. It just got caught in the wrong inbox at the wrong time. It doesn’t need to be banned. It needs to be understood. And honestly? I’d take an earnest Comic Sans over a thoughtless Bodoni any day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4af232c2a8a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>