editione1.0.2
Updated July 24, 2024Youโre reading an excerpt of Creative Doing, by Herbert Lui. 75 practical techniques to unlock creative potential in your work, hobby, or next career. Purchase now for instant, lifetime access to the book.
Early into his career as a designer at Adobe, Andrei Herasimchuk had designed and programmed a prototype over the weekend and a few days into his workweek. One of the product managers, who had worked at Adobe for a while and was well liked by the team, stopped by Harsimchukโs cubicle.
After a question on how long this took, they said, โWhile I certainly applaud your effort, I must say that you really donโt need to go to this length. Youโll have to do this all the time for all the products going forward. These screenshots you have here are plenty. Itโs all weโve ever done before, so thereโs really no need to spend this kind of time on a prototype.โ
Herasimchuk identifies the point when things went wrong, which is when he accepted the product managerโs feedback blindly, โUmโฆ Ok. I guess. If you think so.โ He never built another prototype while working at Adobe. His coding skills would dull over five years, and he missed a chance to make coding a part of Adobeโs design culture.
Listening to other peopleโs feedback is importantโfor certain. But as it turns out, they just might not understand your work. Or, they might not have been deliberate and thoughtful about your situation. If thatโs the case, it would be terrible for you to limit yourself because of one personโs off-handed comment about your work or your process.
Throw out something that somebody else had said. Donโt listen to it. If someone has told you they donโt like seeing this part of your work, and youโve cut it out, try to put it back in. If youโre looking for a place to start, throw out the piece of feedback that drains your personal energy, and makes you feel less excited about your work.